diariovasco.com

Readiness by lane

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

Priority fixes for diariovasco.com

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

1. Priority 1 · Harden

   Certificate has more than 14 days left

   Observed: The certificate from Certainly was due to expire on 2026-11-04 (11 days after the check).

   Why it matters: An expired certificate makes browsers show a full-page warning. Renewing well ahead of expiry leaves time to fix a failed renewal.

   What to do: Automate renewal with ACME (for example Let's Encrypt or your CDN's managed certificates) and add a renewal review to your release calendar so any certificate inside 21 days of expiry gets attention.

   99% of News & Media peers do this. Limit: Certificate and protocol were observed from one vantage point; CDNs can present different certificates by region.

   Guide: HTTPS and TLS Guide for Website Owners

2. Priority 2 · Accelerate

   Modern image formats in use

   Observed: The homepage had 150 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.

   44% of News & Media peers do this.

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

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

   Content Security Policy present

   Observed: The homepage response did not include a Content-Security-Policy header.

   What to do: Start with Content-Security-Policy-Report-Only to see what would break, tighten the policy over a few weeks, then enforce it.

   29% of News & Media peers do this.

   Guide: Payment Security and PCI DSS: What Website Owners Need to Know

What diariovasco.com already does well

Practices fewer than half of News & Media peers use.

• HSTS kept for at least a yearHSTS with a 365-day max-age.35% of peers
• HTTP/3 advertisedHTTP/3 advertised.36% of peers
• DMARC policy enforces quarantine or rejectDMARC policy p=quarantine.37% of peers

What we saw

Homepage checked

https://www.diariovasco.com/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

Certainly, 29-day validity, expiring 2026-11-04

Platform or framework

WordPress

DNS operators

Google Cloud DNS

HSTS

max-age 365 days

DMARC policy

p=quarantine

Homepage HTML

483 KB, gzip

Images on homepage

150 (jpg 90, svg 37, png 14)

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

• comicbook.com65
• cookist.it65
• diariodorio.com65
• dinamalar.com65
• doolnews.com65

News & Media readiness benchmark