Website readiness profile · Snapshot 23 October 2026
qcc.com
qcc.com's public homepage, certificate and DNS checked against 31 practices and compared with 233 Data & Analytics sites.
- Readiness index
- 56/100
- Ahead of
- 27%
- Practices observed
- 15/31
- Popularity band
- Top 50K
Data & Analytics median 63
of measured Data & Analytics sites
0 of 31 could not be measured
Chrome UX Report top-sites list
Readiness by lane
Green: qcc.com. Thin bar: Data & Analytics peer median.
Enable
67/100
Peers 78
Harden
55/100
Peers 56
Accelerate
50/100
Peers 63
Recover
0/100
Peers 8
Priority fixes for qcc.com
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 no max-age, 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.
49% of Data & Analytics 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: Strict-Transport-Security was sent with a max-age of 180 days, below the one-year benchmark.
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 Data & Analytics 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.
63% of Data & Analytics peers do this.
Guide: XML Sitemap Guide: Include Only URLs You Stand Behind
Priority 4 · Harden
DMARC policy enforces quarantine or reject
Observed: No DMARC record was found at _dmarc.qcc.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.
38% of Data & Analytics peers do this.
What qcc.com already does well
Practices fewer than half of Data & Analytics peers use.
- Content Security Policy presentContent-Security-Policy present.24% of peers
- X-Content-Type-Options: nosniffnosniff header present.46% of peers
What we saw
- Homepage checked
- https://www.qcc.com/
- Homepage response
- HTTP 200
- TLS
- TLSv1.3, HTTP/2
- Certificate
- DigiCert, 394-day validity, expiring 2027-02-25
- CDN or edge
- Alibaba Cloud CDN
- DNS operators
- Alibaba Cloud DNS
- HSTS
- max-age 180 days, includeSubDomains
- Homepage HTML
- 38 KB, gzip
- Images on homepage
- 28 (svg 17, png 9, gif 2)
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
- HSTS kept for at least a year
- 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
- Referrer-Policy set
- HTTP/3 advertised
- Static files cached for 30 days or more
- Modern image formats in use
- Offscreen images lazy-loaded
- XML sitemap discoverable
- Reachable over IPv6
- Structured data present
- Social preview image set
- Nameservers spread across providers
Observed 15
- HTTP requests move to HTTPS
- TLS 1.3 negotiated
- Certificate has more than 14 days left
- X-Content-Type-Options: nosniff
- Framing restricted
- Content Security Policy present
- HTTP/2 negotiated
- HTML compressed
- 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
Own qcc.com?
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: qcc.com. This profile covers configuration only.