STATUS IS UPREADINESS PROFILE

Website readiness profile · Snapshot 23 October 2026

pgyer.com

pgyer.com's public homepage, certificate and DNS checked against 31 practices and compared with 40 Web Hosting & Infrastructure sites.

Readiness index
57/100

Web Hosting & Infrastructure median 74

Ahead of
20%

of measured Web Hosting & Infrastructure sites

Practices observed
14/30

1 of 31 could not be measured

Popularity band
Top 50K

Chrome UX Report top-sites list

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

Readiness by lane

Green: pgyer.com. Thin bar: Web Hosting & Infrastructure peer median.

Enable

79/100

Peers 83

Harden

38/100

Peers 67

Accelerate

65/100

Peers 70

Recover

n/a/100

Peers 18

Priority fixes for pgyer.com

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

  1. Priority 1 · Harden

    HSTS kept for at least a year

    Observed: The homepage response did not include a Strict-Transport-Security header.

    Why it matters: HSTS tells browsers to use HTTPS for your host on every later visit, which removes the window where a first HTTP request can be intercepted.

    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.

    53% of Web Hosting & Infrastructure peers do this. Limit: Read from the homepage response only; other pages or regions may send different headers.

  2. Priority 2 · Accelerate

    Modern image formats in use

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

    65% of Web Hosting & Infrastructure peers do this.

  3. Priority 3 · Harden

    DMARC policy enforces quarantine or reject

    Observed: No DMARC record was found at _dmarc.pgyer.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.

    63% of Web Hosting & Infrastructure peers do this.

  4. Priority 4 · Accelerate

    Offscreen images lazy-loaded

    Observed: The homepage had 174 images and none used loading="lazy".

    What to do: Add loading="lazy" to images below the fold. Do not lazy-load the main hero image, because that delays the largest visible element.

    68% of Web Hosting & Infrastructure peers do this.

What we saw

Homepage checked
https://www.pgyer.com/
Homepage response
HTTP 200
TLS
TLSv1.3, HTTP/2
Certificate
WoTrus CA Limited, 396-day validity, expiring 2027-03-12
CDN or edge
Alibaba Cloud CDN
Homepage HTML
203 KB, br
Images on homepage
174 (png 151, svg 16, jpg 7)

Limits: homepage only, one location, one moment. Header checks reflect the homepage response; other pages may differ.

All 31 checks

Select a gap for the method and fix. How each check works

Observed 14

  • HTTP requests move to HTTPS
  • TLS 1.3 negotiated
  • Certificate has more than 14 days left
  • HTTP/2 negotiated
  • HTML compressed
  • Static files cached for 30 days or more
  • No render-blocking scripts in <head>
  • robots.txt published
  • XML sitemap discoverable
  • Canonical URL declared
  • Meta description written
  • Mobile viewport configured
  • Page language declared
  • At most one redirect to the homepage

Not measured 1

  • Nameservers spread across providers

Own pgyer.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: pgyer.com. This profile covers configuration only.

Compare with other Web Hosting & Infrastructure sites