surveroid.jp

Readiness by lane

Green: surveroid.jp. Thin bar: Data & Analytics peer median.

Priority fixes for surveroid.jp

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 no max-age, 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.

   49% of Data & Analytics 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 · 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.

   54% of Data & Analytics peers do this.

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

3. Priority 3 · Accelerate

   Modern image formats in use

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

   31% of Data & Analytics peers do this.

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

4. Priority 4 · Accelerate

   HTTP/3 advertised

   Observed: The homepage did not advertise HTTP/3 through an Alt-Svc header.

   What to do: Turn on HTTP/3 at your CDN. Browsers fall back to HTTP/2 automatically, so the risk is low.

   37% of Data & Analytics peers do this.

   Guide: CDN Guide for Website Owners

What surveroid.jp already does well

Practices fewer than half of Data & Analytics peers use.

• HSTS kept for at least a yearHSTS with a 365-day max-age.34% of peers
• DMARC policy enforces quarantine or rejectDMARC policy p=quarantine.38% of peers
• X-Content-Type-Options: nosniffnosniff header present.46% of peers

What we saw

Homepage checked

https://surveroid.jp/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

Amazon, 197-day validity, expiring 2027-02-19

DNS operators

Amazon Route 53

HSTS

max-age 365 days

DMARC policy

p=quarantine

Homepage HTML

135 KB, gzip

Images on homepage

120 (png 68, svg 49, jpg 3)

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 Data & Analytics sites

• artificialanalysis.ai66
• buholegal.com67
• dak.gg67
• metatft.com67
• technical.city67

Data & Analytics readiness benchmark