frontiersin.org

Readiness by lane

Green: frontiersin.org. Thin bar: Online Publishing peer median.

Priority fixes for frontiersin.org

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

1. Priority 1 · Harden

   HSTS kept for at least a year

   Observed: The homepage response did not include a Strict-Transport-Security header.

   Why it matters: HSTS tells browsers to use HTTPS for your host on every later visit, which removes the window where a first HTTP request can be intercepted.

   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.

   On Azure Front Door/CDN: Add a response header action in a Front Door rule set.

   27% of Online Publishing peers do this. Limit: Read from the homepage response only; other pages or regions may send different headers.

   Guide: HTTPS and TLS Guide for Website Owners

2. Priority 2 · Accelerate

   Offscreen images lazy-loaded

   Observed: The homepage had 29 images and none used loading="lazy".

   What to do: Add loading="lazy" to images below the fold. Do not lazy-load the main hero image, because that delays the largest visible element.

   58% of Online Publishing peers do this.

   Guide: Lazy Loading Without Broken Pages

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

   41% of Online Publishing peers do this.

   Guide: CDN Guide for Website Owners

4. Priority 4 · Harden

   Certificate lifetime of 100 days or less

   Observed: The certificate from GoDaddy.com, Inc. had a 397-day validity period, longer than the 100-day maximum that applies from March 2027.

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

   71% of Online Publishing peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

What frontiersin.org already does well

Practices fewer than half of Online Publishing peers use.

• DMARC policy enforces quarantine or rejectDMARC policy p=reject.20% of peers
• Modern image formats in useWebP or AVIF images detected.38% of peers
• No render-blocking scripts in <head>Head scripts load without blocking.45% of peers

What we saw

Homepage checked

https://www.frontiersin.org/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

GoDaddy, 397-day validity, expiring 2026-11-28

CDN or edge

Azure Front Door/CDN

Platform or framework

Nuxt

DNS operators

Azure DNS

DMARC policy

p=reject

Homepage HTML

244 KB, gzip

Images on homepage

29 (webp 25, png 12, jpg 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 Online Publishing sites

• factfeed.com68
• gocomics.com68
• hjweb.jp68
• lasi.lv69
• meillakotona.fi69

Online Publishing readiness benchmark