Website readiness profile · Snapshot 23 October 2026
megalotto.pl
megalotto.pl's public homepage, certificate and DNS checked against 31 practices and compared with 343 Uncategorized sites.
- Readiness index
- 43/100
- Ahead of
- 6.7%
- Practices observed
- 12/31
- Popularity band
- Top 50K
Uncategorized median 62
of measured Uncategorized sites
0 of 31 could not be measured
Chrome UX Report top-sites list
Readiness by lane
Green: megalotto.pl. Thin bar: Uncategorized peer median.
Enable
56/100
Peers 80
Harden
52/100
Peers 54
Accelerate
13/100
Peers 58
Recover
100/100
Peers 12
Priority fixes for megalotto.pl
Ordered by impact and by how common each practice is among peers.
Priority 1 · Accelerate
HTML compressed
Observed: The homepage HTML (80 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.
92% of Uncategorized 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 · Accelerate
HTTP/2 negotiated
Observed: The TLS handshake selected http/1.1 instead of HTTP/2.
What to do: Enable HTTP/2 on your CDN or server. Most CDNs do this by default.
87% of Uncategorized peers do this.
Priority 3 · 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.
75% of Uncategorized peers do this.
Guide: XML Sitemap Guide: Include Only URLs You Stand Behind
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.
34% of Uncategorized peers do this.
What megalotto.pl already does well
Practices fewer than half of Uncategorized peers use.
- Nameservers spread across providersNameservers spread across more than one operator.12% of peers
- No render-blocking scripts in <head>Head scripts load without blocking.37% of peers
- DMARC policy enforces quarantine or rejectDMARC policy p=reject.39% of peers
What we saw
- Homepage checked
- https://megalotto.pl/
- Homepage response
- HTTP 200
- TLS
- TLSv1.3, http/1.1
- Certificate
- Let's Encrypt, 89-day validity, expiring 2027-01-03
- DNS operators
- OVHcloud DNS, plus 1 self-run or other nameserver domain
- DMARC policy
- p=reject
- Homepage HTML
- 80 KB, uncompressed
- Images on homepage
- 8 (png 8)
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 19
- HSTS kept for at least a year
- CAA records limit who can issue certificates
- DNSSEC signed
- security.txt published
- X-Content-Type-Options: nosniff
- Framing restricted
- Content Security Policy present
- Referrer-Policy set
- 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
- XML sitemap discoverable
- Reachable over IPv6
- Canonical URL declared
- Structured data present
- Social preview image set
Observed 12
- 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
- No render-blocking scripts in <head>
- robots.txt published
- Meta description written
- Mobile viewport configured
- Page language declared
- At most one redirect to the homepage
- Nameservers spread across providers
Own megalotto.pl?
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: megalotto.pl. This profile covers configuration only.