Website readiness profile · Snapshot 23 October 2026
rodaemotor.com
rodaemotor.com's public homepage, certificate and DNS checked against 31 practices and compared with 492 Web Tools sites.
- Readiness index
- 55/100
- Ahead of
- 14%
- Practices observed
- 16/31
- Popularity band
- Top 50K
Web Tools median 67
of measured Web Tools sites
0 of 31 could not be measured
Chrome UX Report top-sites list
Readiness by lane
Green: rodaemotor.com. Thin bar: Web Tools peer median.
Enable
62/100
Peers 84
Harden
34/100
Peers 55
Accelerate
88/100
Peers 69
Recover
0/100
Peers 6
Priority fixes for rodaemotor.com
Ordered by impact and by how common each practice is among peers.
Priority 1 · Harden
HTTP requests move to HTTPS
Observed: A request to http://rodaemotor.com/ was not redirected to HTTPS.
Why it matters: Visitors who type the address or follow an old link start on unencrypted HTTP. A redirect moves them to the encrypted site before any cookies or form data are sent.
What to do: Add a permanent (301 or 308) redirect from every http:// URL to the same https:// URL at your CDN, load balancer or web server.
On Cloudflare: Turn on Always Use HTTPS under SSL/TLS > Edge Certificates.
94% of Web Tools peers do this. Limit: Measured for the homepage only, from one location, at the time of the check.
Priority 2 · 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.
Guide: XML Sitemap Guide: Include Only URLs You Stand Behind
Priority 3 · Accelerate
No render-blocking scripts in <head>
Observed: The homepage <head> loaded 1 external script 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 Next.js: Use the next/script component with an appropriate loading strategy.
69% of Web Tools peers do this.
Guide: Control Third-Party Scripts Before They Control Your Page
Priority 4 · Harden
HSTS kept for at least a year
Observed: The homepage response did not include a Strict-Transport-Security header.
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.
30% of Web Tools peers do this.
What rodaemotor.com already does well
Practices fewer than half of Web Tools peers use.
- CAA records limit who can issue certificatesCAA limits issuance to comodoca.com, digicert.com, globalsign.com and others.14% of peers
- Modern image formats in useWebP or AVIF images detected.37% of peers
What we saw
- Homepage checked
- https://rodaemotor.com/
- Homepage response
- HTTP 200
- TLS
- TLSv1.3, HTTP/2
- Certificate
- Google Trust Services, 90-day validity, expiring 2027-01-21
- CDN or edge
- Cloudflare
- Platform or framework
- Next.js
- DNS operators
- Cloudflare
- DMARC policy
- p=none
- Homepage HTML
- 102 KB, br
- Images on homepage
- 27 (webp 27)
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 15
- HTTP requests move to HTTPS
- HSTS kept for at least a year
- DNSSEC signed
- security.txt published
- DMARC policy enforces quarantine or reject
- X-Content-Type-Options: nosniff
- Framing restricted
- Content Security Policy present
- Referrer-Policy set
- No render-blocking scripts in <head>
- XML sitemap discoverable
- Canonical URL declared
- Structured data present
- Social preview image set
- Nameservers spread across providers
Observed 16
- TLS 1.3 negotiated
- Certificate has more than 14 days left
- Certificate lifetime of 100 days or less
- CAA records limit who can issue certificates
- HTTP/2 negotiated
- HTTP/3 advertised
- HTML compressed
- Static files cached for 30 days or more
- Modern image formats in use
- Offscreen images lazy-loaded
- robots.txt published
- Reachable over IPv6
- Meta description written
- Mobile viewport configured
- Page language declared
- At most one redirect to the homepage
Own rodaemotor.com?
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: rodaemotor.com. This profile covers configuration only.