Catalog / dangleverse.com
65

SEO audit for dangleverse.com

Dangleverse

mediaNext.js

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

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

Hockey stick handling video game system. Use your existing Apple or Android devices and whatever puck or ball you already own.

Screenshot of dangleverse.com
16
pages crawled
15
indexable pages
0
errors
30
warnings
103
notices
2
orphan pages
0
broken links
Category breakdown
CategoryScoreErrorsWarningsNotices
Performance 81 0 10 22
Structured Data 87 0 7 10
Canonical 91 0 5 0
Duplicate 94 0 3 2
Content 96 0 2 19
Links 96 0 2 6
Budget 98 0 1 0
Crawlability 100 0 0 1
Images 100 0 0 10
Meta Description 100 0 0 2
Security 100 0 0 15
Sitemap 100 0 0 1
Social 100 0 0 6
Titles 100 0 0 9
Findings

Warnings (8 rules)

warning robots.txt-disallowed URL receives internal links (crawl-budget leak)

Rule budget.disallow_linked · Budget · 1 occurrence(s)

  • https://dangleverse.com/cart — internal links point to https://dangleverse.com/cart, which robots.txt disallows for Googlebot — Googlebot discovers the URL, checks robots, then rejects it without indexing, wasting crawl budget and losing the link equity. Remove the internal links, or use noindex instead of Disallow if the page should be fetchable. Linked from: https://dangleverse.com/products/odd-man-rush, https://dangleverse.com/products/danglemat?bumpers=1&game=1, https://dangleverse.com/products/danglemat.

warning Missing canonical tag

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

warning Thin content (low word count)

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

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

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

  • https://dangleverse.com/ — https://www.dangleverse.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 · 2 occurrence(s)

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

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

  • https://dangleverse.com/ — the likely hero/LCP image (dangleverse-logo-pill.022a6599.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://dangleverse.com/download — the likely hero/LCP image (dangleverse-logo-pill.022a6599.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://dangleverse.com/guides/hockey-stick-handling-game — the likely hero/LCP image (dangleverse-logo-pill.022a6599.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://dangleverse.com/guides/hockey-stick-handling-mat — the likely hero/LCP image (dangleverse-logo-pill.022a6599.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://dangleverse.com/help/danglemat — the likely hero/LCP image (dangleverse-logo-pill.022a6599.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://dangleverse.com/privacy — the likely hero/LCP image (dangleverse-logo-pill.022a6599.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://dangleverse.com/products/odd-man-rush — the likely hero/LCP image (image) 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://dangleverse.com/products/odd-man-rush?stand=1 — the likely hero/LCP image (image) 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://dangleverse.com/return-policy — the likely hero/LCP image (dangleverse-logo-pill.022a6599.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://dangleverse.com/terms — the likely hero/LCP image (dangleverse-logo-pill.022a6599.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 Orphan page (no internal inlinks)

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

warning LocalBusiness schema missing required properties (name/address)

Rule schema.localbusiness_incomplete · Structured Data · 7 occurrence(s)

  • https://dangleverse.com/products/bumpers — LocalBusiness structured data is missing required property (address) — without them Google won't generate the rich result. Add each field (and validate with the Rich Results Test). It is also missing recommended properties (telephone, openingHoursSpecification, geo, priceRange), which enrich the result.
  • https://dangleverse.com/products/danglemat — LocalBusiness structured data is missing required property (address) — without them Google won't generate the rich result. Add each field (and validate with the Rich Results Test). It is also missing recommended properties (telephone, openingHoursSpecification, geo, priceRange), which enrich the result.
  • https://dangleverse.com/products/danglemat?bumpers=1 — LocalBusiness structured data is missing required property (address) — without them Google won't generate the rich result. Add each field (and validate with the Rich Results Test). It is also missing recommended properties (telephone, openingHoursSpecification, geo, priceRange), which enrich the result.
  • https://dangleverse.com/products/danglemat?bumpers=1&game=1 — LocalBusiness structured data is missing required property (address) — without them Google won't generate the rich result. Add each field (and validate with the Rich Results Test). It is also missing recommended properties (telephone, openingHoursSpecification, geo, priceRange), which enrich the result.
  • https://dangleverse.com/products/odd-man-rush — LocalBusiness structured data is missing required property (address) — without them Google won't generate the rich result. Add each field (and validate with the Rich Results Test). It is also missing recommended properties (telephone, openingHoursSpecification, geo, priceRange), which enrich the result.
  • https://dangleverse.com/products/odd-man-rush?stand=1 — LocalBusiness structured data is missing required property (address) — without them Google won't generate the rich result. Add each field (and validate with the Rich Results Test). It is also missing recommended properties (telephone, openingHoursSpecification, geo, priceRange), which enrich the result.
  • https://dangleverse.com/products/stand — LocalBusiness structured data is missing required property (address) — without them Google won't generate the rich result. Add each field (and validate with the Rich Results Test). It is also missing recommended properties (telephone, openingHoursSpecification, geo, priceRange), which enrich the result.

Notices (21 rules)

notice Low text-to-HTML ratio

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

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

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

  • https://dangleverse.com/return-policy — 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.

notice Duplicate meta description across pages

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

