Website readiness profile · Snapshot 23 October 2026
rpp.pe
rpp.pe's public homepage, certificate and DNS checked against 31 practices and compared with 3,856 News & Media sites.
- Readiness index
- 74/100
- Ahead of
- 73%
- Practices observed
- 20/30
- Popularity band
- Top 10K
News & Media median 68
of measured News & Media sites
1 of 31 could not be measured
Chrome UX Report top-sites list
Readiness by lane
Green: rpp.pe. Thin bar: News & Media peer median.
Enable
95/100
Peers 89
Harden
66/100
Peers 56
Accelerate
71/100
Peers 68
Recover
0/100
Peers 11
Priority fixes for rpp.pe
Ordered by impact and by how common each practice is among peers.
Priority 1 · Accelerate
Modern image formats in use
Observed: The homepage had 187 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.
44% of News & Media peers do this. Limit: Based on the homepage HTML delivered to an automated client; scripts that run later were not executed.
Guide: AVIF, WebP, JPEG, and PNG: Choose the Right Image Format
Priority 2 · Harden
DMARC policy enforces quarantine or reject
Observed: No DMARC record was found at _dmarc.rpp.pe.
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.
37% of News & Media peers do this.
Priority 3 · 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.
Priority 4 · Harden
X-Content-Type-Options: nosniff
Observed: The homepage response did not include X-Content-Type-Options: nosniff.
What to do: Send X-Content-Type-Options: nosniff on all responses and make sure each file is served with the correct Content-Type.
42% of News & Media peers do this.
What rpp.pe already does well
Practices fewer than half of News & Media peers use.
- Content Security Policy presentContent-Security-Policy present.29% of peers
- HSTS kept for at least a yearHSTS with a 365-day max-age.35% of peers
- Framing restrictedFraming controls present.42% of peers
What we saw
- Homepage checked
- https://rpp.pe/
- Homepage response
- HTTP 200
- TLS
- TLSv1.3, HTTP/2
- Certificate
- Let's Encrypt, 89-day validity, expiring 2026-12-17
- DNS operators
- Amazon Route 53
- HSTS
- max-age 365 days
- Homepage HTML
- 499 KB, gzip
- Images on homepage
- 187 (jpg 419, svg 24, png 19)
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 10
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
- Framing restricted
- Content Security Policy present
- HTTP/2 negotiated
- HTML compressed
- 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
- Structured data present
- Social preview image set
- Page language declared
- At most one redirect to the homepage
Not measured 1
- Static files cached for 30 days or more
Own rpp.pe?
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: rpp.pe. This profile covers configuration only.