Website readiness profile · Snapshot 23 October 2026
faucetpay.io
faucetpay.io's public homepage, certificate and DNS checked against 31 practices and compared with 157 Online Payment & Wallets sites.
- Readiness index
- 82/100
- Ahead of
- 87%
- Practices observed
- 24/31
- Popularity band
- Top 50K
Online Payment & Wallets median 64
of measured Online Payment & Wallets sites
0 of 31 could not be measured
Chrome UX Report top-sites list
Readiness by lane
Green: faucetpay.io. Thin bar: Online Payment & Wallets peer median.
Enable
92/100
Peers 72
Harden
83/100
Peers 63
Accelerate
73/100
Peers 61
Recover
0/100
Peers 6
Priority fixes for faucetpay.io
Ordered by impact and by how common each practice is among peers.
Priority 1 · Accelerate
Modern image formats in use
Observed: The homepage had 21 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.
47% of Online Payment & Wallets 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 · 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.
On Next.js: Use the next/script component with an appropriate loading strategy.
49% of Online Payment & Wallets peers do this.
Guide: Control Third-Party Scripts Before They Control Your Page
Priority 3 · Enable
Social preview image set
Observed: The homepage had no og:image, so shared links may show without a preview image.
What to do: Add Open Graph tags, including og:image with a 1200 x 630 image.
56% of Online Payment & Wallets peers do this.
Priority 4 · Harden
CAA records limit who can issue certificates
Observed: No CAA record was found for faucetpay.io, so any public certificate authority may issue for it.
What to do: Publish CAA records naming every CA you actually use, including the CAs your CDN uses for managed certificates. Add an iodef contact if you want reports.
On Cloudflare: Cloudflare documents which CAs its managed certificates need; include them in your CAA records.
18% of Online Payment & Wallets peers do this.
What faucetpay.io already does well
Practices fewer than half of Online Payment & Wallets peers use.
- Reachable over IPv6IPv6 address published.28% of peers
- Static files cached for 30 days or moreLong-lived caching on static files.32% of peers
- HTTP/3 advertisedHTTP/3 advertised.35% of peers
What we saw
- Homepage checked
- https://faucetpay.io/
- Homepage response
- HTTP 200
- TLS
- TLSv1.3, HTTP/2
- Certificate
- Google Trust Services, 90-day validity, expiring 2027-01-15
- CDN or edge
- Cloudflare
- Platform or framework
- Next.js
- DNS operators
- Cloudflare
- HSTS
- max-age 730 days
- DMARC policy
- p=reject
- Homepage HTML
- 650 KB, br
- Images on homepage
- 21 (png 17, svg 4)
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 7
Observed 24
- 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
- DMARC policy enforces quarantine or reject
- X-Content-Type-Options: nosniff
- Framing restricted
- Content Security Policy present
- Referrer-Policy set
- HTTP/2 negotiated
- HTTP/3 advertised
- 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
- Page language declared
- At most one redirect to the homepage
Own faucetpay.io?
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: faucetpay.io. This profile covers configuration only.