chess-results.com speed test — 20 Oct 2026

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

https://chess-results.com/

20 October 2026 at 14:53 UTC · Free test · report pt_4a5af26a4550
Grade
B
87/100
Performance89/100
Structure83/100

12 audit(s) passed, 4 need work

First byte (TTFB)594 msmeasured from this server
Fully loaded1.51 sfirst byte + slowest asset
Requests7document + assets
Page weight40.8 KBcompressed transfer
HTML document12.0 KBgzip
ProtocolHTTP/3Microsoft-IIS/10.0

Where the first byte went

  • DNS lookup 52 ms 9%
  • TCP connect 168 ms 28%
  • Server wait 374 ms 63%

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 62% of 4,999 pages tested here594 ms against a median of 448 ms
Page weightlighter than 92% of 4,999 pages tested here40.8 KB against a median of 650.5 KB
Fully loadedfaster than 69% of 4,999 pages tested here1.51 s against a median of 1.84 s
Requestssends fewer requests than 91% of 4,999 pages tested here7 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 took 594 ms. Everything else waits for that number, so the server is where to start: caching, a slow query, or an overloaded host.
  • The page transfers 40.8 KB over 7 request(s), which is lean. Images files are 49% of it, so resize and recompress the largest images before anything else.
  • 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 744 ms, inside the 2.5 s Google calls good.
  • Layout stayed still (CLS 0.022), so nothing jumps under the reader's cursor.
  • The main thread was blocked for 661 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.

Mobile screenshot of chess-results.com
Mobile 390 × 844 · 143.4 KB · page is 2410 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 paint744 msgood is under 2.5 s
Cumulative layout shift0.022under 0.1 is stable
Total blocking time661 mslong tasks during load
First contentful paint744 msfirst content on screen
Browser page weight2.96 MB1315 request(s), scripts included
Failed requests40blocked or unreachable
Largest contentful paint744 ms
Goodgood under 2.5 s, poor over 4 s
Cumulative layout shift0.022
Goodgood under 0.1, poor over 0.25
Total blocking time661 ms
Poorgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Images 4 requests
19.8 KB 49%
Css 1 request
9.0 KB 22%

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

Top issues

Server response time (TTFB)

high impact

The first byte arrived after 594 ms. Of that, 374 ms was the server thinking and 220 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

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

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

IMAGESchess-results.com/images/chessResults_ENG_1000x90.jpg
917 ms
IMAGESchess-results.com/images/Icon_32x32.png
885 ms
CSSchess-results.com/StylesI.CSS
843 ms
IMAGESchess-results.com/images/werbung/Abstand_160x6.png
725 ms
IMAGESchess-results.com/images/ECU.gif
705 ms
OTHERcdn.fuseplatform.net/publift/tags/2/3060/fuse.js
131 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://chess-results.com/images/chessResults_ENG_1000x90.jpgimages200917 ms15.8 KB
https://chess-results.com/images/Icon_32x32.pngimages200885 ms1.1 KB
https://chess-results.com/StylesI.CSScss200843 ms9.0 KB
https://chess-results.com/images/werbung/Abstand_160x6.pngimages200725 ms145 B
https://chess-results.com/images/ECU.gifimages200705 ms2.7 KB
https://cdn.fuseplatform.net/publift/tags/2/3060/fuse.js 3rd partyother405131 ms0 B
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.