ign.com

Readiness by lane

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

Priority fixes for ign.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: Strict-Transport-Security was sent with a max-age of 0 days, below the one-year benchmark.

   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.

   On Next.js: Add the header in the headers() option of next.config.js for all routes.

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

   Guide: HTTPS and TLS Guide for Website Owners

2. Priority 2 · Accelerate

   Modern image formats in use

   Observed: The homepage had 82 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 WordPress: WordPress has supported WebP uploads since 5.8 and AVIF since 6.5; image plugins or the host can convert existing images.

   43% of Gaming Platforms & Consoles peers do this.

   Guide: AVIF, WebP, JPEG, and PNG: Choose the Right Image Format

3. Priority 3 · Harden

   Certificate lifetime of 100 days or less

   Observed: The certificate from GlobalSign nv-sa had a 198-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 Next.js: Add it in next.config.js headers().

   43% of Gaming Platforms & Consoles peers do this.

   Guide: A Practical Website Health Check for Owners

What ign.com already does well

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

• DMARC policy enforces quarantine or rejectDMARC policy p=quarantine.26% of peers
• Structured data presentJSON-LD structured data found.40% of peers
• Offscreen images lazy-loadedNative lazy loading in use.49% of peers

What we saw

Homepage checked

https://www.ign.com/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

GlobalSign, 198-day validity, expiring 2027-05-02

Platform or framework

WordPress, Next.js

DNS operators

Amazon Route 53

HSTS

max-age 0 days

DMARC policy

p=quarantine

Homepage HTML

384 KB, gzip

Images on homepage

82 (jpg 107, png 50, svg 8)

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

• keymailer.co66
• ls-portal.eu66
• roll20.net67
• sims4pack.ru67
• supercell.com67

Gaming Platforms & Consoles readiness benchmark