login.gov speed test — 20 Oct 2026

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

https://login.gov/

20 October 2026 at 15:00 UTC · Free test · report pt_fc614a3989fa
Grade
A
98/100
Performance99/100
Structure97/100

15 audit(s) passed, 1 need work

First byte (TTFB)254 msmeasured from this server
Fully loaded1.17 sfirst byte + slowest asset
Requests18document + assets
Page weight267.1 KBcompressed transfer
HTML document4.5 KBgzip
ProtocolHTTP/3server not sent
Third-party176.2 KBother hosts

Where the first byte went

  • DNS lookup 87 ms 34%
  • TCP connect 32 ms 13%
  • Server wait 135 ms 53%

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 84% of 4,999 pages tested here254 ms against a median of 449 ms
Page weightlighter than 74% of 4,999 pages tested here267.1 KB against a median of 650.5 KB
Fully loadedfaster than 89% of 4,999 pages tested here1.17 s against a median of 1.84 s
Requestssends fewer requests than 81% of 4,999 pages tested here18 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 254 ms. That is workable, and the cheapest win left is caching or a warmer connection.
  • The page transfers 267.1 KB over 18 request(s). Javascript files are 71% of it, so defer what is not needed for the first screen, and drop tags nobody uses.
  • The HTML itself arrives gzip-compressed.
  • It runs over HTTP/3, so the assets share a connection instead of opening one each.
  • 66% of the weight comes from other hosts (analytics, fonts, embeds), which also means their slow day becomes your slow day.
  • The largest element painted at 664 ms, inside the 2.5 s Google calls good.
  • Layout stayed still (CLS 0.001), so nothing jumps under the reader's cursor.
  • The main thread was blocked for 110 ms in total, which is not enough to feel.

Fix first: Cache static assets - Version filenames on change and serve them with a long max-age plus immutable. That is what makes a returning visitor fast.

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 login.gov
Desktop 1366 × 768 · 195.7 KB · page is 1794 px tall
Mobile screenshot of login.gov
Mobile 390 × 844 · 50.6 KB · page is 2556 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 paint664 msgood is under 2.5 s
Cumulative layout shift0.001under 0.1 is stable
Total blocking time110 mslong tasks during load
First contentful paint532 msfirst content on screen
Browser page weight1,020.8 KB32 request(s), scripts included
Largest contentful paint664 ms
Goodgood under 2.5 s, poor over 4 s
Cumulative layout shift0.001
Goodgood under 0.1, poor over 0.25
Total blocking time110 ms
Goodgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Javascript 4 requests
189.2 KB 71%
Css 1 request
63.8 KB 24%
Images 10 requests
9.3 KB 3%
Other 1 request
173 B 0%
Html 1 request
92 B 0%

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

Top issues

Cache static assets

medium impact

1 asset(s) answer without a Cache-Control max-age, so browsers revalidate them on every visit.

Fix: Version filenames on change and serve them with a long max-age plus immutable. That is what makes a returning visitor fast.

Waterfall

Slowest requests

IMAGESlogin.gov/favicon-16x16.png
912 ms
IMAGESlogin.gov/apple-touch-icon.png
884 ms
CSSlogin.gov/assets/css/main.css
860 ms
HTMLwww.googletagmanager.com/ns.html
853 ms
IMAGESlogin.gov/favicon-32x32.png
843 ms
JAVASCRIPTwww.googletagmanager.com/gtag/js
834 ms
JAVASCRIPTlogin.gov/assets/js/init.js
833 ms
IMAGESlogin.gov/assets/img/gsa-logo.svg
828 ms
JAVASCRIPTlogin.gov/assets/js/main.js
826 ms
IMAGESlogin.gov/assets/img/globe-blue.svg
826 ms

Each bar is one request's own response time, scaled to the slowest. Assets were fetched in parallel, so the bars overlap in real time rather than stacking. first party third party

RequestTypeStatusTimeSize
https://login.gov/favicon-16x16.pngimages200912 ms911 B
https://login.gov/apple-touch-icon.pngimages200884 ms3.8 KB
https://login.gov/assets/css/main.csscss200860 ms63.8 KB
https://www.googletagmanager.com/ns.html?id=GTM-M3KZGM4 3rd partyhtml200853 ms92 B
https://login.gov/favicon-32x32.pngimages200843 ms1.3 KB
https://www.googletagmanager.com/gtag/js?id=G-HBYXWFP794 3rd partyjavascript200834 ms167.1 KB
https://login.gov/assets/js/init.jsjavascript200833 ms133 B
https://login.gov/assets/img/gsa-logo.svgimages200828 ms642 B
https://login.gov/assets/js/main.jsjavascript200826 ms13.0 KB
https://login.gov/assets/img/globe-blue.svgimages200826 ms471 B
https://login.gov/assets/img/icon-https.svgimages200820 ms402 B
https://dap.digitalgov.gov/Universal-Federated-Analytics-Min.js?agency=GSA&subagency=TTS 3rd partyjavascript200808 ms9.0 KB
https://login.gov/assets/img/close.svgimages200808 ms180 B
https://login.gov/assets/img/us-flag.pngimages200801 ms284 B
https://login.gov/assets/img/logo.svgimages200798 ms1008 B
https://login.gov/assets/img/icon-dot-gov.svgimages200795 ms378 B
https://login.gov/manifest.jsonother200791 ms173 B
Report this page

The page is removed when the owner agrees. Sending this removes nothing by itself.

Run this test on your own site

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