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://Mood.mozoo.com

Accessibility

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

SCORE

69

GRADE

D

FIX

8

REVIEW

5

PASS

11

INFO

0

Checks

24

11 PASS 5 REVIEW 8 FIX

D

Landmark Structure

Action

2 landmarks

FIX

2 landmarks

No <main> landmark found

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

No <nav> landmark 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

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

Why this matters

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.

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

F

Heading Hierarchy

Action

330 headings, 21 skip(s)

FIX

330 headings, 21 skip(s)

Single H1 present

Heading level skipped: H1 → H3 (missing H2)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H3 → H5 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H3 → H5 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H3 → H5 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H3 → H5 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H3 → H5 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H3 → H5 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H3 → H5 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H3 → H5 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H3 → H5 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H3 → H5 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H3 → H5 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H3 → H5 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H3 → H5 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H3 → H5 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H3 → H5 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H3 → H5 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H3 → H5 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H3 → H5 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H3 → H5 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H3 → H5 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

F

Form Accessibility

Action

31 of 31 controls have issues

FIX

31 of 31 controls have issues

15 control(s) without accessible label

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

Got: <input type="text" name="copy_the_link">; <input type="text" name="copy_the_link">; <input type="text" name="copy_the_link">; <input type="text" name="copy_the_link">; <input type="text" name="copy_the_link">; <input type="text" name="copy_the_link">; <input type="text" name="copy_the_link">; <input type="text" name="copy_the_link">; <input type="text" name="copy_the_link">; <input type="text" name="copy_the_link"> (+5 more)

16 control(s) rely on placeholder only

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

Got: <input type="text" name="search" id="search">; <input type="email" name="enter_mail_address">; <input type="email" name="enter_mail_address">; <input type="email" name="enter_mail_address">; <input type="email" name="enter_mail_address">; <input type="email" name="enter_mail_address">; <input type="email" name="enter_mail_address">; <input type="email" name="enter_mail_address">; <input type="email" name="enter_mail_address">; <input type="email" name="enter_mail_address"> (+6 more)

31 controls

0 labeled

16 placeholder only

15 unlabeled

Control	Type	Label	Method
#search	text	(Search by Brands, Authors...)	placeholder only
enter_mail_address	email	(Enter email address)	placeholder only
enter_mail_address	email	(Enter email address)	placeholder only
enter_mail_address	email	(Enter email address)	placeholder only
enter_mail_address	email	(Enter email address)	placeholder only
enter_mail_address	email	(Enter email address)	placeholder only
enter_mail_address	email	(Enter email address)	placeholder only
enter_mail_address	email	(Enter email address)	placeholder only
enter_mail_address	email	(Enter email address)	placeholder only
enter_mail_address	email	(Enter email address)	placeholder only
enter_mail_address	email	(Enter email address)	placeholder only
enter_mail_address	email	(Enter email address)	placeholder only
enter_mail_address	email	(Enter email address)	placeholder only
enter_mail_address	email	(Enter email address)	placeholder only
enter_mail_address	email	(Enter email address)	placeholder only
enter_mail_address	email	(Enter email address)	placeholder only
copy_the_link	text	(none)	none
copy_the_link	text	(none)	none
copy_the_link	text	(none)	none
copy_the_link	text	(none)	none
copy_the_link	text	(none)	none
copy_the_link	text	(none)	none
copy_the_link	text	(none)	none
copy_the_link	text	(none)	none
copy_the_link	text	(none)	none
copy_the_link	text	(none)	none
copy_the_link	text	(none)	none
copy_the_link	text	(none)	none
copy_the_link	text	(none)	none
copy_the_link	text	(none)	none
copy_the_link	text	(none)	none

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

<input type="text" name="copy_the_link">; <input type="text" name="copy_the_link">; <input type="text" name="copy_the_link">; <input type="text" name="copy_the_link">; <input type="text" name="copy_the_link">; <input type="text" name="copy_the_link">; <input type="text" name="copy_the_link">; <input type="text" name="copy_the_link">; <input type="text" name="copy_the_link">; <input type="text" name="copy_the_link"> (+5 more)

Why this matters

Form controls without labels — assistive tech announces 'edit text' with no context; users can't complete forms.

Source: WCAG 2.1 SC 3.3.2

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

