Website readiness profile · Snapshot 23 October 2026
mobiles24.co
mobiles24.co's public homepage, certificate and DNS checked against 31 practices and compared with 343 Uncategorized sites.
- Readiness index
- 49/100
- Ahead of
- 17%
- Practices observed
- 13/30
- Popularity band
- Top 50K
Uncategorized median 62
of measured Uncategorized sites
1 of 31 could not be measured
Chrome UX Report top-sites list
Readiness by lane
Green: mobiles24.co. Thin bar: Uncategorized peer median.
Enable
67/100
Peers 80
Harden
33/100
Peers 54
Accelerate
58/100
Peers 58
Recover
0/100
Peers 12
Priority fixes for mobiles24.co
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.
87% of Uncategorized peers do this. Limit: Certificate and protocol were observed from one vantage point; CDNs can present different certificates by region.
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.
75% of Uncategorized peers do this.
Guide: XML Sitemap Guide: Include Only URLs You Stand Behind
Priority 3 · 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.
Priority 4 · Accelerate
Static files cached for 30 days or more
Observed: A same-site stylesheet or script was cacheable for no max-age, short of the 30-day benchmark.
What to do: Give versioned (fingerprinted) CSS, JavaScript, fonts and images Cache-Control: public, max-age=31536000, immutable, and change the file name whenever the content changes.
44% of Uncategorized peers do this.
What mobiles24.co already does well
Practices fewer than half of Uncategorized peers use.
- Modern image formats in useWebP or AVIF images detected.33% of peers
- No render-blocking scripts in <head>Head scripts load without blocking.37% of peers
What we saw
- Homepage checked
- https://www.mobiles24.co/
- Homepage response
- HTTP 200
- TLS
- TLSv1.3, http/1.1
- Certificate
- Let's Encrypt, 89-day validity, expiring 2026-11-30
- DNS operators
- 1 self-run or other nameserver domain
- Homepage HTML
- 82 KB, gzip
- Images on homepage
- 43 (png 16, jpg 8, webp 8, gif 8, 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 17
- HSTS kept for at least a year
- 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
- Static files cached for 30 days or more
- XML sitemap discoverable
- Reachable over IPv6
- Structured data present
- Social preview image set
- Nameservers spread across providers
Observed 13
- TLS 1.3 negotiated
- Certificate has more than 14 days left
- Certificate lifetime of 100 days or less
- HTML compressed
- Modern image formats in use
- Offscreen images lazy-loaded
- No render-blocking scripts in <head>
- robots.txt published
- Canonical URL declared
- Meta description written
- Mobile viewport configured
- Page language declared
- At most one redirect to the homepage
Not measured 1
- HTTP requests move to HTTPS
Own mobiles24.co?
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: mobiles24.co. This profile covers configuration only.