Browse & Analyze

Browse recent website audits and performance trends

Explore technology stacks detected across the web

Side-by-side technology comparisons and market share

Curated technology stacks and the sites that use them

Editorial deep-dives on the state of web performance

Browse and download favicons from analyzed websites

Learn

Common questions about BeaverCheck scores and checks

How we calculate scores across 100+ checks

The story behind BeaverCheck and the team

Practical guides to fix common web performance issues

Migration Guides

Step-by-step guides for moving between web technologies

Definitions for performance, SEO, and web platform terms

Contrast Checker

Check WCAG color contrast ratios between any two colors

Inspect HTTP response headers for any URL

Analyze SSL/TLS certificate details and chain

Look up DNS records for any domain

Redirect Checker

Trace the full redirect chain for any URL

Real-user INP and Core Web Vitals from Google's Chrome UX Report.

RESTful API for programmatic website audits

Embed an auto-updating health score badge on your site

https://home-run.co/?srsltid=AfmBOooLD5kDUxNEgXCM6Hw3QThoBhDzSDsHBurtQjqybXPmKxsuvHan

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.

SCORE

76

GRADE

C

FIX

7

REVIEW

5

PASS

12

INFO

0

Checks

24

12 PASS 5 REVIEW 7 FIX

D

Mobile Keyboard & Autofill

Action

2/2 eligible field(s) missing autocomplete or inputmode

FIX

2/2 eligible field(s) missing autocomplete or inputmode

1 field(s) missing recommended autocomplete attribute

WCAG 1.3.5 (Level AA): inputs whose purpose maps to a Common Input Purpose value should declare it via `autocomplete=`. Required for password managers, browser autofill, and assistive tech that customizes inputs (e.g., simplified keyboards). Mobile autofill in particular cuts form-completion time by 30-50% when these are present. Affected purposes: email.

Got: <input type="email">

1 field(s) would benefit from inputmode attribute

Mobile browsers pick the on-screen keyboard layout from `inputmode=` when present (numeric pad, tel dialpad, email keyboard). Without it, users see the default text keyboard and must mode-switch -- 2-3 extra taps per phone-number or numeric-ID field. Type-based defaults exist (`type=tel` shows the tel keyboard on most browsers) but `inputmode` is the explicit, cross-browser way to control this. Affected types: email.

Got: <input type="email">

D

Tabindex Anti-Patterns

Action

0 positive, 13 -1-on-focusable

FIX

0 positive, 13 -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.)

D

Mobile-Readable Font Sizes

Action

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

FIX

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

69 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: <div> 10.0px ("60"); <div> 10.0px ("Mins"); <p> 10.0px ("Deliver To"); <span> 10.0px ("60 Mins"); <span> 10.0px ("Pay on Delivery").

D

Web Manifest

Action

Not found

FIX

Not found

No web manifest found

No manifest at standard paths (/manifest.json, /site.webmanifest). A manifest is optional but enables PWA features like home screen installation and standalone display.

No web manifest found.

D

Dark Mode Support

Action

No dark mode signals

FIX

No dark mode signals

No dark mode signals detected

Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.

Detection limited to meta tags and inline styles

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

Dark ModeNo Dark Mode Detected

color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Not detected ✗

Detection limited to meta tags and inline styles.

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

No navigation patterns

FIX

No navigation patterns

1 navigation landmark(s) detected

Hamburger menu detected (responsive design)

No breadcrumbs, search, or skip link detected

These navigation aids help users orient themselves and find content efficiently, especially on large sites.

Breadcrumbs

Search

Skip Link

Labeled Navigation 1 <nav> element(s)

Back to Top

Hamburger Menu

Sticky Navigation Cannot reliably detect (CSS-based)

2 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.

B

Link & Button Quality

1 issue(s) across 108 links and 48 buttons

REVIEW

1 issue(s) across 108 links and 48 buttons

5 link(s) open in new tab without warning

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

Got: https://economictimes.indiatimes.com/tech/funding/homerun-raises-6-6-million-…; https://homerun.page.link/tzH3; https://play.google.com/store/apps/details?id=com.homerun.app; https://apps.apple.com/in/app/homerun-materials-in-60-mins/id6740008084; https://wa.me/+918088321083

1 button(s) with no accessible text

Icon-only buttons need an aria-label so screen readers can announce them.