<input type="text" name="search" id="search">; <input type="email" name="enter_mail_address">; <input type="email" name="enter_mail_address">; <input type="email" name="enter_mail_address">; <input type="email" name="enter_mail_address">; <input type="email" name="enter_mail_address">; <input type="email" name="enter_mail_address">; <input type="email" name="enter_mail_address">; <input type="email" name="enter_mail_address">; <input type="email" name="enter_mail_address"> (+6 more)

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

D

Favicon & Branding

Action

3 icon(s) detected

FIX

3 icon(s) detected

No favicon.ico at site root

Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.

HTML icon links detected

Apple touch icon present

✗ favicon.ico Missing

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

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

Theme color only

FIX

Theme color only

Theme-color present but no dark variant

A theme-color is set but no dark-specific variant was found. The browser toolbar may not adapt for dark mode users.

Got: #c3a1ff

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 ModePartial Dark Mode

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 ✗

B

Alt Text Quality

3 of 5 images have issues

REVIEW

3 of 5 images have issues

1 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

2 image(s) with generic alt text

2 image(s) with good alt text

5 images 2 good alt text 2 generic 1 missing

Issue	Count
missing	1 image(s)
generic	2 image(s)

Images without alt text are invisible to screen readers.

Why this matters

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

C

Link & Button Quality

Action

51 issue(s) across 341 links and 67 buttons

REVIEW

51 issue(s) across 341 links and 67 buttons

1 link(s) with no accessible text

Links without text are announced as raw URLs by screen readers.

Got: https://mood.mozoo.com/signin?signin

49 link(s) open in new tab without warning

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

Got: https://www.linkedin.com/company/mozoogroup/; https://www.instagram.com/wearemozoo/; https://mood.mozoo.com/search?search=Oreo; https://mood.mozoo.com/search?search_cat=54; https://mood.mozoo.com/search?search_cat=16; https://mood.mozoo.com/search?search=MAE; https://mood.mozoo.com/search?search_cat=55; https://mood.mozoo.com/search?search_cat=9; https://mood.mozoo.com/search?search=Alpro; https://mood.mozoo.com/search?search_cat=55 (+39 more)

50 button(s) with no accessible text

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

