STATUS IS UPREADINESS PROFILE

Website readiness profile · Snapshot 23 October 2026

speedtest.net

speedtest.net's public homepage, certificate and DNS checked against 31 practices and compared with 492 Web Tools sites.

Readiness index
82/100

Web Tools median 67

Ahead of
91%

of measured Web Tools sites

Practices observed
21/28

3 of 31 could not be measured

Popularity band
Top 1K

Chrome UX Report top-sites list

Measured 2026-10-23 11:25:16 UTC from one location. How we measure

Readiness by lane

Green: speedtest.net. Thin bar: Web Tools peer median.

Enable

85/100

Peers 84

Harden

89/100

Peers 55

Accelerate

67/100

Peers 69

Recover

0/100

Peers 6

Priority fixes for speedtest.net

Ordered by impact and by how common each practice is among peers.

  1. Priority 1 · Accelerate

    Modern image formats in use

    Observed: The homepage had 5 images and none used WebP or AVIF.

    Why it matters: WebP and AVIF are typically much smaller than JPEG or PNG at similar quality, and images are often the heaviest part of a page.

    What to do: Serve WebP or AVIF with a JPEG or PNG fallback, either through an image CDN or by generating both formats at build time.

    On Cloudflare: Cloudflare Polish can convert images to WebP.

    37% of Web Tools peers do this. Limit: Based on the homepage HTML delivered to an automated client; scripts that run later were not executed.

  2. Priority 2 · Accelerate

    HTTP/3 advertised

    Observed: The homepage did not advertise HTTP/3 through an Alt-Svc header.

    What to do: Turn on HTTP/3 at your CDN. Browsers fall back to HTTP/2 automatically, so the risk is low.

    On Cloudflare: Enable HTTP/3 (with QUIC) under Speed > Optimization > Protocol Optimization.

    56% of Web Tools peers do this.

  3. Priority 3 · Enable

    Structured data present

    Observed: The homepage had no JSON-LD structured data.

    What to do: Add JSON-LD for your organization and main content types, then test it with Google's Rich Results Test.

    51% of Web Tools peers do this.

  4. Priority 4 · Harden

    CAA records limit who can issue certificates

    Observed: No CAA record was found for speedtest.net, so any public certificate authority may issue for it.

    What to do: Publish CAA records naming every CA you actually use, including the CAs your CDN uses for managed certificates. Add an iodef contact if you want reports.

    On Cloudflare: Cloudflare documents which CAs its managed certificates need; include them in your CAA records.

    14% of Web Tools peers do this.

What speedtest.net already does well

Practices fewer than half of Web Tools peers use.

  • security.txt publishedsecurity.txt with a contact found.4.8% of peers
  • Content Security Policy presentContent-Security-Policy present.15% of peers
  • DMARC policy enforces quarantine or rejectDMARC policy p=quarantine.23% of peers

What we saw

Homepage checked
https://www.speedtest.net/
Homepage response
HTTP 200
TLS
TLSv1.3, HTTP/2
Certificate
Google Trust Services, 90-day validity, expiring 2026-12-10
CDN or edge
Cloudflare
DNS operators
Amazon Route 53
HSTS
max-age 365 days, includeSubDomains, preload
DMARC policy
p=quarantine
Homepage HTML
202 KB, gzip
Images on homepage
5 (svg 5)

Limits: homepage only, one location, one moment. Header checks reflect the homepage response; other pages may differ.

Stack and providers

Seen in the homepage response, certificate and DNS. Provider pages compare how their customers configure the same checks.

All 31 checks

Select a gap for the method and fix. How each check works

Observed 21

  • HTTP requests move to HTTPS
  • HSTS kept for at least a year
  • TLS 1.3 negotiated
  • Certificate has more than 14 days left
  • Certificate lifetime of 100 days or less
  • security.txt published
  • DMARC policy enforces quarantine or reject
  • X-Content-Type-Options: nosniff
  • Framing restricted
  • Content Security Policy present
  • Referrer-Policy set
  • HTTP/2 negotiated
  • HTML compressed
  • No render-blocking scripts in <head>
  • XML sitemap discoverable
  • Canonical URL declared
  • Meta description written
  • Mobile viewport configured
  • Social preview image set
  • Page language declared
  • At most one redirect to the homepage

Not measured 3

  • Static files cached for 30 days or more
  • Offscreen images lazy-loaded
  • robots.txt published

Own speedtest.net?

Re-run the checks after a change, keep a private action plan in a free workspace, or report a mistake.

Live status for this site: Status Is Down: speedtest.net. This profile covers configuration only.

Compare with other Web Tools sites