Website readiness profile · Snapshot 23 October 2026
cuttty.com
cuttty.com's public homepage, certificate and DNS checked against 31 practices and compared with 492 Web Tools sites.
- Readiness index
- 71/100
- Ahead of
- 65%
- Practices observed
- 19/29
- Popularity band
- Top 10K
Web Tools median 67
of measured Web Tools sites
2 of 31 could not be measured
Chrome UX Report top-sites list
Readiness by lane
Green: cuttty.com. Thin bar: Web Tools peer median.
Enable
79/100
Peers 84
Harden
69/100
Peers 55
Accelerate
71/100
Peers 69
Recover
0/100
Peers 6
Priority fixes for cuttty.com
Ordered by impact and by how common each practice is among peers.
Priority 1 · Enable
XML sitemap discoverable
Observed: No sitemap was listed in robots.txt or found at /sitemap.xml.
Why it matters: A sitemap helps search engines find new and updated pages, especially on large or frequently updated sites.
What to do: Generate an XML sitemap of canonical URLs, reference it in robots.txt and submit it in Google Search Console.
73% of Web Tools peers do this. Limit: Only the standard location was requested, once, at the time of the check.
Guide: XML Sitemap Guide: Include Only URLs You Stand Behind
Priority 2 · Accelerate
Modern image formats in use
Observed: The homepage had 32 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.
On Cloudflare: Cloudflare Polish can convert images to WebP.
37% of Web Tools peers do this.
Guide: AVIF, WebP, JPEG, and PNG: Choose the Right Image Format
Priority 3 · Harden
DMARC policy enforces quarantine or reject
Observed: No DMARC record was found at _dmarc.cuttty.com.
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.
23% of Web Tools peers do this.
Priority 4 · Accelerate
Offscreen images lazy-loaded
Observed: The homepage had 32 images and none used loading="lazy".
What to do: Add loading="lazy" to images below the fold. Do not lazy-load the main hero image, because that delays the largest visible element.
59% of Web Tools peers do this.
What cuttty.com already does well
Practices fewer than half of Web Tools peers use.
- HSTS kept for at least a yearHSTS with a 365-day max-age.30% of peers
- X-Content-Type-Options: nosniffnosniff header present.44% of peers
- Framing restrictedFraming controls present.48% of peers
What we saw
- Homepage checked
- https://cuttty.com/
- Homepage response
- HTTP 200, after 1 redirect
- TLS
- TLSv1.3, HTTP/2
- Certificate
- Google Trust Services, 90-day validity, expiring 2027-01-08
- CDN or edge
- Cloudflare
- DNS operators
- Cloudflare
- HSTS
- max-age 365 days
- Homepage HTML
- 50 KB, br
- Images on homepage
- 32 (png 17, svg 11, jpg 4)
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 19
- HTTP requests move to HTTPS
- HSTS kept for at least a year
- TLS 1.3 negotiated
- Certificate has more than 14 days left
- Certificate lifetime of 100 days or less
- X-Content-Type-Options: nosniff
- Framing restricted
- HTTP/2 negotiated
- HTTP/3 advertised
- HTML compressed
- No render-blocking scripts in <head>
- robots.txt published
- Reachable over IPv6
- Canonical URL declared
- Meta description written
- Mobile viewport configured
- Social preview image set
- Page language declared
- At most one redirect to the homepage
Not measured 2
- security.txt published
- Static files cached for 30 days or more
Own cuttty.com?
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: cuttty.com. This profile covers configuration only.