pcmax.jp

Readiness by lane

Green: pcmax.jp. Thin bar: Dating Apps peer median.

Priority fixes for pcmax.jp

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

1. Priority 1 · Enable

   XML sitemap discoverable

   Observed: No sitemap was listed in robots.txt or found at /sitemap.xml.

   Why it matters: A sitemap helps search engines find new and updated pages, especially on large or frequently updated sites.

   What to do: Generate an XML sitemap of canonical URLs, reference it in robots.txt and submit it in Google Search Console.

   On WordPress: WordPress has generated a basic sitemap at /wp-sitemap.xml since 5.5; SEO plugins can replace it.

   64% of Dating Apps peers do this. Limit: Only the standard location was requested, once, at the time of the check.

   Guide: XML Sitemap Guide: Include Only URLs You Stand Behind

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

   54% of Dating Apps peers do this.

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

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

   35% of Dating Apps peers do this.

   Guide: Browser Caching Guide for Website Owners

4. Priority 4 · Harden

   HSTS kept for at least a year

   Observed: Strict-Transport-Security was sent with a max-age of 186 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 Amazon CloudFront: Attach a response headers policy with Strict-Transport-Security to each distribution.

   22% of Dating Apps peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

What pcmax.jp already does well

Practices fewer than half of Dating Apps peers use.

• Modern image formats in useWebP or AVIF images detected.27% of peers
• Structured data presentJSON-LD structured data found.29% of peers
• Offscreen images lazy-loadedNative lazy loading in use.31% of peers

What we saw

Homepage checked

https://pcmax.jp/

Homepage response

HTTP 200, after 1 redirect

TLS

TLSv1.3, HTTP/2

Certificate

DigiCert, 396-day validity, expiring 2026-11-23

CDN or edge

Amazon CloudFront

Platform or framework

WordPress

DNS operators

Amazon Route 53

HSTS

max-age 186 days

DMARC policy

p=quarantine

Homepage HTML

98 KB, gzip

Images on homepage

38 (png 12, svg 11, jpg 7, 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 Dating Apps sites

• colombiancupid.com59
• divineva.com60
• estama.jp59
• yyc.co.jp61
• zapisanisobie.pl61

Dating Apps readiness benchmark