notdrink.ru

Readiness by lane

Green: notdrink.ru. Thin bar: Forums & Communities peer median.

Priority fixes for notdrink.ru

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

1. Priority 1 · Enable

   XML sitemap discoverable

   Observed: No sitemap was listed in robots.txt or found at /sitemap.xml.

   Why it matters: A sitemap helps search engines find new and updated pages, especially on large or frequently updated sites.

   What to do: Generate an XML sitemap of canonical URLs, reference it in robots.txt and submit it in Google Search Console.

   61% of Forums & Communities peers do this. Limit: Only the standard location was requested, once, at the time of the check.

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

2. Priority 2 · Harden

   DMARC policy enforces quarantine or reject

   Observed: The DMARC policy for notdrink.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.

   31% of Forums & Communities peers do this.

   Guide: A Practical Website Health Check for Owners

3. Priority 3 · Accelerate

   Modern image formats in use

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

   30% of Forums & Communities peers do this.

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

4. Priority 4 · Accelerate

   No render-blocking scripts in <head>

   Observed: The homepage <head> loaded 1 external script without async or defer.

   What to do: Add defer to scripts that need the DOM, async to independent ones such as analytics, or move them to the end of the body.

   41% of Forums & Communities peers do this.

   Guide: Control Third-Party Scripts Before They Control Your Page

What notdrink.ru already does well

Practices fewer than half of Forums & Communities peers use.

• HSTS kept for at least a yearHSTS with a 365-day max-age.28% of peers
• Structured data presentJSON-LD structured data found.37% of peers
• X-Content-Type-Options: nosniffnosniff header present.47% of peers

What we saw

Homepage checked

https://notdrink.ru/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

Let's Encrypt, 89-day validity, expiring 2026-12-06

DNS operators

1 self-run or other nameserver domain

HSTS

max-age 365 days

DMARC policy

p=none

Homepage HTML

109 KB, gzip

Images on homepage

18 (jpg 28, png 3)

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 Forums & Communities sites

• girlschannel.net64
• inkbunny.net64
• mypetition.org64
• qhamian.ir64
• secrant.com64

Forums & Communities readiness benchmark