pixeldrain.com speed test — 20 Oct 2026

Measured from the wfix.shop server on 20 October 2026 at 14:43 UTC. Grade A (93/100), with the screenshots, the timings and the fixes that matter.

https://pixeldrain.com/

20 October 2026 at 14:43 UTC · Free test · report pt_49ec4b6e9181
Grade
A
93/100
Performance96/100
Structure89/100

13 audit(s) passed, 3 need work

First byte (TTFB)333 msmeasured from this server
Fully loaded1.05 sfirst byte + slowest asset
Requests12document + assets
Page weight545.7 KBcompressed transfer
HTML document5.0 KBno compression
ProtocolHTTP/2server not sent
Third-party2.9 KBother hosts

Where the first byte went

  • DNS lookup 84 ms 25%
  • TCP connect 66 ms 20%
  • Server wait 183 ms 55%

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

First bytefaster than 68% of 4,999 pages tested here333 ms against a median of 449 ms
Page weightlighter than 55% of 4,999 pages tested here545.7 KB against a median of 650.5 KB
Fully loadedfaster than 91% of 4,999 pages tested here1.05 s against a median of 1.84 s
Requestssends fewer requests than 86% of 4,999 pages tested here12 against a median of 26

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 333 ms. That is workable, and the cheapest win left is caching or a warmer connection.
  • The page transfers 545.7 KB over 12 request(s), which is lean. Javascript files are 84% of it, so defer what is not needed for the first screen, and drop tags nobody uses.
  • It runs over HTTP/2, so the assets share a connection instead of opening one each.
  • The largest element painted at 980 ms, inside the 2.5 s Google calls good.

Fix first: Compress text responses - Turn on brotli (preferred) or gzip for text/css, javascript and text/html in the web server. This is the cheapest win available on almost any site.

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.

Mobile screenshot of pixeldrain.com
Mobile 390 × 844 · 177.6 KB · page is 5368 px tall

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.

Largest contentful paint980 msgood is under 2.5 s
Cumulative layout shift0.000under 0.1 is stable
Total blocking timenone over 50 mslong tasks during load
First contentful paint336 msfirst content on screen
Browser page weight1.00 MB14 request(s), scripts included
Largest contentful paint980 ms
Goodgood under 2.5 s, poor over 4 s
Cumulative layout shift0.000
Goodgood under 0.1, poor over 0.25
Total blocking timenone over 50 ms
Goodgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Javascript 2 requests
457.2 KB 84%
Images 7 requests
68.2 KB 12%
Css 2 requests
15.3 KB 3%

Transfer size, compressed as sent. 12 request(s) in total, 545.7 KB across all of them.

Top issues

Compress text responses

high impact

2 text response(s) of 10 KB or more are sent uncompressed, and the document itself is not compressed. That is 467.3 KB of compressible text.

Fix: Turn on brotli (preferred) or gzip for text/css, javascript and text/html in the web server. This is the cheapest win available on almost any site.

Cache static assets

medium impact

1 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 impact

1 JavaScript file(s) over 200 KB: home_page.js (454.3 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

JAVASCRIPTstats.pixeldrain.com/js/script.js
713 ms
JAVASCRIPTpixeldrain.com/res/svelte/home_page.js
673 ms
IMAGESpixeldrain.com/res/img/pixeldrain_128.png
643 ms
IMAGESpixeldrain.com/res/img/pixeldrain_32.png
616 ms
IMAGESpixeldrain.com/res/img/pixeldrain_256.png
586 ms
IMAGESpixeldrain.com/res/img/pixeldrain_196.png
569 ms
IMAGESpixeldrain.com/res/img/pixeldrain_192.png
569 ms
IMAGESpixeldrain.com/res/img/pixeldrain_152.png
518 ms
IMAGESpixeldrain.com/res/img/pixeldrain_180.png
499 ms
CSSpixeldrain.com/res/style/layout.css
465 ms

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

RequestTypeStatusTimeSize
https://stats.pixeldrain.com/js/script.js 3rd partyjavascript200713 ms2.9 KB
https://pixeldrain.com/res/svelte/home_page.js?v497659javascript200673 ms454.3 KB
https://pixeldrain.com/res/img/pixeldrain_128.pngimages200643 ms7.6 KB
https://pixeldrain.com/res/img/pixeldrain_32.pngimages200616 ms1.7 KB
https://pixeldrain.com/res/img/pixeldrain_256.pngimages200586 ms14.8 KB
https://pixeldrain.com/res/img/pixeldrain_196.pngimages200569 ms12.1 KB
https://pixeldrain.com/res/img/pixeldrain_192.pngimages200569 ms11.9 KB
https://pixeldrain.com/res/img/pixeldrain_152.pngimages200518 ms9.2 KB
https://pixeldrain.com/res/img/pixeldrain_180.pngimages200499 ms11.0 KB
https://pixeldrain.com/res/style/layout.css?v497659css200465 ms13.0 KB
https://pixeldrain.com/theme.csscss200465 ms2.3 KB
Report this page

The page is removed when the owner agrees. Sending this removes nothing by itself.

Run this test on your own site

The same engine, free, with the screenshots and the fixes. No account needed.