ilmakiage.com

Readiness by lane

Green: ilmakiage.com. Thin bar: E-Commerce & Marketplaces peer median.

Priority fixes for ilmakiage.com

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

1. Priority 1 · Accelerate

   Static files cached for 30 days or more

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

   Why it matters: Returning visitors and later page views reuse cached files instead of downloading them again.

   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.

   On Cloudflare: Use Cache Rules to set edge and browser TTLs for static file paths.

   60% of E-Commerce & Marketplaces peers do this. Limit: Read from the homepage response only; other pages or regions may send different headers.

   Guide: Browser Caching Guide for Website Owners

2. Priority 2 · Enable

   Meta description written

   Observed: The homepage had no meta description.

   What to do: Write a short, specific description of the page for people, not a list of keywords.

   95% of E-Commerce & Marketplaces peers do this.

   Guide: Meta Titles and Descriptions That Match Search Intent

3. Priority 3 · Harden

   HSTS kept for at least a year

   Observed: Strict-Transport-Security was sent with a max-age of 0 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 Cloudflare: Enable HSTS under SSL/TLS > Edge Certificates > HTTP Strict Transport Security and raise max-age gradually.

   32% of E-Commerce & Marketplaces peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

4. Priority 4 · Enable

   Canonical URL declared

   Observed: The homepage did not declare a canonical URL.

   What to do: Add a self-referencing canonical link to every indexable page, using the final https:// URL.

   85% of E-Commerce & Marketplaces peers do this.

   Guide: Canonical Tags: A Decision Guide for Duplicate URLs

What ilmakiage.com already does well

Practices fewer than half of E-Commerce & Marketplaces peers use.

• security.txt publishedsecurity.txt with a contact found.7.6% of peers
• DMARC policy enforces quarantine or rejectDMARC policy p=quarantine.39% of peers
• Reachable over IPv6IPv6 address published.40% of peers

What we saw

Homepage checked

https://www.ilmakiage.com/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

Let's Encrypt, 89-day validity, expiring 2026-11-28

CDN or edge

Cloudflare

DNS operators

Cloudflare

HSTS

max-age 0 days, includeSubDomains, preload

DMARC policy

p=quarantine

Homepage HTML

39 KB, br

Images on homepage

0

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 E-Commerce & Marketplaces sites

• felissimo.co.jp63
• fragment.com63
• fylliana.gr63
• intersport.de63
• izumi.jp63

E-Commerce & Marketplaces readiness benchmark