www.volvocars.com/us speed test — 20 Oct 2026

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

https://www.volvocars.com/us/

20 October 2026 at 13:48 UTC · Free test · report pt_ce1147ab573e

Re-test this page Test your own site

Grade

80/100

Performance78/100

Structure83/100

13 audit(s) passed, 3 need work

First byte (TTFB)875 msmeasured from this server

Fully loaded2.52 sfirst byte + slowest asset

Requests26document + assets

Page weight585.3 KBcompressed transfer

HTML document60.7 KBgzip

ProtocolHTTP/3server not sent

Where the first byte went

DNS lookup 83 ms 9%
TCP connect 23 ms 3%
Server wait 768 ms 88%

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 80% of 4,999 pages tested here875 ms against a median of 448 ms

Page weightlighter than 53% of 4,999 pages tested here585.3 KB against a median of 650.5 KB

Fully loadedslower than 74% of 4,999 pages tested here2.52 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 875 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 585.3 KB over 26 request(s). Images files are 90% 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 224 ms, inside the 2.5 s Google calls good.

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 www.volvocars.com — **Desktop** 1366 × 768 · 24.2 KB · page is 768 px tall

Mobile screenshot of www.volvocars.com — **Mobile** 390 × 844 · 7.8 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 paint224 msgood is under 2.5 s

Cumulative layout shift0.000under 0.1 is stable

Total blocking timenone over 50 mslong tasks during load

First contentful paint224 msfirst content on screen

Browser page weight635 B1 request(s), scripts included

Largest contentful paint224 ms

Goodgood under 2.5 s, poor over 4 s

Cumulative layout shift0.000

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 25 requests

524.6 KB 90%

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

Top issues

Server response time (TTFB)

high impact

The first byte arrived after 875 ms. Of that, 768 ms was the server thinking and 106 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.

Render-blocking resources

high impact

14 render-blocking resource(s) in the document head (1 script(s), 13 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.

Avoid extra redirects

medium impact

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