Catalog / laydot.com
65

SEO audit for laydot.com

IoT 스마트 농업 솔루션 | 레이닷

other

Health 65/100 (fair) · 36 pages crawled · generated 2026-08-26

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

레이닷은 IoT 기반 스마트 농업 솔루션을 제공합니다. 팜로거, 팜그로브, 팜일루미니, 그리드라이트 등 혁신적인 농업 기술로 효율적인 영농 환경을 지원합니다.

Screenshot of laydot.com
36
pages crawled
36
indexable pages
0
errors
114
warnings
350
notices
18
orphan pages
0
broken links
Category breakdown
CategoryScoreErrorsWarningsNotices
Performance 70 0 36 108
Headings 80 0 24 3
Content 81 0 23 79
Hreflang 90 0 12 0
Links 90 0 12 3
Agent Readiness 95 0 6 3
AI Content 99 0 1 0
Cache 100 0 0 36
Canonical 100 0 0 30
Images 100 0 0 3
Meta Description 100 0 0 27
Robots 100 0 0 1
Security 100 0 0 36
Titles 100 0 0 21
Findings

Warnings (7 rules)

warning Control has no accessible name

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

warning Unfilled template or prompt-leak text

Rule ai.prompt_leak · AI Content · 1 occurrence(s)

  • https://laydot.com/en/policy — The page contains unfilled template or prompt-echo text — e.g. "[Company Name]". This usually means a generation template was published without being completed or cleaned up. Fill in or remove the placeholder so readers and crawlers don't see the scaffolding.

warning Self hreflang language disagrees with html lang

Rule hreflang.mismatch_html_lang · Hreflang · 12 occurrence(s)

  • https://laydot.com/jp — the self-referencing hreflang is "ja" but <html lang> is "jp" — contradictory language signals can make Google distrust the hreflang cluster. Align both to the same BCP-47 language.
  • https://laydot.com/jp/about/company — the self-referencing hreflang is "ja" but <html lang> is "jp" — contradictory language signals can make Google distrust the hreflang cluster. Align both to the same BCP-47 language.
  • https://laydot.com/jp/about/location — the self-referencing hreflang is "ja" but <html lang> is "jp" — contradictory language signals can make Google distrust the hreflang cluster. Align both to the same BCP-47 language.
  • https://laydot.com/jp/business — the self-referencing hreflang is "ja" but <html lang> is "jp" — contradictory language signals can make Google distrust the hreflang cluster. Align both to the same BCP-47 language.
  • https://laydot.com/jp/business/farm-grove — the self-referencing hreflang is "ja" but <html lang> is "jp" — contradictory language signals can make Google distrust the hreflang cluster. Align both to the same BCP-47 language.
  • https://laydot.com/jp/business/farm-lilumini — the self-referencing hreflang is "ja" but <html lang> is "jp" — contradictory language signals can make Google distrust the hreflang cluster. Align both to the same BCP-47 language.
  • https://laydot.com/jp/business/farm-logger — the self-referencing hreflang is "ja" but <html lang> is "jp" — contradictory language signals can make Google distrust the hreflang cluster. Align both to the same BCP-47 language.
  • https://laydot.com/jp/business/grid-light — the self-referencing hreflang is "ja" but <html lang> is "jp" — contradictory language signals can make Google distrust the hreflang cluster. Align both to the same BCP-47 language.
  • https://laydot.com/jp/contact — the self-referencing hreflang is "ja" but <html lang> is "jp" — contradictory language signals can make Google distrust the hreflang cluster. Align both to the same BCP-47 language.
  • https://laydot.com/jp/media/news — the self-referencing hreflang is "ja" but <html lang> is "jp" — contradictory language signals can make Google distrust the hreflang cluster. Align both to the same BCP-47 language.
  • https://laydot.com/jp/media/notices — the self-referencing hreflang is "ja" but <html lang> is "jp" — contradictory language signals can make Google distrust the hreflang cluster. Align both to the same BCP-47 language.
  • https://laydot.com/jp/policy — the self-referencing hreflang is "ja" but <html lang> is "jp" — contradictory language signals can make Google distrust the hreflang cluster. Align both to the same BCP-47 language.

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

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

  • https://laydot.com/en — the likely hero/LCP image (logo_white.png) 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://laydot.com/en/about/company — the likely hero/LCP image (logo_white.png) 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://laydot.com/en/about/location — the likely hero/LCP image (logo_white.png) 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://laydot.com/en/business — the likely hero/LCP image (logo_white.png) 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://laydot.com/en/business/farm-grove — the likely hero/LCP image (logo_white.png) 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://laydot.com/en/business/farm-lilumini — the likely hero/LCP image (logo_white.png) 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://laydot.com/en/business/farm-logger — the likely hero/LCP image (logo_white.png) 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://laydot.com/en/business/grid-light — the likely hero/LCP image (logo_white.png) 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://laydot.com/jp — the likely hero/LCP image (logo_white.png) 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://laydot.com/jp/about/company — the likely hero/LCP image (logo_white.png) 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://laydot.com/jp/about/location — the likely hero/LCP image (logo_white.png) 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://laydot.com/jp/business — the likely hero/LCP image (logo_white.png) 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://laydot.com/jp/business/farm-grove — the likely hero/LCP image (logo_white.png) 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://laydot.com/jp/business/farm-lilumini — the likely hero/LCP image (logo_white.png) 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://laydot.com/jp/business/farm-logger — the likely hero/LCP image (logo_white.png) 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://laydot.com/jp/business/grid-light — the likely hero/LCP image (logo_white.png) 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://laydot.com/ko — the likely hero/LCP image (logo_white.png) 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://laydot.com/ko/about/company — the likely hero/LCP image (logo_white.png) 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://laydot.com/ko/about/location — the likely hero/LCP image (logo_white.png) 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://laydot.com/ko/business — the likely hero/LCP image (logo_white.png) 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://laydot.com/ko/business/farm-grove — the likely hero/LCP image (logo_white.png) 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://laydot.com/ko/business/farm-lilumini — the likely hero/LCP image (logo_white.png) 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://laydot.com/ko/business/farm-logger — the likely hero/LCP image (logo_white.png) 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://laydot.com/ko/business/grid-light — the likely hero/LCP image (logo_white.png) 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://laydot.com/ko/media/news — the likely hero/LCP image (logo_white.png) 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 Orphan page (no internal inlinks)

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

