gog.com

Readiness by lane

Green: gog.com. Thin bar: Gaming Platforms & Consoles peer median.

Priority fixes for gog.com

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

1. Priority 1 · Accelerate

   Static files cached for 30 days or more

   Observed: A same-site stylesheet or script was cacheable for 0 seconds, short of the 30-day benchmark.

   Why it matters: Returning visitors and later page views reuse cached files instead of downloading them again.

   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 Cloudflare: Use Cache Rules to set edge and browser TTLs for static file paths.

   46% of Gaming Platforms & Consoles peers do this. Limit: Read from the homepage response only; other pages or regions may send different headers.

   Guide: Browser Caching Guide for Website Owners

2. 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.

   61% of Gaming Platforms & Consoles peers do this.

   Guide: XML Sitemap Guide: Include Only URLs You Stand Behind

3. Priority 3 · Harden

   Certificate lifetime of 100 days or less

   Observed: The certificate from DigiCert Inc had a 396-day validity period, longer than the 100-day maximum that applies from March 2027.

   What to do: Move to automated issuance and renewal now, while you still have time to test it.

   76% of Gaming Platforms & Consoles peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

4. Priority 4 · 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.

   On Cloudflare: Add the header with a response header transform rule.

   43% of Gaming Platforms & Consoles peers do this.

   Guide: A Practical Website Health Check for Owners

What gog.com already does well

Practices fewer than half of Gaming Platforms & Consoles peers use.

• security.txt publishedsecurity.txt with a contact found.3.7% of peers
• DMARC policy enforces quarantine or rejectDMARC policy p=reject.26% of peers
• HSTS kept for at least a yearHSTS with a 365-day max-age.30% of peers

What we saw

Homepage checked

https://www.gog.com/

Homepage response

HTTP 200, after 1 redirect

TLS

TLSv1.3, HTTP/2

Certificate

DigiCert, 396-day validity, expiring 2027-03-14

CDN or edge

Fastly

Platform or framework

Angular

DNS operators

Cloudflare

HSTS

max-age 365 days

DMARC policy

p=reject

Homepage HTML

1,591 KB, br

Images on homepage

166 (jpg 254, webp 246, png 19, svg 3)

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

Compare with other Gaming Platforms & Consoles sites

• ea.com71
• eaglercraft.com71
• genshindrop.io71
• ldplayer.net71
• leagueoflegends.com71

Gaming Platforms & Consoles readiness benchmark