metropoles.com

Readiness by lane

Green: metropoles.com. Thin bar: News & Media peer median.

Priority fixes for metropoles.com

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

1. Priority 1 · Harden

   HTTP requests move to HTTPS

   Observed: A request to http://www.metropoles.com/ was not redirected to HTTPS.

   Why it matters: Visitors who type the address or follow an old link start on unencrypted HTTP. A redirect moves them to the encrypted site before any cookies or form data are sent.

   What to do: Add a permanent (301 or 308) redirect from every http:// URL to the same https:// URL at your CDN, load balancer or web server.

   On WordPress: Set both WordPress Address and Site Address to https:// in Settings > General, then add the server or CDN redirect.

   96% of News & Media peers do this. Limit: Measured for the homepage only, from one location, at the time of the check.

   Guide: HTTPS and TLS 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 · Accelerate

   No render-blocking scripts in <head>

   Observed: The homepage <head> loaded 1 external script without async or defer.

   What to do: Add defer to scripts that need the DOM, async to independent ones such as analytics, or move them to the end of the body.

   On WordPress: Since WordPress 6.3, scripts can be registered with a defer or async loading strategy.

   42% of News & Media peers do this.

   Guide: Control Third-Party Scripts Before They Control Your Page

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 metropoles.com already does well

Practices fewer than half of News & Media peers use.

• Nameservers spread across providersNameservers spread across more than one operator.11% of peers
• DMARC policy enforces quarantine or rejectDMARC policy p=quarantine.37% of peers
• Modern image formats in useWebP or AVIF images detected.44% of peers

What we saw

Homepage checked

https://www.metropoles.com/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

Let's Encrypt, 89-day validity, expiring 2027-01-05

CDN or edge

Google edge

Platform or framework

WordPress, Next.js

DNS operators

3 self-run or other nameserver domains

DMARC policy

p=quarantine

Homepage HTML

940 KB, gzip

Images on homepage

145 (jpg 531, png 45, webp 19)

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

• mediatakeout.com63
• mel.fm63
• metronieuws.nl63
• msn.com63
• n1info.ba63

News & Media readiness benchmark