Skip to content
https://tibzi.com

SEO

· 14 checks — Canonical, meta, content depth, internal links, image SEO, and hreflang rolled into one auditable list.
SCORE
97
GRADE
A+
FIX
0
REVIEW
0
PASS
13
INFO
1

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

Checks
14
13 PASS
A+
Canonical URL
Properly configured
PASS
Properly configured
Info::
Canonical tag present
Got: https://tibzi.com
Info::
Canonical is self-referencing
Info::
Canonical matches final URL after redirects
Info::
Canonical target returns 200
Canonical URL Configured
Page URL https://tibzi.com Canonical https://tibzi.com Match Self-referencing (correct) Target 200 ✓
A+
Meta Tags
Title: 61 chars
PASS
Title: 61 chars
Info::
Page title is set
Got: Free Website Audit — Security, SEO, Performance | Tibzi.com
Info::
Title is 61 characters — may be truncated in search results
Info::
Meta description length (145 chars) is optimal
Info::
Title and H1 are well-aligned
Title

"Free Website Audit — Security, SEO, Performance | Tibzi.com"

61 characters Will truncate
Title: Free Website Audit — Security, SEO, Performance | Tibzi.com
H1: Free Website Audit — Security, SEO and Performance
Match: Similar ✓
Robots: Indexable (no restrictions)
A
Title Style Depth
1 title-style issue(s) detected
PASS
1 title-style issue(s) detected
Info::
Title uses 2 different separator characters: —, |
The page title `Free Website Audit — Security, SEO, Performance | Tibzi.com` uses multiple separator characters (—, |). Consistent separator use is a soft signal of careful editorial control; mixed separators usually mean the title was assembled from multiple template fragments (CMS title + brand + section) without a normalization step. Pick one separator (commonly `|`, `-`, or `:`) and stick with it across the whole site.
Got: 2 separators: — |
A
Content Depth
1122 words, Difficult
PASS
1122 words, Difficult
Info::
Page has 1122 words — good depth for search engines
Info::
Text-to-HTML ratio is 4%
Very low ratio suggests heavy framework overhead or boilerplate.
Info::
Reading level: Difficult (grade 9)
1122 words

Good depth

Reading level

Very Easy
Easy
Fairly Easy
Standard
Fairly Difficult
Difficult
Very Difficult

Grade 9

Text-to-HTML Ratio

4% text 96% HTML

7 KB / 177 KB

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.

A+
Image SEO
2 images, 2 descriptive filenames
PASS
2 images, 2 descriptive filenames
Info::
All images have descriptive filenames
2 descriptive
0 hash-based
0 generic
2 total
All images have descriptive filenames and proper SEO attributes.

See Accessibility tab for detailed alt text quality analysis.

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 Freshness
Sitemap updated within 90 days (253/253 URLs have lastmod)
PASS
Sitemap updated within 90 days (253/253 URLs have lastmod)
Info::
Sitemap actively maintained — newest lastmod: 2 months ago
Got: 2026-07-14T00:00:00Z
A+
Sitemap × Robots Consistency
No sitemap-vs-robots conflicts in the URL sample
PASS
No sitemap-vs-robots conflicts in the URL sample
Info::
All 5 sampled sitemap URLs are crawlable per robots.txt
A+
Sitemap Hygiene
Sitemap structure / size look healthy (253 URLs, 43 KB)
PASS
Sitemap structure / size look healthy (253 URLs, 43 KB)
Info::
Sitemap structure / size look healthy (253 URLs)
A+
Markup Quality
1 markup-quality issue(s) detected
PASS
1 markup-quality issue(s) detected
Info::
1 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
10 schema types detected
PASS

Rich result eligibility

WebSite Eligible

Sitelinks search box

Organization Eligible

Organization knowledge panel

FAQPage Eligible

FAQ rich results

BreadcrumbList Eligible

Breadcrumb trail

WebSite Eligible

Sitelinks search box

Organization Eligible

Organization knowledge panel

FAQPage Eligible

FAQ rich results

Detected schema types

WebSite json-ld → Sitelinks search box
2/2 required · 0/1 recommended
Required fields (Google)
  • name — Required for the sitelinks search box
  • url — Required to anchor the search box to your domain
Recommended fields
  • potentialAction — Add a SearchAction with target and query-input Enables the in-SERP search box
Google's spec for this type
Organization json-ld → Organization knowledge panel
2/2 required · 3/4 recommended
Required fields (Google)
  • name — Required for the knowledge panel
  • url — Required for entity matching
Recommended fields
  • logo — Strongly recommended — appears in the knowledge panel header
  • sameAs — Connects the entity across the web
  • contactPoint — Enables direct contact from the knowledge panel
  • description — Add an organization description Used as the panel summary
Google's spec for this type
FAQPage json-ld → FAQ rich results
1/1 required
Required fields (Google)
  • mainEntity — Required — without this the FAQ schema is invalid
Google's spec for this type
Service json-ld
0/0 required
SoftwareApplication json-ld
0/0 required
BreadcrumbList json-ld → Breadcrumb trail
1/1 required
Required fields (Google)
  • itemListElement — Required — the breadcrumb chain renders nothing without this
Google's spec for this type
WebSite json-ld → Sitelinks search box
2/2 required · 0/1 recommended
Required fields (Google)
  • name — Required for the sitelinks search box
  • url — Required to anchor the search box to your domain
Recommended fields
  • potentialAction — Add a SearchAction with target and query-input Enables the in-SERP search box
Google's spec for this type
Organization json-ld → Organization knowledge panel
2/2 required · 3/4 recommended
Required fields (Google)
  • name — Required for the knowledge panel
  • url — Required for entity matching
Recommended fields
  • logo — Strongly recommended — appears in the knowledge panel header
  • sameAs — Connects the entity across the web
  • contactPoint — Enables direct contact from the knowledge panel
  • description — Add an organization description Used as the panel summary
Google's spec for this type
FAQPage json-ld → FAQ rich results
1/1 required
Required fields (Google)
  • mainEntity — Required — without this the FAQ schema is invalid
Google's spec for this type
SoftwareApplication json-ld
0/0 required

Missing schema opportunities

  • moderate

    Review

    Page has review markup or testimonials that could be marked up

    Enables star-rating snippets in search

Adding these recommended fields improves chances of getting Sitelinks search box in search results.

Why this matters

Schema entity has required fields but could add recommended ones for richer SERP layouts (star ratings, prices, etc.).

Source: Google Search Central

Adding these recommended fields improves chances of getting Organization knowledge panel in search results.

Why this matters

Schema entity has required fields but could add recommended ones for richer SERP layouts (star ratings, prices, etc.).

Source: Google Search Central

Adding these recommended fields improves chances of getting Sitelinks search box in search results.

Why this matters

Schema entity has required fields but could add recommended ones for richer SERP layouts (star ratings, prices, etc.).

Source: Google Search Central

Adding these recommended fields improves chances of getting Organization knowledge panel in search results.

Why this matters

Schema entity has required fields but could add recommended ones for richer SERP layouts (star ratings, prices, etc.).

Source: Google Search Central

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