Notices (17 rules)

notice Heading levels skip a level

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

notice Page served uncached (no-store/private or CDN bypass)

Rule cache.not_cacheable · Cache · 36 occurrence(s)

notice Canonical target reachable only via a canonical tag (no inlinks)

Rule canonical.isolated_url · Canonical · 6 occurrence(s)

  • https://laydot.com/ko/about/location — this URL is a canonical target but has no internal links pointing to it — crawlers only learn of it via the canonical tag. Add direct internal links (or list it in the sitemap).
  • https://laydot.com/ko/business/farm-grove — this URL is a canonical target but has no internal links pointing to it — crawlers only learn of it via the canonical tag. Add direct internal links (or list it in the sitemap).
  • https://laydot.com/ko/business/farm-lilumini — this URL is a canonical target but has no internal links pointing to it — crawlers only learn of it via the canonical tag. Add direct internal links (or list it in the sitemap).
  • https://laydot.com/ko/business/farm-logger — this URL is a canonical target but has no internal links pointing to it — crawlers only learn of it via the canonical tag. Add direct internal links (or list it in the sitemap).
  • https://laydot.com/ko/media/news — this URL is a canonical target but has no internal links pointing to it — crawlers only learn of it via the canonical tag. Add direct internal links (or list it in the sitemap).
  • https://laydot.com/ko/policy — this URL is a canonical target but has no internal links pointing to it — crawlers only learn of it via the canonical tag. Add direct internal links (or list it in the sitemap).