Got: button.relative (#228 on page)

103 link(s) with descriptive text

108 links

0 empty

0 generic text

5 new tab

1 empty buttons

Element	Text	Issue	Suggested Fix
/search	Search for CementPlywoodFevic…	img no alt	Add alt attribute to the image
/search	Search for CementPlywoodFevic…	img no alt	Add alt attribute to the image
/collections/cement	Cement	img no alt	Add alt attribute to the image
/collections/tiling	Tiling	img no alt	Add alt attribute to the image
/collections/painting	Painting	img no alt	Add alt attribute to the image
/collections/waterproofing	Water Proofing	img no alt	Add alt attribute to the image
/collections/plywood-mdf-hdhmr	Plywood, MDF & HDHMR	img no alt	Add alt attribute to the image
/collections/fevicol	Fevicol	img no alt	Add alt attribute to the image
/collections/wires	Wires, MCB & Distribution Boar…	img no alt	Add alt attribute to the image
/collections/kitchen-sinks-faucets	Kitchen Sinks & Faucets	img no alt	Add alt attribute to the image
/collections/sanitary-bath-fittings	Sanitary & Bath Fittings	img no alt	Add alt attribute to the image
/collections/switches-sockets	Switches & Sockets	img no alt	Add alt attribute to the image
/collections/hinges-channels-handles	Hinges, Channels & Handles	img no alt	Add alt attribute to the image
/collections/kitchen-systems-accessories	Kitchen Systems & Accessories	img no alt	Add alt attribute to the image
/collections/wardrobe-bed-fittings	Wardrobe & Bed Fittings	img no alt	Add alt attribute to the image
/collections/door-locks-hardware	Door Locks & Hardware	img no alt	Add alt attribute to the image
/collections/electrical-conduit-pipes	Conduits & GI Boxes	img no alt	Add alt attribute to the image
/collections/lighting	Lighting	img no alt	Add alt attribute to the image
/collections/plumbing	CPVC Pipes & Overhead Tanks	img no alt	Add alt attribute to the image
/collections/ceilingfans-exhaust	Ceiling Fans & Exhaust	img no alt	Add alt attribute to the image
/collections/power-tools-accessories	Power Tools & Accessories	img no alt	Add alt attribute to the image
/collections/cctv-surveillance	CCTV & Surveillance	img no alt	Add alt attribute to the image
/collections/home-appliances-power-backu…	Home Appliances & Power Backup	img no alt	Add alt attribute to the image
/collections/general-hardware-tools	General Hardware & Tools	img no alt	Add alt attribute to the image
/collections/safety-tools-workwear	Safety Tool & Workwear	img no alt	Add alt attribute to the image
/collections/glass-hardware	Glass Door Hardware	img no alt	Add alt attribute to the image
https://economictimes.indiatimes.com/tec…	Read how HomeRun raised $6.6 m…	new tab	Add '(opens in new tab)' to text
https://homerun.page.link/tzH3	Download the HomeRun app	new tab	Add '(opens in new tab)' to text
/collections/hettich-hardware	Furniture & Architectural Hard…	img no alt	Add alt attribute to the image
/collections/waterproofing	Waterproofing	img no alt	Add alt attribute to the image
/collections/fevicol	Fevicol	img no alt	Add alt attribute to the image
/collections/putty-primer	Putty & Primer	img no alt	Add alt attribute to the image
/collections/electrical-piping	Electrical Piping	img no alt	Add alt attribute to the image
https://play.google.com/store/apps/detai…	Google Play	new tab	Add '(opens in new tab)' to text
https://apps.apple.com/in/app/homerun-ma…	App Store	new tab	Add '(opens in new tab)' to text
https://wa.me/+918088321083	Contact	new tab	Add '(opens in new tab)' to text
<button>	(empty)	empty	Add button text or aria-label

150 links and buttons have descriptive text

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

https://economictimes.indiatimes.com/tech/funding/homerun-raises-6-6-million-…; https://homerun.page.link/tzH3; https://play.google.com/store/apps/details?id=com.homerun.app; https://apps.apple.com/in/app/homerun-materials-in-60-mins/id6740008084; https://wa.me/+918088321083

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

Icon-only buttons need an aria-label so screen readers can announce them.

button.relative (#228 on page)

Why this matters

Buttons with no accessible text (icon-only, no aria-label) can't be activated by voice control or understood by screen readers.

Source: WCAG 2.1 SC 4.1.2

B

Tap Target Adequacy

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

REVIEW

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

1 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 HomeRun ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗

B

Favicon & Branding

4 icon(s) detected

REVIEW

4 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✓ Multiple Sizes Present

C

Color Contrast (Screenshot)

Action

20 text elements analyzed, 1 fail WCAG AA

REVIEW

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

19 pass 1 fail WCAG AA 5 pass AA only

span Search for

1.88:1

#000000

on

#771309

needs 4.5:1 (normal text)

16px · above the fold

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Construction materia…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Deals Of The Week	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Newly Launched	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Customers love HomeR…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Get a first peek at …	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Company	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Policy	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Contact Information	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title Cement, Ply, Hardwar…	12.58:1	4.5:1	#000000	#EFC41A	Pass
p Open 8 am to 8 pm al…	16.99:1	4.5:1	#000000	#F9E7A3	Pass
p Open 8 am to 8 pm al…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
div Mins	21.00:1	4.5:1	#000000	#FFFFFF	Pass
p Deliver To	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span 560035	5.91:1	4.5:1	#000000	#B87770	Pass
span Search for	1.88:1	4.5:1	#000000	#771309	Fail
div Cement	5.99:1	4.5:1	#000000	#A18185	Pass
div Plywood	5.78:1	4.5:1	#000000	#878686	Pass
div Fevicol	5.10:1	4.5:1	#000000	#9B764F	Pass
div Cement	6.44:1	4.5:1	#000000	#B78452	Pass
span Wallet	12.42:1	4.5:1	#000000	#D7C4B1	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.

A

Landmark Structure

4 landmarks

PASS

4 landmarks

<main> landmark present

1 <nav> landmark(s) found

Skip navigation link is missing (WCAG 2.4.1)

Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.

Page Structure — as a screen reader sees it

Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.

Why this matters

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

A+

Heading Hierarchy

8 headings

PASS

8 headings

Single H1 present

H1 Construction materials with 60-minute delivery in Bangalore
H2 Deals Of The Week
H2 Newly Launched
H2 Customers love HomeRun
H3 Company
H3 Policy
H3 Contact Information
H2 Get a first peek at New Products, Special Offers, and so much more.

A+

Heading Text Quality

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

PASS

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

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

A

Alt Text Quality

3 of 125 images have issues

PASS

3 of 125 images have issues

3 image(s) with generic alt text

100 decorative image(s) correctly marked

22 image(s) with good alt text

125 images 22 good alt text 100 decorative 3 generic

Issue	Count
generic	3 image(s)

A

Form Accessibility

1 of 1 controls have issues

PASS

1 of 1 controls have issues

1 control(s) rely on placeholder only

Placeholder text disappears on focus and is not a reliable label.

Got: <input type="email">

1 controls

0 labeled

1 placeholder only

0 unlabeled

Control	Type	Label	Method
input	email	(Email)	placeholder only

Placeholder text disappears on focus and is not a reliable label.

<input type="email">

Why this matters

Placeholder-only labels disappear when the user starts typing — they must remember what the field was for.

Learn more ▾

Placeholders are NOT labels. They vanish on input, fail color contrast checks (most are gray), and don't satisfy WCAG SC 3.3.2. Always use a real <label> alongside (or aria-labelledby).

Source: WCAG 2.1 SC 3.3.2 / Nielsen Norman

A+

Form Input Types

1 form control(s) checked, no type mismatches

PASS

1 form control(s) checked, no type mismatches

No input-type mismatches detected

A+

Form Input Quality

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

PASS

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

All form input semantics look correct

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

No iframes on this page

A+

PWA Depth

No PWA depth issues detected

PASS

No PWA depth issues detected

No PWA depth issues detected

A+

Mobile UX Depth

1 mobile-depth signal(s) detected

PASS

1 mobile-depth signal(s) detected

No `<meta name="theme-color">` -- browser chrome falls back to default

Without `theme-color`, Android Chrome's status bar and iOS Safari's toolbar fall back to a generic gray. Adding a single hex color in `<meta name="theme-color" content="#0066cc">` tints them to your brand color across all mobile browsers.

A

Lighthouse Accessibility Audits

Score 93/100 — 3 failing, 24 passed

PASS

93

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.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Deliver To `div.flex > button.flex > div.min-w-0 > p.truncate`
Free Delivery `div.flex > div.flex > span.flex > span.text-[11px]`
on orders above ₹500 `article.group > div.flex > div.flex > span.text-[10px]`
₹ 440 `div.flex > div.flex > div.flex > span.text-sm`
Unlock Bulk Prices of ₹390 `div.flex > div.flex > div.h-5.5 > button.text-xs`
Free Delivery `div.flex > div.flex > span.flex > span.text-[11px]`
on orders above ₹500 `article.group > div.flex > div.flex > span.text-[10px]`
₹ 729 `div.flex > div.flex > div.flex > span.text-sm`
Free Delivery `div.flex > div.flex > span.flex > span.text-[11px]`
on orders above ₹500 `article.group > div.flex > div.flex > span.text-[10px]`
Free Delivery `div.flex > div.flex > span.flex > span.text-[11px]`
on orders above ₹500 `article.group > div.flex > div.flex > span.text-[10px]`
₹ 1,580 `div.flex > div.flex > div.flex > span.text-sm`
Free Delivery `div.flex > div.flex > span.flex > span.text-[11px]`
on orders above ₹500 `article.group > div.flex > div.flex > span.text-[10px]`
₹ 3,811 `div.flex > div.flex > div.flex > span.text-sm`
Free Delivery `div.flex > div.flex > span.flex > span.text-[11px]`
on orders above ₹500 `article.group > div.flex > div.flex > span.text-[10px]`
₹ 5,999 `div.flex > div.flex > div.flex > span.text-sm`
Unlock Bulk Prices of ₹2990 `div.flex > div.flex > div.h-5.5 > button.text-xs`
Free Delivery `div.flex > div.flex > span.flex > span.text-[11px]`
on orders above ₹500 `article.group > div.flex > div.flex > span.text-[10px]`
₹ 2,799 `div.flex > div.flex > div.flex > span.text-sm`
Free Delivery `div.flex > div.flex > span.flex > span.text-[11px]`
on orders above ₹500 `article.group > div.flex > div.flex > span.text-[10px]`
₹ 8,550 `div.flex > div.flex > div.flex > span.text-sm`
Free Delivery `div.flex > div.flex > span.flex > span.text-[11px]`
on orders above ₹500 `article.group > div.flex > div.flex > span.text-[10px]`
₹ 5,000 `div.flex > div.flex > div.flex > span.text-sm`
Free Delivery `div.flex > div.flex > span.flex > span.text-[11px]`
on orders above ₹500 `article.group > div.flex > div.flex > span.text-[10px]`
₹ 4,550 `div.flex > div.flex > div.flex > span.text-sm`
Free Delivery `div.flex > div.flex > span.flex > span.text-[11px]`
on orders above ₹500 `article.group > div.flex > div.flex > span.text-[10px]`
₹ 6,999 `div.flex > div.flex > div.flex > span.text-sm`
Unlock Bulk Prices of ₹3759 `div.flex > div.flex > div.h-5.5 > button.text-xs`
Free Delivery `div.flex > div.flex > span.flex > span.text-[11px]`
on orders above ₹500 `article.group > div.flex > div.flex > span.text-[10px]`
₹ 6,500 `div.flex > div.flex > div.flex > span.text-sm`
Free Delivery `div.flex > div.flex > span.flex > span.text-[11px]`
on orders above ₹500 `article.group > div.flex > div.flex > span.text-[10px]`
₹ 8,790 `div.flex > div.flex > div.flex > span.text-sm`

These are opportunities to improve the legibility of your content.

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
icon `div.flex > div.flex > div.flex > button.relative`

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
7% OFF `div.no-scrollbar > div.min-w-0 > article.group > a.block`
29% OFF `div.no-scrollbar > div.min-w-0 > article.group > a.block`
38% OFF `div.no-scrollbar > div.min-w-0 > article.group > a.block`
50% OFF `div.no-scrollbar > div.min-w-0 > article.group > a.block`
44% OFF `div.no-scrollbar > div.min-w-0 > article.group > a.block`
4% OFF `div.no-scrollbar > div.min-w-0 > article.group > a.block`
31% OFF `div.no-scrollbar > div.min-w-0 > article.group > a.block`
28% OFF `div.no-scrollbar > div.min-w-0 > article.group > a.block`
25% OFF `div.no-scrollbar > div.min-w-0 > article.group > a.block`
43% OFF `div.no-scrollbar > div.min-w-0 > article.group > a.block`
42% OFF `div.no-scrollbar > div.min-w-0 > article.group > a.block`
23% OFF `div.no-scrollbar > div.min-w-0 > article.group > a.block`

○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]` 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

●Document has a `<title>` element

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

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

●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

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

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

○`[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 an ARIA `[role]` that require children to contain a specific `[role]` have all required children.

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

○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

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

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

○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

○Links are distinguishable without relying on color.

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

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

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

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

○`[lang]` attributes have a valid value

○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.

○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.

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

Send Feedback