fcm.org.co

Readiness by lane

Green: fcm.org.co. Thin bar: Government Services peer median.

Priority fixes for fcm.org.co

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

1. Priority 1 · Accelerate

   HTML compressed

   Observed: The homepage HTML (247 KB) was delivered without gzip, Brotli or zstd compression.

   Why it matters: Compression usually shrinks HTML several times over, so the first bytes of the page arrive sooner on slow connections.

   What to do: Enable Brotli or gzip for text responses (HTML, CSS, JavaScript, JSON, SVG) at the CDN or origin.

   74% of Government Services peers do this. Limit: Read from the homepage response only; other pages or regions may send different headers.

   Guide: How to Set a Website Performance Budget That Teams Can Keep

2. Priority 2 · Accelerate

   No render-blocking scripts in <head>

   Observed: The homepage <head> loaded 32 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

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

4. Priority 4 · Harden

   CAA records limit who can issue certificates

   Observed: No CAA record was found for fcm.org.co, so any public certificate authority may issue for it.

   What to do: Publish CAA records naming every CA you actually use, including the CAs your CDN uses for managed certificates. Add an iodef contact if you want reports.

   17% of Government Services peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

What fcm.org.co already does well

Practices fewer than half of Government Services peers use.

• Modern image formats in useWebP or AVIF images detected.15% of peers
• Structured data presentJSON-LD structured data found.15% of peers
• Static files cached for 30 days or moreLong-lived caching on static files.30% of peers

What we saw

Homepage checked

https://www.fcm.org.co/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

GoDaddy, 365-day validity, expiring 2026-12-12

Platform or framework

WordPress

DNS operators

1 self-run or other nameserver domain

HSTS

max-age 365 days, includeSubDomains, preload

DMARC policy

p=quarantine

Homepage HTML

247 KB, uncompressed

Images on homepage

41 (jpg 64, png 12, webp 1, svg 1)

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

• pagibigfund.gov.ph69
• quebec.ca69
• sarkaricsc.com70
• service-public.gouv.fr70
• woah.org70

Government Services readiness benchmark