www.patagonia.com/home speed test — 20 Oct 2026

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

https://www.patagonia.com/home/

20 October 2026 at 16:12 UTC · Free test · report pt_87e36b46b20e

Re-test this page Test your own site

Grade

84/100

Performance86/100

Structure80/100

12 audit(s) passed, 4 need work

First byte (TTFB)499 msmeasured from this server

Fully loaded3.01 sfirst byte + slowest asset

Requests26document + assets

Page weight162.5 KBcompressed transfer

HTML document50.5 KBbr

ProtocolHTTP/3cloudflare

Third-party86.2 KBother hosts

Where the first byte went

DNS lookup 67 ms 13%
TCP connect 28 ms 6%
Server wait 404 ms 81%

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

Page weightlighter than 82% of 4,999 pages tested here162.5 KB against a median of 650.5 KB

Fully loadedslower than 82% of 4,999 pages tested here3.01 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 499 ms. That is workable, and the cheapest win left is caching or a warmer connection.
The page transfers 162.5 KB over 26 request(s). Javascript files are 44% of it, so defer what is not needed for the first screen, and drop tags nobody uses.
The HTML itself arrives br-compressed.
It runs over HTTP/3, so the assets share a connection instead of opening one each.
53% of the weight comes from other hosts (analytics, fonts, embeds), which also means their slow day becomes your slow day.

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.

No screenshot for this report.

The headless browser did not capture this page when the test ran, so only the server measurements are shown.

Page weight by type

What the page is made of

Javascript 4 requests

70.7 KB 44%

Html 19 requests

25.9 KB 16%

Images 2 requests

15.3 KB 9%

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

Top issues

Server response time (TTFB)

high impact

The first byte arrived after 499 ms. Of that, 404 ms was the server thinking and 95 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

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

Third-party weight

low impact

6 third-party host(s) serve 86.2 KB of this page. Each one is another DNS lookup, TLS handshake and point of failure you do not control.

Fix: Self-host the libraries you can, drop the tags you cannot justify, and preconnect the ones you keep.