Catalog / tsudakiyo-honpo.com
77

SEO audit for tsudakiyo-honpo.com

つだきよ本舗

other

Health 77/100 (good) · 43 pages crawled · generated 2026-07-29

Download Markdown report (feed to ChatGPT / Claude / Cursor)
Screenshot of tsudakiyo-honpo.com
43
pages crawled
25
indexable pages
0
errors
161
warnings
250
notices
4
orphan pages
0
broken links
Category breakdown
CategoryScoreErrorsWarningsNotices
Content 83 0 24 7
Meta Description 83 0 24 0
Mobile 85 0 22 7
Security 85 0 22 30
Headings 86 0 20 0
Images 87 0 19 8
Duplicate 91 0 13 0
Agent Readiness 96 0 6 7
Links 97 0 4 12
Performance 97 0 4 63
Canonical 99 0 2 9
Crawlability 99 0 1 0
Robots 100 0 0 1
Sitemap 100 0 0 1
Social 100 0 0 48
Structured Data 100 0 0 24
Titles 100 0 0 19
URL 100 0 0 14
Findings

Warnings (13 rules)

warning Control has no accessible name

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

warning Missing canonical tag

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

warning Thin content (low word count)

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

warning Homepage duplicated across protocol/host variants (no redirect)

Rule duplicate.protocol_host · Duplicate · 3 occurrence(s)

  • https://tsudakiyo-honpo.com/ — http://tsudakiyo-honpo.com/ serves the same homepage content with a 200 and no redirect — Google sees a duplicate. Pick one canonical host/scheme and 301-redirect the others.
  • https://tsudakiyo-honpo.com/ — http://www.tsudakiyo-honpo.com/ serves the same homepage content with a 200 and no redirect — Google sees a duplicate. Pick one canonical host/scheme and 301-redirect the others.
  • https://tsudakiyo-honpo.com/ — https://www.tsudakiyo-honpo.com/ serves the same homepage content with a 200 and no redirect — Google sees a duplicate. Pick one canonical host/scheme and 301-redirect the others.

warning Duplicate <title> across pages

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

warning Incomplete/empty response after retries (likely transient — re-crawl)

Rule fetch.incomplete · Crawlability · 1 occurrence(s)

warning Missing <h1>

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

warning Content-Type header doesn't match the actual content

Rule headers.content_type_mismatch · Security · 22 occurrence(s)

  • https://tsudakiyo-honpo.com/ — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • https://tsudakiyo-honpo.com/10aniv/ — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • https://tsudakiyo-honpo.com/6aniv/ — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • https://tsudakiyo-honpo.com/about/ — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • https://tsudakiyo-honpo.com/book/ — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • https://tsudakiyo-honpo.com/customer/ — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • https://tsudakiyo-honpo.com/newspapar5.html — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • https://tsudakiyo-honpo.com/profile/ — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • https://tsudakiyo-honpo.com/talk_lovekove/ — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • https://www.tsudakiyo-honpo.com/ — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • https://www.tsudakiyo-honpo.com/10aniv/ — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • https://www.tsudakiyo-honpo.com/6aniv/ — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • https://www.tsudakiyo-honpo.com/about/ — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • https://www.tsudakiyo-honpo.com/book/ — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • https://www.tsudakiyo-honpo.com/customer/ — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • https://www.tsudakiyo-honpo.com/newspapar.html — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • https://www.tsudakiyo-honpo.com/newspapar2.html — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • https://www.tsudakiyo-honpo.com/newspapar4.html — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • https://www.tsudakiyo-honpo.com/newspapar5.html — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • https://www.tsudakiyo-honpo.com/privacy/ — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • https://www.tsudakiyo-honpo.com/profile/ — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • https://www.tsudakiyo-honpo.com/talk_lovekove/ — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".

warning Images missing alt text

Rule images.missing_alt · Images · 19 occurrence(s)

warning Orphan page (no internal inlinks)

Rule links.orphan · Links · 4 occurrence(s)

warning Missing meta description

Rule meta_desc.missing · Meta Description · 24 occurrence(s)

warning Missing viewport meta tag

Rule mobile.viewport_missing · Mobile · 22 occurrence(s)

warning Render-blocking script in <head> (no defer/async)

Rule perf.render_blocking · Performance · 4 occurrence(s)

Notices (25 rules)

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 · 6 occurrence(s)

notice Canonical points to a different URL

Rule canonical.non_self · Canonical · 9 occurrence(s)

notice Low text-to-HTML ratio

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

notice Missing <!DOCTYPE html> (quirks-mode rendering risk)

Rule encoding.doctype_missing · Content · 2 occurrence(s)

notice Missing html lang attribute

Rule i18n.lang_missing · Mobile · 7 occurrence(s)

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

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

  • https://tsudakiyo-honpo.com/ — 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://tsudakiyo-honpo.com/profile/ — 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.tsudakiyo-honpo.com/ — 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.tsudakiyo-honpo.com/profile/ — 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.

