investor.vanguard.com/corporate-portal speed test — 20 Oct 2026

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

https://investor.vanguard.com/corporate-portal

20 October 2026 at 13:25 UTC · Free test · report pt_d52a05f4b0c5

Re-test this page Test your own site

Grade

95/100

Performance99/100

Structure89/100

13 audit(s) passed, 3 need work

First byte (TTFB)233 msmeasured from this server

Fully loaded1.52 sfirst byte + slowest asset

Requests18document + assets

Page weight11.7 KBcompressed transfer

HTML document7.0 KBgzip

ProtocolHTTP/3server not sent

Third-party4.7 KBother hosts

Where the first byte went

DNS lookup 56 ms 24%
TCP connect 27 ms 12%
Server wait 149 ms 64%

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

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

Fully loadedfaster than 69% of 4,999 pages tested here1.52 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 233 ms. That is workable, and the cheapest win left is caching or a warmer connection.
The page transfers 11.7 KB over 18 request(s). Javascript files are 40% 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.
40% 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 2.01 s, inside the 2.5 s Google calls good.
The main thread was blocked for 135 ms in total, which is not enough to feel.

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 investor.vanguard.com — **Mobile** 390 × 844 · 236.1 KB · page is 5526 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.01 sgood is under 2.5 s

Cumulative layout shift0.000under 0.1 is stable

Total blocking time135 mslong tasks during load

First contentful paint2.01 sfirst content on screen

Browser page weight1.75 MB59 request(s), scripts included

Failed requests3blocked or unreachable

Largest contentful paint2.01 s

Goodgood under 2.5 s, poor over 4 s

Cumulative layout shift0.000

Goodgood under 0.1, poor over 0.25

Total blocking time135 ms

Goodgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Javascript 1 request

4.7 KB 40%

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

Top issues

Render-blocking resources

high impact

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

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.

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.