cloudsign.jp

Readiness by lane

Green: cloudsign.jp. Thin bar: Business Tools peer median.

Priority fixes for cloudsign.jp

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

1. Priority 1 · Accelerate

   HTML compressed

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

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

   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 2 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 181 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 cloudsign.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
• HSTS kept for at least a yearHSTS with a 730-day max-age covering subdomains.45% of peers
• Framing restrictedFraming controls present.48% of peers

What we saw

Homepage checked

https://www.cloudsign.jp/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

Amazon, 197-day validity, expiring 2027-03-10

CDN or edge

Amazon CloudFront

Platform or framework

WordPress

DNS operators

Amazon Route 53

HSTS

max-age 730 days, includeSubDomains, preload

DMARC policy

p=quarantine

Homepage HTML

150 KB, uncompressed

Images on homepage

181 (svg 149, png 18, jpg 8, webp 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 Business Tools sites

• ati.su63
• bouncy.ai64
• livehealth.solutions63
• reservo.cl64
• takipciarttirma.net63

Business Tools readiness benchmark