Stack playbook · Snapshot 23 October 2026
Angular: readiness playbook
What 192 measured sites on this platform or framework get right, where they fall short, and the Angular-specific steps that close each gap.
- Sites measured
- 192
- Median readiness index
- 71/100
- Profiles on this stack
- 117
detected from homepage HTML and headers
all sites: 64
top-50K sites
Readiness by lane
Enable
86/100
All sites 77
Harden
60/100
All sites 56
Accelerate
72/100
All sites 64
Recover
14/100
All sites 10
The Angular playbook
Gaps ordered by impact, with the platform-specific step where one exists.
security.txt published
7.4% observed · all sites 7.1%
Publish /.well-known/security.txt with at least Contact and Expires fields, as RFC 9116 requires, and review it before it expires.
HSTS kept for at least a year
50% observed · all sites 34%
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.
CAA records limit who can issue certificates
16% observed · all sites 13%
Publish CAA records naming every CA you actually use, including the CAs your CDN uses for managed certificates. Add an iodef contact if you want reports.
HTTP/3 advertised
28% observed · all sites 37%
Turn on HTTP/3 at your CDN. Browsers fall back to HTTP/2 automatically, so the risk is low.
DMARC policy enforces quarantine or reject
52% observed · all sites 39%
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.
DNSSEC signed
7.8% observed · all sites 8%
Enable DNSSEC at your DNS provider, then add the DS record at your registrar. Plan provider moves carefully: a stale DS record can make the domain fail to resolve.
Guide: Website Uptime Readiness: Prepare Before Traffic Arrives
Content Security Policy present
35% observed · all sites 32%
Start with Content-Security-Policy-Report-Only to see what would break, tighten the policy over a few weeks, then enforce it.
Guide: Payment Security and PCI DSS: What Website Owners Need to Know
Modern image formats in use
58% observed · all sites 40%
Serve WebP or AVIF with a JPEG or PNG fallback, either through an image CDN or by generating both formats at build time.
Guide: AVIF, WebP, JPEG, and PNG: Choose the Right Image Format
Where Angular sites lead
- No render-blocking scripts in <head>72% observedall sites 48%
- Offscreen images lazy-loaded81% observedall sites 62%
- Modern image formats in use58% observedall sites 40%
- HSTS kept for at least a year50% observedall sites 34%