STATUS IS UPREADINESS PROFILE

Website readiness profile · Snapshot 23 October 2026

fast.com

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

Readiness index
55/100

Web Tools median 67

Ahead of
14%

of measured Web Tools sites

Practices observed
13/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: fast.com. Thin bar: Web Tools peer median.

Enable

47/100

Peers 84

Harden

55/100

Peers 55

Accelerate

67/100

Peers 69

Recover

0/100

Peers 6

Priority fixes for fast.com

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

  1. Priority 1 · Enable

    Mobile viewport configured

    Observed: The homepage had no viewport meta tag, so phones may render it zoomed out.

    Why it matters: Without it, phones render the page at desktop width and shrink it, which makes text tiny and hard to use.

    What to do: Add <meta name="viewport" content="width=device-width, initial-scale=1"> and check the layout on small screens.

    97% 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 · Harden

    TLS 1.3 negotiated

    Observed: The TLS connection negotiated TLSv1.2.

    What to do: Enable TLS 1.3 on your CDN or server. Keep TLS 1.2 available for older clients unless you have checked your audience.

    92% of Web Tools peers do this.

  3. Priority 3 · Accelerate

    Static files cached for 30 days or more

    Observed: A same-site stylesheet or script was cacheable for 5 days, short of the 30-day benchmark.

    What to do: Give versioned (fingerprinted) CSS, JavaScript, fonts and images Cache-Control: public, max-age=31536000, immutable, and change the file name whenever the content changes.

    54% of Web Tools peers do this.

  4. Priority 4 · Enable

    XML sitemap discoverable

    Observed: No sitemap was listed in robots.txt or found at /sitemap.xml.

    What to do: Generate an XML sitemap of canonical URLs, reference it in robots.txt and submit it in Google Search Console.

    73% of Web Tools peers do this.

What fast.com already does well

Practices fewer than half of Web Tools peers use.

  • CAA records limit who can issue certificatesCAA limits issuance to entrust.net, pki.goog, thawte.com.14% of peers
  • DMARC policy enforces quarantine or rejectDMARC policy p=reject.23% of peers
  • HSTS kept for at least a yearHSTS with a 365-day max-age.30% of peers

What we saw

Homepage checked
https://fast.com/
Homepage response
HTTP 200
TLS
TLSv1.2, HTTP/2
Certificate
DigiCert, 198-day validity, expiring 2027-04-16
DNS operators
Akamai Edge DNS
HSTS
max-age 365 days
DMARC policy
p=reject
Homepage HTML
26 KB, gzip
Images on homepage
0

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 13

  • HTTP requests move to HTTPS
  • HSTS kept for at least a year
  • Certificate has more than 14 days left
  • CAA records limit who can issue certificates
  • DMARC policy enforces quarantine or reject
  • HTTP/2 negotiated
  • HTML compressed
  • No render-blocking scripts in <head>
  • Reachable over IPv6
  • Canonical URL declared
  • Meta description written
  • Social preview image set
  • At most one redirect to the homepage

Not measured 3

  • Modern image formats in use
  • Offscreen images lazy-loaded
  • robots.txt published

Own fast.com?

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: fast.com. This profile covers configuration only.

Compare with other Web Tools sites