Website readiness profile · Snapshot 23 October 2026
kosmo.com.my
kosmo.com.my's public homepage, certificate and DNS checked against 31 practices and compared with 3,856 News & Media sites.
- Readiness index
- 66/100
- Ahead of
- 40%
- Practices observed
- 19/31
- Popularity band
- Top 10K
News & Media median 68
of measured News & Media sites
0 of 31 could not be measured
Chrome UX Report top-sites list
Readiness by lane
Green: kosmo.com.my. Thin bar: News & Media peer median.
Enable
100/100
Peers 89
Harden
43/100
Peers 56
Accelerate
73/100
Peers 68
Recover
0/100
Peers 11
Priority fixes for kosmo.com.my
Ordered by impact and by how common each practice is among peers.
Priority 1 · Accelerate
Static files cached for 30 days or more
Observed: A same-site stylesheet or script was cacheable for 4 hours, short of the 30-day benchmark.
Why it matters: Returning visitors and later page views reuse cached files instead of downloading them again.
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.
On Cloudflare: Use Cache Rules to set edge and browser TTLs for static file paths.
60% of News & Media peers do this. Limit: Read from the homepage response only; other pages or regions may send different headers.
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.
35% of News & Media peers do this.
Priority 3 · Harden
DMARC policy enforces quarantine or reject
Observed: The DMARC policy for kosmo.com.my 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.
37% of News & Media peers do this.
Priority 4 · Accelerate
No render-blocking scripts in <head>
Observed: The homepage <head> loaded 19 external scripts 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 WordPress: Since WordPress 6.3, scripts can be registered with a defer or async loading strategy.
42% of News & Media peers do this.
Guide: Control Third-Party Scripts Before They Control Your Page
What kosmo.com.my already does well
Practices fewer than half of News & Media peers use.
- HTTP/3 advertisedHTTP/3 advertised.36% of peers
- Modern image formats in useWebP or AVIF images detected.44% of peers
What we saw
- Homepage checked
- https://www.kosmo.com.my/
- Homepage response
- HTTP 200
- TLS
- TLSv1.3, HTTP/2
- Certificate
- Google Trust Services, 90-day validity, expiring 2026-12-03
- CDN or edge
- Cloudflare
- Platform or framework
- WordPress
- DNS operators
- Cloudflare
- DMARC policy
- p=none
- Homepage HTML
- 816 KB, br
- Images on homepage
- 65 (jpg 143, png 59, webp 7)
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 12
- 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
- Static files cached for 30 days or more
- No render-blocking scripts in <head>
- Nameservers spread across providers
Observed 19
- HTTP requests move to HTTPS
- TLS 1.3 negotiated
- Certificate has more than 14 days left
- Certificate lifetime of 100 days or less
- HTTP/2 negotiated
- HTTP/3 advertised
- HTML compressed
- Modern image formats in use
- Offscreen images lazy-loaded
- robots.txt published
- XML sitemap discoverable
- Reachable over IPv6
- 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 kosmo.com.my?
Re-run the checks after a change, keep a private action plan in a free workspace, or report a mistake.
Live status for this site: Status Is Down: kosmo.com.my. This profile covers configuration only.