yanmaga.jp

Readiness by lane

Green: yanmaga.jp. Thin bar: Online Publishing peer median.

Priority fixes for yanmaga.jp

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

1. Priority 1 · Accelerate

   HTML compressed

   Observed: The homepage HTML (200 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.

   On Amazon CloudFront: Enable Compress objects automatically on the cache behaviour.

   94% of Online Publishing 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 · Accelerate

   Modern image formats in use

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

   38% of Online Publishing peers do this.

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

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

   45% of Online Publishing peers do this.

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

4. Priority 4 · Accelerate

   Offscreen images lazy-loaded

   Observed: The homepage had 208 images and none used loading="lazy".

   What to do: Add loading="lazy" to images below the fold. Do not lazy-load the main hero image, because that delays the largest visible element.

   58% of Online Publishing peers do this.

   Guide: Lazy Loading Without Broken Pages

What yanmaga.jp already does well

Practices fewer than half of Online Publishing peers use.

• Referrer-Policy setReferrer-Policy present.20% of peers
• HSTS kept for at least a yearHSTS with a 730-day max-age covering subdomains.27% of peers
• Framing restrictedFraming controls present.37% of peers

What we saw

Homepage checked

https://yanmaga.jp/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

Amazon, 393-day validity, expiring 2027-01-20

CDN or edge

Amazon CloudFront

DNS operators

Amazon Route 53

HSTS

max-age 730 days, includeSubDomains

DMARC policy

p=none

Homepage HTML

200 KB, uncompressed

Images on homepage

208 (jpg 170, svg 31, png 7)

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 Online Publishing sites

• aikatu.jp60
• moneyvloger.com62
• readnovelfull.com62
• souspark.ru62
• teller.jp61

Online Publishing readiness benchmark