Website readiness profile · Snapshot 23 October 2026
quackquack.in
quackquack.in's public homepage, certificate and DNS checked against 31 practices and compared with 218 Dating Apps sites.
- Readiness index
- 72/100
- Ahead of
- 82%
- Practices observed
- 20/30
- Popularity band
- Top 50K
Dating Apps median 58
of measured Dating Apps sites
1 of 31 could not be measured
Chrome UX Report top-sites list
Readiness by lane
Green: quackquack.in. Thin bar: Dating Apps peer median.
Enable
95/100
Peers 71
Harden
69/100
Peers 52
Accelerate
56/100
Peers 53
Recover
0/100
Peers 7
Priority fixes for quackquack.in
Ordered by impact and by how common each practice is among peers.
Priority 1 · Accelerate
HTTP/2 negotiated
Observed: The TLS handshake selected HTTP/1.1 instead of HTTP/2.
Why it matters: HTTP/2 sends many files over one connection, which speeds up pages with lots of images, styles and scripts.
What to do: Enable HTTP/2 on your CDN or server. Most CDNs do this by default.
83% of Dating Apps peers do this. Limit: Certificate and protocol were observed from one vantage point; CDNs can present different certificates by region.
Priority 2 · Harden
TLS 1.3 negotiated
Observed: The TLS connection negotiated TLSv1.2.
What to do: Enable TLS 1.3 on your CDN or server. Keep TLS 1.2 available for older clients unless you have checked your audience.
82% of Dating Apps 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.
64% of Dating Apps peers do this.
Priority 4 · Accelerate
Offscreen images lazy-loaded
Observed: The homepage had 9 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.
31% of Dating Apps peers do this.
What quackquack.in already does well
Practices fewer than half of Dating Apps peers use.
- Referrer-Policy setReferrer-Policy present.17% of peers
- HSTS kept for at least a yearHSTS with a 365-day max-age covering subdomains.22% of peers
- Content Security Policy presentContent-Security-Policy present.23% of peers
What we saw
- Homepage checked
- https://www.quackquack.in/
- Homepage response
- HTTP 200
- TLS
- TLSv1.2
- Certificate
- Amazon, 197-day validity, expiring 2027-04-19
- DNS operators
- Amazon Route 53
- HSTS
- max-age 365 days, includeSubDomains, preload
- DMARC policy
- p=quarantine
- Homepage HTML
- 128 KB, gzip
- Images on homepage
- 9 (jpg 3, webp 2, png 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 10
Observed 20
- HTTP requests move to HTTPS
- HSTS kept for at least a year
- Certificate has more than 14 days left
- DMARC policy enforces quarantine or reject
- X-Content-Type-Options: nosniff
- Framing restricted
- Content Security Policy present
- Referrer-Policy set
- HTML compressed
- Modern image formats in use
- No render-blocking scripts in <head>
- robots.txt published
- XML sitemap discoverable
- 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
Not measured 1
- Static files cached for 30 days or more
Own quackquack.in?
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: quackquack.in. This profile covers configuration only.