userreport.com speed test — 20 Oct 2026
Measured from the wfix.shop server on 20 October 2026 at 15:43 UTC. Grade E (57/100), with the screenshots, the timings and the fixes that matter.
Where the first byte went
- DNS lookup 91 ms 7%
- TCP connect 34 ms 3%
- Server wait 1.10 s 90%
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 1.22 s. Everything else waits for that number, so the server is where to start: caching, a slow query, or an overloaded host.
- The page transfers 3.91 MB over 19 request(s). Media files are 91% of it, so let video load on demand instead of on first paint.
- The HTML itself arrives br-compressed.
- It runs over HTTP/3, so the assets share a connection instead of opening one each.
- The largest element painted at 1.93 s, inside the 2.5 s Google calls good.
- Layout stayed still (CLS 0.001), so nothing jumps under the reader's cursor.
- The main thread was blocked for 246 ms, so taps and scrolling wait while scripts run.
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. 19 request(s) in total, 3.91 MB across all of them.
Top issues
Server response time (TTFB)
high impactThe first byte arrived after 1219 ms. Of that, 1095 ms was the server thinking and 125 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 impact4 render-blocking resource(s) in the document head (3 script(s), 1 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
high impactThe page transfers 3.91 MB across 19 request(s), with the document itself at 28.9 KB.
Fix: Work through the heaviest assets first: images, then fonts, then third-party scripts.
Third-party weight
medium impact6 third-party host(s) serve 258.1 KB of this page. Each one is another DNS lookup, TLS handshake and point of failure you do not control.
Fix: Self-host the libraries you can, drop the tags you cannot justify, and preconnect the ones you keep.
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://js.hs-scripts.com/3446419.js 3rd party | javascript | 200 | 1.10 s | 661 B |
| https://i0.wp.com/userreport.com/wp-content/uploads/illustration_premium.png?w=659&ssl=1 3rd party | images | 200 | 1.07 s | 64.2 KB |
| https://i0.wp.com/userreport.com/wp-content/uploads/illustration_feedback_forum.png?w=659&ssl=1 3rd party | images | 200 | 983 ms | 43.0 KB |
| https://i0.wp.com/userreport.com/wp-content/uploads/userreport_illustration.png?w=821&ssl=1 3rd party | images | 200 | 983 ms | 34.8 KB |
| https://i0.wp.com/userreport.com/wp-content/uploads/illustration_survey.png?w=659&ssl=1 3rd party | images | 200 | 966 ms | 44.6 KB |
| https://userreport.com/wp-content/themes/product/_assets/video/cta_bg.mp4 | media | 200 | 945 ms | 3.55 MB |
| https://cdnjs.cloudflare.com/ajax/libs/balance-text/3.1.0/balancetext.min.js 3rd party | javascript | 200 | 819 ms | 2.4 KB |
| https://userreport.com/wp-content/themes/product-userreport/_assets/css/main.css?v=1.1 | css | 200 | 810 ms | 24.1 KB |
| https://s0.wp.com/i/webclip.png 3rd party | images | 200 | 810 ms | 6.1 KB |
| https://userreport.com/wp-content/themes/product-userreport/_assets/favicons/favicon.png | images | 200 | 808 ms | 580 B |
| https://userreport.com/wp-content/themes/product/_assets/js/min/app-min.js?v=1.21 | javascript | 200 | 804 ms | 6.1 KB |
| https://s0.wp.com/wp-content/js/bilmur.min.js?m=202643 3rd party | javascript | 200 | 802 ms | 4.9 KB |
| https://stats.wp.com/e-202643.js 3rd party | javascript | 200 | 802 ms | 1.4 KB |
| https://userreport.com/wp-content/themes/product/_assets/js/min/plugins-min.js?v=1.21 | javascript | 200 | 798 ms | 41.5 KB |
| https://i0.wp.com/userreport.com/wp-content/uploads/stefan.jpg?w=200&ssl=1 3rd party | images | 200 | 798 ms | 13.3 KB |
| https://i0.wp.com/userreport.com/wp-content/uploads/Malthe.jpg?w=200&ssl=1 3rd party | images | 200 | 793 ms | 7.2 KB |
| https://c0.wp.com/c/7.1.3/wp-includes/js/jquery/jquery-migrate.min.js 3rd party | javascript | 200 | 791 ms | 4.9 KB |
| https://c0.wp.com/c/7.1.3/wp-includes/js/jquery/jquery.min.js 3rd party | javascript | 200 | 786 ms | 30.7 KB |
Report this page
Run this test on your own site
The same engine, free, with the screenshots and the fixes. No account needed.