www.histats.com speed test — 20 Oct 2026

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

https://www.histats.com/

20 October 2026 at 13:27 UTC · Free test · report pt_a0898a985163
Grade
C
79/100
Performance78/100
Structure80/100

12 audit(s) passed, 4 need work

First byte (TTFB)949 msmeasured from this server
Fully loaded2.04 sfirst byte + slowest asset
Requests26document + assets
Page weight667.8 KBcompressed transfer
HTML document6.1 KBbr
ProtocolHTTP/3cloudflare
Third-party661.7 KBother hosts

Where the first byte went

  • DNS lookup 166 ms 17%
  • TCP connect 32 ms 3%
  • Server wait 751 ms 79%

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 83% of 4,999 pages tested here949 ms against a median of 448 ms
Page weightheavier than 51% of 4,999 pages tested here667.8 KB against a median of 650.3 KB
Fully loadedslower than 58% of 4,999 pages tested here2.04 s against a median of 1.84 s
Requestssends more requests than 100% of 4,999 pages tested here26 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 949 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 667.8 KB over 26 request(s). Images files are 99% of it, so resize and recompress the largest images before anything else.
  • The HTML itself arrives br-compressed.
  • It runs over HTTP/3, so the assets share a connection instead of opening one each.
  • 99% of the weight comes from other hosts (analytics, fonts, embeds), which also means their slow day becomes your slow day.
  • The largest element took 2.92 s to paint, past the 2.5 s threshold: usually a hero image that is too big or a render-blocking script in front of it.
  • Layout stayed still (CLS 0.001), so nothing jumps under the reader's cursor.
  • The main thread was blocked for 5 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.

Mobile screenshot of www.histats.com
Mobile 390 × 844 · 183.3 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 paint2.92 sgood is under 2.5 s
Cumulative layout shift0.001under 0.1 is stable
Total blocking time5 mslong tasks during load
First contentful paint1.09 sfirst content on screen
Browser page weight1.89 MB93 request(s), scripts included
Failed requests1blocked or unreachable
Largest contentful paint2.92 s
Needs improvementgood under 2.5 s, poor over 4 s
Cumulative layout shift0.001
Goodgood under 0.1, poor over 0.25
Total blocking time5 ms
Goodgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Images 25 requests
661.7 KB 99%

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

Top issues

Server response time (TTFB)

high impact

The first byte arrived after 949 ms. Of that, 751 ms was the server thinking and 198 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.

Third-party weight

medium impact

1 third-party host(s) serve 661.7 KB of this page. Each one is another DNS lookup, TLS handshake and point of failure you do not control.

Fix: Self-host the libraries you can, drop the tags you cannot justify, and preconnect the ones you keep.

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.

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.

Waterfall

Slowest requests

IMAGESi.histats.com/images/ICO_1px.gif
1.09 s
IMAGESi.histats.com/images/SCRhome_f6.png
1.08 s
IMAGESi.histats.com/images/SCRhome_f8.png
1.07 s
IMAGESi.histats.com/images/SCRhome_f5.png
1.07 s
IMAGESi.histats.com/images/top_logo/svg-spot-3.png
1.07 s
IMAGESi.histats.com/images/top_logo/svg-spot-1.png
1.07 s
IMAGESi.histats.com/images/SCRhome_f4.png
1.06 s
IMAGESi.histats.com/images/SCRhome_f10.png
1.06 s
IMAGESi.histats.com/images/SCRhome_f2.png
1.06 s
IMAGESi.histats.com/images/pointPX_d.png
1.05 s

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://i.histats.com/images/ICO_1px.gif 3rd partyimages2001.09 s43 B
https://i.histats.com/images/SCRhome_f6.png 3rd partyimages2001.08 s22.6 KB
https://i.histats.com/images/SCRhome_f8.png 3rd partyimages2001.07 s31.3 KB
https://i.histats.com/images/SCRhome_f5.png 3rd partyimages2001.07 s20.5 KB
https://i.histats.com/images/top_logo/svg-spot-3.png 3rd partyimages2001.07 s5.8 KB
https://i.histats.com/images/top_logo/svg-spot-1.png 3rd partyimages2001.07 s5.2 KB
https://i.histats.com/images/SCRhome_f4.png 3rd partyimages2001.06 s10.6 KB
https://i.histats.com/images/SCRhome_f10.png 3rd partyimages2001.06 s19.6 KB
https://i.histats.com/images/SCRhome_f2.png 3rd partyimages2001.06 s16.6 KB
https://i.histats.com/images/pointPX_d.png 3rd partyimages2001.05 s954 B
https://i.histats.com/images/top_logo/svg-spot-2.png 3rd partyimages2001.05 s5.8 KB
https://i.histats.com/images/SCRhome_f9.png 3rd partyimages2001.04 s10.1 KB
https://i.histats.com/images/SCRhome_f7.png 3rd partyimages2001.04 s9.2 KB
https://i.histats.com/images/Hs_5.jpg 3rd partyimages2001.03 s84.7 KB
https://i.histats.com/images/SCRhome_f3.png 3rd partyimages2001.03 s14.3 KB
https://i.histats.com/images/Hs_4.jpg 3rd partyimages2001.03 s73.7 KB
https://i.histats.com/images/Hs_6.jpg 3rd partyimages2001.03 s49.1 KB
https://i.histats.com/images/Hs_1.jpg 3rd partyimages2001.02 s84.1 KB
https://i.histats.com/images/Hs_3.jpg 3rd partyimages2001.02 s83.4 KB
https://i.histats.com/images/Hs_2.jpg 3rd partyimages2001.02 s81.0 KB
https://i.histats.com/images/liveDemo.png 3rd partyimages2001.02 s14.8 KB
https://i.histats.com/images/playICO.png 3rd partyimages2001.02 s11.5 KB
https://i.histats.com/images/SCRhome_f1.png 3rd partyimages2001.02 s4.8 KB
https://i.histats.com/images/keyICO.png 3rd partyimages2001.02 s1.2 KB
https://i.histats.com/images/pointPX.png 3rd partyimages2001.02 s935 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.