Skip to content
https://www.fabsound.ie

SEO

· 14 checks — Canonical, meta, content depth, internal links, image SEO, and hreflang rolled into one auditable list.
SCORE
84
GRADE
B
FIX
1
REVIEW
4
PASS
8
INFO
1

Cross-tab audit — SEO, performance, crawlability, mobile, structured data

Checks
14
8 PASS 4 REVIEW 1 FIX
F
Content Depth
Action
104 words, Fairly Difficult
FIX
104 words, Fairly Difficult
Warning::
Page has 104 words — thin content
Most well-ranking pages have 300+ words of substantive content.
Info::
Text-to-HTML ratio is 1%
Very low ratio suggests heavy framework overhead or boilerplate.
Info::
Reading level: Fairly Difficult (grade 8)
Warning::
Thin content — only 104 words
Got: 104 words
104 words

Thin content

Reading level

Very Easy
Easy
Fairly Easy
Standard
Fairly Difficult
Difficult
Very Difficult

Grade 8

Text-to-HTML Ratio

1% text 99% HTML

1 KB / 109 KB

Most well-ranking pages have 300+ words of substantive content.

Why this matters

Thin content (<300 words) rarely ranks — Google quality guidelines explicitly call out thin pages.

Source: Google Search Quality Guidelines

Very low ratio suggests heavy framework overhead or boilerplate.

Why this matters

Informational: ratio of visible text bytes to total HTML bytes. Very low ratios suggest excessive markup overhead.

B
Canonical URL
Minor issues
REVIEW
Minor issues
Warning::
No canonical tag found
Search engines will determine the canonical URL themselves, which may cause duplicate content issues.
No Canonical URL Set
Page URL https://www.fabsound.ie Canonical (not set)

Search engines will determine the canonical URL themselves, which may cause duplicate content issues.

Why this matters

Without a canonical, Google may treat each URL variant (with/without slash, with tracking params, http/https) as duplicate content and split ranking.

Learn more ▾

A canonical link tells Google which URL is the 'real' one when multiple URLs serve identical content. Without it, link equity gets split across variants and none of them rank as well as a single canonical version would. One <link rel="canonical"> tag in <head> covers it.

Source: Google Search Central

B
Meta Tags
Title: 11 chars
REVIEW
Title: 11 chars
Info::
Page title is set
Got: fabsound.ie
Warning::
Title is only 11 characters — consider expanding
Warning::
No meta description tag found
Without a meta description, Google auto-generates a snippet from page content -- usually less click-attractive than a hand-written summary. Add `<meta name="description" content="...">` with a 70-160 char summary.
Info::
Title and H1 are identical
Consider differentiating — the title is for search results, the H1 is for the page.
Title

"fabsound.ie"

11 characters Too short
Title: fabsound.ie
H1: FABsound
Match: Similar ✓
Robots: Indexable (no restrictions)

Without a meta description, Google auto-generates a snippet from page content -- usually less click-attractive than a hand-written summary. Add `<meta name="description" content="...">` with a 70-160 char summary.

Why this matters

No meta description -- Google auto-generates a SERP snippet from page content, usually less click-attractive than a hand-written summary.

Learn more ▾

Meta description is shown as the snippet under the title in search results. A well-written description significantly improves click-through rate. Add `<meta name="description" content="...">` with a 70-160 character summary.

Source: Google Search Central

Consider differentiating — the title is for search results, the H1 is for the page.

Why this matters

Title and H1 match exactly — internally consistent but misses an opportunity to optimize each for its audience (Title for SERP CTR, H1 for on-page).

Learn more ▾

Title and H1 don't have to be identical — and often shouldn't be. The Title competes for SERP click-through (lead with keyword + value prop), while the H1 confirms to the visitor they're on the right page (more conversational is fine). Differentiating gains both surfaces.

Source: Google Search Central / on-page SEO

C
Sitemap Freshness
Action
No sitemap.xml found
REVIEW
No sitemap.xml found
Info::
No sitemap.xml found
Sitemaps help search engines discover and prioritize URLs. Not strictly required for small sites where every page is linked from the homepage, but recommended once a site grows beyond a few dozen URLs.
C
Sitemap × Robots Consistency
Action
Sitemap or robots.txt missing -- consistency check skipped
REVIEW
Sitemap or robots.txt missing -- consistency check skipped
Info::
Cross-check skipped (sitemap or robots.txt absent)
A+
Title Style Depth
Title style is clean -- consistent separator, no stale year, no keyword stuffing
PASS
Title style is clean -- consistent separator, no stale year, no keyword stuffing
Info::
Title style is clean
A+
Image SEO
No images
PASS
No images
Info::
No images on this page
No images on this page.
A+
Hreflang URL Quality
No hreflang tags on the page
PASS
No hreflang tags on the page
Info::
No hreflang tags on the page
A+
Hreflang Completeness
No hreflang tags on this page -- check is N/A (single-language site or unannotated)
PASS
No hreflang tags on this page -- check is N/A (single-language site or unannotated)
Info::
No hreflang tags found -- completeness check is N/A
A+
Sitemap Hygiene
No sitemap to evaluate -- depth check is N/A
PASS
No sitemap to evaluate -- depth check is N/A
Info::
No sitemap fetched -- depth check skipped
A
Markup Quality
2 markup-quality issue(s) detected
PASS
2 markup-quality issue(s) detected
Info::
`<meta charset>` declared at byte 5023 -- past the 1024-byte spec window
The HTML5 spec requires the encoding declaration to appear in the first 1024 bytes. Browsers that started parsing in a default encoding and discover the real charset later DISCARD parsing state and re-parse from the top -- a measurable hit to First Contentful Paint. Move the `<meta charset>` tag to be the first child of `<head>`.
Info::
11 redundant ARIA role attribute(s) on native semantic element(s)
The W3C "ARIA in HTML" spec calls this its first rule: don't use ARIA when a native HTML element already conveys the semantics. `<button role="button">`, `<a href role="link">`, `<nav role="navigation">`, `<main role="main">` -- the role attribute either does nothing or shadows the native semantic, occasionally breaking assistive-tech behaviors. Remove the redundant role.
A+
Schema Markup Audit
Per-type completeness vs Schema.org requirements + rich-result eligibility
PASS

No structured data detected

Without JSON-LD or microdata, this page can't qualify for any of Google's rich result formats. Even basic Organization or WebSite schema is a quick win.

Hreflang
0 hreflang tags
INFO
0 hreflang tags

No hreflang tags detected.

Hreflang tags are only needed for multilingual or multi-regional sites.

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback