www.gm.com speed test — 20 Oct 2026

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

https://www.gm.com/

20 October 2026 at 13:30 UTC · Free test · report pt_581d3bc0b39c

Re-test this page Test your own site

Grade

70/100

Performance69/100

Structure71/100

10 audit(s) passed, 6 need work

First byte (TTFB)422 msmeasured from this server

Fully loaded1.51 sfirst byte + slowest asset

Requests26document + assets

Page weight4.40 MBcompressed transfer

HTML document23.7 KBgzip

ProtocolHTTP/3server not sent

Third-party70.3 KBother hosts

Where the first byte went

DNS lookup 218 ms 52%
TCP connect 53 ms 13%
Server wait 151 ms 36%

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

Page weightheavier than 92% of 4,999 pages tested here4.40 MB against a median of 650.3 KB

Fully loadedfaster than 69% of 4,999 pages tested here1.51 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 arrived in 422 ms. That is workable, and the cheapest win left is caching or a warmer connection.
The page transfers 4.40 MB over 26 request(s). Images files are 98% 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 204 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.gm.com — **Desktop** 1366 × 768 · 23.8 KB · page is 768 px tall

Mobile screenshot of www.gm.com — **Mobile** 390 × 844 · 7.9 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 paint204 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 paint204 msfirst content on screen

Browser page weight548 B1 request(s), scripts included

Largest contentful paint204 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 23 requests

4.31 MB 98%

Javascript 2 requests

71.1 KB 2%

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

Top issues

Server response time (TTFB)

high impact

The first byte arrived after 422 ms. Of that, 151 ms was the server thinking and 271 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.

Image delivery and format

high impact

11 image(s) over 200 KB and 18 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 (2 script(s), 1 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 4.40 MB across 26 request(s), with the document itself at 23.7 KB.

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

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.