Website readiness profile · Snapshot 23 October 2026
theconversation.com
theconversation.com's public homepage, certificate and DNS checked against 31 practices and compared with 3,856 News & Media sites.
- Readiness index
- 76/100
- Ahead of
- 79%
- Practices observed
- 20/31
- Popularity band
- Top 10K
News & Media median 68
of measured News & Media sites
0 of 31 could not be measured
Chrome UX Report top-sites list
Readiness by lane
Green: theconversation.com. Thin bar: News & Media peer median.
Enable
72/100
Peers 89
Harden
69/100
Peers 56
Accelerate
90/100
Peers 68
Recover
100/100
Peers 11
Priority fixes for theconversation.com
Ordered by impact and by how common each practice is among peers.
Priority 1 · Enable
Page language declared
Observed: The homepage <html> element had no lang attribute.
Why it matters: Screen readers use it to choose pronunciation, and browsers use it to offer translation.
What to do: Set lang on the html element (for example lang="en") and on any sections in another language.
97% of News & Media peers do this. Limit: Based on the homepage HTML delivered to an automated client; scripts that run later were not executed.
Priority 2 · 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.
76% of News & Media peers do this.
Priority 3 · Enable
Social preview image set
Observed: The homepage had no og:image, so shared links may show without a preview image.
What to do: Add Open Graph tags, including og:image with a 1200 x 630 image.
71% of News & Media peers do this.
Priority 4 · 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.
36% of News & Media peers do this.
What theconversation.com already does well
Practices fewer than half of News & Media peers use.
- Nameservers spread across providersNameservers spread across more than one operator.11% of peers
- HSTS kept for at least a yearHSTS with a 365-day max-age covering subdomains.35% of peers
- DMARC policy enforces quarantine or rejectDMARC policy p=reject.37% of peers
What we saw
- Homepage checked
- https://theconversation.com/
- Homepage response
- HTTP 200, after 1 redirect
- TLS
- TLSv1.3, HTTP/2
- Certificate
- Let's Encrypt, 89-day validity, expiring 2027-01-08
- CDN or edge
- Fastly, Google edge
- Platform or framework
- Next.js
- DNS operators
- 5 self-run or other nameserver domains
- HSTS
- max-age 365 days, includeSubDomains, preload
- DMARC policy
- p=reject
- Homepage HTML
- 594 KB, gzip
- Images on homepage
- 114 (jpg 1400, png 168, svg 2)
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
Not observed 11
Observed 20
- 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
- DMARC policy enforces quarantine or reject
- Framing restricted
- HTTP/2 negotiated
- HTML compressed
- Static files cached for 30 days or more
- Modern image formats in use
- Offscreen images lazy-loaded
- No render-blocking scripts in <head>
- robots.txt published
- XML sitemap discoverable
- Canonical URL declared
- Meta description written
- Mobile viewport configured
- At most one redirect to the homepage
- Nameservers spread across providers
Own theconversation.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: theconversation.com. This profile covers configuration only.