Website readiness profile · Snapshot 23 October 2026
funpay.com
funpay.com's public homepage, certificate and DNS checked against 31 practices and compared with 5,718 E-Commerce & Marketplaces sites.
- Readiness index
- 50/100
- Ahead of
- 5.5%
- Practices observed
- 12/29
- Popularity band
- Top 1K
E-Commerce & Marketplaces median 71
of measured E-Commerce & Marketplaces sites
2 of 31 could not be measured
Chrome UX Report top-sites list
Readiness by lane
Green: funpay.com. Thin bar: E-Commerce & Marketplaces peer median.
Enable
71/100
Peers 86
Harden
35/100
Peers 60
Accelerate
58/100
Peers 69
Recover
0/100
Peers 11
Priority fixes for funpay.com
Ordered by impact and by how common each practice is among peers.
Priority 1 · Harden
TLS 1.3 negotiated
Observed: The TLS connection negotiated TLSv1.2.
Why it matters: TLS 1.3 removes legacy cipher suites and completes the handshake in fewer round trips, so it is both safer and faster for new connections.
What to do: Enable TLS 1.3 on your CDN or server. Keep TLS 1.2 available for older clients unless you have checked your audience.
On Cloudflare: Turn on TLS 1.3 under SSL/TLS > Edge Certificates.
93% of E-Commerce & Marketplaces peers do this. Limit: Certificate and protocol were observed from one vantage point; CDNs can present different certificates by region.
Priority 2 · Enable
XML sitemap discoverable
Observed: No sitemap was listed in robots.txt or found at /sitemap.xml.
What to do: Generate an XML sitemap of canonical URLs, reference it in robots.txt and submit it in Google Search Console.
87% of E-Commerce & Marketplaces peers do this.
Guide: XML Sitemap Guide: Include Only URLs You Stand Behind
Priority 3 · Accelerate
Modern image formats in use
Observed: The homepage had 3 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.
47% of E-Commerce & Marketplaces peers do this.
Guide: AVIF, WebP, JPEG, and PNG: Choose the Right Image Format
Priority 4 · Harden
HSTS kept for at least a year
Observed: Strict-Transport-Security was sent with a max-age of 183 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.
32% of E-Commerce & Marketplaces peers do this.
What we saw
- Homepage checked
- https://funpay.com/
- Homepage response
- HTTP 200, after 1 redirect
- TLS
- TLSv1.2, HTTP/2
- Certificate
- Sectigo, 198-day validity, expiring 2027-04-07
- DNS operators
- Cloudflare
- HSTS
- max-age 183 days, includeSubDomains
- DMARC policy
- p=none
- Homepage HTML
- 593 KB, gzip
- Images on homepage
- 3 (svg 2, jpg 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 17
- HSTS kept for at least a year
- TLS 1.3 negotiated
- Certificate lifetime of 100 days or less
- CAA records limit who can issue certificates
- DNSSEC signed
- security.txt published
- DMARC policy enforces quarantine or reject
- X-Content-Type-Options: nosniff
- Content Security Policy present
- Referrer-Policy set
- HTTP/3 advertised
- Modern image formats in use
- No render-blocking scripts in <head>
- XML sitemap discoverable
- Reachable over IPv6
- Social preview image set
- Nameservers spread across providers
Observed 12
- HTTP requests move to HTTPS
- Certificate has more than 14 days left
- Framing restricted
- HTTP/2 negotiated
- HTML compressed
- Static files cached for 30 days or more
- Canonical URL declared
- Meta description written
- Mobile viewport configured
- Structured data present
- Page language declared
- At most one redirect to the homepage
Not measured 2
- Offscreen images lazy-loaded
- robots.txt published
Own funpay.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: funpay.com. This profile covers configuration only.