medellin.gov.co

Readiness by lane

Green: medellin.gov.co. Thin bar: Government Services peer median.

Priority fixes for medellin.gov.co

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.

   55% of Government Services 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

   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.

   51% of Government Services 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 2 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 WordPress: Since WordPress 6.3, scripts can be registered with a defer or async loading strategy.

   39% of Government Services peers do this.

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

4. Priority 4 · Accelerate

   Modern image formats in use

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

What medellin.gov.co already does well

Practices fewer than half of Government Services peers use.

• Structured data presentJSON-LD structured data found.15% of peers
• CAA records limit who can issue certificatesCAA limits issuance to amazonaws.com, digicert.com, globalsign.com and others.17% of peers
• Reachable over IPv6IPv6 address published.27% of peers

What we saw

Homepage checked

https://www.medellin.gov.co/

Homepage response

HTTP 200

TLS

TLSv1.3, http/1.1

Certificate

DigiCert, 396-day validity, expiring 2027-03-14

Platform or framework

WordPress

DNS operators

1 self-run or other nameserver domain

DMARC policy

p=reject

Homepage HTML

683 KB, gzip

Images on homepage

137 (jpg 176, png 162, svg 12)

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

• inpi.fr66
• irs.gov66
• kanta.fi66
• msa.fr66
• odigostoupoliti.eu66

Government Services readiness benchmark