Website readiness profile · Snapshot 23 October 2026
railway.com
railway.com's public homepage, certificate and DNS checked against 31 practices and compared with 23 Web & Cloud Hosting sites.
- Readiness index
- 73/100
- Ahead of
- 70%
- Practices observed
- 21/31
- Popularity band
- Top 50K
Web & Cloud Hosting median 68
of measured Web & Cloud Hosting sites
0 of 31 could not be measured
Chrome UX Report top-sites list
Readiness by lane
Green: railway.com. Thin bar: Web & Cloud Hosting peer median.
Enable
95/100
Peers 80
Harden
65/100
Peers 60
Accelerate
70/100
Peers 66
Recover
0/100
Peers 9
Priority fixes for railway.com
Ordered by impact and by how common each practice is among peers.
Priority 1 · Accelerate
HTML compressed
Observed: The homepage HTML (221 KB) was delivered without gzip, Brotli or zstd compression.
Why it matters: Compression usually shrinks HTML several times over, so the first bytes of the page arrive sooner on slow connections.
What to do: Enable Brotli or gzip for text responses (HTML, CSS, JavaScript, JSON, SVG) at the CDN or origin.
On Cloudflare: Cloudflare compresses eligible responses; check compression rules if HTML arrives uncompressed.
91% of Web & Cloud Hosting peers do this. Limit: Read from the homepage response only; other pages or regions may send different headers.
Guide: How to Set a Website Performance Budget That Teams Can Keep
Priority 2 · 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.
43% of Web & Cloud Hosting 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.
On Cloudflare: Enable HTTP/3 (with QUIC) under Speed > Optimization > Protocol Optimization.
39% of Web & Cloud Hosting peers do this.
Priority 4 · Harden
CAA records limit who can issue certificates
Observed: No CAA record was found for railway.com, so any public certificate authority may issue for it.
What to do: Publish CAA records naming every CA you actually use, including the CAs your CDN uses for managed certificates. Add an iodef contact if you want reports.
On Cloudflare: Cloudflare documents which CAs its managed certificates need; include them in your CAA records.
30% of Web & Cloud Hosting peers do this.
What railway.com already does well
Practices fewer than half of Web & Cloud Hosting peers use.
- Content Security Policy presentContent-Security-Policy present.22% of peers
- Framing restrictedFraming controls present.43% of peers
- Modern image formats in useWebP or AVIF images detected.47% of peers
What we saw
- Homepage checked
- https://railway.com/
- Homepage response
- HTTP 200
- TLS
- TLSv1.3, HTTP/2
- Certificate
- Let's Encrypt, 89-day validity, expiring 2027-01-12
- DNS operators
- Cloudflare
- DMARC policy
- p=quarantine
- Homepage HTML
- 221 KB, uncompressed
- Images on homepage
- 60 (svg 35, webp 31)
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 21
- HTTP requests move to HTTPS
- 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
- Content Security Policy present
- HTTP/2 negotiated
- 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
- Structured data present
- Social preview image set
- Page language declared
- At most one redirect to the homepage
Own railway.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: railway.com. This profile covers configuration only.