Catalog / code4japan.org
63

SEO audit for code4japan.org

一般社団法人コード・フォー・ジャパン | Code for Japan

otherNext.js

Health 63/100 (fair) · 50 pages crawled · generated 2026-08-26

Download Markdown report (feed to ChatGPT / Claude / Cursor)

Code for Japanは市民（Civic）が技術（Tech）を使って地域や身近な困りごとを解決する、シビックテック活動に取り組む団体です。Code for Japanの仲間と一緒にシビックテックを楽しみましょう！

Screenshot of code4japan.org
50
pages crawled
49
indexable pages
2
errors
236
warnings
523
notices
0
orphan pages
1
broken links
Category breakdown
CategoryScoreErrorsWarningsNotices
Links 78 1 33 0
Crawlability 98 1 0 2
Agent Readiness 71 0 49 56
Canonical 71 0 49 0
Performance 71 0 49 102
Content 82 0 30 55
Duplicate 86 0 23 23
Headings 99 0 2 12
Titles 99 0 1 0
Images 100 0 0 53
Meta Description 100 0 0 22
Security 100 0 0 99
Sitemap 100 0 0 48
Structured Data 100 0 0 49
URL 100 0 0 2
Findings

Errors (2 rules)

error Broken internal link (target 4xx/5xx)

Rule links.broken_internal · Links · 1 occurrence(s)

error Client error (4xx) response

Rule status.4xx · Crawlability · 1 occurrence(s)

Warnings (9 rules)

warning Control has no accessible name

Rule agent.control_no_name · Agent Readiness · 49 occurrence(s)

warning Missing canonical tag

Rule canonical.missing · Canonical · 49 occurrence(s)

warning Thin content (low word count)

Rule content.thin · Content · 30 occurrence(s)

warning Duplicate page content

Rule duplicate.content · Duplicate · 2 occurrence(s)

warning Duplicate <title> across pages

Rule duplicate.title · Duplicate · 21 occurrence(s)

warning Missing <h1>

Rule h1.missing · Headings · 2 occurrence(s)

warning Hero/LCP image is lazy-loaded (loading=lazy delays LCP)

Rule images.no_lazy_lcp_candidate · Performance · 49 occurrence(s)

  • https://www.code4japan.org/ — the likely hero/LCP image (codeforjapan_logo.6ccc2171.svg) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.
  • https://www.code4japan.org/aboutus — the likely hero/LCP image (codeforjapan_logo.6ccc2171.svg) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.
  • https://www.code4japan.org/aboutus/team — the likely hero/LCP image (codeforjapan_logo.6ccc2171.svg) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.
  • https://www.code4japan.org/activity — the likely hero/LCP image (codeforjapan_logo.6ccc2171.svg) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.
  • https://www.code4japan.org/activity/community — the likely hero/LCP image (codeforjapan_logo.6ccc2171.svg) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.
  • https://www.code4japan.org/brigade — the likely hero/LCP image (codeforjapan_logo.6ccc2171.svg) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.
  • https://www.code4japan.org/brigade/all — the likely hero/LCP image (codeforjapan_logo.6ccc2171.svg) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.
  • https://www.code4japan.org/en — the likely hero/LCP image (codeforjapan_logo.6ccc2171.svg) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.
  • https://www.code4japan.org/en/aboutus — the likely hero/LCP image (codeforjapan_logo.6ccc2171.svg) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.
  • https://www.code4japan.org/en/activity — the likely hero/LCP image (codeforjapan_logo.6ccc2171.svg) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.
  • https://www.code4japan.org/en/activity/community — the likely hero/LCP image (codeforjapan_logo.6ccc2171.svg) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.
  • https://www.code4japan.org/en/brigade — the likely hero/LCP image (codeforjapan_logo.6ccc2171.svg) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.
  • https://www.code4japan.org/en/case — the likely hero/LCP image (codeforjapan_logo.6ccc2171.svg) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.
  • https://www.code4japan.org/en/news — the likely hero/LCP image (codeforjapan_logo.6ccc2171.svg) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.
  • https://www.code4japan.org/en/voice — the likely hero/LCP image (codeforjapan_logo.6ccc2171.svg) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.
  • https://www.code4japan.org/news — the likely hero/LCP image (codeforjapan_logo.6ccc2171.svg) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.
  • https://www.code4japan.org/news/civic-tech-fun-fun-report-2026-05 — the likely hero/LCP image (codeforjapan_logo.6ccc2171.svg) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.
  • https://www.code4japan.org/news/civic-tech-fun-fun-report-2026-06 — the likely hero/LCP image (codeforjapan_logo.6ccc2171.svg) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.
  • https://www.code4japan.org/news/civic-tech-fun-fun-report-2026-07 — the likely hero/LCP image (codeforjapan_logo.6ccc2171.svg) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.
  • https://www.code4japan.org/news/tomodachi_2025 — the likely hero/LCP image (codeforjapan_logo.6ccc2171.svg) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.
  • https://www.code4japan.org/privacy-policy — the likely hero/LCP image (codeforjapan_logo.6ccc2171.svg) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.
  • https://www.code4japan.org/privacy-policy-20200416/ — the likely hero/LCP image (codeforjapan_logo.6ccc2171.svg) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.
  • https://www.code4japan.org/security — the likely hero/LCP image (codeforjapan_logo.6ccc2171.svg) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.
  • https://www.code4japan.org/teikan — the likely hero/LCP image (codeforjapan_logo.6ccc2171.svg) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.
  • https://www.code4japan.org/voice — the likely hero/LCP image (codeforjapan_logo.6ccc2171.svg) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.

