www.nordstrom.com speed test — 20 Oct 2026

Measured from the wfix.shop server on 20 October 2026 at 14:26 UTC. Grade A (94/100), with the screenshots, the timings and the fixes that matter.

https://www.nordstrom.com/

20 October 2026 at 14:26 UTC · Free test · report pt_5533fe528a33

Re-test this page Test your own site

Grade

94/100

Performance96/100

Structure92/100

13 audit(s) passed, 3 need work

First byte (TTFB)344 msmeasured from this server

Fully loaded344 msfirst byte + slowest asset

Requests1document + assets

Page weight133.7 KBcompressed transfer

HTML document133.7 KBgzip

ProtocolHTTP/3server not sent

Where the first byte went

DNS lookup 59 ms 17%
TCP connect 48 ms 14%
Server wait 236 ms 69%

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

Page weightlighter than 85% of 4,999 pages tested here133.7 KB against a median of 650.5 KB

Fully loadedfaster than 99% of 4,999 pages tested here344 ms against a median of 1.84 s

Requestssends fewer requests than 98% of 4,999 pages tested here1 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 344 ms. That is workable, and the cheapest win left is caching or a warmer connection.
The page transfers 133.7 KB over 1 request(s), which is lean.
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 132 ms, inside the 2.5 s Google calls good.

Fix first: HTML document size - Paginate long listings, move repeated markup into a template, and stop inlining large data URIs into the HTML.

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

Mobile screenshot of www.nordstrom.com — **Mobile** 390 × 844 · 24.0 KB · page is 844 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 paint132 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 paint132 msfirst content on screen

Browser page weight229.5 KB3 request(s), scripts included

Largest contentful paint132 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

Top issues

HTML document size

medium impact

The document transfers 133.7 KB. A bloated document delays every other request, because nothing else can start until it is parsed.

Fix: Paginate long listings, move repeated markup into a template, and stop inlining large data URIs into the HTML.

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.

Mobile viewport

medium impact

No viewport meta tag, so a phone renders the desktop layout scaled down.

Fix: Add a viewport meta tag with width=device-width and an initial scale of 1.

Report this page

Run this test on your own site

The same engine, free, with the screenshots and the fixes. No account needed.

Run a website speed test Have it fixed