whatsapp.com

Readiness by lane

Green: whatsapp.com. Thin bar: Social Media & Networking peer median.

Priority fixes for whatsapp.com

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

1. Priority 1 · Harden

   Certificate has more than 14 days left

   Observed: The certificate from DigiCert Inc was due to expire on 2026-10-30 (7 days after the check).

   Why it matters: An expired certificate makes browsers show a full-page warning. Renewing well ahead of expiry leaves time to fix a failed renewal.

   What to do: Automate renewal with ACME (for example Let's Encrypt or your CDN's managed certificates) and add a renewal review to your release calendar so any certificate inside 21 days of expiry gets attention.

   96% of Social Media & Networking peers do this. Limit: Certificate and protocol were observed from one vantage point; CDNs can present different certificates by region.

   Guide: HTTPS and TLS 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.

   54% of Social Media & Networking peers do this.

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

3. Priority 3 · Accelerate

   Modern image formats in use

   Observed: The homepage had 22 images and none used WebP or AVIF.

   What to do: Serve WebP or AVIF with a JPEG or PNG fallback, either through an image CDN or by generating both formats at build time.

   34% of Social Media & Networking peers do this.

   Guide: AVIF, WebP, JPEG, and PNG: Choose the Right Image Format

4. Priority 4 · Accelerate

   Offscreen images lazy-loaded

   Observed: The homepage had 22 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.

   47% of Social Media & Networking peers do this.

   Guide: Lazy Loading Without Broken Pages

What whatsapp.com already does well

Practices fewer than half of Social Media & Networking peers use.

• CAA records limit who can issue certificatesCAA limits issuance to digicert.com.11% of peers
• security.txt publishedsecurity.txt with a contact found.13% of peers
• Content Security Policy presentContent-Security-Policy present.28% of peers

What we saw

Homepage checked

https://www.whatsapp.com/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

DigiCert, 90-day validity, expiring 2026-10-30

DNS operators

1 self-run or other nameserver domain

HSTS

max-age 365 days, includeSubDomains, preload

DMARC policy

p=reject

Homepage HTML

285 KB, br

Images on homepage

22 (png 96, svg 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

Compare with other Social Media & Networking sites

• band.us73
• monkey.app72
• omar-thing.site72
• sharechat.com73
• snap.com73

Social Media & Networking readiness benchmark