he.net speed test — 20 Oct 2026

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

https://he.net/

20 October 2026 at 12:39 UTC · Free test · report pt_c5dd23e7e69d
Grade
B
86/100
Performance92/100
Structure76/100

12 audit(s) passed, 4 need work

First byte (TTFB)210 msmeasured from this server
Fully loaded553 msfirst byte + slowest asset
Requests7document + assets
Page weight1.84 MBcompressed transfer
HTML document5.4 KBgzip
ProtocolHTTP/2Apache
Third-party148.6 KBother hosts

Where the first byte went

  • DNS lookup 47 ms 22%
  • TCP connect 43 ms 20%
  • Server wait 120 ms 57%

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 91% of 4,999 pages tested here210 ms against a median of 449 ms
Page weightheavier than 79% of 4,999 pages tested here1.84 MB against a median of 650.3 KB
Fully loadedfaster than 98% of 4,999 pages tested here553 ms 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 arrived in 210 ms. That is workable, and the cheapest win left is caching or a warmer connection.
  • The page transfers 1.84 MB over 7 request(s), which is lean. Images files are 92% of it, so resize and recompress the largest images before anything else.
  • The HTML itself arrives gzip-compressed.
  • It runs over HTTP/2, so the assets share a connection instead of opening one each.
  • The largest element painted at 252 ms, inside the 2.5 s Google calls good.
  • Layout stayed still (CLS 0.058), so nothing jumps under the reader's cursor.

Fix first: Image delivery and format - Serve WebP or AVIF with a JPEG fallback, size images to the space they occupy, and lazy-load anything below the fold. Images are usually more than half of a slow page.

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 he.net
Mobile 390 × 844 · 61.2 KB · page is 2590 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 paint252 msgood is under 2.5 s
Cumulative layout shift0.058under 0.1 is stable
Total blocking timenone over 50 mslong tasks during load
First contentful paint232 msfirst content on screen
Browser page weight1.87 MB13 request(s), scripts included
Failed requests2blocked or unreachable
Largest contentful paint252 ms
Goodgood under 2.5 s, poor over 4 s
Cumulative layout shift0.058
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 5 requests
1.69 MB 92%
Javascript 1 request
148.6 KB 8%

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

Top issues

Image delivery and format

high impact

1 image(s) over 200 KB and 0 large image(s) still served as JPEG or PNG.

Fix: Serve WebP or AVIF with a JPEG fallback, size images to the space they occupy, and lazy-load anything below the fold. Images are usually more than half of a slow page.

Total page weight

high impact

The page transfers 1.84 MB across 7 request(s), with the document itself at 5.4 KB.

Fix: Work through the heaviest assets first: images, then fonts, then third-party scripts.

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.

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

IMAGEShe.net/images/homepage-smallmap.png
343 ms
JAVASCRIPTwww.googletagmanager.com/gtag/js
299 ms
IMAGEShe.net/images/homepage-smallcolo.png
292 ms
IMAGEShe.net/3d-map/images/3d-map-thumbnail-170px.gif
268 ms
IMAGEShe.net/images/homepage-smallcert.png
267 ms
IMAGEShe.net/images/helogo.gif
227 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://he.net/images/homepage-smallmap.pngimages200343 ms31.1 KB
https://www.googletagmanager.com/gtag/js?id=AW-1068215855 3rd partyjavascript200299 ms148.6 KB
https://he.net/images/homepage-smallcolo.pngimages200292 ms47.4 KB
https://he.net/3d-map/images/3d-map-thumbnail-170px.gifimages200268 ms1.57 MB
https://he.net/images/homepage-smallcert.pngimages200267 ms40.1 KB
https://he.net/images/helogo.gifimages200227 ms4.2 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.