notice Canonical points to a different URL

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

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

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

  • https://laydot.com/en — 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://laydot.com/en/about/company — this page reads as very difficult (Flesch Reading Ease 13, 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://laydot.com/en/about/location — this page reads as difficult (Flesch Reading Ease 47, 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://laydot.com/en/business — this page reads as very difficult (Flesch Reading Ease 3, 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://laydot.com/en/business/farm-grove — this page reads as difficult (Flesch Reading Ease 41, 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://laydot.com/en/business/farm-lilumini — this page reads as very difficult (Flesch Reading Ease 24, 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://laydot.com/en/business/farm-logger — this page reads as very difficult (Flesch Reading Ease 3, 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://laydot.com/en/business/grid-light — this page reads as very difficult (Flesch Reading Ease 30, 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://laydot.com/en/contact — this page reads as difficult (Flesch Reading Ease 38, 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://laydot.com/en/policy — this page reads as difficult (Flesch Reading Ease 37, 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 Multiple <h1> elements

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

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

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

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

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

notice Legacy <meta name=keywords> tag present (Google ignores it)

Rule meta.keywords_present · Content · 36 occurrence(s)

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

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

  • https://laydot.com/en — 16 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://laydot.com/en/about/company — 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://laydot.com/en/about/location — 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://laydot.com/en/business — 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://laydot.com/en/business/farm-grove — 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://laydot.com/en/business/farm-lilumini — 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://laydot.com/en/business/farm-logger — 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://laydot.com/en/business/grid-light — 6 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://laydot.com/jp — 16 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://laydot.com/jp/about/company — 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://laydot.com/jp/about/location — 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://laydot.com/jp/business — 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://laydot.com/jp/business/farm-grove — 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://laydot.com/jp/business/farm-lilumini — 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://laydot.com/jp/business/farm-logger — 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://laydot.com/jp/business/grid-light — 6 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://laydot.com/ko — 16 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://laydot.com/ko/about/company — 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://laydot.com/ko/about/location — 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://laydot.com/ko/business — 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://laydot.com/ko/business/farm-grove — 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://laydot.com/ko/business/farm-lilumini — 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://laydot.com/ko/business/farm-logger — 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://laydot.com/ko/business/grid-light — 6 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://laydot.com/ko/media/news — 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.

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

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

  • https://laydot.com/en — 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://laydot.com/en/about/company — 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://laydot.com/en/about/location — 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://laydot.com/en/business — 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://laydot.com/en/business/farm-grove — 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://laydot.com/en/business/farm-lilumini — 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://laydot.com/en/business/farm-logger — 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://laydot.com/en/business/grid-light — 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://laydot.com/jp — 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://laydot.com/jp/about/company — 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://laydot.com/jp/about/location — 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://laydot.com/jp/business — 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://laydot.com/jp/business/farm-grove — 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://laydot.com/jp/business/farm-lilumini — 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://laydot.com/jp/business/farm-logger — 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://laydot.com/jp/business/grid-light — 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://laydot.com/ko — 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://laydot.com/ko/about/company — 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://laydot.com/ko/about/location — 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://laydot.com/ko/business — 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://laydot.com/ko/business/farm-grove — 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://laydot.com/ko/business/farm-lilumini — 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://laydot.com/ko/business/farm-logger — 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://laydot.com/ko/business/grid-light — 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://laydot.com/ko/media/news — 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 · 36 occurrence(s)

  • https://laydot.com/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://laydot.com/en/about/company — 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://laydot.com/en/about/location — 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://laydot.com/en/business — 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://laydot.com/en/business/farm-grove — 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://laydot.com/en/business/farm-lilumini — 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://laydot.com/en/business/farm-logger — 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://laydot.com/en/business/grid-light — 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://laydot.com/jp — 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://laydot.com/jp/about/company — 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://laydot.com/jp/about/location — 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://laydot.com/jp/business — 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://laydot.com/jp/business/farm-grove — 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://laydot.com/jp/business/farm-lilumini — 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://laydot.com/jp/business/farm-logger — 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://laydot.com/jp/business/grid-light — 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://laydot.com/ko — 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://laydot.com/ko/about/company — 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://laydot.com/ko/about/location — 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://laydot.com/ko/business — 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://laydot.com/ko/business/farm-grove — 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://laydot.com/ko/business/farm-lilumini — 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://laydot.com/ko/business/farm-logger — 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://laydot.com/ko/business/grid-light — 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://laydot.com/ko/media/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.

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

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

  • https://laydot.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)
