Website readiness profile · Snapshot 23 October 2026
mirage.ru
mirage.ru's public homepage, certificate and DNS checked against 31 practices and compared with 387 Events & Online Ticketing sites.
- Readiness index
- 57/100
- Ahead of
- 30%
- Practices observed
- 15/31
- Popularity band
- Top 50K
Events & Online Ticketing median 63
of measured Events & Online Ticketing sites
0 of 31 could not be measured
Chrome UX Report top-sites list
Readiness by lane
Green: mirage.ru. Thin bar: Events & Online Ticketing peer median.
Enable
77/100
Peers 78
Harden
49/100
Peers 57
Accelerate
48/100
Peers 59
Recover
100/100
Peers 7
Priority fixes for mirage.ru
Ordered by impact and by how common each practice is among peers.
Priority 1 · Accelerate
HTTP/2 negotiated
Observed: The TLS handshake selected http/1.1 instead of HTTP/2.
Why it matters: HTTP/2 sends many files over one connection, which speeds up pages with lots of images, styles and scripts.
What to do: Enable HTTP/2 on your CDN or server. Most CDNs do this by default.
90% of Events & Online Ticketing peers do this. Limit: Certificate and protocol were observed from one vantage point; CDNs can present different certificates by region.
Priority 2 · Harden
DMARC policy enforces quarantine or reject
Observed: The DMARC policy for mirage.ru was p=none, which asks receivers to take no action on failing mail.
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.
44% of Events & Online Ticketing peers do this.
Priority 3 · Accelerate
Modern image formats in use
Observed: The homepage had 65 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.
42% of Events & Online Ticketing peers do this.
Guide: AVIF, WebP, JPEG, and PNG: Choose the Right Image Format
Priority 4 · 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.
65% of Events & Online Ticketing peers do this.
What mirage.ru already does well
Practices fewer than half of Events & Online Ticketing peers use.
- Nameservers spread across providersNameservers spread across more than one operator.7.2% of peers
- No render-blocking scripts in <head>Head scripts load without blocking.35% of peers
- HSTS kept for at least a yearHSTS with a 365-day max-age.42% of peers
What we saw
- Homepage checked
- https://www.mirage.ru/
- Homepage response
- HTTP 200
- TLS
- TLSv1.3, http/1.1
- Certificate
- GlobalSign, 396-day validity, expiring 2026-12-25
- DNS operators
- 2 self-run or other nameserver domains
- HSTS
- max-age 365 days
- DMARC policy
- p=none
- Homepage HTML
- 105 KB, gzip
- Images on homepage
- 65 (jpg 60, svg 3)
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 16
- Certificate lifetime of 100 days or less
- CAA records limit who can issue certificates
- 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
- HTTP/2 negotiated
- HTTP/3 advertised
- Modern image formats in use
- Offscreen images lazy-loaded
- Reachable over IPv6
- Canonical URL declared
- Structured data present
Observed 15
- HTTP requests move to HTTPS
- HSTS kept for at least a year
- TLS 1.3 negotiated
- Certificate has more than 14 days left
- HTML compressed
- Static files cached for 30 days or more
- No render-blocking scripts in <head>
- robots.txt published
- XML sitemap discoverable
- Meta description written
- Mobile viewport configured
- Social preview image set
- Page language declared
- At most one redirect to the homepage
- Nameservers spread across providers
Own mirage.ru?
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: mirage.ru. This profile covers configuration only.