notice Article page has no author attribution (E-E-A-T)

Rule eeat.no_author · Content · 2 occurrence(s)

notice Image alt text is very long (possible keyword stuffing)

Rule images.alt_too_long · Images · 1 occurrence(s)

notice Likely hero image lacks fetchpriority=high

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

  • https://dangleverse.com/products/bumpers — the likely hero/LCP image (image) 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://dangleverse.com/products/danglemat — the likely hero/LCP image (image) 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://dangleverse.com/products/danglemat?bumpers=1 — the likely hero/LCP image (image) 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://dangleverse.com/products/danglemat?bumpers=1&game=1 — the likely hero/LCP image (image) 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://dangleverse.com/products/stand — the likely hero/LCP image (image) 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 · 9 occurrence(s)

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

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

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

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

notice Meta description too short

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

notice Missing Open Graph tags

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

notice Large DOM (over 1500 elements) slows rendering & interaction

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

  • https://dangleverse.com/products/odd-man-rush — the page has 2267 DOM elements (recommended maximum is around 1500) — a large DOM increases style-recalculation, layout and paint cost, hurting LCP and INP. Flatten deep nesting, paginate long lists/tables, and lazy-render off-screen elements.
  • https://dangleverse.com/products/odd-man-rush?stand=1 — the page has 2267 DOM elements (recommended maximum is around 1500) — a large DOM increases style-recalculation, layout and paint cost, hurting LCP and INP. Flatten deep nesting, paginate long lists/tables, and lazy-render off-screen elements.

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

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

  • https://dangleverse.com/ — 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://dangleverse.com/download — 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://dangleverse.com/guides/hockey-stick-handling-game — 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://dangleverse.com/guides/hockey-stick-handling-mat — 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://dangleverse.com/help/danglemat — 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://dangleverse.com/privacy — 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://dangleverse.com/products/bumpers — 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://dangleverse.com/products/danglemat — 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://dangleverse.com/products/danglemat?bumpers=1 — 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://dangleverse.com/products/danglemat?bumpers=1&game=1 — 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://dangleverse.com/products/odd-man-rush — 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://dangleverse.com/products/odd-man-rush?stand=1 — 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://dangleverse.com/products/stand — 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://dangleverse.com/return-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://dangleverse.com/terms — 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 Blocked by robots.txt

Rule robots.blocked · Crawlability · 1 occurrence(s)

notice Article schema missing recommended properties (Top Stories / image carousel)

Rule schema.article_incomplete · Structured Data · 2 occurrence(s)

  • https://dangleverse.com/guides/hockey-stick-handling-game — Article structured data is missing recommended properties (image, datePublished, author) — these feed Top Stories and image-carousel eligibility. Google defines no required Article properties, so this is advisory: add author, headline, image and datePublished where they apply.
  • https://dangleverse.com/guides/hockey-stick-handling-mat — Article structured data is missing recommended properties (image, datePublished, author) — these feed Top Stories and image-carousel eligibility. Google defines no required Article properties, so this is advisory: add author, headline, image and datePublished where they apply.

notice Deep page has no BreadcrumbList structured data

Rule schema.breadcrumb_missing · Structured Data · 3 occurrence(s)

notice No structured data detected

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

notice Missing recommended security headers

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

notice Indexable page not listed in sitemap

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

notice Title tag is identical to the H1 (missed keyword variation)

Rule title.same_as_h1 · Titles · 4 occurrence(s)

notice Title is very short

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

Pages (showing 16 of 16)
URLStatusIndexableWordsIn-links
https://dangleverse.com/privacy
Privacy policy - Dangleverse		 200 yes 1353 15
https://dangleverse.com/terms
Terms of service - Dangleverse		 200 yes 2183 15
https://dangleverse.com/
Dangleverse		 200 yes 393 14
https://dangleverse.com/return-policy
Return policy - Dangleverse		 200 yes 571 1
https://dangleverse.com/products/danglemat
The Danglemat		 200 yes 1426 3
https://dangleverse.com/products/odd-man-rush
Odd Man Rush - Dangleverse		 200 yes 6591 3
https://dangleverse.com/products/stand
Device stand - Dangleverse		 200 yes 95 2
https://dangleverse.com/guides/hockey-stick-handling-game
Hockey stick handling game - Dangleverse		 200 yes 1190 1
https://dangleverse.com/guides/hockey-stick-handling-mat
Hockey stick handling mat - Dangleverse		 200 yes 1299 1
https://dangleverse.com/products/bumpers
Bumpers - Dangleverse		 200 yes 86 1
https://dangleverse.com/products/danglemat?bumpers=1&game=1
The Danglemat		 200 yes 1426 3
https://dangleverse.com/products/odd-man-rush?stand=1
Odd Man Rush - Dangleverse		 200 yes 6591 1
https://dangleverse.com/products/danglemat?bumpers=1
The Danglemat		 200 yes 1426 1
https://dangleverse.com/download
Dangleverse		 200 yes 857 0
https://dangleverse.com/help/danglemat
Danglemat instructions + care		 200 yes 558 0
https://dangleverse.com/cart 0 no 0 7

Audit your own site — free

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

Scan your site →