www.ripe.net speed test — 20 Oct 2026

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

https://www.ripe.net/

20 October 2026 at 13:31 UTC · Free test · report pt_7fd660512abd
Grade
B
85/100
Performance84/100
Structure86/100

12 audit(s) passed, 4 need work

First byte (TTFB)744 msmeasured from this server
Fully loaded1.82 sfirst byte + slowest asset
Requests25document + assets
Page weight652.3 KBcompressed transfer
HTML document18.9 KBgzip
ProtocolHTTP/3nginx
Third-party283.8 KBother hosts

Where the first byte went

  • DNS lookup 79 ms 11%
  • TCP connect 40 ms 5%
  • Server wait 625 ms 84%

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 72% of 4,999 pages tested here744 ms against a median of 448 ms
Page weightlighter than 50% of 4,999 pages tested here652.3 KB against a median of 650.3 KB
Fully loadedfaster than 51% of 4,999 pages tested here1.82 s against a median of 1.84 s
Requestssends fewer requests than 74% of 4,999 pages tested here25 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 744 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 652.3 KB over 25 request(s). Images files are 88% of it, so resize and recompress the largest images before anything else.
  • The HTML itself arrives gzip-compressed.
  • It runs over HTTP/3, so the assets share a connection instead of opening one each.
  • 44% 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 136 ms, inside the 2.5 s Google calls good.

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.ripe.net
Desktop 1366 × 768 · 18.8 KB · page is 768 px tall
Mobile screenshot of www.ripe.net
Mobile 390 × 844 · 7.0 KB · page is 2121 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 paint136 msgood is under 2.5 s
Cumulative layout shift0.000under 0.1 is stable
Total blocking timenone over 50 mslong tasks during load
First contentful paint136 msfirst content on screen
Browser page weight474 B1 request(s), scripts included
Largest contentful paint136 ms
Goodgood under 2.5 s, poor over 4 s
Cumulative layout shift0.000
Goodgood under 0.1, poor over 0.25
Total blocking timenone over 50 ms
Goodgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Images 15 requests
576.0 KB 88%
Css 1 request
25.8 KB 4%
Fonts 1 request
24.6 KB 4%
Javascript 1 request
5.8 KB 1%
Html 5 requests
1.1 KB 0%
Other 1 request
200 B 0%

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

Top issues

Server response time (TTFB)

high impact

The first byte arrived after 744 ms. Of that, 625 ms was the server thinking and 119 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.

Image delivery and format

medium impact

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

Third-party weight

medium impact

2 third-party host(s) serve 283.8 KB of this page. Each one is another DNS lookup, TLS handshake and point of failure you do not control.

Fix: Self-host the libraries you can, drop the tags you cannot justify, and preconnect the ones you keep.

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.

Waterfall

Slowest requests

JAVASCRIPTwww-static.ripe.net/static/webcomponents/embed-consent-v1.…
1.08 s
IMAGESlabs.ripe.net/media/images/Screenshot_2026-07-08_at_…
1.04 s
IMAGESlabs.ripe.net/media/images/Big_One_Square.2e16d0ba.f…
1.04 s
IMAGESlabs.ripe.net/media/images/Screenshot_2022-04-06_at_…
1.04 s
IMAGESwww.ripe.net/media/images/RIPE_84_NCC_BERL.2e16d0ba…
1.03 s
IMAGESlabs.ripe.net/media/images/iStock-1474578060.2e16d0b…
1.03 s
IMAGESlabs.ripe.net/media/images/MirjamKuehne-RIPENCC-smal…
1.03 s
IMAGESlabs.ripe.net/media/images/DSC_0440_small.ef870e68.f…
1.02 s
IMAGESwww.ripe.net/static/favicons/favicon.svg
1.00 s
HTMLwww.ripe.net/static/favicons/favicon.ico
1.00 s

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-static.ripe.net/static/webcomponents/embed-consent-v1.1.6.min.js 3rd partyjavascript2001.08 s5.8 KB
https://labs.ripe.net/media/images/Screenshot_2026-07-08_at_13.38.41.2e16d0ba.fill-868x384.png 3rd partyimages2001.04 s50.9 KB
https://labs.ripe.net/media/images/Big_One_Square.2e16d0ba.fill-96x96.png 3rd partyimages2001.04 s15.9 KB
https://labs.ripe.net/media/images/Screenshot_2022-04-06_at_12.06.16.2e16d0ba.fill-868x384.png 3rd partyimages2001.04 s84.6 KB
https://www.ripe.net/media/images/RIPE_84_NCC_BERL.2e16d0ba.format-jpeg.fill-1024x576-c100.jpgimages2001.03 s147.6 KB
https://labs.ripe.net/media/images/iStock-1474578060.2e16d0ba.fill-868x384.jpg 3rd partyimages2001.03 s121.0 KB
https://labs.ripe.net/media/images/MirjamKuehne-RIPENCC-small.2e16d0ba.fill-96x96.jpg 3rd partyimages2001.03 s2.8 KB
https://labs.ripe.net/media/images/DSC_0440_small.ef870e68.fill-96x96.jpg 3rd partyimages2001.02 s2.9 KB
https://www.ripe.net/static/favicons/favicon.svgimages2001.00 s458 B
https://www.ripe.net/static/favicons/favicon.icohtml4291.00 s221 B
https://www.ripe.net/media/images/RIPE_84_NCC_BER.2e16d0ba.format-webp.fill-1024x576-c100.webphtml429993 ms221 B
https://www.ripe.net/static/favicons/favicon-32x32.pnghtml429966 ms221 B
https://www.ripe.net/static/CACHE/js/js.a91a1190a5da.jshtml429951 ms221 B
https://www.ripe.net/static/favicons/apple-touch-icon.pnghtml429950 ms221 B
https://www.ripe.net/static/favicons/favicon-16x16.pngimages200938 ms1.1 KB
https://www.ripe.net/media/images/RIPE-Community-P.2e16d0ba.format-jpeg.fill-1024x576-c100.jpgimages200933 ms67.1 KB
https://www.ripe.net/media/images/RIPE-Community-.2e16d0ba.format-webp.fill-1024x576-c100.webpimages200920 ms36.5 KB
https://www.ripe.net/static/images/ripe-ncc-logo-2025.svgimages200917 ms1.3 KB
https://www.ripe.net/static/images/ripe-community-logo.svgimages200917 ms1.2 KB
https://www.ripe.net/media/images/Join-Us-93_URL.2e16d0ba.fill-720x405-c25.format-webp.webpimages200914 ms42.2 KB
https://www.ripe.net/static/CACHE/css/style.6be2b5fa6221.csscss200893 ms25.8 KB
https://www.ripe.net/static/images/rss.svgimages200892 ms495 B
https://www.ripe.net/static/fonts/public-sans-latin-normal.woff2fonts200891 ms24.6 KB
https://www.ripe.net/static/favicons/site.webmanifestother200891 ms200 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.