www.ietf.org speed test — 20 Oct 2026

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

https://www.ietf.org/

20 October 2026 at 12:24 UTC · Free test · report pt_5b156efbb6ca
Grade
A
91/100
Performance99/100
Structure80/100

11 audit(s) passed, 5 need work

First byte (TTFB)235 msmeasured from this server
Fully loaded1.05 sfirst byte + slowest asset
Requests13document + assets
Page weight727.4 KBcompressed transfer
HTML document8.6 KBbr
ProtocolHTTP/3cloudflare
Third-party2.3 KBother hosts

Where the first byte went

  • DNS lookup 60 ms 26%
  • TCP connect 32 ms 14%
  • Server wait 143 ms 61%

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 here235 ms against a median of 449 ms
Page weightheavier than 53% of 4,999 pages tested here727.4 KB against a median of 650.3 KB
Fully loadedfaster than 91% of 4,999 pages tested here1.05 s against a median of 1.84 s
Requestssends fewer requests than 85% of 4,999 pages tested here13 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 235 ms. That is workable, and the cheapest win left is caching or a warmer connection.
  • The page transfers 727.4 KB over 13 request(s), which is lean. Images files are 81% 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.

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.

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

Images 9 requests
589.8 KB 81%
Javascript 1 request
77.3 KB 11%
Css 2 requests
51.7 KB 7%

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

Top issues

Image delivery and format

high impact

1 image(s) over 200 KB and 1 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.

Cache static assets

medium impact

3 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

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.

Mobile viewport

medium impact

No viewport meta tag, so a phone renders the desktop layout scaled down.

Fix: Add a viewport meta tag with width=device-width and an initial scale of 1.

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.

Waterfall

Slowest requests

IMAGESanalytics.ietf.org/matomo.php
819 ms
CSSstatic.ietf.org/fonts/inter/import.css
697 ms
IMAGESstatic.ietf.org/logos/ietf.svg
686 ms
IMAGESwww.ietf.org/media/images/111-SanFrancisco.height-2…
497 ms
IMAGESwww.ietf.org/media/images/IMG_15.width-600.jpg
495 ms
IMAGESwww.ietf.org/media/images/111-SanFrancisco.max-4000…
466 ms
CSSwww.ietf.org/static/dist/main.6fff6370f135.css
466 ms
IMAGESwww.ietf.org/media/images/_MG_4832.width-600.jpg
466 ms
IMAGESwww.ietf.org/media/images/ietf128-kuala-lumpur.heig…
466 ms
IMAGESwww.ietf.org/media/images/things.width-600.jpg
466 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://analytics.ietf.org/matomo.php?idsite=1 3rd partyimages200819 ms43 B
https://static.ietf.org/fonts/inter/import.css 3rd partycss200697 ms625 B
https://static.ietf.org/logos/ietf.svg 3rd partyimages200686 ms1.7 KB
https://www.ietf.org/media/images/111-SanFrancisco.height-245.jpgimages200497 ms14.0 KB
https://www.ietf.org/media/images/IMG_15.width-600.jpgimages200495 ms40.6 KB
https://www.ietf.org/media/images/111-SanFrancisco.max-4000x4000.jpgimages200466 ms398.2 KB
https://www.ietf.org/static/dist/main.6fff6370f135.csscss200466 ms51.1 KB
https://www.ietf.org/media/images/_MG_4832.width-600.jpgimages200466 ms47.9 KB
https://www.ietf.org/media/images/ietf128-kuala-lumpur.height-245.jpgimages200466 ms33.2 KB
https://www.ietf.org/media/images/things.width-600.jpgimages200466 ms29.7 KB
https://www.ietf.org/media/images/ietf-logo.width-600.jpgimages200466 ms24.5 KB
https://www.ietf.org/static/dist/main.fbd56cfccb3b.jsjavascript200408 ms77.3 KB
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.