Website readiness profile · Snapshot 23 October 2026
bit.ly
bit.ly's public homepage, certificate and DNS checked against 31 practices and compared with 492 Web Tools sites.
- Readiness index
- 76/100
- Ahead of
- 77%
- Practices observed
- 20/29
- Popularity band
- Top 1K
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: bit.ly. Thin bar: Web Tools peer median.
Enable
94/100
Peers 84
Harden
62/100
Peers 55
Accelerate
85/100
Peers 69
Recover
100/100
Peers 6
Priority fixes for bit.ly
Ordered by impact and by how common each practice is among peers.
Priority 1 · Accelerate
No render-blocking scripts in <head>
Observed: The homepage <head> loaded 1 external script without async or defer.
Why it matters: A plain <script src> in the head stops the browser from showing anything until that file has downloaded and run.
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.
69% of Web Tools peers do this. Limit: Based on the homepage HTML delivered to an automated client; scripts that run later were not executed.
Guide: Control Third-Party Scripts Before They Control Your Page
Priority 2 · Harden
DMARC policy enforces quarantine or reject
Observed: The DMARC policy for bit.ly 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.
23% of Web Tools peers do this.
Priority 3 · Harden
Certificate lifetime of 100 days or less
Observed: The certificate from Amazon had a 197-day validity period, longer than the 100-day maximum that applies from March 2027.
What to do: Move to automated issuance and renewal now, while you still have time to test it.
87% of Web Tools peers do this.
Priority 4 · Harden
X-Content-Type-Options: nosniff
Observed: The homepage response did not include X-Content-Type-Options: nosniff.
What to do: Send X-Content-Type-Options: nosniff on all responses and make sure each file is served with the correct Content-Type.
44% of Web Tools peers do this.
What bit.ly already does well
Practices fewer than half of Web Tools peers use.
- Nameservers spread across providersNameservers spread across Amazon Route 53 and Google Cloud DNS.6.1% of peers
- CAA records limit who can issue certificatesCAA limits issuance to amazon.com.14% of peers
- HSTS kept for at least a yearHSTS with a 365-day max-age.30% of peers
What we saw
- Homepage checked
- https://bit.ly/
- Homepage response
- HTTP 200, after 1 redirect
- TLS
- TLSv1.3, HTTP/2
- Certificate
- Amazon, 197-day validity, expiring 2027-02-09
- CDN or edge
- Google edge
- Platform or framework
- WordPress
- DNS operators
- Amazon Route 53, Google Cloud DNS
- HSTS
- max-age 365 days
- DMARC policy
- p=none
- Homepage HTML
- 304 KB, br
- Images on homepage
- 40 (webp 43, svg 13, png 6, 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 9
Observed 20
- HTTP requests move to HTTPS
- HSTS kept for at least a year
- TLS 1.3 negotiated
- Certificate has more than 14 days left
- CAA records limit who can issue certificates
- Framing restricted
- HTTP/2 negotiated
- HTTP/3 advertised
- HTML compressed
- Modern image formats in use
- Offscreen images lazy-loaded
- robots.txt published
- 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
- Nameservers spread across providers
Not measured 2
- Static files cached for 30 days or more
- XML sitemap discoverable
Own bit.ly?
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: bit.ly. This profile covers configuration only.