warning Internal link points to a redirect

Rule links.redirect_target · Links · 33 occurrence(s)

warning Title likely truncated in SERP (too wide)

Rule title.too_long · Titles · 1 occurrence(s)

Notices (21 rules)

notice Heading levels skip a level

Rule agent.heading_skip · Agent Readiness · 8 occurrence(s)

notice No llms.txt for AI agents

Rule agent.llms_txt_missing · Agent Readiness · 1 occurrence(s)

notice No main landmark for AI agents

Rule agent.no_main_landmark · Agent Readiness · 47 occurrence(s)

notice Low text-to-HTML ratio

Rule content.low_ratio · Content · 41 occurrence(s)

notice Main text is hard to read (low Flesch Reading Ease)

Rule content.readability_poor · Content · 14 occurrence(s)

  • https://www.code4japan.org/en/aboutus — this page reads as difficult (Flesch Reading Ease 45, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.
  • https://www.code4japan.org/en/aboutus/team — this page reads as very difficult (Flesch Reading Ease -76, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.
  • https://www.code4japan.org/en/activity — this page reads as very difficult (Flesch Reading Ease 26, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.
  • https://www.code4japan.org/en/activity/civictech — this page reads as difficult (Flesch Reading Ease 44, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.
  • https://www.code4japan.org/en/activity/community — this page reads as difficult (Flesch Reading Ease 42, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.
  • https://www.code4japan.org/en/activity/donation — this page reads as very difficult (Flesch Reading Ease 25, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.
  • https://www.code4japan.org/en/activity/global — this page reads as difficult (Flesch Reading Ease 43, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.
  • https://www.code4japan.org/en/activity/govtech — this page reads as very difficult (Flesch Reading Ease 12, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.
  • https://www.code4japan.org/en/activity/gussuri — this page reads as very difficult (Flesch Reading Ease 26, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.
  • https://www.code4japan.org/en/activity/ikunowa — this page reads as very difficult (Flesch Reading Ease 5, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.
  • https://www.code4japan.org/en/activity/jibungoto-planet — this page reads as very difficult (Flesch Reading Ease 25, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.
  • https://www.code4japan.org/en/activity/summit — this page reads as difficult (Flesch Reading Ease 34, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.
  • https://www.code4japan.org/en/brigade — this page reads as difficult (Flesch Reading Ease 40, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.
  • https://www.code4japan.org/en/case — this page reads as very difficult (Flesch Reading Ease 6, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.

