www.spamhaus.org speed test — 20 Oct 2026

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

https://www.spamhaus.org/

20 October 2026 at 12:36 UTC · Free test · report pt_bd439591b705
Grade
C
74/100
Performance75/100
Structure73/100

10 audit(s) passed, 6 need work

First byte (TTFB)210 msmeasured from this server
Fully loaded1.46 sfirst byte + slowest asset
Requests26document + assets
Page weight4.33 MBcompressed transfer
HTML document135.0 KBgzip
ProtocolHTTP/3cloudflare
Third-party50.4 KBother hosts

Where the first byte went

  • DNS lookup 45 ms 21%
  • TCP connect 35 ms 17%
  • Server wait 130 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 91% of 4,999 pages tested here210 ms against a median of 449 ms
Page weightheavier than 92% of 4,999 pages tested here4.33 MB against a median of 650.3 KB
Fully loadedfaster than 73% of 4,999 pages tested here1.46 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 first byte arrived in 210 ms. That is workable, and the cheapest win left is caching or a warmer connection.
  • The page transfers 4.33 MB over 26 request(s). Css files are 36% of it, so split the stylesheet so the first screen does not download the whole site.
  • The HTML itself arrives gzip-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

Css 4 requests
1.57 MB 36%
Images 16 requests
1.16 MB 27%
Javascript 1 request
603.9 KB 14%
Fonts 2 requests
574.8 KB 13%
Other 1 request
329.2 KB 7%
Html 1 request
92 B 0%

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

Top issues

Image delivery and format

high impact

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

5 render-blocking resource(s) in the document head (1 script(s), 4 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 4.33 MB across 26 request(s), with the document itself at 135.0 KB.

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

HTML document size

medium impact

The document transfers 135.0 KB. A bloated document delays every other request, because nothing else can start until it is parsed.

Fix: Paginate long listings, move repeated markup into a template, and stop inlining large data URIs into the HTML.

JavaScript weight

medium impact

1 JavaScript file(s) over 200 KB: entry.CNANpXVa.js (603.9 KB)

Fix: Split routes, remove unused dependencies, and prefer a two-file build (one pinned library, one application bundle) over many small ones.

Waterfall

Slowest requests

IMAGESwww.spamhaus.org/_nuxt/bg-error-blue.fOSKE4Di.webp
1.25 s
IMAGESwww.spamhaus.org/_nuxt/bg-how-much.ClWN-MKR.webp
1.14 s
IMAGESwww.spamhaus.org/_nuxt/bg-error-yellow.Cmg2qh4O.webp
1.08 s
FONTSwww.spamhaus.org/_nuxt/uicons-solid-straight-ITFA7HIK.D…
1.07 s
OTHERwww.spamhaus.org/_nuxt/uicons-solid-straight-W4CCEH4W.t…
1.04 s
CSSfonts.googleapis.com/css2
995 ms
IMAGESwww.spamhaus.org/_nuxt/bg-cta.i1Y2ENKG.webp
985 ms
FONTSwww.spamhaus.org/_nuxt/uicons-solid-straight-4DZ3VA4V.h…
972 ms
IMAGESwww.spamhaus.org/_nuxt/bg-footer.BTUjP0C9.webp
962 ms
IMAGESwww.spamhaus.org/_nuxt/bg-header.B01Vn0TW.webp
955 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.spamhaus.org/_nuxt/bg-error-blue.fOSKE4Di.webpimages2001.25 s63.6 KB
https://www.spamhaus.org/_nuxt/bg-how-much.ClWN-MKR.webpimages2001.14 s277.1 KB
https://www.spamhaus.org/_nuxt/bg-error-yellow.Cmg2qh4O.webpimages2001.08 s112.5 KB
https://www.spamhaus.org/_nuxt/uicons-solid-straight-ITFA7HIK.D8xIydPE.wofffonts2001.07 s328.4 KB
https://www.spamhaus.org/_nuxt/uicons-solid-straight-W4CCEH4W.tgviSdRN.eot#iefixother2001.04 s329.2 KB
https://fonts.googleapis.com/css2?family=Montserrat:wght@300;400;500;600;700;800&display=swap 3rd partycss200995 ms251 B
https://www.spamhaus.org/_nuxt/bg-cta.i1Y2ENKG.webpimages200985 ms57.3 KB
https://www.spamhaus.org/_nuxt/uicons-solid-straight-4DZ3VA4V.h_sLUC1L.woff2fonts200972 ms246.4 KB
https://www.spamhaus.org/_nuxt/bg-footer.BTUjP0C9.webpimages200962 ms39.7 KB
https://www.spamhaus.org/_nuxt/bg-header.B01Vn0TW.webpimages200955 ms66.4 KB
https://content.spamhaus.org/d71af756-aa81-41c7-b93c-af0d35301b83.png 3rd partyimages200947 ms50.0 KB
https://www.spamhaus.org/_nuxt/bg-hero.zFkavSth.webpimages200927 ms33.7 KB
https://www.spamhaus.org/_nuxt/bg-faq.BUhW55lE.webpimages200914 ms130.5 KB
https://www.spamhaus.org/_nuxt/style.UbryamDJ.csscss200893 ms1.57 MB
https://www.googletagmanager.com/ns.html?id=GTM-K9S544M 3rd partyhtml200893 ms92 B
https://www.spamhaus.org/_nuxt/entry.CNANpXVa.jsjavascript200877 ms603.9 KB
https://www.spamhaus.org/_nuxt/countries.Cdf8h20H.webpimages200877 ms20.7 KB
https://www.spamhaus.org/_nuxt/domains.Br6QxP3i.webpimages200877 ms16.2 KB
https://www.spamhaus.org/_nuxt/registrars.Ba8s7KTY.webpimages200877 ms13.9 KB
https://www.spamhaus.org/_nuxt/isps.Bi6EJOO7.webpimages200877 ms13.3 KB
https://www.spamhaus.org/_nuxt/logo.tPE1gnpS.svgimages200877 ms6.2 KB
https://www.spamhaus.org/_nuxt/entry.BcQQH_ep.csscss200877 ms4.3 KB
https://www.spamhaus.org/_nuxt/index.CriyoXjA.csscss200877 ms775 B
https://www.spamhaus.org/_nuxt/bg-dark-blue.DQrlEMpb.webpimages200876 ms193.9 KB
https://www.spamhaus.org/_nuxt/bg-check.B0OUyihm.webpimages200876 ms92.9 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.