Accessibility

D

Tabindex Anti-Patterns

Action

0 positive, 37 -1-on-focusable

FIX

0 positive, 37 -1-on-focusable

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

D

Mobile-Readable Font Sizes

Action

62% of visible text renders at >= 12 CSS px (192 below threshold)

FIX

62% of visible text renders at >= 12 CSS px (192 below threshold)

192 text node(s) render below 12 CSS pixels on mobile

Mobile browsers default the root font-size to 16 px; text below ~ 12 px (75% of root) is hard to read without zooming. WCAG 1.4.4 (Resize Text) requires the page to support 200% zoom without loss of functionality -- which most layouts handle, but small base text still costs readability and conversion. Audit which selectors set sizes below 12 px (often footers, fine print, table cells) and bump them to 14-16 px or use rem units that scale with user preferences. Examples: <span> 11.2px ("Website health audit"); <p> 11.0px ("By scanning, you confirm you own this we..."); <span> 10.0px ("Real before & after"); <span> 10.0px ("From public scan history"); <span> 10.0px ("Real result").

D

Print Stylesheet

Action

No print styles

FIX

No print styles

No print-specific styles detected

When users print this page, they get the screen layout including navigation and non-essential elements. Add @media print rules to hide navigation and optimize layout for paper.

Print Stylesheet No Print Styles

Print stylesheet Not found ✗Inline @media print Not detected ✗

F

Navigation UX

Action

1 navigation pattern(s)

FIX

1 navigation pattern(s)

Skip navigation link detected

1 navigation landmark(s) detected

Hamburger menu detected (responsive design)

Breadcrumbs

Search

Skip Link Skip link detected

Labeled Navigation 1 <nav> element(s)

Back to Top

Hamburger Menu

Sticky Navigation Cannot reliably detect (CSS-based)

3 of 6 testable patterns navigation patterns detected. Strong navigation UX with multiple discovery paths.

C

Tap Target Adequacy

Action

7 tap target(s) too small or too close together

REVIEW

7 tap target(s) too small or too close together

7 tap target(s) too small or too close to neighbors

WCAG 2.5.5 (Level AAA) requires interactive targets to be at least 44x44 CSS pixels; WCAG 2.5.8 (Level AA, added in 2.2) requires 24x24 minimum. Failing targets cause mis-taps for users with motor impairments, large fingers, or shaky hands -- and are a major bounce-rate driver on mobile commerce flows. Lighthouse measures rendered rects + adjacent-element spacing; the failing list is in the Lighthouse 'tap-targets' audit detail panel.

B

404 Error Page

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Navigation links present on 404 page

Homepage link present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Page not found | WebScore ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗

B

Web Manifest

Valid manifest

REVIEW

Valid manifest

Name present: WebScore

192x192 icon present

512x512 icon present

Display mode: standalone

PWA Install Criteria Not Installable

Name WebScore ✓192×192 icon ✓512×512 icon ✓Start URL ✗Display Mode standalone ✓

Name WebScore Display Mode standalone Theme Color #ffffff Background Color #ffffff Icons 2 icon(s)

B

Dark Mode Support

Dark mode detected

REVIEW

Dark mode detected

Dark-specific theme-color detected

A theme-color with media='(prefers-color-scheme: dark)' adapts the browser toolbar for dark mode.

prefers-color-scheme CSS detected in inline styles

Detection limited to meta tags and inline styles

External CSS files may contain prefers-color-scheme rules not visible to this scan.

Dark Mode✓ Dark Mode Supported

color-scheme meta Not set ✗Dark theme-color white ✓CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

C

Color Contrast (Screenshot)

Action

20 text elements analyzed, 20 fail WCAG AA

REVIEW

Analyzes text contrast against the actual rendered page, including background images, gradients, and overlays that CSS-based tools cannot detect.

0 pass 20 fail WCAG AA

h2 Your agent can audit, fix and verify.

1.17:1

#000000

on

#171717

needs 3.0:1 (large text)

24px · bottom of viewport

h2 See your complete website health

1.17:1

#000000

on

#171717

needs 3.0:1 (large text)

24px · bottom of viewport

h2 From URL to a

1.17:1

#000000

on

#171717

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Know what good

1.17:1

#000000

on

#171717

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Useful after the

1.17:1

#000000

on

#171717

needs 3.0:1 (large text)

24px · bottom of viewport

h2 A speed score is only the

1.17:1

#000000

on