Got: button.popin-close-cross (#438 on page); button.popin_right_btn2 (#442 on page); button.popin_right_btn3 (#446 on page); button.popin-close-cross (#629 on page); button.popin_right_btn2 (#633 on page); button.popin_right_btn3 (#637 on page); button.popin-close-cross (#820 on page); button.popin_right_btn2 (#824 on page); button.popin_right_btn3 (#828 on page); button.popin-close-cross (#1006 on page) (+40 more)

291 link(s) with descriptive text

341 links

1 empty

0 generic text

49 new tab

50 empty buttons

Element	Text	Issue	Suggested Fix
https://mood.mozoo.com/signin?signin	(empty)	empty	Add link text or aria-label
https://www.linkedin.com/company/mozoogr…	Linkedin	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/wearemozoo/	Instagram	new tab	Add '(opens in new tab)' to text
https://mood.mozoo.com/search?search=Ore…	Oreo	new tab	Add '(opens in new tab)' to text
https://mood.mozoo.com/search?search_cat…	Instagram	new tab	Add '(opens in new tab)' to text
https://mood.mozoo.com/search?search_cat…	Food	new tab	Add '(opens in new tab)' to text
https://mood.mozoo.com/search?search=MAE	MAE	new tab	Add '(opens in new tab)' to text
https://mood.mozoo.com/search?search_cat…	Tik Tok	new tab	Add '(opens in new tab)' to text
https://mood.mozoo.com/search?search_cat…	Bank / Insurance	new tab	Add '(opens in new tab)' to text
https://mood.mozoo.com/search?search=Alp…	Alpro	new tab	Add '(opens in new tab)' to text
https://mood.mozoo.com/search?search_cat…	Tik Tok	new tab	Add '(opens in new tab)' to text
https://mood.mozoo.com/search?search_cat…	Food	new tab	Add '(opens in new tab)' to text
https://mood.mozoo.com/search?search=Sol…	Solarbox	new tab	Add '(opens in new tab)' to text
https://mood.mozoo.com/search?search_cat…	Display	new tab	Add '(opens in new tab)' to text
https://mood.mozoo.com/search?search_cat…	Power & Energy	new tab	Add '(opens in new tab)' to text
https://mood.mozoo.com/search?search_cat…	Display	new tab	Add '(opens in new tab)' to text
https://mood.mozoo.com/search?search_cat…	Beauty / Perfume	new tab	Add '(opens in new tab)' to text
https://mood.mozoo.com/search?search=CLI…	CLINIQUE	new tab	Add '(opens in new tab)' to text
https://mood.mozoo.com/search?search_cat…	Instagram	new tab	Add '(opens in new tab)' to text
https://mood.mozoo.com/search?search_cat…	Beauty / Perfume	new tab	Add '(opens in new tab)' to text
https://mood.mozoo.com/search?search=Pos…	Posca	new tab	Add '(opens in new tab)' to text
https://mood.mozoo.com/search?search_cat…	Instagram	new tab	Add '(opens in new tab)' to text
https://mood.mozoo.com/search?search_cat…	Art / Entertainment	new tab	Add '(opens in new tab)' to text
https://mood.mozoo.com/search?search_cat…	Display	new tab	Add '(opens in new tab)' to text
https://mood.mozoo.com/search?search_cat…	Pharmaceuticals	new tab	Add '(opens in new tab)' to text
https://mood.mozoo.com/search?search=Aid…	Aides	new tab	Add '(opens in new tab)' to text
https://mood.mozoo.com/search?search_cat…	Tik Tok	new tab	Add '(opens in new tab)' to text
https://mood.mozoo.com/search?search_cat…	NPO	new tab	Add '(opens in new tab)' to text
https://mood.mozoo.com/search?search=CDi…	CDiscount	new tab	Add '(opens in new tab)' to text
https://mood.mozoo.com/search?search_cat…	Display	new tab	Add '(opens in new tab)' to text
https://mood.mozoo.com/search?search_cat…	Retail	new tab	Add '(opens in new tab)' to text
https://mood.mozoo.com/search?search=URI…	URIAGE - Baby	new tab	Add '(opens in new tab)' to text
https://mood.mozoo.com/search?search_cat…	Tik Tok	new tab	Add '(opens in new tab)' to text
https://mood.mozoo.com/search?search_cat…	Health	new tab	Add '(opens in new tab)' to text
https://mood.mozoo.com/search?search=Col…	Colgate	new tab	Add '(opens in new tab)' to text
https://mood.mozoo.com/search?search_cat…	Instagram	new tab	Add '(opens in new tab)' to text
https://mood.mozoo.com/search?search_cat…	Health	new tab	Add '(opens in new tab)' to text
https://mood.mozoo.com/search?search_cat…	Display	new tab	Add '(opens in new tab)' to text
https://mood.mozoo.com/search?search_cat…	Home / Decoration	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/p/BYso2nmFy3O/	Instagram	new tab	Add '(opens in new tab)' to text
https://mood.mozoo.com/search?search=Soc…	Société Générale	new tab	Add '(opens in new tab)' to text
https://mood.mozoo.com/search?search_cat…	Instagram	new tab	Add '(opens in new tab)' to text
https://mood.mozoo.com/search?search_cat…	Bank / Insurance	new tab	Add '(opens in new tab)' to text
https://mood.mozoo.com/search?search=EBA…	EBAY	new tab	Add '(opens in new tab)' to text
https://mood.mozoo.com/search?search_cat…	Tik Tok	new tab	Add '(opens in new tab)' to text
https://mood.mozoo.com/search?search_cat…	Online / App	new tab	Add '(opens in new tab)' to text
terms	Terms & conditions	new tab	Add '(opens in new tab)' to text
legal-notice	Legal Notice	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/company/mozoogr…	Linkedin	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/wearemozoo/	Instagram	new tab	Add '(opens in new tab)' to text
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label

308 links and buttons have descriptive text

Links without text are announced as raw URLs by screen readers.

https://mood.mozoo.com/signin?signin

Why this matters

Links with no accessible text (empty <a></a>, image-only no alt, icon-only no aria-label) are unidentifiable to screen readers.

Source: WCAG 2.1 SC 2.4.4

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

https://www.linkedin.com/company/mozoogroup/; https://www.instagram.com/wearemozoo/; https://mood.mozoo.com/search?search=Oreo; https://mood.mozoo.com/search?search_cat=54; https://mood.mozoo.com/search?search_cat=16; https://mood.mozoo.com/search?search=MAE; https://mood.mozoo.com/search?search_cat=55; https://mood.mozoo.com/search?search_cat=9; https://mood.mozoo.com/search?search=Alpro; https://mood.mozoo.com/search?search_cat=55 (+39 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

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

button.popin-close-cross (#438 on page); button.popin_right_btn2 (#442 on page); button.popin_right_btn3 (#446 on page); button.popin-close-cross (#629 on page); button.popin_right_btn2 (#633 on page); button.popin_right_btn3 (#637 on page); button.popin-close-cross (#820 on page); button.popin_right_btn2 (#824 on page); button.popin_right_btn3 (#828 on page); button.popin-close-cross (#1006 on page) (+40 more)

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

C

Mobile-Readable Font Sizes

Action

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

REVIEW

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

5 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: <a> 10.0px ("Login"); <a> 10.0px ("Sign Up"); <span> 10.0px ("Instagram"); <span> 10.0px ("Tik Tok"); <span> 10.0px ("Tik Tok").

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

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Home | Mood by Mozoo ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✗

B

Lighthouse Accessibility Audits

Score 88/100 — 3 failing, 12 passed

REVIEW

88

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
LOGIN `div > div.df > a.t14 > button.btn`
SIGN UP `div > div.df > a > button.btn`
SIGN IN NOW `div.home-middle > div.container > div.pr > a.btn`

These are opportunities to improve the legibility of your content.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
JAGUAR `div.listing-bot > div.fc > div.listing-name > h3.t14`
MPU `div.listing-bot > div.fc > div.listing-name > h5.t9`
INTERSTITIEL `div.listing-bot > div.fc > div.listing-name > h5.t9`
CTV `div.listing-bot > div.fc > div.listing-name > h5.t9`
SLIDEVIEW `div.listing-bot > div.fc > div.listing-name > h5.t9`
SLIDEVIEW `div.listing-bot > div.fc > div.listing-name > h5.t9`

These are opportunities to improve keyboard navigation in your application.

Best practices

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html `html`

These items highlight common accessibility best practices.

○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-hidden="true"]` is not present on the document `<body>`

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

●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

●Touch targets have sufficient size and spacing.

○`[accesskey]` values are unique

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

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

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

○Deprecated ARIA roles were not used

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

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

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○Elements use only permitted ARIA attributes

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

○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

○`[role]` values are valid

○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

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

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

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

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

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

○Identical links have the same purpose.

○Elements with visible text labels have matching accessible names.

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

A+

Heading Text Quality

1 heading-text-quality issue(s) detected

PASS

1 heading-text-quality issue(s) detected

24 heading(s) are all-uppercase (excluding short acronyms)

Headings rendered in all-uppercase are a styling choice that should be done via CSS (`text-transform: uppercase`), not by typing the text in caps. Capitalized text is read letter-by-letter by some screen readers (e.g., "H-E-L-L-O W-O-R-L-D" instead of "hello world"). It's also a soft signal of CMS-migration artifacts where the original lowercase intent was lost.

Got: 24 all-caps heading(s)

A+

Form Input Types

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

PASS

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

Input "search" should use type="search" (currently type="text")

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

A+

Form Input Quality

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

PASS

31 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+

Tabindex Anti-Patterns

No explicit tabindex attributes found

PASS

No explicit tabindex attributes found

No explicit tabindex attributes found

A+

Iframe Accessibility

No iframes on this page

PASS

No iframes on this page

No iframes on this page

A+

Tap Target Adequacy

All tap targets meet WCAG 2.5.5/2.5.8 sizing

PASS

All tap targets meet WCAG 2.5.5/2.5.8 sizing

All tap targets meet WCAG 2.5.5 (44x44px) sizing

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

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.

A+

Color Contrast (Screenshot)

20 text elements analyzed, 0 fail WCAG AA

PASS

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

20 pass

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Sign up	16.41:1	3.0:1	#000000	#ABEEFF	Pass
h1 for full access	16.41:1	3.0:1	#000000	#ABEEFF	Pass
h3 Oreo	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Send a link	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Send by mail	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Oreo	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 MAE	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Send a link	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Send by mail	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 MAE	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Alpro	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Send a link	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Send by mail	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Alpro	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Solarbox	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Send a link	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Send by mail	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Test the creative on…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Solarbox	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Wilkinson	21.00:1	3.0:1	#000000	#FFFFFF	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.

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

Send Feedback