www.brookings.edu speed test — 20 Oct 2026

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

https://www.brookings.edu/

20 October 2026 at 13:31 UTC · Free test · report pt_2c0dd0fa6608

Re-test this page Test your own site

Grade

73/100

Performance75/100

Structure71/100

11 audit(s) passed, 5 need work

First byte (TTFB)193 msmeasured from this server

Fully loaded1.27 sfirst byte + slowest asset

Requests26document + assets

Page weight15.10 MBcompressed transfer

HTML document32.3 KBbr

ProtocolHTTP/3cloudflare

Where the first byte went

DNS lookup 68 ms 35%
TCP connect 4 ms 2%
Server wait 120 ms 62%

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

Page weightheavier than 99% of 4,999 pages tested here15.10 MB against a median of 650.3 KB

Fully loadedfaster than 84% of 4,999 pages tested here1.27 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 193 ms, which is fast: almost all of the wait is the page itself, not the host.
The page transfers 15.10 MB over 26 request(s). Images files are 100% of it, so resize and recompress the largest images before anything else.
The HTML itself arrives br-compressed.
It runs over HTTP/3, so the assets share a connection instead of opening one each.
The largest element painted at 1.08 s, inside the 2.5 s Google calls good.
Layout stayed still (CLS 0.065), so nothing jumps under the reader's cursor.
The main thread was blocked for 903 ms, so taps and scrolling wait while scripts run.

Fix first: Image delivery and format - Serve WebP or AVIF with a JPEG fallback, size images to the space they occupy, and lazy-load anything below the fold. Images are usually more than half of a slow page.

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 www.brookings.edu — **Mobile** 390 × 844 · 220.0 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 paint1.08 sgood is under 2.5 s

Cumulative layout shift0.065under 0.1 is stable

Total blocking time903 mslong tasks during load

First contentful paint988 msfirst content on screen

Browser page weight4.32 MB125 request(s), scripts included

Failed requests3blocked or unreachable

Largest contentful paint1.08 s

Goodgood under 2.5 s, poor over 4 s

Cumulative layout shift0.065

Goodgood under 0.1, poor over 0.25

Total blocking time903 ms

Poorgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Images 25 requests

15.07 MB 100%

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

Top issues

Image delivery and format

high impact

3 image(s) over 200 KB and 4 large image(s) still served as JPEG or PNG.

Fix: Serve WebP or AVIF with a JPEG fallback, size images to the space they occupy, and lazy-load anything below the fold. Images are usually more than half of a slow page.

Render-blocking resources

high impact

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

Total page weight

high impact

The page transfers 15.10 MB across 26 request(s), with the document itself at 32.3 KB.

Fix: Work through the heaviest assets first: images, then fonts, then third-party scripts.

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.

Strict-Transport-Security

low impact

HSTS is not set, so the first visit on a hostile network can still be downgraded to HTTP.

Fix: Send Strict-Transport-Security with a max-age of at least six months. Add includeSubDomains once every subdomain is HTTPS.