fox8.com

Readiness by lane

Green: fox8.com. Thin bar: News & Media peer median.

Priority fixes for fox8.com

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

1. Priority 1 · Harden

   HSTS kept for at least a year

   Observed: Strict-Transport-Security was sent with a max-age of 0 days, below the one-year benchmark.

   Why it matters: HSTS tells browsers to use HTTPS for your host on every later visit, which removes the window where a first HTTP request can be intercepted.

   What to do: Send Strict-Transport-Security on HTTPS responses. Start with a short max-age (for example 300 seconds), confirm every subdomain works over HTTPS, then raise it in steps to 31536000. Add includeSubDomains only when all subdomains are HTTPS. HSTS preload is optional and hard to undo; hstspreload.org itself does not recommend it by default.

   On Fastly: Add the header in VCL or a header rule as described in Fastly's HSTS guide.

   35% of News & Media peers do this. Limit: Read from the homepage response only; other pages or regions may send different headers.

   Guide: HTTPS and TLS Guide for Website Owners

2. Priority 2 · Accelerate

   Modern image formats in use

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

   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 WordPress: WordPress has supported WebP uploads since 5.8 and AVIF since 6.5; image plugins or the host can convert existing images.

   44% of News & Media peers do this.

   Guide: AVIF, WebP, JPEG, and PNG: Choose the Right Image Format

3. Priority 3 · Accelerate

   No render-blocking scripts in <head>

   Observed: The homepage <head> loaded 15 external scripts without async or defer.

   What to do: Add defer to scripts that need the DOM, async to independent ones such as analytics, or move them to the end of the body.

   On WordPress: Since WordPress 6.3, scripts can be registered with a defer or async loading strategy.

   42% of News & Media peers do this.

   Guide: Control Third-Party Scripts Before They Control Your Page

4. Priority 4 · Harden

   Framing restricted

   Observed: The homepage did not send frame-ancestors or X-Frame-Options, so other sites may frame it.

   What to do: Send Content-Security-Policy: frame-ancestors 'self' (or a list of trusted origins). X-Frame-Options: SAMEORIGIN covers older browsers.

   On Blogger: this setting is largely controlled by the platform. Check the platform's settings and documentation, or ask its support team whether it can be changed for your domain.

   42% of News & Media peers do this.

   Guide: A Practical Website Health Check for Owners

What fox8.com already does well

Practices fewer than half of News & Media peers use.

• Content Security Policy presentContent-Security-Policy present.29% of peers
• DMARC policy enforces quarantine or rejectDMARC policy p=reject.37% of peers

What we saw

Homepage checked

https://fox8.com/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

Let's Encrypt, 89-day validity, expiring 2027-01-16

CDN or edge

Fastly, WordPress VIP

Platform or framework

WordPress, Blogger

DNS operators

1 self-run or other nameserver domain

HSTS

max-age 0 days, includeSubDomains

DMARC policy

p=reject

Homepage HTML

1,088 KB, gzip

Images on homepage

128 (jpg 719, png 186, svg 10, gif 1)

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

Compare with other News & Media sites

• extra.cw68
• faz.net68
• fortune.com68
• ftnews.jp68
• fvn.no68

News & Media readiness benchmark