line.me

Readiness by lane

Green: line.me. Thin bar: Social Media & Networking peer median.

Priority fixes for line.me

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

1. Priority 1 · Accelerate

   HTTP/2 negotiated

   Observed: The TLS handshake selected http/1.1 instead of HTTP/2.

   Why it matters: HTTP/2 sends many files over one connection, which speeds up pages with lots of images, styles and scripts.

   What to do: Enable HTTP/2 on your CDN or server. Most CDNs do this by default.

   On Amazon CloudFront: Choose HTTP/2 (or HTTP/2 and HTTP/3) as supported versions on the distribution.

   88% of Social Media & Networking peers do this. Limit: Certificate and protocol were observed from one vantage point; CDNs can present different certificates by region.

   Guide: CDN Guide for Website Owners

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

   55% of Social Media & Networking peers do this.

   Guide: Browser Caching Guide for Website Owners

3. Priority 3 · Harden

   HSTS kept for at least a year

   Observed: Strict-Transport-Security was sent with a max-age of 183 days, below the one-year benchmark.

   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.

   On Amazon CloudFront: Attach a response headers policy with Strict-Transport-Security to each distribution.

   38% of Social Media & Networking peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

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

   64% of Social Media & Networking peers do this.

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

What line.me already does well

Practices fewer than half of Social Media & Networking peers use.

• Nameservers spread across providersNameservers spread across more than one operator.4.7% of peers
• security.txt publishedsecurity.txt with a contact found.13% of peers
• Referrer-Policy setReferrer-Policy present.29% of peers

What we saw

Homepage checked

https://line.me/

Homepage response

HTTP 200, after 1 redirect

TLS

TLSv1.3, http/1.1

Certificate

GlobalSign, 199-day validity, expiring 2027-03-01

CDN or edge

Amazon CloudFront

DNS operators

2 self-run or other nameserver domains

HSTS

max-age 183 days

DMARC policy

p=none

Homepage HTML

35 KB, br

Images on homepage

33 (png 118, jpg 28)

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 Social Media & Networking sites

• draugiem.lv50
• getblock.me49
• pocha3.com51
• poipiku.com51
• utherverse.com47

Social Media & Networking readiness benchmark