superonline.net

Readiness by lane

Green: superonline.net. Thin bar: Telecommunications & Internet peer median.

Priority fixes for superonline.net

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

1. Priority 1 · Accelerate

   HTTP/2 negotiated

   Observed: The TLS handshake selected HTTP/1.1 instead of HTTP/2.

   Why it matters: HTTP/2 sends many files over one connection, which speeds up pages with lots of images, styles and scripts.

   What to do: Enable HTTP/2 on your CDN or server. Most CDNs do this by default.

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

   Guide: CDN Guide for Website Owners

2. Priority 2 · Harden

   DMARC policy enforces quarantine or reject

   Observed: The DMARC policy for superonline.net was p=none, which asks receivers to take no action on failing mail.

   What to do: Publish DMARC with p=none and a reporting address first, fix any legitimate senders that fail SPF or DKIM alignment, then move to quarantine and finally reject.

   59% of Telecommunications & Internet peers do this.

   Guide: A Practical Website Health Check for Owners

3. Priority 3 · Accelerate

   Static files cached for 30 days or more

   Observed: A same-site stylesheet or script was cacheable for 1 hours, 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

4. Priority 4 · Accelerate

   No render-blocking scripts in <head>

   Observed: The homepage <head> loaded 3 external scripts 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 Next.js: Use the next/script component with an appropriate loading strategy.

   37% of Telecommunications & Internet peers do this.

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

What superonline.net already does well

Practices fewer than half of Telecommunications & Internet peers use.

• Content Security Policy presentContent-Security-Policy present.48% of peers

What we saw

Homepage checked

https://www.superonline.net/

Homepage response

HTTP 200

TLS

TLSv1.3

Certificate

GlobalSign, 396-day validity, expiring 2027-04-10

Platform or framework

Next.js

DNS operators

1 self-run or other nameserver domain

HSTS

max-age 365 days, includeSubDomains, preload

DMARC policy

p=none

Homepage HTML

860 KB, gzip

Images on homepage

101 (webp 60, svg 30, png 6, jpg 5)

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

• koodomobile.com63
• personal.com.ar64
• swisscom.ch63
• totalwireless.com63
• tuenti.com.ar64

Telecommunications & Internet readiness benchmark