pulkovoairport.ru

Readiness by lane

Green: pulkovoairport.ru. Thin bar: Airlines peer median.

Priority fixes for pulkovoairport.ru

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

1. Priority 1 · Accelerate

   HTML compressed

   Observed: The homepage HTML (135 KB) was delivered without gzip, Brotli or zstd compression.

   Why it matters: Compression usually shrinks HTML several times over, so the first bytes of the page arrive sooner on slow connections.

   What to do: Enable Brotli or gzip for text responses (HTML, CSS, JavaScript, JSON, SVG) at the CDN or origin.

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

   Guide: How to Set a Website Performance Budget That Teams Can Keep

2. Priority 2 · Harden

   DMARC policy enforces quarantine or reject

   Observed: The DMARC policy for pulkovoairport.ru was p=none, which asks receivers to take no action on failing mail.

   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.

   63% of Airlines peers do this.

   Guide: A Practical Website Health Check for Owners

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.

   76% of Airlines peers do this.

   Guide: XML Sitemap Guide: Include Only URLs You Stand Behind

4. Priority 4 · Accelerate

   Modern image formats in use

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

   31% of Airlines peers do this.

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

What pulkovoairport.ru already does well

Practices fewer than half of Airlines peers use.

• Nameservers spread across providersNameservers spread across more than one operator.19% of peers
• Static files cached for 30 days or moreLong-lived caching on static files.40% of peers
• No render-blocking scripts in <head>Head scripts load without blocking.45% of peers

What we saw

Homepage checked

https://pulkovoairport.ru/

Homepage response

HTTP 200

Platform or framework

Bitrix

DNS operators

2 self-run or other nameserver domains

HSTS

max-age 730 days

DMARC policy

p=none

Homepage HTML

135 KB, uncompressed

Images on homepage

12 (png 8, svg 3)

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

Compare with other Airlines sites

• aerlingus.com40
• belavia.by43
• csair.com42
• skymark.co.jp36
• svo.aero48

Airlines readiness benchmark