#171717

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Pay for the detail

1.17:1

#000000

on

#171717

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Clear answers,

1.17:1

#000000

on

#171717

needs 3.0:1 (large text)

24px · bottom of viewport

h2 One URL. One clear

1.17:1

#000000

on

#171717

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Your website is already showing you what…

1.17:1

#000000

on

#171717

needs 3.0:1 (large text)

24px · bottom of viewport

h3 Make every first impression faster

1.17:1

#000000

on

#171717

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Scan the page

1.17:1

#000000

on

#171717

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Follow the evidence

1.17:1

#000000

on

#171717

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Ship and verify

1.17:1

#000000

on

#171717

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Start with a free scan

1.17:1

#000000

on

#171717

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Keep every report unlocked

1.17:1

#000000

on

#171717

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Audit

1.17:1

#000000

on

#171717

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Learn

1.17:1

#000000

on

#171717

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Trust

1.17:1

#000000

on

#171717

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Popular free tools

1.17:1

#000000

on

#171717

needs 3.0:1 (large text)

19px · bottom of viewport

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h2 Your agent can audit…	1.17:1	3.0:1	#000000	#171717	Fail
h2 See your complete we…	1.17:1	3.0:1	#000000	#171717	Fail
h2 From URL to a	1.17:1	3.0:1	#000000	#171717	Fail
h2 Know what good	1.17:1	3.0:1	#000000	#171717	Fail
h2 Useful after the	1.17:1	3.0:1	#000000	#171717	Fail
h2 A speed score is onl…	1.17:1	3.0:1	#000000	#171717	Fail
h2 Pay for the detail	1.17:1	3.0:1	#000000	#171717	Fail
h2 Clear answers,	1.17:1	3.0:1	#000000	#171717	Fail
h2 One URL. One clear	1.17:1	3.0:1	#000000	#171717	Fail
h2 Your website is alre…	1.17:1	3.0:1	#000000	#171717	Fail
h3 Make every first imp…	1.17:1	3.0:1	#000000	#171717	Fail
h3 Scan the page	1.17:1	3.0:1	#000000	#171717	Fail
h3 Follow the evidence	1.17:1	3.0:1	#000000	#171717	Fail
h3 Ship and verify	1.17:1	3.0:1	#000000	#171717	Fail
h3 Start with a free sc…	1.17:1	3.0:1	#000000	#171717	Fail
h3 Keep every report un…	1.17:1	3.0:1	#000000	#171717	Fail
h3 Audit	1.17:1	3.0:1	#000000	#171717	Fail
h3 Learn	1.17:1	3.0:1	#000000	#171717	Fail
h3 Trust	1.17:1	3.0:1	#000000	#171717	Fail
h3 Popular free tools	1.17:1	3.0:1	#000000	#171717	Fail

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.

A+

Landmark Structure

26 landmarks

PASS

26 landmarks

<main> landmark present

1 <nav> landmark(s) found

Skip navigation link present

Page Structure — as a screen reader sees it

A+

Heading Hierarchy

30 headings

PASS

30 headings

Single H1 present

H1 Audit your site.Fix what matters.
H2 Your agent can audit, fix and verify.
H2 See your complete website health overview.
H3 Make every first impression faster
H2 From URL to a verified fix.
H3 Scan the page
H3 Follow the evidence
H3 Ship and verify
H2 Know what good looks like.
H2 Useful after the score.
H2 A speed score is only the first clue.
H2 Pay for the detail you need.
H3 Start with a free scan
H3 Keep every report unlocked
H2 Clear answers, up front.
H3 What is a website audit, and what does WebScore check?
H3 How is WebScore different from Google Lighthouse?
H3 How does pay-as-you-go work?
H3 What does Lifetime access include?
H3 How does automated monitoring work?
H3 What is the AI Conversion Audit?
H3 Can I use WebScore with my AI (MCP server)?
H3 Is Lifetime really a one-time payment?
H3 What if I only need one report?
H2 One URL. One clear place to start.
H2 Your website is already showing you what to fix next.
H3 Audit
H3 Learn
H3 Trust
H3 Popular free tools

A+

Heading Text Quality

All 30 heading(s) have substantive, well-formed text

PASS

All 30 heading(s) have substantive, well-formed text

Heading text quality is clean -- no placeholder, length, or styling issues

A+

Alt Text Quality

All 95 images OK

PASS

All 95 images OK

5 decorative image(s) correctly marked

90 image(s) with good alt text

