proof.ovh.net speed test — 20 Oct 2026

Measured from the wfix.shop server on 20 October 2026 at 12:26 UTC. Grade B (89/100), with the screenshots, the timings and the fixes that matter.

https://proof.ovh.net/

20 October 2026 at 12:26 UTC · Free test · report pt_bbf23cdd73f3
Grade
B
89/100
Performance92/100
Structure85/100

12 audit(s) passed, 4 need work

First byte (TTFB)489 msmeasured from this server
Fully loaded1.26 sfirst byte + slowest asset
Requests10document + assets
Page weight103.9 KBcompressed transfer
HTML document5.8 KBgzip
ProtocolHTTP/3nginx

Where the first byte went

  • DNS lookup 50 ms 10%
  • TCP connect 135 ms 28%
  • Server wait 304 ms 62%

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 byteslower than 54% of 4,999 pages tested here489 ms against a median of 448 ms
Page weightlighter than 87% of 4,999 pages tested here103.9 KB against a median of 650.5 KB
Fully loadedfaster than 85% of 4,999 pages tested here1.26 s against a median of 1.84 s
Requestssends fewer requests than 88% of 4,999 pages tested here10 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 489 ms. That is workable, and the cheapest win left is caching or a warmer connection.
  • The page transfers 103.9 KB over 10 request(s), which is lean. Fonts files are 43% of it, so subset the fonts and stop preloading the weights you do not render.
  • 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 988 ms, inside the 2.5 s Google calls good.
  • Layout stayed still (CLS 0.003), so nothing jumps under the reader's cursor.
  • The main thread was blocked for 64 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.

Desktop screenshot of proof.ovh.net
Desktop 1366 × 768 · 77.6 KB · page is 1251 px tall
Mobile screenshot of proof.ovh.net
Mobile 390 × 844 · 44.2 KB · page is 1055 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 paint988 msgood is under 2.5 s
Cumulative layout shift0.003under 0.1 is stable
Total blocking time64 mslong tasks during load
First contentful paint988 msfirst content on screen
Browser page weight178.6 KB31 request(s), scripts included
Largest contentful paint988 ms
Goodgood under 2.5 s, poor over 4 s
Cumulative layout shift0.003
Goodgood under 0.1, poor over 0.25
Total blocking time64 ms
Goodgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Fonts 2 requests
45.1 KB 43%
Javascript 1 request
18.5 KB 18%
Css 1 request
14.3 KB 14%
Images 4 requests
12.6 KB 12%
Html 1 request
7.5 KB 7%

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

Top issues

Server response time (TTFB)

high impact

The first byte arrived after 489 ms. Of that, 304 ms was the server thinking and 185 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.

Cache static assets

medium impact

4 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.

Avoid extra redirects

medium impact

1 redirect hop(s) before the page load started, each one a full round trip before the first byte.

Fix: Link to the canonical URL (and make sure http, the apex domain and www all point at it) so no visitor pays a redirect first.

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

IMAGESproof.ovh.net/favicon.ico
769 ms
IMAGESproof.ovh.net/icon.svg
729 ms
HTMLproof.ovh.net/speedtest/
725 ms
JAVASCRIPTproof.ovh.net/js/main.js
672 ms
FONTSproof.ovh.net/fonts/jetbrains-mono-v24-latin-400-800…
644 ms
FONTSproof.ovh.net/fonts/source-sans-pro-v23-latin-400.woff2
640 ms
IMAGESproof.ovh.net/logo_com.png
637 ms
CSSproof.ovh.net/style.css
630 ms
IMAGESproof.ovh.net/apple-touch-icon.png
615 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://proof.ovh.net/favicon.icoimages200769 ms2.2 KB
https://proof.ovh.net/icon.svgimages200729 ms439 B
https://proof.ovh.net/speedtest/html200725 ms7.5 KB
https://proof.ovh.net/js/main.jsjavascript200672 ms18.5 KB
https://proof.ovh.net/fonts/jetbrains-mono-v24-latin-400-800.woff2fonts200644 ms30.6 KB
https://proof.ovh.net/fonts/source-sans-pro-v23-latin-400.woff2fonts200640 ms14.5 KB
https://proof.ovh.net/logo_com.pngimages200637 ms7.7 KB
https://proof.ovh.net/style.csscss200630 ms14.3 KB
https://proof.ovh.net/apple-touch-icon.pngimages200615 ms2.4 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.