estama.jp

Readiness by lane

Green: estama.jp. Thin bar: Dating Apps peer median.

Priority fixes for estama.jp

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

1. Priority 1 · Enable

   Mobile viewport configured

   Observed: The homepage had no viewport meta tag, so phones may render it zoomed out.

   Why it matters: Without it, phones render the page at desktop width and shrink it, which makes text tiny and hard to use.

   What to do: Add <meta name="viewport" content="width=device-width, initial-scale=1"> and check the layout on small screens.

   79% 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: Responsive Web Design Checklist for Real Devices

2. Priority 2 · Harden

   TLS 1.3 negotiated

   Observed: The TLS connection negotiated TLSv1.2.

   What to do: Enable TLS 1.3 on your CDN or server. Keep TLS 1.2 available for older clients unless you have checked your audience.

   82% of Dating Apps peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

3. Priority 3 · Accelerate

   Static files cached for 30 days or more

   Observed: A same-site stylesheet or script was cacheable for no max-age, short of the 30-day benchmark.

   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.

   35% of Dating Apps peers do this.

   Guide: Browser Caching Guide for Website Owners

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

What estama.jp already does well

Practices fewer than half of Dating Apps peers use.

• CAA records limit who can issue certificatesCAA limits issuance to amazon.com, letsencrypt.org, sectigo.com.8.3% of peers
• Modern image formats in useWebP or AVIF images detected.27% of peers
• Offscreen images lazy-loadedNative lazy loading in use.31% of peers

What we saw

Homepage checked

https://estama.jp/

Homepage response

HTTP 200

TLS

TLSv1.2, HTTP/2

Certificate

GoGetSSL, 198-day validity, expiring 2027-01-13

DNS operators

Amazon Route 53

DMARC policy

p=quarantine

Homepage HTML

120 KB, gzip

Images on homepage

121 (jpg 105, png 16)

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

• colombiancupid.com59
• divineva.com60
• internationalcupid.com59
• nekto.me59
• pcmax.jp60

Dating Apps readiness benchmark