cne.gob.ec

Readiness by lane

Green: cne.gob.ec. Thin bar: Government Services peer median.

Priority fixes for cne.gob.ec

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

1. Priority 1 · Accelerate

   No render-blocking scripts in <head>

   Observed: The homepage <head> loaded 5 external scripts without async or defer.

   Why it matters: A plain <script src> in the head stops the browser from showing anything until that file has downloaded and run.

   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.

   39% of Government Services peers do this. Limit: Based on the homepage HTML delivered to an automated client; scripts that run later were not executed.

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

2. Priority 2 · Enable

   Meta description written

   Observed: The homepage had no meta description.

   What to do: Write a short, specific description of the page for people, not a list of keywords.

   58% of Government Services peers do this.

   Guide: Meta Titles and Descriptions That Match Search Intent

3. Priority 3 · Accelerate

   Modern image formats in use

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

   15% of Government Services peers do this.

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

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.

   41% of Government Services peers do this.

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

What cne.gob.ec already does well

Practices fewer than half of Government Services peers use.

• Canonical URL declaredCanonical link present.41% of peers
• XML sitemap discoverableSitemap found.42% of peers

What we saw

Homepage checked

https://www.cne.gob.ec/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

DigiCert, 198-day validity, expiring 2027-04-07

CDN or edge

Imperva

Platform or framework

WordPress

DNS operators

1 self-run or other nameserver domain

HSTS

max-age 365 days

DMARC policy

p=reject

Homepage HTML

226 KB, gzip

Images on homepage

8 (png 7, jpg 7, svg 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 Government Services sites

• chileatiende.gob.cl60
• claveunica.gob.cl60
• educacionfpydeportes.gob.es60
• estelamonline.net60
• rnpdigital.com61

Government Services readiness benchmark