xfolio.jp

Readiness by lane

Green: xfolio.jp. Thin bar: Design & Content Creation peer median.

Priority fixes for xfolio.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.

   84% of Design & Content Creation 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

   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.

   57% of Design & Content Creation 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 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.

   49% of Design & Content Creation 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 223 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.

   72% of Design & Content Creation peers do this.

   Guide: Lazy Loading Without Broken Pages

What xfolio.jp already does well

Practices fewer than half of Design & Content Creation peers use.

• Content Security Policy presentContent-Security-Policy present.29% of peers
• HSTS kept for at least a yearHSTS with a 365-day max-age.37% of peers
• DMARC policy enforces quarantine or rejectDMARC policy p=reject.41% of peers

What we saw

Homepage checked

https://xfolio.jp/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

GlobalSign, 396-day validity, expiring 2027-01-09

DNS operators

Amazon Route 53

HSTS

max-age 365 days

DMARC policy

p=reject

Homepage HTML

262 KB, br

Images on homepage

223 (webp 197, svg 14, png 7, gif 5)

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 Design & Content Creation sites

• deviantart.com65
• facee.ru65
• stealthwriter.ai66
• vibes.ai66
• vikasedit.com66

Design & Content Creation readiness benchmark