www.rfc-editor.org speed test — 20 Oct 2026

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

https://www.rfc-editor.org/

20 October 2026 at 12:29 UTC · Free test · report pt_91753e9ecd97
Grade
B
81/100
Performance82/100
Structure80/100

11 audit(s) passed, 5 need work

First byte (TTFB)853 msmeasured from this server
Fully loaded1.48 sfirst byte + slowest asset
Requests12document + assets
Page weight139.9 KBcompressed transfer
HTML document33.8 KBbr
ProtocolHTTP/3cloudflare
Third-party625 Bother hosts

Where the first byte went

  • DNS lookup 54 ms 6%
  • TCP connect 11 ms 1%
  • Server wait 788 ms 92%

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 byteslower than 78% of 4,999 pages tested here853 ms against a median of 448 ms
Page weightlighter than 84% of 4,999 pages tested here139.9 KB against a median of 650.5 KB
Fully loadedfaster than 71% of 4,999 pages tested here1.48 s against a median of 1.84 s
Requestssends fewer requests than 86% of 4,999 pages tested here12 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 took 853 ms. Everything else waits for that number, so the server is where to start: caching, a slow query, or an overloaded host.
  • The page transfers 139.9 KB over 12 request(s), which is lean. Css files are 42% of it, so split the stylesheet so the first screen does not download the whole site.
  • 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.11 s, inside the 2.5 s Google calls good.
  • Layout stayed still (CLS 0.046), so nothing jumps under the reader's cursor.
  • The main thread was blocked for 50 ms in total, which is not enough to feel.

Fix first: Server response time (TTFB) - Cut server think time: page cache, query indexes, fewer synchronous calls to third parties inside the request. Connection setup is distance, so a nearer region or a CDN edge helps instead.

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.rfc-editor.org
Desktop 1366 × 768 · 121.7 KB · page is 1642 px tall
Mobile screenshot of www.rfc-editor.org
Mobile 390 × 844 · 60.8 KB · page is 3285 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.11 sgood is under 2.5 s
Cumulative layout shift0.046under 0.1 is stable
Total blocking time50 mslong tasks during load
First contentful paint1.11 sfirst content on screen
Browser page weight468.6 KB29 request(s), scripts included
Largest contentful paint1.11 s
Goodgood under 2.5 s, poor over 4 s
Cumulative layout shift0.046
Goodgood under 0.1, poor over 0.25
Total blocking time50 ms
Goodgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Css 2 requests
58.4 KB 42%
Images 8 requests
47.6 KB 34%
Javascript 1 request
135 B 0%

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

Top issues

Server response time (TTFB)

high impact

The first byte arrived after 853 ms. Of that, 788 ms was the server thinking and 65 ms was connection setup. A first byte under 400 ms is what a visitor feels as instant.

Fix: Cut server think time: page cache, query indexes, fewer synchronous calls to third parties inside the request. Connection setup is distance, so a nearer region or a CDN edge helps instead.

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

7 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.

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

IMAGESwww.rfc-editor.org/api/v1/favicon/180x180.png
629 ms
IMAGESwww.rfc-editor.org/_nuxt/1.141.1/logo-mobile.CoO2D8c2.svg
577 ms
CSSstatic.ietf.org/fonts/inter/import.css
577 ms
JAVASCRIPTwww.rfc-editor.org/_nuxt/1.141.1/CZBM8QAZ.js
577 ms
IMAGESwww.rfc-editor.org/api/v1/favicon/32x32.png
567 ms
IMAGESwww.rfc-editor.org/api/v1/favicon/16x16.png
553 ms
IMAGESwww.rfc-editor.org/api/v1/favicon/48x48.png
545 ms
IMAGESwww.rfc-editor.org/api/v1/favicon/512x512.png
543 ms
IMAGESwww.rfc-editor.org/api/v1/favicon/192x192.png
541 ms
CSSwww.rfc-editor.org/_nuxt/1.141.1/style.BU5uCkVr.css
525 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://www.rfc-editor.org/api/v1/favicon/180x180.pngimages200629 ms6.8 KB
https://www.rfc-editor.org/_nuxt/1.141.1/logo-mobile.CoO2D8c2.svgimages200577 ms2.8 KB
https://static.ietf.org/fonts/inter/import.css 3rd partycss200577 ms625 B
https://www.rfc-editor.org/_nuxt/1.141.1/CZBM8QAZ.jsjavascript200577 ms135 B
https://www.rfc-editor.org/api/v1/favicon/32x32.pngimages200567 ms1017 B
https://www.rfc-editor.org/api/v1/favicon/16x16.pngimages200553 ms524 B
https://www.rfc-editor.org/api/v1/favicon/48x48.pngimages200545 ms1.7 KB
https://www.rfc-editor.org/api/v1/favicon/512x512.pngimages200543 ms21.7 KB
https://www.rfc-editor.org/api/v1/favicon/192x192.pngimages200541 ms7.0 KB
https://www.rfc-editor.org/_nuxt/1.141.1/style.BU5uCkVr.csscss200525 ms57.8 KB
https://www.rfc-editor.org/_nuxt/1.141.1/logo-desktop.DmfyR5wx.svgimages200495 ms6.2 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.