notice Duplicate meta description across pages

Rule duplicate.meta_desc · Duplicate · 23 occurrence(s)

notice Multiple <h1> elements

Rule h1.multiple · Headings · 12 occurrence(s)

notice Image filename is generic/auto-generated (missed image-search signal)

Rule images.generic_filename · Images · 17 occurrence(s)

  • https://www.code4japan.org/activity — 1 image(s) use a generic/auto-generated filename (e.g. IMG_1234.jpg, photo1.png, a bare UUID). Google reads the filename as a signal of image content, so rename files descriptively (hyphen-separated words) before upload.
  • https://www.code4japan.org/activity/community — 1 image(s) use a generic/auto-generated filename (e.g. IMG_1234.jpg, photo1.png, a bare UUID). Google reads the filename as a signal of image content, so rename files descriptively (hyphen-separated words) before upload.
  • https://www.code4japan.org/activity/global — 1 image(s) use a generic/auto-generated filename (e.g. IMG_1234.jpg, photo1.png, a bare UUID). Google reads the filename as a signal of image content, so rename files descriptively (hyphen-separated words) before upload.
  • https://www.code4japan.org/activity/partner — 1 image(s) use a generic/auto-generated filename (e.g. IMG_1234.jpg, photo1.png, a bare UUID). Google reads the filename as a signal of image content, so rename files descriptively (hyphen-separated words) before upload.
  • https://www.code4japan.org/en/activity — 1 image(s) use a generic/auto-generated filename (e.g. IMG_1234.jpg, photo1.png, a bare UUID). Google reads the filename as a signal of image content, so rename files descriptively (hyphen-separated words) before upload.
  • https://www.code4japan.org/en/activity/community — 1 image(s) use a generic/auto-generated filename (e.g. IMG_1234.jpg, photo1.png, a bare UUID). Google reads the filename as a signal of image content, so rename files descriptively (hyphen-separated words) before upload.
  • https://www.code4japan.org/en/case — 6 image(s) use a generic/auto-generated filename (e.g. IMG_1234.jpg, photo1.png, a bare UUID). Google reads the filename as a signal of image content, so rename files descriptively (hyphen-separated words) before upload.
  • https://www.code4japan.org/en/news — 1 image(s) use a generic/auto-generated filename (e.g. IMG_1234.jpg, photo1.png, a bare UUID). Google reads the filename as a signal of image content, so rename files descriptively (hyphen-separated words) before upload.
  • https://www.code4japan.org/en/voice — 8 image(s) use a generic/auto-generated filename (e.g. IMG_1234.jpg, photo1.png, a bare UUID). Google reads the filename as a signal of image content, so rename files descriptively (hyphen-separated words) before upload.
  • https://www.code4japan.org/news — 1 image(s) use a generic/auto-generated filename (e.g. IMG_1234.jpg, photo1.png, a bare UUID). Google reads the filename as a signal of image content, so rename files descriptively (hyphen-separated words) before upload.
  • https://www.code4japan.org/news/activityreport — 1 image(s) use a generic/auto-generated filename (e.g. IMG_1234.jpg, photo1.png, a bare UUID). Google reads the filename as a signal of image content, so rename files descriptively (hyphen-separated words) before upload.
  • https://www.code4japan.org/news/announcement — 3 image(s) use a generic/auto-generated filename (e.g. IMG_1234.jpg, photo1.png, a bare UUID). Google reads the filename as a signal of image content, so rename files descriptively (hyphen-separated words) before upload.
  • https://www.code4japan.org/news/civic-tech-fun-fun-report-2026-06 — 1 image(s) use a generic/auto-generated filename (e.g. IMG_1234.jpg, photo1.png, a bare UUID). Google reads the filename as a signal of image content, so rename files descriptively (hyphen-separated words) before upload.
  • https://www.code4japan.org/news/civic-tech-fun-fun-report-2026-07 — 1 image(s) use a generic/auto-generated filename (e.g. IMG_1234.jpg, photo1.png, a bare UUID). Google reads the filename as a signal of image content, so rename files descriptively (hyphen-separated words) before upload.
  • https://www.code4japan.org/news/media — 11 image(s) use a generic/auto-generated filename (e.g. IMG_1234.jpg, photo1.png, a bare UUID). Google reads the filename as a signal of image content, so rename files descriptively (hyphen-separated words) before upload.
  • https://www.code4japan.org/news/tomodachi_2025 — 1 image(s) use a generic/auto-generated filename (e.g. IMG_1234.jpg, photo1.png, a bare UUID). Google reads the filename as a signal of image content, so rename files descriptively (hyphen-separated words) before upload.
  • https://www.code4japan.org/voice — 8 image(s) use a generic/auto-generated filename (e.g. IMG_1234.jpg, photo1.png, a bare UUID). Google reads the filename as a signal of image content, so rename files descriptively (hyphen-separated words) before upload.

