dataprivacyframework.gov speed test — 20 Oct 2026
Measured from the wfix.shop server on 20 October 2026 at 13:35 UTC. Grade B (84/100), with the screenshots, the timings and the fixes that matter.
Where the first byte went
- DNS lookup 79 ms 15%
- TCP connect 100 ms 19%
- Server wait 345 ms 66%
Measured on the connection that fetched the HTML. Every other request on the page waits for the end of this bar before it can start.
How this page compares
Every report published here is in this comparison, so it is a reference population of pages tested from one server - not a benchmark of the whole web.
What these numbers mean
- The first byte took 525 ms. Everything else waits for that number, so the server is where to start: caching, a slow query, or an overloaded host.
- The page transfers 893.3 KB over 14 request(s), which is lean. Javascript files are 83% of it, so defer what is not needed for the first screen, and drop tags nobody uses.
- The HTML itself arrives gzip-compressed.
- It runs over HTTP/2, so the assets share a connection instead of opening one each.
- The largest element took 2.69 s to paint, past the 2.5 s threshold: usually a hero image that is too big or a render-blocking script in front of it.
- Layout stayed still (CLS 0.026), so nothing jumps under the reader's cursor.
- The main thread was blocked for 87 ms in total, which is not enough to feel.
Fix first: Server response time (TTFB) - Cut server think time: page cache, query indexes, fewer synchronous calls to third parties inside the request. Connection setup is distance, so a nearer region or a CDN edge helps instead.
Read on one shared server, not a visitor's phone: use it to compare pages against each other, not as a promise about every connection. We fix what these tests find.
Screenshot
What the page looks like
Loaded in headless Chromium on this server. Click an image to open it full size.
Browser render
The same URL loaded in a real browser, so these are the readings curl cannot produce. The grade above is still built from the server measurements.
Page weight by type
What the page is made of
Transfer size, compressed as sent. 14 request(s) in total, 893.3 KB across all of them.
Top issues
Server response time (TTFB)
high impactThe first byte arrived after 525 ms. Of that, 345 ms was the server thinking and 179 ms was connection setup. A first byte under 400 ms is what a visitor feels as instant.
Fix: Cut server think time: page cache, query indexes, fewer synchronous calls to third parties inside the request. Connection setup is distance, so a nearer region or a CDN edge helps instead.
Render-blocking resources
high impact11 render-blocking resource(s) in the document head (1 script(s), 10 stylesheet(s)). The page cannot paint until each one arrives.
Fix: Add defer or async to scripts that do not change the first paint, inline the critical CSS, and load the rest with media="print" plus an onload swap.
Total page weight
medium impactThe page transfers 893.3 KB across 14 request(s), with the document itself at 1.1 KB.
Fix: Work through the heaviest assets first: images, then fonts, then third-party scripts.
Cache static assets
medium impact1 asset(s) answer without a Cache-Control max-age, so browsers revalidate them on every visit.
Fix: Version filenames on change and serve them with a long max-age plus immutable. That is what makes a returning visitor fast.
JavaScript weight
medium impact1 JavaScript file(s) over 200 KB: index-DHP4VEMY.js (733.5 KB)
Fix: Split routes, remove unused dependencies, and prefer a two-file build (one pinned library, one application bundle) over many small ones.
Waterfall
Slowest requests
Each bar is one request's own response time, scaled to the slowest. Assets were fetched in parallel, so the bars overlap in real time rather than stacking. first party third party
| Request | Type | Status | Time | Size |
|---|---|---|---|---|
| https://dataprivacyframework.gov/dpflogo.png | images | 200 | 816 ms | 6.2 KB |
| https://dataprivacyframework.gov/styles/bootstrap.css | css | 200 | 731 ms | 29.8 KB |
| https://dataprivacyframework.gov/favicon.ico | images | 200 | 710 ms | 5.8 KB |
| https://dataprivacyframework.gov/styles/jquery.dropdown.min.css | css | 200 | 688 ms | 696 B |
| https://dataprivacyframework.gov/styles/ps.css | css | 200 | 686 ms | 1.6 KB |
| https://dataprivacyframework.gov/assets/index-CYgxv-86.css | css | 200 | 685 ms | 66.6 KB |
| https://dataprivacyframework.gov/assets/index-DHP4VEMY.js | javascript | 200 | 680 ms | 733.5 KB |
| https://dataprivacyframework.gov/styles/global.css | css | 200 | 678 ms | 23.7 KB |
| https://dataprivacyframework.gov/styles/site_template.css | css | 200 | 676 ms | 1.5 KB |
| https://cdnjs.cloudflare.com/ajax/libs/font-awesome/4.7.0/css/font-awesome.css 3rd party | css | 200 | 583 ms | 5.7 KB |
| https://fonts.googleapis.com/css?family=Lato:400,300 3rd party | css | 200 | 580 ms | 193 B |
| https://code.jquery.com/ui/1.11.4/themes/smoothness/jquery-ui.css 3rd party | css | 200 | 568 ms | 7.9 KB |
| https://dap.digitalgov.gov/Universal-Federated-Analytics-Min.js?agency=DOC&subagency=ITA 3rd party | javascript | 200 | 531 ms | 9.0 KB |
Report this page
Run this test on your own site
The same engine, free, with the screenshots and the fixes. No account needed.