fortune.com speed test — 20 Oct 2026

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

https://fortune.com/

20 October 2026 at 12:43 UTC · Free test · report pt_a651f5a35b2a

Re-test this page Test your own site

Grade

82/100

Performance85/100

Structure77/100

12 audit(s) passed, 4 need work

First byte (TTFB)139 msmeasured from this server

Fully loaded2.72 sfirst byte + slowest asset

Requests26document + assets

Page weight2.15 MBcompressed transfer

HTML document97.0 KBgzip

ProtocolHTTP/3nginx

Where the first byte went

DNS lookup 69 ms 50%
TCP connect 5 ms 4%
Server wait 66 ms 47%

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 99% of 4,999 pages tested here139 ms against a median of 449 ms

Page weightheavier than 83% of 4,999 pages tested here2.15 MB against a median of 650.3 KB

Fully loadedslower than 78% of 4,999 pages tested here2.72 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 server answered in 139 ms, which is fast: almost all of the wait is the page itself, not the host.
The page transfers 2.15 MB over 26 request(s). Images files are 96% 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 500 ms, inside the 2.5 s Google calls good.
The main thread was blocked for 1.66 s, so taps and scrolling wait while scripts run.

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.

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 paint500 msgood is under 2.5 s

Cumulative layout shift0.000under 0.1 is stable

Total blocking time1.66 slong tasks during load

First contentful paint428 msfirst content on screen

Browser page weight8.75 MB2028 request(s), scripts included

Failed requests23blocked or unreachable

Largest contentful paint500 ms

Goodgood under 2.5 s, poor over 4 s

Cumulative layout shift0.000

Goodgood under 0.1, poor over 0.25

Total blocking time1.66 s

Poorgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Images 25 requests

2.06 MB 96%

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

Top issues

Image delivery and format

high impact

1 image(s) over 200 KB and 7 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.

Render-blocking resources

high impact

3 render-blocking resource(s) in the document head (1 script(s), 2 stylesheet(s)). The page cannot paint until each one arrives.

Fix: Add defer or async to scripts that do not change the first paint, inline the critical CSS, and load the rest with media="print" plus an onload swap.

Total page weight

high impact

The page transfers 2.15 MB across 26 request(s), with the document itself at 97.0 KB.

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

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.