wordpress.org

Readiness by lane

Green: wordpress.org. Thin bar: Website Builders peer median.

Priority fixes for wordpress.org

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

1. Priority 1 · Harden

   HSTS kept for at least a year

   Observed: Strict-Transport-Security was sent with a max-age of 0 days, below the one-year benchmark.

   Why it matters: HSTS tells browsers to use HTTPS for your host on every later visit, which removes the window where a first HTTP request can be intercepted.

   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.

   26% of Website Builders peers do this. Limit: Read from the homepage response only; other pages or regions may send different headers.

   Guide: HTTPS and TLS Guide for Website Owners

2. Priority 2 · Accelerate

   Offscreen images lazy-loaded

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

   On WordPress: WordPress has added loading="lazy" to images by default since 5.5; check that your theme or a plugin has not removed it.

   61% of Website Builders peers do this.

   Guide: Lazy Loading Without Broken Pages

3. Priority 3 · Accelerate

   HTTP/3 advertised

   Observed: The homepage did not advertise HTTP/3 through an Alt-Svc header.

   What to do: Turn on HTTP/3 at your CDN. Browsers fall back to HTTP/2 automatically, so the risk is low.

   29% of Website Builders peers do this.

   Guide: CDN Guide for Website Owners

4. Priority 4 · Harden

   Content Security Policy present

   Observed: The homepage response did not include a Content-Security-Policy header.

   What to do: Start with Content-Security-Policy-Report-Only to see what would break, tighten the policy over a few weeks, then enforce it.

   26% of Website Builders peers do this.

   Guide: Payment Security and PCI DSS: What Website Owners Need to Know

What wordpress.org already does well

Practices fewer than half of Website Builders peers use.

• CAA records limit who can issue certificatesCAA limits issuance to letsencrypt.org.16% of peers
• security.txt publishedsecurity.txt with a contact found.16% of peers
• Reachable over IPv6IPv6 address published.26% of peers

What we saw

Homepage checked

https://wordpress.org/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

Let's Encrypt, 89-day validity, expiring 2026-12-22

Platform or framework

WordPress

DNS operators

1 self-run or other nameserver domain

HSTS

max-age 0 days

DMARC policy

p=reject

Homepage HTML

174 KB, br

Images on homepage

16 (png 57, webp 7)

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 Website Builders sites

• bolt.new79
• framer.com88
• msha.ke86
• webflow.com82
• webnode.com79

Website Builders readiness benchmark