95 images 90 good alt text 5 decorative

All images have appropriate alt text.

A+

Form Accessibility

All 2 controls labeled

PASS

All 2 controls labeled

2 control(s) properly labeled

2 controls

2 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
input	text	Website URL to analyze	aria-label
input	text	Website URL to analyze	aria-label

A

Link & Button Quality

148 links, 35 buttons — all OK

PASS

148 links, 35 buttons — all OK

85 link(s) open in new tab without warning

Add '(opens in new tab)' to link text or aria-label.

Got: https://x.com/yusukelp; https://www.uneed.best/tool/webscore-now; https://www.producthunt.com/products/webscore-now/reviews/new?utm_source=badg…; https://peerlist.io/scroll/post/ACTHLKLKMDJ8GNEB7FPJQD6OAOLPGD?commentId=CHR8…; https://peerlist.io/scroll/post/ACTHLKLKMDJ8GNEB7FPJQD6OAOLPGD?commentId=CHR8…; https://x.com/yusukelp; https://x.com/yusukelp; https://www.creem.io/; https://orynth.dev/projects/webscore-find-fix-websites-issues; https://startupfa.me/s/webscore?utm_source=webscore.now (+75 more)

63 link(s) with descriptive text

148 links

0 empty

0 generic text

85 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://x.com/yusukelp	Yusuke Matsuba	new tab	Add '(opens in new tab)' to text
https://www.uneed.best/tool/webscore-now	WebScore: Product of the Day w…	new tab	Add '(opens in new tab)' to text
https://www.producthunt.com/products/web…	Review WebScore.now on Product…	new tab	Add '(opens in new tab)' to text
https://peerlist.io/scroll/post/ACTHLKLK…	Nikita B.	new tab	Add '(opens in new tab)' to text
https://peerlist.io/scroll/post/ACTHLKLK…	@bbordiyann	new tab	Add '(opens in new tab)' to text
https://x.com/yusukelp	Yusuke Matsuba	new tab	Add '(opens in new tab)' to text
https://x.com/yusukelp	@yusukelp	new tab	Add '(opens in new tab)' to text
https://www.creem.io/	Payments secured byCreem	new tab	Add '(opens in new tab)' to text
https://orynth.dev/projects/webscore-fin…	Featured on Orynth	new tab	Add '(opens in new tab)' to text
https://startupfa.me/s/webscore?utm_sour…	WebScore - Featured on Startup…	new tab	Add '(opens in new tab)' to text
https://turbo0.com/item/webscore	Listed on Turbo0	new tab	Add '(opens in new tab)' to text
https://www.saashub.com/webscore?utm_sou…	WebScore badge	new tab	Add '(opens in new tab)' to text
https://mozolist.com/launch/webscore	Featured on Mozolist	new tab	Add '(opens in new tab)' to text
https://www.launchit.site/launches/websc…	Launched on Launchit	new tab	Add '(opens in new tab)' to text
https://www.techtrendin.com/products/web…	Featured on TechTrendin'	new tab	Add '(opens in new tab)' to text
https://spotstartups.com	Featured on SpotStartups	new tab	Add '(opens in new tab)' to text
https://findly.tools/webscore-find-fix-w…	Featured on Findly.tools	new tab	Add '(opens in new tab)' to text
https://newtool.site/item/webscorenow-fi…	Featured on NewTool.site	new tab	Add '(opens in new tab)' to text
https://favtool.ai	Featured on FavTool.ai	new tab	Add '(opens in new tab)' to text
https://gets.tools	Featured on Gets.Tools	new tab	Add '(opens in new tab)' to text
https://firstlook.tools	Featured on First Look	new tab	Add '(opens in new tab)' to text
https://toolslisthq.com	Featured on Tools List HQ	new tab	Add '(opens in new tab)' to text
https://startupdirectory.net	Featured on Startup Directory	new tab	Add '(opens in new tab)' to text
https://saasroots.com	Featured on SaaS Roots	new tab	Add '(opens in new tab)' to text
https://huntfortools.com	Featured on Hunt for Tools	new tab	Add '(opens in new tab)' to text
https://drchecker.net/item/webscore.now	Monitor your Domain Rating wit…	new tab	Add '(opens in new tab)' to text
https://appsytools.com/tool/webscore	Featured on Appsy Tools	new tab	Add '(opens in new tab)' to text
https://tooldynamo.com/tools/webscore	Featured on Tool Dynamo	new tab	Add '(opens in new tab)' to text
https://buildlist.io	Featured on Buildlist	new tab	Add '(opens in new tab)' to text
https://goodaitools.com/ai/webscore	Featured on Good AI Tools	new tab	Add '(opens in new tab)' to text
https://verifieddr.com/website/webscore-…	TrueDR	new tab	Add '(opens in new tab)' to text
https://saasgrow.app?ref=webscore.now	Featured on SaasGrow	new tab	Add '(opens in new tab)' to text
https://easydofollow.dev/dev-tools/websc…	Featured on EasyDoFollow	new tab	Add '(opens in new tab)' to text
https://nicklaunches.com/products/websco…	Featured on Nick Launches	new tab	Add '(opens in new tab)' to text
https://marketingdb.live	featured on marketing db	new tab	Add '(opens in new tab)' to text
https://www.foundrlist.com/product/websc…	Featured on FoundrList	new tab	Add '(opens in new tab)' to text
https://wired.business	Featured on Wired Business	new tab	Add '(opens in new tab)' to text
https://launchpadly.co/startup/webscore?…	Featured on Launchpadly	new tab	Add '(opens in new tab)' to text
https://productlistdir.com/product/websc…	Featured on ProductListDir	new tab	Add '(opens in new tab)' to text
https://neeed.directory	Featured on Need	new tab	Add '(opens in new tab)' to text
https://tools.launchllama.co?utm_source=…	Featured badge	new tab	Add '(opens in new tab)' to text
https://uno.directory	Featured on uno directory	new tab	Add '(opens in new tab)' to text
https://launchstreak.dev/dev-tools/websc…	Launched on LaunchStreak	new tab	Add '(opens in new tab)' to text
https://saasfame.com/item/webscore	Featured on SaaSfame	new tab	Add '(opens in new tab)' to text
https://dailypings.com/p/webscore-free-w…	Featured on DailyPings	new tab	Add '(opens in new tab)' to text
https://orynth.dev/projects/webscore-fin…	Featured on Orynth	new tab	Add '(opens in new tab)' to text
https://startupfa.me/s/webscore?utm_sour…	WebScore - Featured on Startup…	new tab	Add '(opens in new tab)' to text
https://turbo0.com/item/webscore	Listed on Turbo0	new tab	Add '(opens in new tab)' to text
https://www.saashub.com/webscore?utm_sou…	WebScore badge	new tab	Add '(opens in new tab)' to text
https://mozolist.com/launch/webscore	Featured on Mozolist	new tab	Add '(opens in new tab)' to text
https://www.launchit.site/launches/websc…	Launched on Launchit	new tab	Add '(opens in new tab)' to text
https://www.techtrendin.com/products/web…	Featured on TechTrendin'	new tab	Add '(opens in new tab)' to text
https://spotstartups.com	Featured on SpotStartups	new tab	Add '(opens in new tab)' to text
https://findly.tools/webscore-find-fix-w…	Featured on Findly.tools	new tab	Add '(opens in new tab)' to text
https://newtool.site/item/webscorenow-fi…	Featured on NewTool.site	new tab	Add '(opens in new tab)' to text
https://favtool.ai	Featured on FavTool.ai	new tab	Add '(opens in new tab)' to text
https://gets.tools	Featured on Gets.Tools	new tab	Add '(opens in new tab)' to text
https://firstlook.tools	Featured on First Look	new tab	Add '(opens in new tab)' to text
https://toolslisthq.com	Featured on Tools List HQ	new tab	Add '(opens in new tab)' to text
https://startupdirectory.net	Featured on Startup Directory	new tab	Add '(opens in new tab)' to text
https://saasroots.com	Featured on SaaS Roots	new tab	Add '(opens in new tab)' to text
https://huntfortools.com	Featured on Hunt for Tools	new tab	Add '(opens in new tab)' to text
https://drchecker.net/item/webscore.now	Monitor your Domain Rating wit…	new tab	Add '(opens in new tab)' to text
https://appsytools.com/tool/webscore	Featured on Appsy Tools	new tab	Add '(opens in new tab)' to text
https://tooldynamo.com/tools/webscore	Featured on Tool Dynamo	new tab	Add '(opens in new tab)' to text
https://buildlist.io	Featured on Buildlist	new tab	Add '(opens in new tab)' to text
https://goodaitools.com/ai/webscore	Featured on Good AI Tools	new tab	Add '(opens in new tab)' to text
https://verifieddr.com/website/webscore-…	TrueDR	new tab	Add '(opens in new tab)' to text
https://saasgrow.app?ref=webscore.now	Featured on SaasGrow	new tab	Add '(opens in new tab)' to text
http://easydofollow.dev/dev-tools/websco…	Featured on EasyDoFollow	new tab	Add '(opens in new tab)' to text
https://nicklaunches.com/products/websco…	Featured on Nick Launches	new tab	Add '(opens in new tab)' to text
https://marketingdb.live	featured on marketing db	new tab	Add '(opens in new tab)' to text
https://www.foundrlist.com/product/websc…	Featured on FoundrList	new tab	Add '(opens in new tab)' to text
https://wired.business	Featured on Wired Business	new tab	Add '(opens in new tab)' to text
https://launchpadly.co/startup/webscore?…	Featured on Launchpadly	new tab	Add '(opens in new tab)' to text
https://productlistdir.com/product/websc…	Featured on ProductListDir	new tab	Add '(opens in new tab)' to text
https://neeed.directory	Featured on Need	new tab	Add '(opens in new tab)' to text
https://tools.launchllama.co?utm_source=…	Featured badge	new tab	Add '(opens in new tab)' to text
https://uno.directory	Featured on uno directory	new tab	Add '(opens in new tab)' to text
https://launchstreak.dev/dev-tools/websc…	Launched on LaunchStreak	new tab	Add '(opens in new tab)' to text
https://saasfame.com/item/webscore	Featured on SaaSfame	new tab	Add '(opens in new tab)' to text
https://dailypings.com/p/webscore-free-w…	Featured on DailyPings	new tab	Add '(opens in new tab)' to text
https://webscore.now/trust/webscore.now	WebScore Trust Badge	new tab	Add '(opens in new tab)' to text
https://gdprfix.eu/?ref=webscore.now	Cookie checker	new tab	Add '(opens in new tab)' to text
https://x.com/WebScore_now	@WebScore_now	new tab	Add '(opens in new tab)' to text