notice Likely hero image lacks fetchpriority=high

Rule images.hero_no_fetchpriority · Performance · 24 occurrence(s)

  • https://tsudakiyo-honpo.com/ — the likely hero/LCP image (head01.jpg) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
  • https://tsudakiyo-honpo.com/10aniv/ — the likely hero/LCP image (bk.jpg) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
  • https://tsudakiyo-honpo.com/6aniv/ — the likely hero/LCP image (bk6.jpg) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
  • https://tsudakiyo-honpo.com/about/ — the likely hero/LCP image (head01.jpg) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
  • https://tsudakiyo-honpo.com/book/ — the likely hero/LCP image (head01.jpg) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
  • https://tsudakiyo-honpo.com/contact/ — the likely hero/LCP image (head01.jpg) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
  • https://tsudakiyo-honpo.com/customer/ — the likely hero/LCP image (head01.jpg) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
  • https://tsudakiyo-honpo.com/newspapar5.html — the likely hero/LCP image (20th_anniversary_header.png) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
  • https://tsudakiyo-honpo.com/profile/ — the likely hero/LCP image (head01.jpg) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
  • https://tsudakiyo-honpo.com/talk_lovekove/ — the likely hero/LCP image (head01.jpg) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
  • https://www.tsudakiyo-honpo.com/ — the likely hero/LCP image (head01.jpg) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
  • https://www.tsudakiyo-honpo.com/10aniv/ — the likely hero/LCP image (bk.jpg) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
  • https://www.tsudakiyo-honpo.com/6aniv/ — the likely hero/LCP image (bk6.jpg) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
  • https://www.tsudakiyo-honpo.com/about/ — the likely hero/LCP image (head01.jpg) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
  • https://www.tsudakiyo-honpo.com/book/ — the likely hero/LCP image (head01.jpg) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
  • https://www.tsudakiyo-honpo.com/contact/ — the likely hero/LCP image (head01.jpg) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
  • https://www.tsudakiyo-honpo.com/customer/ — the likely hero/LCP image (head01.jpg) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
  • https://www.tsudakiyo-honpo.com/newspapar.html — the likely hero/LCP image (newspapar.jpg) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
  • https://www.tsudakiyo-honpo.com/newspapar2.html — the likely hero/LCP image (newspapar2.jpg) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
  • https://www.tsudakiyo-honpo.com/newspapar4.html — the likely hero/LCP image (newspapar4.jpg) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
  • https://www.tsudakiyo-honpo.com/newspapar5.html — the likely hero/LCP image (20th_anniversary_header.png) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
  • https://www.tsudakiyo-honpo.com/privacy/ — the likely hero/LCP image (tt01.gif) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
  • https://www.tsudakiyo-honpo.com/profile/ — the likely hero/LCP image (head01.jpg) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
  • https://www.tsudakiyo-honpo.com/talk_lovekove/ — the likely hero/LCP image (head01.jpg) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.

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

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

notice Internal link has no anchor text / accessible name

Rule links.no_anchor_text · Links · 2 occurrence(s)

  • https://tsudakiyo-honpo.com/ — 2 internal link(s) have no anchor text, aria-label, or image alt — they pass no keyword signal and are unusable to screen readers. Add descriptive text or an aria-label.
  • https://www.tsudakiyo-honpo.com/ — 2 internal link(s) have no anchor text, aria-label, or image alt — they pass no keyword signal and are unusable to screen readers. Add descriptive text or an aria-label.

notice Page has only one internal inlink (fragile crawl path)

Rule links.single_inlink · Links · 10 occurrence(s)

  • https://tsudakiyo-honpo.com/10aniv/ — only one internal link points here — if that source changes, this page becomes an orphan. Add more contextual internal links to strengthen the crawl path.
  • https://tsudakiyo-honpo.com/6aniv/ — only one internal link points here — if that source changes, this page becomes an orphan. Add more contextual internal links to strengthen the crawl path.
  • https://tsudakiyo-honpo.com/book/ — only one internal link points here — if that source changes, this page becomes an orphan. Add more contextual internal links to strengthen the crawl path.
  • https://tsudakiyo-honpo.com/newspapar5.html — only one internal link points here — if that source changes, this page becomes an orphan. Add more contextual internal links to strengthen the crawl path.
  • https://tsudakiyo-honpo.com/talk_lovekove/ — only one internal link points here — if that source changes, this page becomes an orphan. Add more contextual internal links to strengthen the crawl path.
  • https://www.tsudakiyo-honpo.com/10aniv/ — only one internal link points here — if that source changes, this page becomes an orphan. Add more contextual internal links to strengthen the crawl path.
  • https://www.tsudakiyo-honpo.com/6aniv/ — only one internal link points here — if that source changes, this page becomes an orphan. Add more contextual internal links to strengthen the crawl path.
  • https://www.tsudakiyo-honpo.com/book/ — only one internal link points here — if that source changes, this page becomes an orphan. Add more contextual internal links to strengthen the crawl path.
  • https://www.tsudakiyo-honpo.com/newspapar5.html — only one internal link points here — if that source changes, this page becomes an orphan. Add more contextual internal links to strengthen the crawl path.
  • https://www.tsudakiyo-honpo.com/talk_lovekove/ — only one internal link points here — if that source changes, this page becomes an orphan. Add more contextual internal links to strengthen the crawl path.

