1cs.jp

Readiness by lane

Green: 1cs.jp. Thin bar: Business Tools peer median.

Priority fixes for 1cs.jp

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

1. Priority 1 · Harden

   HSTS kept for at least a year

   Observed: The homepage response did not include a Strict-Transport-Security header.

   Why it matters: HSTS tells browsers to use HTTPS for your host on every later visit, which removes the window where a first HTTP request can be intercepted.

   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.

   45% of Business Tools peers do this. Limit: Read from the homepage response only; other pages or regions may send different headers.

   Guide: HTTPS and TLS 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.

   On WordPress: Caching plugins or your host can set long browser cache lifetimes for theme and plugin assets.

   42% of Business Tools peers do this.

   Guide: Browser Caching Guide for Website Owners

3. Priority 3 · Accelerate

   No render-blocking scripts in <head>

   Observed: The homepage <head> loaded 7 external scripts 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.

   On WordPress: Since WordPress 6.3, scripts can be registered with a defer or async loading strategy.

   46% of Business Tools 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 46 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.

   On WordPress: WordPress has added loading="lazy" to images by default since 5.5; check that your theme or a plugin has not removed it.

   62% of Business Tools peers do this.

   Guide: Lazy Loading Without Broken Pages

What 1cs.jp already does well

Practices fewer than half of Business Tools peers use.

• Modern image formats in useWebP or AVIF images detected.42% of peers
• Structured data presentJSON-LD structured data found.49% of peers
• DMARC policy enforces quarantine or rejectDMARC policy p=reject.50% of peers

What we saw

Homepage checked

https://1cs.jp/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

Amazon, 393-day validity, expiring 2027-03-18

CDN or edge

Amazon CloudFront

Platform or framework

WordPress

DNS operators

Amazon Route 53

DMARC policy

p=reject

Homepage HTML

64 KB, gzip

Images on homepage

46 (png 57, jpg 11, webp 10)

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 Business Tools sites

• jambolive.tv60
• labfacil.com60
• ma-kko.com59
• menudigital.ir59
• sayphotobooth.com60

Business Tools readiness benchmark