98 links and buttons have descriptive text

Add '(opens in new tab)' to link text or aria-label.

https://x.com/yusukelp; https://www.uneed.best/tool/webscore-now; https://www.producthunt.com/products/webscore-now/reviews/new?utm_source=badg…; https://peerlist.io/scroll/post/ACTHLKLKMDJ8GNEB7FPJQD6OAOLPGD?commentId=CHR8…; https://peerlist.io/scroll/post/ACTHLKLKMDJ8GNEB7FPJQD6OAOLPGD?commentId=CHR8…; https://x.com/yusukelp; https://x.com/yusukelp; https://www.creem.io/; https://orynth.dev/projects/webscore-find-fix-websites-issues; https://startupfa.me/s/webscore?utm_source=webscore.now (+75 more)

Why this matters

Links with target="_blank" without rel="noopener" leak the originating page's window context — security and UX issue.

Learn more ▾

Without rel="noopener", the new tab can navigate the original tab via window.opener (tab-nabbing attack). Modern browsers default to noopener for target=_blank but only since recent versions. Always set rel="noopener noreferrer" explicitly.

Source: MDN target / OWASP

A

Form Input Types

2 input(s) using type=text where a specific type would help

PASS

2 input(s) using type=text where a specific type would help

Input "Website URL to analyze" should use type="url" (currently type="text")

