www.nps.gov/index.htm speed test — 20 Oct 2026

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

https://www.nps.gov/index.htm

20 October 2026 at 12:56 UTC · Free test · report pt_1120454dfc2b

Re-test this page Test your own site

Grade

80/100

Performance75/100

Structure88/100

14 audit(s) passed, 2 need work

First byte (TTFB)130 msmeasured from this server

Fully loaded10.13 sfirst byte + slowest asset

Requests26document + assets

Page weight121.6 KBcompressed transfer

HTML document13.4 KBgzip

ProtocolHTTP/3NPS.gov

Where the first byte went

DNS lookup 33 ms 25%
TCP connect 13 ms 10%
Server wait 84 ms 65%

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

Page weightlighter than 86% of 4,999 pages tested here121.6 KB against a median of 650.5 KB

Fully loadedslower than 99% of 4,999 pages tested here10.13 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 server answered in 130 ms, which is fast: almost all of the wait is the page itself, not the host.
The page transfers 121.6 KB over 26 request(s). Html files are 89% 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 608 ms, inside the 2.5 s Google calls good.
Layout stayed still (CLS 0.033), so nothing jumps under the reader's cursor.
The main thread was blocked for 207 ms, 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.

Desktop screenshot of www.nps.gov — **Desktop** 1366 × 768 · 1.09 MB · page is 3661 px tall

Mobile screenshot of www.nps.gov — **Mobile** 390 × 844 · 264.4 KB · page is 6000 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 paint608 msgood is under 2.5 s

Cumulative layout shift0.033under 0.1 is stable

Total blocking time207 mslong tasks during load

First contentful paint420 msfirst content on screen

Browser page weight16.99 MB99 request(s), scripts included

Largest contentful paint608 ms

Goodgood under 2.5 s, poor over 4 s

Cumulative layout shift0.033

Goodgood under 0.1, poor over 0.25

Total blocking time207 ms

Needs improvementgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Html 24 requests

108.2 KB 89%

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

Top issues

Render-blocking resources

high impact

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