whitepages.com

Readiness by lane

Green: whitepages.com. Thin bar: Web Tools peer median.

Priority fixes for whitepages.com

Ordered by impact and by how common each practice is among peers.

1. Priority 1 · Accelerate

   Static files cached for 30 days or more

   Observed: A same-site stylesheet or script was cacheable for 1 days, 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.

   On Cloudflare: Use Cache Rules to set edge and browser TTLs for static file paths.

   54% of Web Tools peers do this. Limit: Read from the homepage response only; other pages or regions may send different headers.

   Guide: Browser Caching Guide for Website Owners

2. Priority 2 · Accelerate

   No render-blocking scripts in <head>

   Observed: The homepage <head> loaded 1 external script without async or defer.

   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.

   69% of Web Tools peers do this.

   Guide: Control Third-Party Scripts Before They Control Your Page

3. Priority 3 · Harden

   HSTS kept for at least a year

   Observed: The homepage response did not include a Strict-Transport-Security header.

   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.

   On Cloudflare: Enable HSTS under SSL/TLS > Edge Certificates > HTTP Strict Transport Security and raise max-age gradually.

   30% of Web Tools peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

4. Priority 4 · Harden

   Framing restricted

   Observed: The homepage did not send frame-ancestors or X-Frame-Options, so other sites may frame it.

   What to do: Send Content-Security-Policy: frame-ancestors 'self' (or a list of trusted origins). X-Frame-Options: SAMEORIGIN covers older browsers.

   On Cloudflare: Add the header with a response header transform rule.

   48% of Web Tools peers do this.

   Guide: A Practical Website Health Check for Owners

What whitepages.com already does well

Practices fewer than half of Web Tools peers use.

• DMARC policy enforces quarantine or rejectDMARC policy p=quarantine.23% of peers
• Modern image formats in useWebP or AVIF images detected.37% of peers

What we saw

Homepage checked

https://www.whitepages.com/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

Google Trust Services, 90-day validity, expiring 2026-12-30

CDN or edge

Cloudflare

DNS operators

Amazon Route 53

DMARC policy

p=quarantine

Homepage HTML

372 KB, br

Images on homepage

25 (svg 15, png 9, webp 1)

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

Compare with other Web Tools sites

• 19216811.onl69
• qrfy.com69
• snapsave.io70
• ssstiktok.gold70
• twittervideodownloader.com70

Web Tools readiness benchmark