Field name "Website URL to analyze" suggests type="url". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="url">.

Input "Website URL to analyze" should use type="url" (currently type="text")

Field name "Website URL to analyze" suggests type="url". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="url">.

A+

Form Input Quality

2 form control(s) checked, no input-semantic issues

PASS

2 form control(s) checked, no input-semantic issues

All form input semantics look correct

A+

Mobile Keyboard & Autofill

No autofill-eligible form controls

PASS

No autofill-eligible form controls

No autofill-eligible form controls (no name/email/tel/address fields)

A+

Document Language

Lang attribute set to "en"

PASS

Lang attribute set to "en"

<html lang="en"> is set and valid

Got: en

A+

Iframe Accessibility

No iframes on this page

PASS

No iframes on this page

A

Favicon & Branding

12 icon(s) detected

PASS

12 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

SVG favicon detected — scales perfectly to any size

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✓ SVG Favicon Present

✓ Manifest Icons Present

✓ Multiple Sizes Present

A+

PWA Depth

1 PWA signal(s) surfaced

PASS

1 PWA signal(s) surfaced

Manifest has no maskable icon

Android 12+ Adaptive Icons crop non-maskable icons to a circle or squircle -- frequently hiding important parts of the logo. Add at least one icon entry with `"purpose": "maskable"` (or `"any maskable"`) and a maskable-aware design (16% safe-zone padding around the inner mark).

