Website readiness profile · Snapshot 23 October 2026
mydigipay.com
mydigipay.com's public homepage, certificate and DNS checked against 31 practices and compared with 157 Online Payment & Wallets sites.
- Readiness index
- 64/100
- Ahead of
- 46%
- Practices observed
- 15/30
- Popularity band
- Top 50K
Online Payment & Wallets median 64
of measured Online Payment & Wallets sites
1 of 31 could not be measured
Chrome UX Report top-sites list
Readiness by lane
Green: mydigipay.com. Thin bar: Online Payment & Wallets peer median.
Enable
59/100
Peers 72
Harden
62/100
Peers 63
Accelerate
75/100
Peers 61
Recover
0/100
Peers 6
Priority fixes for mydigipay.com
Ordered by impact and by how common each practice is among peers.
Priority 1 · Enable
Meta description written
Observed: The homepage had no meta description.
Why it matters: Search engines often use it for the snippet under your link, so a clear description can improve click-through.
What to do: Write a short, specific description of the page for people, not a list of keywords.
83% 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: Meta Titles and Descriptions That Match Search Intent
Priority 2 · Accelerate
Static files cached for 30 days or more
Observed: A same-site stylesheet or script was cacheable for no max-age, short of the 30-day benchmark.
What to do: Give versioned (fingerprinted) CSS, JavaScript, fonts and images Cache-Control: public, max-age=31536000, immutable, and change the file name whenever the content changes.
On WordPress: Caching plugins or your host can set long browser cache lifetimes for theme and plugin assets.
32% of Online Payment & Wallets peers do this.
Priority 3 · Harden
Framing restricted
Observed: The homepage did not send frame-ancestors or X-Frame-Options, so other sites may frame it.
What to do: Send Content-Security-Policy: frame-ancestors 'self' (or a list of trusted origins). X-Frame-Options: SAMEORIGIN covers older browsers.
64% of Online Payment & Wallets peers do this.
Priority 4 · Enable
Canonical URL declared
Observed: The homepage did not declare a canonical URL.
What to do: Add a self-referencing canonical link to every indexable page, using the final https:// URL.
59% of Online Payment & Wallets peers do this.
What mydigipay.com already does well
Practices fewer than half of Online Payment & Wallets peers use.
- Modern image formats in useWebP or AVIF images detected.47% of peers
- No render-blocking scripts in <head>Head scripts load without blocking.49% of peers
What we saw
- Homepage checked
- https://www.mydigipay.com/
- Homepage response
- HTTP 200
- TLS
- TLSv1.3, HTTP/2
- Certificate
- Asseco Data Systems S.A., 364-day validity, expiring 2027-02-01
- Platform or framework
- WordPress
- DNS operators
- 1 self-run or other nameserver domain
- HSTS
- max-age 365 days
- DMARC policy
- p=quarantine
- Homepage HTML
- 985 KB, gzip
- Images on homepage
- 488 (webp 286, svg 110, jpg 51, png 32)
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 15
- Certificate lifetime of 100 days or less
- CAA records limit who can issue certificates
- DNSSEC signed
- X-Content-Type-Options: nosniff
- Framing restricted
- Content Security Policy present
- Referrer-Policy set
- HTTP/3 advertised
- Static files cached for 30 days or more
- Reachable over IPv6
- Canonical URL declared
- Meta description written
- Structured data present
- Social preview image set
- Nameservers spread across providers
Observed 15
- HTTP requests move to HTTPS
- HSTS kept for at least a year
- TLS 1.3 negotiated
- Certificate has more than 14 days left
- DMARC policy enforces quarantine or reject
- HTTP/2 negotiated
- HTML compressed
- Modern image formats in use
- Offscreen images lazy-loaded
- No render-blocking scripts in <head>
- robots.txt published
- XML sitemap discoverable
- Mobile viewport configured
- Page language declared
- At most one redirect to the homepage
Not measured 1
- security.txt published
Own mydigipay.com?
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: mydigipay.com. This profile covers configuration only.