www.nvidia.com/en-us/geforce speed test — 20 Oct 2026

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

https://www.nvidia.com/en-us/geforce/

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

Re-test this page Test your own site

Grade

75/100

Performance73/100

Structure79/100

12 audit(s) passed, 4 need work

First byte (TTFB)239 msmeasured from this server

Fully loaded1.62 sfirst byte + slowest asset

Requests26document + assets

Page weight3.97 MBcompressed transfer

HTML document44.9 KBgzip

ProtocolHTTP/3Apache

Where the first byte went

DNS lookup 55 ms 23%
TCP connect 34 ms 14%
Server wait 150 ms 63%

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

Page weightheavier than 91% of 4,999 pages tested here3.97 MB against a median of 650.3 KB

Fully loadedfaster than 62% of 4,999 pages tested here1.62 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 239 ms. That is workable, and the cheapest win left is caching or a warmer connection.
The page transfers 3.97 MB over 26 request(s). Html files are 99% of it, so that one type is worth a look on its own.
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 2.21 s, inside the 2.5 s Google calls good.
The main thread was blocked for 1.11 s, so taps and scrolling wait while scripts run.

Fix first: Render-blocking resources - 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.

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.nvidia.com — **Mobile** 390 × 844 · 85.9 KB · page is 4584 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.21 sgood is under 2.5 s

Cumulative layout shift0.000under 0.1 is stable

Total blocking time1.11 slong tasks during load

First contentful paint920 msfirst content on screen

Browser page weight3.54 MB51 request(s), scripts included

Largest contentful paint2.21 s

Goodgood under 2.5 s, poor over 4 s

Cumulative layout shift0.000

Goodgood under 0.1, poor over 0.25

Total blocking time1.11 s

Poorgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Html 25 requests

3.93 MB 99%

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

Top issues

Render-blocking resources

high impact

14 render-blocking resource(s) in the document head (9 script(s), 5 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 3.97 MB across 26 request(s), with the document itself at 44.9 KB.

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

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.

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.