pg21.ru

Readiness by lane

Green: pg21.ru. Thin bar: News & Media peer median.

Priority fixes for pg21.ru

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 no max-age, 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.

   60% of News & Media 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 · 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 Next.js: Add the header in the headers() option of next.config.js for all routes.

   35% of News & Media peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

3. Priority 3 · Enable

   Structured data present

   Observed: The homepage had no JSON-LD structured data.

   What to do: Add JSON-LD for your organization and main content types, then test it with Google's Rich Results Test.

   76% of News & Media peers do this.

   Guide: Structured Data Basics 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().

   42% of News & Media peers do this.

   Guide: A Practical Website Health Check for Owners

What pg21.ru already does well

Practices fewer than half of News & Media peers use.

• Content Security Policy presentContent-Security-Policy present.29% of peers
• HTTP/3 advertisedHTTP/3 advertised.36% of peers
• DMARC policy enforces quarantine or rejectDMARC policy p=reject.37% of peers

What we saw

Homepage checked

https://pg21.ru/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

Let's Encrypt, 89-day validity, expiring 2026-12-19

Platform or framework

Next.js

DNS operators

1 self-run or other nameserver domain

DMARC policy

p=reject

Homepage HTML

159 KB, gzip

Images on homepage

27 (webp 66, jpg 45, png 21, svg 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

Compare with other News & Media sites

• okaz.com.sa73
• onet.pl73
• otempo.com.br73
• plejada.pl73
• pointdevue.fr73

News & Media readiness benchmark