STATUS IS UPREADINESS PROFILE

Website readiness profile · Snapshot 23 October 2026

gptzero.me

gptzero.me's public homepage, certificate and DNS checked against 31 practices and compared with 492 Web Tools sites.

Readiness index
76/100

Web Tools median 67

Ahead of
77%

of measured Web Tools sites

Practices observed
22/30

1 of 31 could not be measured

Popularity band
Top 50K

Chrome UX Report top-sites list

Measured 2026-10-23 12:20:18 UTC from one location. How we measure

Readiness by lane

Green: gptzero.me. Thin bar: Web Tools peer median.

Enable

100/100

Peers 84

Harden

72/100

Peers 55

Accelerate

63/100

Peers 69

Recover

0/100

Peers 6

Priority fixes for gptzero.me

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

  1. Priority 1 · Accelerate

    No render-blocking scripts in <head>

    Observed: The homepage <head> loaded 2 external scripts 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 Next.js: Use the next/script component with an appropriate 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.

  2. Priority 2 · Harden

    HSTS kept for at least a year

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

    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.

  3. Priority 3 · Accelerate

    Modern image formats in use

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

    On Cloudflare: Cloudflare Polish can convert images to WebP.

    37% of Web Tools peers do this.

  4. Priority 4 · 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.

    On Cloudflare: Enable HTTP/3 (with QUIC) under Speed > Optimization > Protocol Optimization.

    56% of Web Tools peers do this.

What gptzero.me already does well

Practices fewer than half of Web Tools peers use.

  • Content Security Policy presentContent-Security-Policy present.15% of peers
  • DMARC policy enforces quarantine or rejectDMARC policy p=reject.23% of peers
  • Referrer-Policy setReferrer-Policy present.30% of peers

What we saw

Homepage checked
https://gptzero.me/
Homepage response
HTTP 200
TLS
TLSv1.3, HTTP/2
Certificate
Google Trust Services, 90-day validity, expiring 2027-01-01
CDN or edge
Cloudflare
Platform or framework
Next.js
DNS operators
Cloudflare
HSTS
max-age 180 days, preload
DMARC policy
p=reject
Homepage HTML
294 KB, br
Images on homepage
85 (svg 68, png 16)

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

Observed 22

  • HTTP requests move to HTTPS
  • TLS 1.3 negotiated
  • Certificate has more than 14 days left
  • Certificate lifetime of 100 days or less
  • DMARC policy enforces quarantine or reject
  • Framing restricted
  • Content Security Policy present
  • Referrer-Policy set
  • HTTP/2 negotiated
  • HTML compressed
  • Static files cached for 30 days or more
  • Offscreen images lazy-loaded
  • robots.txt published
  • XML sitemap discoverable
  • Reachable over IPv6
  • 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

  • security.txt published

Own gptzero.me?

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: gptzero.me. This profile covers configuration only.

Compare with other Web Tools sites