pixels.com speed test — 20 Oct 2026
Measured from the wfix.shop server on 20 October 2026 at 15:15 UTC. Grade A (93/100), with the screenshots, the timings and the fixes that matter.
Where the first byte went
- DNS lookup 77 ms 18%
- TCP connect 67 ms 16%
- Server wait 274 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 arrived in 418 ms. That is workable, and the cheapest win left is caching or a warmer connection.
- The page transfers 132.4 KB over 26 request(s). Javascript files are 51% 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/3, so the assets share a connection instead of opening one each.
- The largest element painted at 616 ms, inside the 2.5 s Google calls good.
- Layout stayed still (CLS 0.007), so nothing jumps under the reader's cursor.
- The main thread was blocked for 51 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. 26 request(s) in total, 132.4 KB across all of them.
Top issues
Server response time (TTFB)
high impactThe first byte arrived after 418 ms. Of that, 274 ms was the server thinking and 144 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 (0 script(s), 4 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.
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://www.facebook.com/tr?id=441380347490695&ev=PageView&noscript=1 3rd party | images | 200 | 1.11 s | 44 B |
| https://pixels.com/assets/images/ArrowBlueRight.gif | images | 200 | 1.04 s | 1.2 KB |
| https://pixels.com/assets/images/LogoSearchMagnifyingGlass.png | images | 200 | 1.02 s | 609 B |
| https://pixels.com/assets/images/HeaderVerticalArrowAccentTransparent.png | images | 200 | 1.02 s | 255 B |
| https://pixels.com/images/ArrowDownVTransparent.png | images | 200 | 1.02 s | 200 B |
| https://pixels.com/assets/images/Blank.jpg | images | 200 | 1.01 s | 375 B |
| https://pixels.com/images/IconShoppingCart2015.png | images | 200 | 1.01 s | 1.2 KB |
| https://pixels.com/assets/images/logos/logoPixelsBlack2020.png | images | 200 | 997 ms | 4.3 KB |
| https://pixels.com/css/stylesheet.css?v=c62574d1d8 | css | 200 | 983 ms | 8.9 KB |
| https://pixels.com/css/homepages/homepagePixels2020WithAnimation.css?v=c62574d1d8 | css | 200 | 979 ms | 4.8 KB |
| https://www.googletagmanager.com/ns.html?id=GTM-NFNR3KC 3rd party | html | 200 | 976 ms | 92 B |
| https://pixels.com/js/jquery371.js?v=c62574d1d8 | javascript | 200 | 966 ms | 29.6 KB |
| https://pixels.com/js/homepage/animation.js?v=c62574d1d8 | javascript | 200 | 966 ms | 1.1 KB |
| https://pixels.com/css/slickSlider.css?v=c62574d1d8 | css | 200 | 965 ms | 1.2 KB |
| https://pixels.com/js/globalScripts.js?v=c62574d1d8 | javascript | 200 | 963 ms | 13.8 KB |
| https://images.pixels.com/public/images/HomePageSlideshowArrowLeft.gif 3rd party | images | 200 | 961 ms | 279 B |
| https://pixels.com/js/slickSlider.js?v=c62574d1d8 | javascript | 200 | 952 ms | 15.0 KB |
| https://pixels.com/js/lazySizes.js?v=c62574d1d84 | javascript | 200 | 932 ms | 3.4 KB |
| https://images.pixels.com/public/images/HomePageSlideshowArrowRight.gif 3rd party | images | 200 | 932 ms | 280 B |
| https://pixels.com/js/homepage/homepagePixels.js?v=c62574d1d8 | javascript | 200 | 929 ms | 4.9 KB |
| https://images.pixels.com/public/assets/images/LogoInstagramFooter.jpg 3rd party | images | 200 | 929 ms | 1.5 KB |
| https://images.pixels.com/public/assets/images/LogoPinterestFooter.jpg 3rd party | images | 200 | 929 ms | 1.1 KB |
| https://images.pixels.com/public/assets/images/LogoTwitterFooter.jpg 3rd party | images | 200 | 929 ms | 1.0 KB |
| https://images.pixels.com/public/assets/images/LogoFacebookFooter.jpg 3rd party | images | 200 | 929 ms | 1.0 KB |
| https://images.pixels.com/public/assets/images/LogoYouTubeFooter.jpg 3rd party | images | 200 | 929 ms | 831 B |
Report this page
Run this test on your own site
The same engine, free, with the screenshots and the fixes. No account needed.