Pages (showing 36 of 36)
URLStatusIndexableWordsIn-links
https://laydot.com/en
IoT 스마트 농업 솔루션 | 레이닷
200 yes 341 12
https://laydot.com/en/about/company
회사 소개 | 레이닷
200 yes 193 12
https://laydot.com/en/business
사업 소개 | 레이닷
200 yes 367 12
https://laydot.com/en/contact
문의하기 | 레이닷
200 yes 316 12
https://laydot.com/en/media/notices
공지사항 | 레이닷
200 yes 70 12
https://laydot.com/jp
IoT 스마트 농업 솔루션 | 레이닷
200 yes 107 12
https://laydot.com/jp/about/company
회사 소개 | 레이닷
200 yes 59 12
https://laydot.com/jp/business
사업 소개 | 레이닷
200 yes 89 12
https://laydot.com/jp/contact
문의하기 | 레이닷
200 yes 91 12
https://laydot.com/jp/media/notices
공지사항 | 레이닷
200 yes 38 12
https://laydot.com/ko
IoT 스마트 농업 솔루션 | 레이닷
200 yes 290 12
https://laydot.com/ko/about/company
회사 소개 | 레이닷
200 yes 170 12
https://laydot.com/ko/business
사업 소개 | 레이닷
200 yes 292 12
https://laydot.com/ko/contact
문의하기 | 레이닷
200 yes 256 12
https://laydot.com/ko/media/notices
공지사항 | 레이닷
200 yes 57 12
https://laydot.com/en/business/grid-light
그리드라이트 | 스마트 조명 시스템 | 레이닷
200 yes 192 1
https://laydot.com/jp/business/grid-light
그리드라이트 | 스마트 조명 시스템 | 레이닷
200 yes 56 1
https://laydot.com/ko/business/grid-light
그리드라이트 | 스마트 조명 시스템 | 레이닷
200 yes 149 1
https://laydot.com/en/about/location
오시는 길 | 레이닷
200 yes 97 0
https://laydot.com/en/business/farm-grove
팜그로브 | 조명 자동화 | 레이닷
200 yes 212 0
https://laydot.com/en/business/farm-lilumini
팜일루미니 | 절전 조명 | 레이닷
200 yes 217 0
https://laydot.com/en/business/farm-logger
팜로거 | 데이터 모니터링 | 레이닷
200 yes 354 0
https://laydot.com/en/media/news
뉴스 | 레이닷
200 yes 65 0
https://laydot.com/en/policy
개인정보처리방침 | 레이닷
200 yes 1495 0
https://laydot.com/jp/about/location
오시는 길 | 레이닷
200 yes 43 0
https://laydot.com/jp/business/farm-grove
팜그로브 | 조명 자동화 | 레이닷
200 yes 50 0
https://laydot.com/jp/business/farm-lilumini
팜일루미니 | 절전 조명 | 레이닷
200 yes 51 0
https://laydot.com/jp/business/farm-logger
팜로거 | 데이터 모니터링 | 레이닷
200 yes 84 0
https://laydot.com/jp/media/news
뉴스 | 레이닷
200 yes 33 0
https://laydot.com/jp/policy
개인정보처리방침 | 레이닷
200 yes 232 0
https://laydot.com/ko/about/location
오시는 길 | 레이닷
200 yes 74 0
https://laydot.com/ko/business/farm-grove
팜그로브 | 조명 자동화 | 레이닷
200 yes 163 0
https://laydot.com/ko/business/farm-lilumini
팜일루미니 | 절전 조명 | 레이닷
200 yes 162 0
https://laydot.com/ko/business/farm-logger
팜로거 | 데이터 모니터링 | 레이닷
200 yes 282 0
https://laydot.com/ko/media/news
뉴스 | 레이닷
200 yes 52 0
https://laydot.com/ko/policy
개인정보처리방침 | 레이닷
200 yes 1487 0

Audit your own site — free

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

Scan your site →