A+

Mobile UX Depth

2 mobile-depth signal(s) detected

PASS

2 mobile-depth signal(s) detected

Browser-chrome `theme-color` meta tag present

The page sets `<meta name="theme-color" content="...">`, which Android Chrome uses to tint the status bar and iOS Safari uses for the toolbar background. Brand polish that costs nothing and Just Works.

Viewport `viewport-fit=cover` -- supports notched / dynamic-island devices

The viewport meta declares `viewport-fit=cover`, which lets the page draw into the safe-area edges (notch, dynamic island, home indicator) on iPhone X+ devices. Pair with `env(safe-area-inset-*)` CSS to keep critical UI inside the inset rectangle while letting backgrounds extend edge-to-edge.

A

Lighthouse Accessibility Audits

Score 93/100 — 3 failing, 33 passed

PASS

93

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.

ARIA

Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
01 · PERFORMANCE Make every first impression faster Find the images, scripts an… `div.landing-wrap > div.scroll-reveal > div.grid > div.border-t`

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Show results for me-mo.ro `aside.w-full > div.flex > div.flex > button.h-1.5`
Show results for pura-vida-forest-home.com `aside.w-full > div.flex > div.flex > button.h-1.5`
Show results for gdprfix.eu `aside.w-full > div.flex > div.flex > button.h-1.5`
Show results for oanaiurascu.ro `aside.w-full > div.flex > div.flex > button.h-1.5`
Show results for budgetbro.app `aside.w-full > div.flex > div.flex > button.h-1.5`
Nikita B. `figcaption.flex > div > p.text-sm > a.hover:underline`
@bbordiyann `figcaption.flex > div > p.mt-1 > a.hover:underline`

These items highlight common accessibility best practices.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Website 99.96% uptime 30 days ago Today `div.ff-root > a.ff-slim`

○Interactive controls are keyboard focusable

○Interactive elements indicate their purpose and state

○The page has a logical tab order

○Visual order on the page follows DOM order

○User focus is not accidentally trapped in a region

○The user's focus is directed to new content added to the page

○HTML5 landmark elements are used to improve navigation

○Offscreen content is hidden from assistive technology

○Custom controls have associated labels

○Custom controls have ARIA roles

●`[aria-*]` attributes match their roles

●`[aria-hidden="true"]` is not present on the document `<body>`

●`[role]`s have all required `[aria-*]` attributes

●`[role]`s are contained by their required parent element

●`[role]` values are valid

●`[aria-*]` attributes have valid values

●`[aria-*]` attributes are valid and not misspelled

●Buttons have an accessible name

●Image elements have `[alt]` attributes

●Form elements have associated labels

●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.

●ARIA attributes are used as specified for the element's role

●`[aria-hidden="true"]` elements do not contain focusable descendents

●Elements use only permitted ARIA attributes

●Background and foreground colors have a sufficient contrast ratio

●`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.

●Definition list items are wrapped in `<dl>` elements

●Document has a `<title>` element

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●Links are distinguishable without relying on color.

●Links have a discernible name

●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

●No element has a `[tabindex]` value greater than 0

●Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.

●Heading elements appear in a sequentially-descending order

●Skip links are focusable.

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Identical links have the same purpose.

●Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.

●`<td>` elements in a large `<table>` have one or more table headers.

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements have accessible names

○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○Elements with the `role=text` attribute do not have focusable descendents.

○ARIA toggle fields have accessible names

○ARIA `tooltip` elements have accessible names

○ARIA `treeitem` elements have accessible names

○The page contains a heading, skip link, or landmark region

○ARIA IDs are unique

○No form fields have multiple labels

○`<frame>` or `<iframe>` elements have a title

○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.

○Input buttons have discernible text.

○`<input type="image">` elements have `[alt]` text

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○Select elements have associated label elements.

○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.

○`[lang]` attributes have a valid value

○`<video>` elements contain a `<track>` element with `[kind="captions"]`

○Tables have different content in the summary attribute and `<caption>`.

○All heading elements contain content.

○Uses ARIA roles only on compatible elements

○Image elements do not have `[alt]` attributes that are redundant text.