Website readiness profile · Snapshot 23 October 2026
ezgif.com
ezgif.com's public homepage, certificate and DNS checked against 31 practices and compared with 492 Web Tools sites.
- Readiness index
- 74/100
- Ahead of
- 73%
- Practices observed
- 20/30
- Popularity band
- Top 10K
Web Tools median 67
of measured Web Tools sites
1 of 31 could not be measured
Chrome UX Report top-sites list
Readiness by lane
Green: ezgif.com. Thin bar: Web Tools peer median.
Enable
92/100
Peers 84
Harden
60/100
Peers 55
Accelerate
83/100
Peers 69
Recover
0/100
Peers 6
Priority fixes for ezgif.com
Ordered by impact and by how common each practice is among peers.
Priority 1 · Accelerate
Modern image formats in use
Observed: The homepage had 4 images and none used WebP or AVIF.
Why it matters: WebP and AVIF are typically much smaller than JPEG or PNG at similar quality, and images are often the heaviest part of a page.
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. Limit: Based on the homepage HTML delivered to an automated client; scripts that run later were not executed.
Guide: AVIF, WebP, JPEG, and PNG: Choose the Right Image Format
Priority 2 · Harden
DMARC policy enforces quarantine or reject
Observed: No DMARC record was found at _dmarc.ezgif.com.
What to do: Publish DMARC with p=none and a reporting address first, fix any legitimate senders that fail SPF or DKIM alignment, then move to quarantine and finally reject.
23% of Web Tools peers do this.
Priority 3 · Enable
Structured data present
Observed: The homepage had no JSON-LD structured data.
What to do: Add JSON-LD for your organization and main content types, then test it with Google's Rich Results Test.
51% of Web Tools peers do this.
Priority 4 · Harden
X-Content-Type-Options: nosniff
Observed: The homepage response did not include X-Content-Type-Options: nosniff.
What to do: Send X-Content-Type-Options: nosniff on all responses and make sure each file is served with the correct Content-Type.
On Cloudflare: Add the header with a response header transform rule.
44% of Web Tools peers do this.
What ezgif.com already does well
Practices fewer than half of Web Tools peers use.
- HSTS kept for at least a yearHSTS with a 730-day max-age covering subdomains.30% of peers
- Framing restrictedFraming controls present.48% of peers
What we saw
- Homepage checked
- https://ezgif.com/
- Homepage response
- HTTP 200
- TLS
- TLSv1.3, HTTP/2
- Certificate
- Let's Encrypt, 89-day validity, expiring 2026-12-26
- DNS operators
- Cloudflare
- HSTS
- max-age 730 days, includeSubDomains, preload
- Homepage HTML
- 19 KB, gzip
- Images on homepage
- 4 (svg 4, gif 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
Not observed 10
Observed 20
- HTTP requests move to HTTPS
- HSTS kept for at least a year
- TLS 1.3 negotiated
- Certificate has more than 14 days left
- Certificate lifetime of 100 days or less
- Framing restricted
- HTTP/2 negotiated
- HTTP/3 advertised
- HTML compressed
- Static files cached for 30 days or more
- No render-blocking scripts in <head>
- robots.txt published
- XML sitemap discoverable
- Reachable over IPv6
- Canonical URL declared
- Meta description written
- Mobile viewport configured
- Social preview image set
- Page language declared
- At most one redirect to the homepage
Not measured 1
- Offscreen images lazy-loaded
Own ezgif.com?
Re-run the checks after a change, keep a private action plan in a free workspace, or report a mistake.
Live status for this site: Status Is Down: ezgif.com. This profile covers configuration only.