STATUS IS UPREADINESS PROFILE

Website readiness profile · Snapshot 23 October 2026

ebird.org

ebird.org's public homepage, certificate and DNS checked against 31 practices and compared with 233 Data & Analytics sites.

Readiness index
49/100

Data & Analytics median 63

Ahead of
11%

of measured Data & Analytics sites

Practices observed
11/29

2 of 31 could not be measured

Popularity band
Top 10K

Chrome UX Report top-sites list

Measured 2026-10-23 12:18:42 UTC from one location. How we measure

Readiness by lane

Green: ebird.org. Thin bar: Data & Analytics peer median.

Enable

56/100

Peers 78

Harden

38/100

Peers 56

Accelerate

67/100

Peers 63

Recover

0/100

Peers 8

Priority fixes for ebird.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.

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

  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.

    34% of Data & Analytics peers do this.

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

    63% of Data & Analytics peers do this.

  4. Priority 4 · Harden

    DMARC policy enforces quarantine or reject

    Observed: No DMARC record was found at _dmarc.ebird.org.

    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.

    38% of Data & Analytics peers do this.

What we saw

Homepage checked
https://ebird.org/
Homepage response
HTTP 200, after 1 redirect
TLS
TLSv1.3, HTTP/2
Certificate
Internet2, 199-day validity, expiring 2027-01-31
DNS operators
1 self-run or other nameserver domain
Homepage HTML
7 KB, gzip
Images on homepage
2 (jpg 2)

Limits: homepage only, one location, one moment. Header checks reflect the homepage response; other pages may differ.

All 31 checks

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

Observed 11

  • HTTP requests move to HTTPS
  • TLS 1.3 negotiated
  • Certificate has more than 14 days left
  • HTTP/2 negotiated
  • HTML compressed
  • No render-blocking scripts in <head>
  • robots.txt published
  • Meta description written
  • Mobile viewport configured
  • Page language declared
  • At most one redirect to the homepage

Not measured 2

  • Modern image formats in use
  • Offscreen images lazy-loaded

Own ebird.org?

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: ebird.org. This profile covers configuration only.

Compare with other Data & Analytics sites