bgonair.bg

Readiness by lane

Green: bgonair.bg. Thin bar: News & Media peer median.

Priority fixes for bgonair.bg

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 1 hours, 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 WordPress: Caching plugins or your host can set long browser cache lifetimes for theme and plugin assets.

   60% of News & Media 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 · Accelerate

   Modern image formats in use

   Observed: The homepage had 124 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.

   On WordPress: WordPress has supported WebP uploads since 5.8 and AVIF since 6.5; image plugins or the host can convert existing images.

   44% of News & Media peers do this.

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

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

   42% of News & Media peers do this.

   Guide: A Practical Website Health Check for Owners

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

   36% of News & Media peers do this.

   Guide: CDN Guide for Website Owners

What bgonair.bg already does well

Practices fewer than half of News & Media peers use.

• HSTS kept for at least a yearHSTS with a 365-day max-age covering subdomains.35% of peers
• DMARC policy enforces quarantine or rejectDMARC policy p=quarantine.37% of peers
• No render-blocking scripts in <head>Head scripts load without blocking.42% of peers

What we saw

Homepage checked

https://www.bgonair.bg/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

Let's Encrypt, 89-day validity, expiring 2027-01-16

Platform or framework

WordPress

DNS operators

1 self-run or other nameserver domain

HSTS

max-age 365 days, includeSubDomains

DMARC policy

p=quarantine

Homepage HTML

126 KB, gzip

Images on homepage

124 (jpg 77, svg 45, 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 News & Media sites

• arstechnica.com70
• barandbench.com70
• bb.lv70
• birgun.net70
• bladna.nl70

News & Media readiness benchmark