STATUS IS UPREADINESS PROFILE

Website readiness profile · Snapshot 23 October 2026

buildkite.com

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

Readiness index
84/100

Programming & Software median 68

Ahead of
94%

of measured Programming & Software sites

Practices observed
24/31

0 of 31 could not be measured

Popularity band
Top 50K

Chrome UX Report top-sites list

Measured 2026-10-23 12:19:37 UTC from one location. How we measure

Readiness by lane

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

Enable

92/100

Peers 81

Harden

78/100

Peers 59

Accelerate

90/100

Peers 65

Recover

0/100

Peers 7

Priority fixes for buildkite.com

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

  1. Priority 1 · Harden

    Certificate lifetime of 100 days or less

    Observed: The certificate from Amazon had a 394-day validity period, longer than the 100-day maximum that applies from March 2027.

    Why it matters: Under CA/Browser Forum Ballot SC-081v3, the maximum lifetime of public TLS certificates fell to 200 days on 15 March 2026 and falls to 100 days on 15 March 2027 and 47 days on 15 March 2029. Sites that renew by hand will need to renew far more often.

    What to do: Move to automated issuance and renewal now, while you still have time to test it.

    73% of Programming & Software peers do this. Limit: Certificate and protocol were observed from one vantage point; CDNs can present different certificates by region.

  2. Priority 2 · Accelerate

    HTTP/3 advertised

    Observed: The homepage did not advertise HTTP/3 through an Alt-Svc header.

    What to do: Turn on HTTP/3 at your CDN. Browsers fall back to HTTP/2 automatically, so the risk is low.

    On Amazon CloudFront: Select HTTP/3 in the distribution's supported HTTP versions.

    40% of Programming & Software peers do this.

  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.

    32% of Programming & Software peers do this.

  4. Priority 4 · Enable

    Structured data present

    Observed: The homepage had no JSON-LD structured data.

    What to do: Add JSON-LD for your organization and main content types, then test it with Google's Rich Results Test.

    52% of Programming & Software peers do this.

What buildkite.com already does well

Practices fewer than half of Programming & Software peers use.

  • CAA records limit who can issue certificatesCAA limits issuance to amazonaws.com, comodoca.com, digicert.com and others.23% of peers
  • Referrer-Policy setReferrer-Policy present.24% of peers
  • HSTS kept for at least a yearHSTS with a 365-day max-age.40% of peers

What we saw

Homepage checked
https://buildkite.com/
Homepage response
HTTP 200, after 1 redirect
TLS
TLSv1.3, HTTP/2
Certificate
Amazon, 394-day validity, expiring 2027-01-08
CDN or edge
Amazon CloudFront
Platform or framework
Astro
DNS operators
Amazon Route 53
HSTS
max-age 365 days
DMARC policy
p=quarantine
Homepage HTML
362 KB, gzip
Images on homepage
111 (svg 59, png 34, webp 17)

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

Observed 24

  • HTTP requests move to HTTPS
  • HSTS kept for at least a year
  • TLS 1.3 negotiated
  • Certificate has more than 14 days left
  • CAA records limit who can issue certificates
  • DMARC policy enforces quarantine or reject
  • X-Content-Type-Options: nosniff
  • Framing restricted
  • Referrer-Policy set
  • HTTP/2 negotiated
  • HTML compressed
  • Static files cached for 30 days or more
  • Modern image formats in use
  • Offscreen images lazy-loaded
  • No render-blocking scripts in <head>
  • robots.txt published
  • XML sitemap discoverable
  • Reachable over IPv6
  • Canonical URL declared
  • Meta description written
  • Mobile viewport configured
  • Social preview image set
  • Page language declared
  • At most one redirect to the homepage

Own buildkite.com?

Re-run the checks after a change, or verify the site in a free workspace to save reports with history, compare against similar sites and competitors, and track a private action plan. What owners get.

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

Compare with other Programming & Software sites