notice Missing Open Graph tags

Rule og.missing · Social · 24 occurrence(s)

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

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

  • https://tsudakiyo-honpo.com/ — 20 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://tsudakiyo-honpo.com/10aniv/ — 31 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://tsudakiyo-honpo.com/6aniv/ — 31 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://tsudakiyo-honpo.com/about/ — 15 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://tsudakiyo-honpo.com/book/ — 19 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://tsudakiyo-honpo.com/contact/ — 18 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://tsudakiyo-honpo.com/customer/ — 43 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://tsudakiyo-honpo.com/newspapar5.html — 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://tsudakiyo-honpo.com/profile/ — 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://tsudakiyo-honpo.com/talk_lovekove/ — 19 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.tsudakiyo-honpo.com/ — 20 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.tsudakiyo-honpo.com/10aniv/ — 31 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.tsudakiyo-honpo.com/6aniv/ — 31 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.tsudakiyo-honpo.com/about/ — 15 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.tsudakiyo-honpo.com/book/ — 19 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.tsudakiyo-honpo.com/contact/ — 18 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.tsudakiyo-honpo.com/customer/ — 43 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.tsudakiyo-honpo.com/newspapar.html — 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.tsudakiyo-honpo.com/newspapar2.html — 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.tsudakiyo-honpo.com/newspapar4.html — 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.tsudakiyo-honpo.com/newspapar5.html — 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.tsudakiyo-honpo.com/privacy/ — 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.tsudakiyo-honpo.com/profile/ — 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.tsudakiyo-honpo.com/talk_lovekove/ — 19 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 · 6 occurrence(s)

notice No ETag header (no conditional GET for unchanged pages)

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

  • https://tsudakiyo-honpo.com/contact/ — the response carries no ETag header — without an ETag (or Last-Modified) there is no cache-revalidation mechanism, so crawlers re-download the full body every visit. Emit an ETag (a content hash) to enable conditional If-None-Match requests.
  • https://www.tsudakiyo-honpo.com/contact/ — the response carries no ETag header — without an ETag (or Last-Modified) there is no cache-revalidation mechanism, so crawlers re-download the full body every visit. Emit an ETag (a content hash) to enable conditional If-None-Match requests.

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

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

  • https://tsudakiyo-honpo.com/contact/ — 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.tsudakiyo-honpo.com/contact/ — 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 · 5 occurrence(s)

notice robots.txt missing (root returns 404/none)

Rule robots.txt_missing · Robots · 1 occurrence(s)

  • https://tsudakiyo-honpo.com/ — robots.txt did not return a 200 at the site root — a healthy site should serve one (declare your sitemap and confirm the host serves root files)

notice No structured data detected

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

notice Missing recommended security headers

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

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

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

  • https://tsudakiyo-honpo.com/ — 8 external link(s) use target="_blank" without rel="noopener" — the opened page can hijack your tab (reverse tab-napping). Add rel="noopener noreferrer".
  • https://tsudakiyo-honpo.com/customer/ — 51 external link(s) use target="_blank" without rel="noopener" — the opened page can hijack your tab (reverse tab-napping). Add rel="noopener noreferrer".
  • https://tsudakiyo-honpo.com/talk_lovekove/ — 7 external link(s) use target="_blank" without rel="noopener" — the opened page can hijack your tab (reverse tab-napping). Add rel="noopener noreferrer".
  • https://www.tsudakiyo-honpo.com/ — 8 external link(s) use target="_blank" without rel="noopener" — the opened page can hijack your tab (reverse tab-napping). Add rel="noopener noreferrer".
  • https://www.tsudakiyo-honpo.com/customer/ — 51 external link(s) use target="_blank" without rel="noopener" — the opened page can hijack your tab (reverse tab-napping). Add rel="noopener noreferrer".
  • https://www.tsudakiyo-honpo.com/talk_lovekove/ — 7 external link(s) use target="_blank" without rel="noopener" — the opened page can hijack your tab (reverse tab-napping). Add rel="noopener noreferrer".

notice Indexable page not listed in sitemap

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

notice Title is very short

Rule title.too_short · Titles · 19 occurrence(s)

