Accessibility
· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.F404 Error PageActionSoft 404 detectedFIX
The server returned HTTP 200 for a non-existent path. Search engines will index this page as real content. Configure your server to return HTTP 404 for missing pages.
FWeb ManifestActionInvalid JSONFIX
Manifest contains invalid JSON.
DDark Mode SupportActionNo dark mode signalsFIX
Detection limited to meta tags and inline styles.
DPrint StylesheetActionNo print stylesFIX
CLandmark StructureAction2 landmarksREVIEW
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Without a <main> landmark, screen-reader users can't skip past the navigation to the page content — every page starts with re-reading the menu.
Learn more ▾ ▴
The <main> element marks the page's primary content area. Assistive tech offers a 'jump to main' shortcut — but only if <main> exists. Without it, every page navigation forces re-reading the header. Wrap your primary content in a single <main>.
Source: WAI-ARIA / WCAG 2.4.1
Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.
Without a skip-nav link, keyboard users tab through every nav item before reaching content — every page, every visit.
Learn more ▾ ▴
WCAG 2.4.1 (Bypass Blocks) requires a mechanism to skip past repeated content. The standard implementation is a 'Skip to main content' link that's the first focusable element, visually hidden until focused. Three lines of HTML + four of CSS.
Source: WCAG 2.1 SC 2.4.1
CFavicon & BrandingAction4 icon(s) detectedREVIEW
AHeading Hierarchy12 headingsPASS
- H1 Competitors Backlinks FreeGrow Organic Traffic For FREE
- H1 Competitors Backlinks Free: Your Complete Guide to Finding and Using Them duplicate H1
- H2 What Are Competitor Backlinks and Why Should You Care?
- H2 Free Tools to Check Competitors' Backlinks
- H2 Step-by-Step: How to Find Competitors' Backlinks for Free
- H2 How to Identify the Best Link Opportunities from Competitor Data
- H2 Turning Competitor Backlink Insights Into Your Link Building Strategy
- H2 Key Metrics to Track When Analyzing Competitor Backlinks
- H2 How Often Should You Monitor Competitors' Backlinks?
- H2 Common Questions About Free Competitor Backlink Research
- H2 Building a Sustainable Backlink Strategy From Competitor Data
- H2 Wrapping Up: Your Free Competitor Backlink Roadmap
A page should have only one H1. Multiple H1s dilute the document outline.
Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.
Learn more ▾ ▴
HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.
Source: WCAG 2.4.6 / Google Search Central
A+Heading Text QualityAll 12 heading(s) have substantive, well-formed textPASS
AAlt Text Quality1 of 9 images have issuesPASS
| Issue | Count |
|---|---|
| missing | 1 image(s) |
Images without alt text are invisible to screen readers.
Each image without alt text is a WCAG 1.1.1 failure — invisible to screen-reader users, lost from Google Image Search.
Learn more ▾ ▴
WCAG 2.1 Level A requires text alternatives for non-decorative images. Empty alt='' is fine for decorative; meaningful images need descriptive text. Common fixes: CMS audit + bulk add, build-time linter (alt-text-required ESLint rule), CI gate on Lighthouse a11y score.
Source: WCAG 2.1 SC 1.1.1 / WebAIM Million Report
A+Form AccessibilityAll 2 controls labeledPASS
| Control | Type | Label | Method |
|---|---|---|---|
| #your_website | text | ➤ Enter Your Website | for/id |
| #your_keywords | text | ➤ Enter Your Keywords | for/id |
A+Link & Button Quality16 links, 0 buttons — all OKPASS
A+Form Input Types1 input(s) using type=text where a specific type would helpPASS
A+Form Input Quality2 form control(s) checked, no input-semantic issuesPASS
A+Mobile Keyboard & AutofillNo autofill-eligible form controlsPASS
A+Document LanguageLang attribute set to "en"PASS
A+Tabindex Anti-PatternsNo explicit tabindex attributes foundPASS
A+Iframe AccessibilityAll 1 iframe(s) have descriptive titlesPASS
A+Tap Target AdequacyAll tap targets meet WCAG 2.5.5/2.5.8 sizingPASS
A+Mobile-Readable Font SizesAll 158 visible text node(s) render at >= 12 CSS pixelsPASS
A+PWA DepthNo PWA depth issues detectedPASS
A+Mobile UX Depth1 mobile-depth signal(s) detectedPASS
A+Color Contrast (Screenshot)20 text elements analyzed, 0 fail WCAG AAPASS
Analyzes text contrast against the actual rendered page, including background images, gradients, and overlays that CSS-based tools cannot detect.
Show all checked elements (20)
| Element | Ratio | Required | FG | BG | Result |
|---|---|---|---|---|---|
| h1 Competitors Backlink… | 16.20:1 | 3.0:1 | #000000 | #DAE2F7 | Pass |
| h1 Competitors Backlink… | 17.36:1 | 3.0:1 | #000000 | #E5E9F9 | Pass |
| h2 What Are Competitor … | 17.36:1 | 3.0:1 | #000000 | #E5E9F9 | Pass |
| h2 Free Tools to Check … | 17.36:1 | 3.0:1 | #000000 | #E5E9F9 | Pass |
| h2 Step-by-Step: How to… | 17.36:1 | 3.0:1 | #000000 | #E5E9F9 | Pass |
| h2 How to Identify the … | 17.36:1 | 3.0:1 | #000000 | #E5E9F9 | Pass |
| h2 Turning Competitor B… | 17.36:1 | 3.0:1 | #000000 | #E5E9F9 | Pass |
| h2 Key Metrics to Track… | 17.36:1 | 3.0:1 | #000000 | #E5E9F9 | Pass |
| h2 How Often Should You… | 17.36:1 | 3.0:1 | #000000 | #E5E9F9 | Pass |
| h2 Common Questions Abo… | 17.36:1 | 3.0:1 | #000000 | #E5E9F9 | Pass |
| h2 Building a Sustainab… | 17.36:1 | 3.0:1 | #000000 | #E5E9F9 | Pass |
| h2 Wrapping Up: Your Fr… | 17.36:1 | 3.0:1 | #000000 | #E5E9F9 | Pass |
| title Competitors Backlink… | 18.54:1 | 4.5:1 | #000000 | #F0F0F9 | Pass |
| a Rank Now | 18.35:1 | 4.5:1 | #000000 | #EEEFF9 | Pass |
| a Home | 18.35:1 | 4.5:1 | #000000 | #EEEFF9 | Pass |
| a Add/Remove Website | 18.13:1 | 4.5:1 | #000000 | #EBEEF9 | Pass |
| a Contact Us | 17.21:1 | 4.5:1 | #000000 | #E4E8F9 | Pass |
| a Start for Free | 16.97:1 | 4.5:1 | #000000 | #E0E7F9 | Pass |
| span ➤ | 16.22:1 | 4.5:1 | #000000 | #DAE2F8 | Pass |
| a Login | 15.88:1 | 4.5:1 | #000000 | #D6E0F8 | Pass |
Methodology: The top 20 text elements by font size were checked. Background color was sampled from the desktop screenshot using a 5-point pattern. WCAG 2.1 AA requires 4.5:1 for normal text and 3:1 for large text.
ALighthouse Accessibility AuditsScore 91/100 — 2 failing, 16 passedPASS
Accessibility
These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.
Names and labels
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
p.p_animatie_ai > span.ai-rotator-line > span > img p.p_animatie_ai > span.ai-rotator-line > span > img |
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Best practices
One main landmark helps screen reader users navigate a web page. Learn more about landmarks.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
html html |
These items highlight common accessibility best practices.