digimobil.es

Readiness by lane

Green: digimobil.es. Thin bar: Telecommunications & Internet peer median.

Priority fixes for digimobil.es

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

1. Priority 1 · Accelerate

   Modern image formats in use

   Observed: The homepage had 45 images and none used WebP or AVIF.

   Why it matters: WebP and AVIF are typically much smaller than JPEG or PNG at similar quality, and images are often the heaviest part of a page.

   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.

   52% of Telecommunications & Internet peers do this. Limit: Based on the homepage HTML delivered to an automated client; scripts that run later were not executed.

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

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

   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.

   41% of Telecommunications & Internet peers do this.

   Guide: Browser Caching Guide for Website Owners

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

   68% of Telecommunications & Internet peers do this.

   Guide: A Practical Website Health Check for Owners

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.

   48% of Telecommunications & Internet peers do this.

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

What digimobil.es already does well

Practices fewer than half of Telecommunications & Internet peers use.

• security.txt publishedsecurity.txt with a contact found.13% of peers
• Nameservers spread across providersNameservers spread across more than one operator.16% of peers
• No render-blocking scripts in <head>Head scripts load without blocking.37% of peers

What we saw

Homepage checked

https://www.digimobil.es/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

Sectigo, 396-day validity, expiring 2026-11-22

DNS operators

4 self-run or other nameserver domains

HSTS

max-age 365 days, includeSubDomains

DMARC policy

p=reject

Homepage HTML

351 KB, gzip

Images on homepage

45 (svg 17, png 4)

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 Telecommunications & Internet sites

• doctorsim.com72
• fido.ca72
• tele2.se73
• telia.fi73
• virginmedia.com73

Telecommunications & Internet readiness benchmark