notice Missing Twitter Card tag

Rule twitter.missing · Social · 24 occurrence(s)

notice Underscores in URL path (prefer hyphens)

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

Pages (showing 43 of 43)
URLStatusIndexableWordsIn-links
https://www.tsudakiyo-honpo.com/
つだきよ本舗		 200 yes 59 10
https://www.tsudakiyo-honpo.com/about/
つだきよ本舗		 200 yes 26 7
https://www.tsudakiyo-honpo.com/contact/
つだきよ本舗		 200 yes 8 7
https://www.tsudakiyo-honpo.com/customer/
つだきよ本舗 お取引先		 200 yes 62 7
https://www.tsudakiyo-honpo.com/profile/
つだきよ本舗 プロフィール		 200 yes 43 7
https://tsudakiyo-honpo.com/
つだきよ本舗		 200 yes 59 8
https://tsudakiyo-honpo.com/about/
つだきよ本舗		 200 yes 26 7
https://tsudakiyo-honpo.com/contact/
つだきよ本舗		 200 yes 8 7
https://tsudakiyo-honpo.com/customer/
つだきよ本舗 お取引先		 200 yes 62 7
https://tsudakiyo-honpo.com/profile/
つだきよ本舗 プロフィール		 200 yes 43 7
https://www.tsudakiyo-honpo.com/10aniv/
つだきよ本舗　10周年記念「感謝の集い」		 200 yes 2 1
https://www.tsudakiyo-honpo.com/6aniv/
つだきよ本舗　6周年記念		 200 yes 2 1
https://www.tsudakiyo-honpo.com/book/
つだきよ本舗		 200 yes 23 1
https://www.tsudakiyo-honpo.com/newspapar5.html
つだきよ本舗 創立20周年記念「大同窓会 つだきよ祭」		 200 yes 5 1
https://www.tsudakiyo-honpo.com/talk_lovekove/
つだきよ本舗		 200 yes 79 1
https://tsudakiyo-honpo.com/10aniv/
つだきよ本舗　10周年記念「感謝の集い」		 200 yes 2 1
https://tsudakiyo-honpo.com/6aniv/
つだきよ本舗　6周年記念		 200 yes 2 1
https://tsudakiyo-honpo.com/book/
つだきよ本舗		 200 yes 23 1
https://tsudakiyo-honpo.com/newspapar5.html
つだきよ本舗 創立20周年記念「大同窓会 つだきよ祭」		 200 yes 5 1
https://tsudakiyo-honpo.com/talk_lovekove/
つだきよ本舗		 200 yes 79 1
https://www.tsudakiyo-honpo.com/newspapar.html
つだきよ本舗		 200 yes 1 0
https://www.tsudakiyo-honpo.com/newspapar2.html
つだきよ本舗		 200 yes 0 0
https://www.tsudakiyo-honpo.com/newspapar3.html
つだきよ本舗		 200 yes 0 0
https://www.tsudakiyo-honpo.com/newspapar4.html
つだきよ本舗		 200 yes 0 0
https://www.tsudakiyo-honpo.com/privacy/
つだきよ本舗　プライバシーポリシー		 200 yes 7 0
https://tsudakiyo-honpo.com/img/file_01.pdf 200 no 0 1
https://tsudakiyo-honpo.com/img/file_02.pdf 200 no 0 1
https://tsudakiyo-honpo.com/img/july.pdf 200 no 0 1
https://tsudakiyo-honpo.com/img/np_10.11.24.pdf 200 no 0 1
https://tsudakiyo-honpo.com/img/np_12.5.16.pdf 200 no 0 1
https://tsudakiyo-honpo.com/img/np_16.10.8.pdf 200 no 0 1
https://tsudakiyo-honpo.com/img/np_2.18.pdf 200 no 0 1
https://tsudakiyo-honpo.com/pdf/01.pdf 200 no 0 1
https://tsudakiyo-honpo.com/pdf/02.pdf 200 no 0 1
https://www.tsudakiyo-honpo.com/img/file_01.pdf 200 no 0 1
https://www.tsudakiyo-honpo.com/img/file_02.pdf 200 no 0 1
https://www.tsudakiyo-honpo.com/img/july.pdf 200 no 0 1
https://www.tsudakiyo-honpo.com/img/np_10.11.24.pdf 200 no 0 1
https://www.tsudakiyo-honpo.com/img/np_12.5.16.pdf 200 no 0 1
https://www.tsudakiyo-honpo.com/img/np_16.10.8.pdf 200 no 0 1
https://www.tsudakiyo-honpo.com/img/np_2.18.pdf 200 no 0 1
https://www.tsudakiyo-honpo.com/pdf/01.pdf 200 no 0 1
https://www.tsudakiyo-honpo.com/pdf/02.pdf 200 no 0 1

Audit your own site — free

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

Scan your site →