Website readiness profile · Snapshot 23 October 2026

gitlab.com

gitlab.com's public homepage, certificate and DNS checked against 31 practices and compared with 231 Programming & Software sites.

Readiness index: 74/100
Ahead of: 71%
Practices observed: 20/30
Popularity band: Top 5K

Measured 2026-10-23 11:26:08 UTC from one location. How we measure

Readiness by lane

Green: gitlab.com. Thin bar: Programming & Software peer median.

Enable

87/100

Peers 81

Harden

69/100

Peers 59

Accelerate

73/100

Peers 65

Recover

0/100

Peers 7

Priority fixes for gitlab.com

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

Priority 1 · Accelerate
Static files cached for 30 days or more
Observed: A same-site stylesheet or script was cacheable for 0 seconds, 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.
On Cloudflare: Use Cache Rules to set edge and browser TTLs for static file paths.
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
Priority 2 · Enable
XML sitemap discoverable
Observed: No sitemap was listed in robots.txt or found at /sitemap.xml.
What to do: Generate an XML sitemap of canonical URLs, reference it in robots.txt and submit it in Google Search Console.
69% of Programming & Software peers do this.
Guide: XML Sitemap Guide: Include Only URLs You Stand Behind
Priority 3 · Accelerate
No render-blocking scripts in <head>
Observed: The homepage <head> loaded 4 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.
51% of Programming & Software peers do this.
Guide: Control Third-Party Scripts Before They Control Your Page
Priority 4 · Harden
Framing restricted
Observed: The homepage did not send frame-ancestors or X-Frame-Options, so other sites may frame it.
What to do: Send Content-Security-Policy: frame-ancestors 'self' (or a list of trusted origins). X-Frame-Options: SAMEORIGIN covers older browsers.
On Cloudflare: Add the header with a response header transform rule.
47% of Programming & Software peers do this.
Guide: A Practical Website Health Check for Owners

What gitlab.com already does well

Practices fewer than half of Programming & Software peers use.

security.txt publishedsecurity.txt with a contact found.15% of peers
HSTS kept for at least a yearHSTS with a 365-day max-age.40% of peers
HTTP/3 advertisedHTTP/3 advertised.40% of peers

What we saw

Homepage checked: https://gitlab.com/
Homepage response: HTTP 200, after 1 redirect
TLS: TLSv1.3, HTTP/2
Certificate: Sectigo, 198-day validity, expiring 2026-11-10
CDN or edge: Cloudflare
Platform or framework: Nuxt
DNS operators: Cloudflare
HSTS: max-age 365 days
DMARC policy: p=reject
Homepage HTML: 213 KB, gzip
Images on homepage: 39 (svg 30, png 11, jpg 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.

Nuxt readiness playbook Nuxt on Cloudflare playbook Cloudflare (cdn and edge platform)Cloudflare (dns operator)Sectigo (certificate authority)Service guide: Cloudflare

All 31 checks

Select a gap for the method and fix. How each check works

Not observed 10

Observed 20

HTTP requests move to HTTPS
HSTS kept for at least a year
TLS 1.3 negotiated
Certificate has more than 14 days left
security.txt published
DMARC policy enforces quarantine or reject
HTTP/2 negotiated
HTTP/3 advertised
HTML compressed
Modern image formats in use
Offscreen images lazy-loaded
robots.txt published
Reachable over IPv6
Canonical URL declared
Meta description written
Mobile viewport configured
Structured data present
Social preview image set
Page language declared
At most one redirect to the homepage

Not measured 1

CAA records limit who can issue certificates

Own gitlab.com?

Re-run the checks after a change, keep a private action plan in a free workspace, or report a mistake.

Re-check gitlab.com now Add to owner workspace Request a correction or removal

Live status for this site: Status Is Down: gitlab.com. This profile covers configuration only.

Compare with other Programming & Software sites

Programming & Software readiness benchmark