desync.com speed test — 20 Oct 2026

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

https://desync.com/

20 October 2026 at 14:13 UTC · Free test · report pt_353c9e1dd97e
Grade
A
96/100
Performance97/100
Structure94/100

14 audit(s) passed, 2 need work

First byte (TTFB)316 msmeasured from this server
Fully loaded688 msfirst byte + slowest asset
Requests3document + assets
Page weight67.4 KBcompressed transfer
HTML document363 Bzstd
ProtocolHTTP/3nginx/1.30.4

Where the first byte went

  • DNS lookup 75 ms 24%
  • TCP connect 67 ms 21%
  • Server wait 174 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 71% of 4,999 pages tested here316 ms against a median of 449 ms
Page weightlighter than 90% of 4,999 pages tested here67.4 KB against a median of 650.5 KB
Fully loadedfaster than 96% of 4,999 pages tested here688 ms against a median of 1.84 s
Requestssends fewer requests than 95% of 4,999 pages tested here3 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 316 ms. That is workable, and the cheapest win left is caching or a warmer connection.
  • The page transfers 67.4 KB over 3 request(s), which is lean. Images files are 99% of it, so resize and recompress the largest images before anything else.
  • The HTML itself arrives zstd-compressed.
  • It runs over HTTP/3, so the assets share a connection instead of opening one each.
  • The largest element painted at 612 ms, inside the 2.5 s Google calls good.

Fix first: Mobile viewport - Add a viewport meta tag with width=device-width and an initial scale of 1.

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 desync.com
Mobile 390 × 844 · 28.0 KB · page is 2121 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 paint612 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 paint428 msfirst content on screen
Browser page weight68.2 KB3 request(s), scripts included
Largest contentful paint612 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

Images 2 requests
67.1 KB 99%

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

Top issues

Mobile viewport

medium impact

No viewport meta tag, so a phone renders the desktop layout scaled down.

Fix: Add a viewport meta tag with width=device-width and an initial scale of 1.

Strict-Transport-Security

low impact

HSTS is not set, so the first visit on a hostile network can still be downgraded to HTTP.

Fix: Send Strict-Transport-Security with a max-age of at least six months. Add includeSubDomains once every subdomain is HTTPS.

Waterfall

Slowest requests

IMAGESdesync.com/headerlogo.png
372 ms
IMAGESdesync.com/headerbg.png
308 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://desync.com/headerlogo.pngimages200372 ms3.1 KB
https://desync.com/headerbg.pngimages200308 ms63.9 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.