postgresql.org

Readiness by lane

Green: postgresql.org. Thin bar: Programming & Software peer median.

Priority fixes for postgresql.org

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

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

   Why it matters: Returning visitors and later page views reuse cached files instead of downloading them again.

   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.

   50% of Programming & Software peers do this. Limit: Read from the homepage response only; other pages or regions may send different headers.

   Guide: Browser Caching Guide for Website Owners

2. Priority 2 · Harden

   DMARC policy enforces quarantine or reject

   Observed: The DMARC policy for postgresql.org 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.

   45% of Programming & Software peers do this.

   Guide: A Practical Website Health Check for Owners

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.

   42% of Programming & Software peers do this.

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

4. Priority 4 · Accelerate

   No render-blocking scripts in <head>

   Observed: The homepage <head> loaded 1 external script 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.

   51% of Programming & Software peers do this.

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

What postgresql.org already does well

Practices fewer than half of Programming & Software peers use.

• DNSSEC signedDNSSEC delegation (DS record) present.12% of peers
• CAA records limit who can issue certificatesCAA limits issuance to amazontrust.com, letsencrypt.org.23% of peers
• Content Security Policy presentContent-Security-Policy present.32% of peers

What we saw

Homepage checked

https://www.postgresql.org/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

Let's Encrypt, 89-day validity, expiring 2026-12-30

DNS operators

1 self-run or other nameserver domain

HSTS

max-age 365 days

DMARC policy

p=none

Homepage HTML

24 KB, gzip

Images on homepage

8 (svg 6, png 2)

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 Programming & Software sites

• an1.com66
• deltaexecuttor.com.mx66
• mongodb.com65
• pdalife.com66
• scriptpastebin.com66

Programming & Software readiness benchmark