STATUS IS UPREADINESS PROFILE

Website readiness profile · Snapshot 23 October 2026

prizegrab.com

prizegrab.com's public homepage, certificate and DNS checked against 31 practices and compared with 343 Uncategorized sites.

Readiness index
45/100

Uncategorized median 62

Ahead of
8.7%

of measured Uncategorized sites

Practices observed
11/31

0 of 31 could not be measured

Popularity band
Top 10K

Chrome UX Report top-sites list

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

Readiness by lane

Green: prizegrab.com. Thin bar: Uncategorized peer median.

Enable

56/100

Peers 80

Harden

38/100

Peers 54

Accelerate

48/100

Peers 58

Recover

0/100

Peers 12

Priority fixes for prizegrab.com

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

  1. Priority 1 · Enable

    XML sitemap discoverable

    Observed: No sitemap was listed in robots.txt or found at /sitemap.xml.

    Why it matters: A sitemap helps search engines find new and updated pages, especially on large or frequently updated sites.

    What to do: Generate an XML sitemap of canonical URLs, reference it in robots.txt and submit it in Google Search Console.

    75% of Uncategorized peers do this. Limit: Only the standard location was requested, once, at the time of the check.

  2. Priority 2 · Harden

    HSTS kept for at least a year

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

    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 Amazon CloudFront: Attach a response headers policy with Strict-Transport-Security to each distribution.

    34% of Uncategorized peers do this.

  3. Priority 3 · Accelerate

    Static files cached for 30 days or more

    Observed: A same-site stylesheet or script was cacheable for 7 days, 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.

    44% of Uncategorized peers do this.

  4. Priority 4 · Harden

    DMARC policy enforces quarantine or reject

    Observed: The DMARC policy for prizegrab.com was p=none, which asks receivers to take no action on failing mail.

    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.

    39% of Uncategorized peers do this.

What prizegrab.com already does well

Practices fewer than half of Uncategorized peers use.

  • HTTP/3 advertisedHTTP/3 advertised.33% of peers

What we saw

Homepage checked
https://prizegrab.com/
Homepage response
HTTP 200
TLS
TLSv1.3, HTTP/2
Certificate
Amazon, 197-day validity, expiring 2027-03-29
CDN or edge
Amazon CloudFront
DNS operators
Amazon Route 53
DMARC policy
p=none
Homepage HTML
40 KB, gzip
Images on homepage
10 (png 7, 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

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

Compare with other Uncategorized sites