love.ru

Readiness by lane

Green: love.ru. Thin bar: Dating Apps peer median.

Priority fixes for love.ru

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

1. Priority 1 · Accelerate

   No render-blocking scripts in <head>

   Observed: The homepage <head> loaded 7 external scripts without async or defer.

   Why it matters: A plain <script src> in the head stops the browser from showing anything until that file has downloaded and run.

   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.

   54% of Dating Apps peers do this. Limit: Based on the homepage HTML delivered to an automated client; scripts that run later were not executed.

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

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.

   22% of Dating Apps peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

3. Priority 3 · Accelerate

   Modern image formats in use

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

   27% of Dating Apps peers do this.

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

4. Priority 4 · Harden

   Certificate lifetime of 100 days or less

   Observed: The certificate from GlobalSign nv-sa had a 396-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.

   64% of Dating Apps peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

What love.ru already does well

Practices fewer than half of Dating Apps peers use.

• HTTP/3 advertisedHTTP/3 advertised.18% of peers
• Reachable over IPv6IPv6 address published.34% of peers
• Static files cached for 30 days or moreLong-lived caching on static files.35% of peers

What we saw

Homepage checked

https://love.ru/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

GlobalSign, 396-day validity, expiring 2026-11-11

DNS operators

1 self-run or other nameserver domain

DMARC policy

p=reject

Homepage HTML

38 KB, br

Images on homepage

22 (svg 11, png 9, gif 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 Dating Apps sites

• beboo.ru67
• cougarillo.com66
• lablue.de66
• mawada.net66
• rande.cz66

Dating Apps readiness benchmark