Website readiness profile · Snapshot 23 October 2026
tpi.li
tpi.li's public homepage, certificate and DNS checked against 31 practices and compared with 306 Online Publishing sites.
- Readiness index
- 65/100
- Ahead of
- 52%
- Practices observed
- 17/29
- Popularity band
- Top 50K
Online Publishing median 64
of measured Online Publishing sites
2 of 31 could not be measured
Chrome UX Report top-sites list
Readiness by lane
Green: tpi.li. Thin bar: Online Publishing peer median.
Enable
74/100
Peers 84
Harden
54/100
Peers 51
Accelerate
80/100
Peers 65
Recover
0/100
Peers 5
Priority fixes for tpi.li
Ordered by impact and by how common each practice is among peers.
Priority 1 · Harden
HSTS kept for at least a year
Observed: The homepage response did not include a Strict-Transport-Security header.
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 Cloudflare: Enable HSTS under SSL/TLS > Edge Certificates > HTTP Strict Transport Security and raise max-age gradually.
27% of Online Publishing peers do this. Limit: Read from the homepage response only; other pages or regions may send different headers.
Priority 2 · Accelerate
Modern image formats in use
Observed: The homepage had 4 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 Cloudflare: Cloudflare Polish can convert images to WebP.
38% of Online Publishing peers do this.
Guide: AVIF, WebP, JPEG, and PNG: Choose the Right Image Format
Priority 3 · Enable
Canonical URL declared
Observed: The homepage did not declare a canonical URL.
What to do: Add a self-referencing canonical link to every indexable page, using the final https:// URL.
80% of Online Publishing peers do this.
Priority 4 · Harden
DMARC policy enforces quarantine or reject
Observed: No DMARC record was found at _dmarc.tpi.li.
What to do: Publish DMARC with p=none and a reporting address first, fix any legitimate senders that fail SPF or DKIM alignment, then move to quarantine and finally reject.
20% of Online Publishing peers do this.
What tpi.li already does well
Practices fewer than half of Online Publishing peers use.
- Framing restrictedFraming controls present.37% of peers
- HTTP/3 advertisedHTTP/3 advertised.41% of peers
- X-Content-Type-Options: nosniffnosniff header present.43% of peers
What we saw
- Homepage checked
- https://tpi.li/
- Homepage response
- HTTP 200
- TLS
- TLSv1.3, HTTP/2
- Certificate
- Google Trust Services, 90-day validity, expiring 2026-12-28
- CDN or edge
- Cloudflare
- DNS operators
- Cloudflare
- Homepage HTML
- 14 KB, br
- Images on homepage
- 4 (svg 4)
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 12
- HSTS kept for at least a year
- CAA records limit who can issue certificates
- DNSSEC signed
- security.txt published
- DMARC policy enforces quarantine or reject
- Content Security Policy present
- Referrer-Policy set
- Modern image formats in use
- Canonical URL declared
- Structured data present
- Social preview image set
- Nameservers spread across providers
Observed 17
- HTTP requests move to HTTPS
- TLS 1.3 negotiated
- Certificate has more than 14 days left
- Certificate lifetime of 100 days or less
- X-Content-Type-Options: nosniff
- Framing restricted
- HTTP/2 negotiated
- HTTP/3 advertised
- HTML compressed
- No render-blocking scripts in <head>
- robots.txt published
- XML sitemap discoverable
- Reachable over IPv6
- Meta description written
- Mobile viewport configured
- Page language declared
- At most one redirect to the homepage
Not measured 2
- Static files cached for 30 days or more
- Offscreen images lazy-loaded
Own tpi.li?
Re-run the checks after a change, or verify the site in a free workspace to save reports with history, compare against similar sites and competitors, and track a private action plan. What owners get.
Live status for this site: Status Is Down: tpi.li. This profile covers configuration only.