notice Images without width/height (layout shift / CLS)

Rule images.missing_dimensions · Images · 36 occurrence(s)

notice Meta description too long

Rule meta_desc.too_long · Meta Description · 2 occurrence(s)

notice Meta description too short

Rule meta_desc.too_short · Meta Description · 20 occurrence(s)

notice Legacy image format (jpg/png/gif) with no next-gen fallback

Rule perf.images_legacy_format · Performance · 49 occurrence(s)

  • https://www.code4japan.org/ — 3 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • https://www.code4japan.org/aboutus — 4 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • https://www.code4japan.org/aboutus/team — 34 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • https://www.code4japan.org/activity — 9 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • https://www.code4japan.org/activity/community — 2 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • https://www.code4japan.org/brigade — 3 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • https://www.code4japan.org/brigade/all — 65 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • https://www.code4japan.org/en — 3 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • https://www.code4japan.org/en/aboutus — 4 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • https://www.code4japan.org/en/activity — 7 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • https://www.code4japan.org/en/activity/community — 2 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • https://www.code4japan.org/en/brigade — 3 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • https://www.code4japan.org/en/case — 12 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • https://www.code4japan.org/en/news — 10 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • https://www.code4japan.org/en/voice — 13 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • https://www.code4japan.org/news — 10 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • https://www.code4japan.org/news/civic-tech-fun-fun-report-2026-05 — 3 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • https://www.code4japan.org/news/civic-tech-fun-fun-report-2026-06 — 3 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • https://www.code4japan.org/news/civic-tech-fun-fun-report-2026-07 — 3 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • https://www.code4japan.org/news/tomodachi_2025 — 4 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • https://www.code4japan.org/privacy-policy — 1 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • https://www.code4japan.org/privacy-policy-20200416/ — 1 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • https://www.code4japan.org/security — 3 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • https://www.code4japan.org/teikan — 1 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • https://www.code4japan.org/voice — 13 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.

notice Large HTML document

Rule perf.large_html · Performance · 2 occurrence(s)

notice No Last-Modified header (no conditional GET for unchanged pages)

Rule perf.no_last_modified · Performance · 49 occurrence(s)

  • https://www.code4japan.org/ — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
  • https://www.code4japan.org/aboutus — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
  • https://www.code4japan.org/aboutus/team — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
  • https://www.code4japan.org/activity — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
  • https://www.code4japan.org/activity/community — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
  • https://www.code4japan.org/brigade — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
  • https://www.code4japan.org/brigade/all — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
  • https://www.code4japan.org/en — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
  • https://www.code4japan.org/en/aboutus — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
  • https://www.code4japan.org/en/activity — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
  • https://www.code4japan.org/en/activity/community — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
  • https://www.code4japan.org/en/brigade — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
  • https://www.code4japan.org/en/case — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
  • https://www.code4japan.org/en/news — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
  • https://www.code4japan.org/en/voice — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
  • https://www.code4japan.org/news — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
  • https://www.code4japan.org/news/civic-tech-fun-fun-report-2026-05 — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
  • https://www.code4japan.org/news/civic-tech-fun-fun-report-2026-06 — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
  • https://www.code4japan.org/news/civic-tech-fun-fun-report-2026-07 — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
  • https://www.code4japan.org/news/tomodachi_2025 — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
  • https://www.code4japan.org/privacy-policy — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
  • https://www.code4japan.org/privacy-policy-20200416/ — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
  • https://www.code4japan.org/security — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
  • https://www.code4japan.org/teikan — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
  • https://www.code4japan.org/voice — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.

notice Slow server response

Rule perf.slow_response · Performance · 2 occurrence(s)

notice URL redirects to another URL

Rule redirect.single · Crawlability · 2 occurrence(s)

notice No structured data detected

Rule schema.none · Structured Data · 49 occurrence(s)

notice Missing recommended security headers

Rule security.missing_headers · Security · 50 occurrence(s)

notice target=_blank link without rel=noopener (tab-napping)

Rule security.unsafe_cross_origin_links · Security · 49 occurrence(s)

notice Indexable page not listed in sitemap

Rule sitemap.orphan_not_listed · Sitemap · 48 occurrence(s)

notice Underscores in URL path (prefer hyphens)

Rule url.underscores · URL · 2 occurrence(s)

Pages (showing 50 of 50)
URLStatusIndexableWordsIn-links
https://www.code4japan.org/aboutus
団体概要 | Code for Japan		 200 yes 133 50
https://www.code4japan.org/activity
活動 | Code for Japan		 200 yes 107 50
https://www.code4japan.org/activity/community
コミュニティ | 活動 | Code for Japan		 200 yes 117 50
https://www.code4japan.org/activity/donation
寄付 | 活動 | Code for Japan		 200 yes 86 50
https://www.code4japan.org/activity/partner
法人協賛 | 活動 | Code for Japan		 200 yes 102 50
https://www.code4japan.org/brigade
ブリゲード | Code for Japan		 200 yes 109 50
https://www.code4japan.org/news
ニュース | Code for Japan		 200 yes 159 50
https://www.code4japan.org/news/activityreport
活動レポート一覧 | ニュース | Code for Japan		 200 yes 168 50
https://www.code4japan.org/news/announcement
お知らせ一覧 | ニュース | Code for Japan		 200 yes 126 50
https://www.code4japan.org/news/media
メディア掲載一覧 | ニュース | Code for Japan		 200 yes 126 50
https://www.code4japan.org/privacy-policy
プライバシーポリシー | Code for Japan		 200 yes 134 50
https://www.code4japan.org/security
情報セキュリティについて | Code for Japan		 200 yes 99 50
https://www.code4japan.org/
一般社団法人コード・フォー・ジャパン | Code for Japan		 200 yes 349 31
https://www.code4japan.org/aboutus/team
一般社団法人コード・フォー・ジャパン | Code for Japan		 200 yes 271 31
https://www.code4japan.org/voice
インタビュー | Code for Japan		 200 yes 136 31
https://www.code4japan.org/news/tomodachi_2025
学生がプロダクトのチーム開発を通じて、グローバルに挑む ——TOMODACHI Boeing Entrepreneurship Seminar | ニュース | Code for Japan		 200 yes 192 8
https://www.code4japan.org/news/civic-tech-fun-fun-report-2026-05
Civic Tech Fun! Fun! Report!　2026年5月号 | ニュース | Code for Japan		 200 yes 154 7
https://www.code4japan.org/news/civic-tech-fun-fun-report-2026-06
Civic Tech Fun! Fun! Report!　2026年6月号 | ニュース | Code for Japan		 200 yes 151 7
https://www.code4japan.org/news/civic-tech-fun-fun-report-2026-07
Civic Tech Fun! Fun! Report!　2026年7月号 | ニュース | Code for Japan		 200 yes 141 7
https://www.code4japan.org/en
一般社団法人コード・フォー・ジャパン | Code for Japan		 200 yes 349 19
https://www.code4japan.org/en/aboutus
団体概要 | Code for Japan		 200 yes 333 19
https://www.code4japan.org/en/aboutus/team
一般社団法人コード・フォー・ジャパン | Code for Japan		 200 yes 283 19
https://www.code4japan.org/en/activity
活動 | Code for Japan		 200 yes 277 19
https://www.code4japan.org/en/brigade
ブリゲード | Code for Japan		 200 yes 512 19
https://www.code4japan.org/en/news
ニュース | Code for Japan		 200 yes 171 19
https://www.code4japan.org/en/privacy-policy
プライバシーポリシー | Code for Japan		 200 yes 1114 19
https://www.code4japan.org/en/voice
インタビュー | Code for Japan		 200 yes 148 19
https://www.code4japan.org/brigade/all
ブリゲード | Code for Japan		 200 yes 412 2
https://www.code4japan.org/privacy-policy-20200416/
プライバシーポリシー (2020年4月16日制定版) | Code for Japan		 200 yes 161 2
https://www.code4japan.org/teikan
一般社団法人コード・フォー・ジャパン定款 | Code for Japan		 200 yes 388 2
https://www.code4japan.org/activity/civictech
シビックテックプロジェクト | 活動 | Code for Japan		 200 yes 133 4
https://www.code4japan.org/activity/tomodachi
TOMODACHI Boeing Entrepreneurship Seminar | 活動 | Code for Japan		 200 yes 206 2
https://www.code4japan.org/activity/moc
MoCデータ連携基盤 | 活動 | Code for Japan		 200 yes 130 2
https://www.code4japan.org/en/activity/donation
寄付 | 活動 | Code for Japan		 200 yes 98 3
https://www.code4japan.org/en/activity/community
Community | 活動 | Code for Japan		 200 yes 575 3
https://www.code4japan.org/activity/decidim
Decidim | 活動 | Code for Japan		 200 yes 127 1
https://www.code4japan.org/activity/global
海外連携 / 国際コミュニティ | 活動 | Code for Japan		 200 yes 132 1
https://www.code4japan.org/activity/govtech
GovTechプログラム | 活動 | Code for Japan		 200 yes 101 1
https://www.code4japan.org/activity/ikunowa
ikunowa | 活動 | Code for Japan		 200 yes 137 1
https://www.code4japan.org/activity/jibungoto-planet
カーボンフットプリント可視化アプリ | 活動 | Code for Japan		 200 yes 146 1
https://www.code4japan.org/activity/public_knowledge_engineering_studio
公共ナレッジエンジニアリング開発室 | 活動 | Code for Japan		 200 yes 162 1
https://www.code4japan.org/en/case
事例 | Code for Japan		 200 yes 105 2
https://www.code4japan.org/en/activity/civictech
Civic Tech Projects | 活動 | Code for Japan		 200 yes 574 1
https://www.code4japan.org/en/activity/global
International Collaboration / Global Community | 活動 | Code for Japan		 200 yes 355 1
https://www.code4japan.org/en/activity/govtech
Govtech | 活動 | Code for Japan		 200 yes 504 1
https://www.code4japan.org/en/activity/gussuri
Gussuri | 活動 | Code for Japan		 200 yes 1068 1
https://www.code4japan.org/en/activity/ikunowa
ikunowa | 活動 | Code for Japan		 200 yes 787 1
https://www.code4japan.org/en/activity/jibungoto-planet
Jibungoto-Planet | 活動 | Code for Japan		 200 yes 990 1
https://www.code4japan.org/en/activity/summit
Code for Japan Summit | 活動 | Code for Japan		 200 yes 356 1
https://www.code4japan.org/9dd9cd85f07942c1bd5f6ef73efdb122
404: 5秒後にトップに戻ります		 404 no 63 1

Audit your own site — free

157 checks, internal PageRank, render-diff. No signup, results in ~30s.

Scan your site →