Skip to content
https://www.lapressemedia.it

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
79
GRADE
C
FIX
4
REVIEW
7
PASS
13
INFO
0
Checks
24
13 PASS 7 REVIEW 4 FIX
D
Web Manifest
Action
Not found
FIX
Not found
Info::
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
Info::
No dark mode signals detected
Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.
Info::
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
Info::
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
Info::
7 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Info::
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 7 <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.
C
Alt Text Quality
Action
8 of 23 images have issues
REVIEW
8 of 23 images have issues
Critical::
8 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Info::
9 decorative image(s) correctly marked
Info::
6 image(s) with good alt text
23 images 6 good alt text 9 decorative 8 missing
IssueCount
missing8 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

B
Form Accessibility
2 of 6 controls have issues
REVIEW
2 of 6 controls have issues
Critical::
1 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="button" name="Submit">
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="email" name="user[email]" id="acym__user__edit__email">
Info::
4 control(s) properly labeled
6 controls
4 labeled
1 placeholder only
1 unlabeled
ControlTypeLabelMethod
#fusion-live-search-input-0searchCerca per:none
inputsubmitCercaaria-label
#fusion-live-search-input-1searchCerca per:none
inputsubmitCercaaria-label
#acym__user__edit__emailemail(Email)placeholder only
Submitbutton(none)none

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

<input type="button" name="Submit">

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="email" name="user[email]" id="acym__user__edit__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

B
Mobile-Readable Font Sizes
99% of visible text renders at >= 12 CSS px (1 below threshold)
REVIEW
99% of visible text renders at >= 12 CSS px (1 below threshold)
Info::
1 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> 10.0px ("Powered by").
B
Favicon & Branding
4 icon(s) detected
REVIEW
4 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
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, 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
h1 Da 30 anni, lasciamo parlare i fatti
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
32px · bottom of viewport
h2 2.500 lanci al giorno e un flusso di new…
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Premio Pulitzer Fotografia vincitrice pe…
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Premio Pulitzer Fotografia premiata 1965
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Premio Pulitzer Miglior fotografia di cr…
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Premio Pulitzer Fotografia vincitrice pe…
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Foto
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Gianni Agnelli in arte l’Avvocato
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Sophia!
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 The Royals – Amori a Corte
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Motor Trend Mag
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Produzioni TV
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Spari contro Trump a un comizio in Penns…
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Crollo a Scampia, i residenti: “Rabbia…
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Parigi 2024: la torcia olimpica davanti …
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Valle d’Aosta, a Cervinia si scava nel…
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Video News
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h3 Ultime News:
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Create a connection with arresting photo…
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
19px · bottom of viewport
h3 ON AIR
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
19px · bottom of viewport
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Da 30 anni, lasciamo…1.00:13.0:1
#000000
#000000
Fail
h2 2.500 lanci al giorn…1.00:13.0:1
#000000
#000000
Fail
h2 Premio Pulitzer Foto…1.00:13.0:1
#000000
#000000
Fail
h2 Premio Pulitzer Foto…1.00:13.0:1
#000000
#000000
Fail
h2 Premio Pulitzer Migl…1.00:13.0:1
#000000
#000000
Fail
h2 Premio Pulitzer Foto…1.00:13.0:1
#000000
#000000
Fail
h2 Foto1.00:13.0:1
#000000
#000000
Fail
h2 Gianni Agnelli in ar…1.00:13.0:1
#000000
#000000
Fail
h2 Sophia!1.00:13.0:1
#000000
#000000
Fail
h2 The Royals – Amori…1.00:13.0:1
#000000
#000000
Fail
h2 Motor Trend Mag1.00:13.0:1
#000000
#000000
Fail
h2 Produzioni TV1.00:13.0:1
#000000
#000000
Fail
h2 Spari contro Trump a…1.00:13.0:1
#000000
#000000
Fail
h2 Crollo a Scampia, i …1.00:13.0:1
#000000
#000000
Fail
h2 Parigi 2024: la torc…1.00:13.0:1
#000000
#000000
Fail
h2 Valle d’Aosta, a C…1.00:13.0:1
#000000
#000000
Fail
h2 Video News1.00:13.0:1
#000000
#000000
Fail
h3 Ultime News:1.00:13.0:1
#000000
#000000
Fail
h3 Create a connection …1.00:13.0:1
#000000
#000000
Fail
h3 ON AIR1.00:13.0:1
#000000
#000000
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.

B
Lighthouse Accessibility Audits
Score 85/100 — 5 failing, 21 passed
REVIEW
85

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
ULTIME NEWS: div.fusion-layout-column > div.fusion-column-wrapper > div.fusion-title > h3.fusion-title-heading
VISITA LAPRESSE.IT div.fusion-column-wrapper > div.fusion-button-wrapper > a.fusion-button > span.fusion-button-text
VISITA OLYCOM.IT div.fusion-column-wrapper > div.fusion-button-wrapper > a.fusion-button > span.fusion-button-text
CREATE A CONNECTION WITH ARRESTING PHOTOGRAPHY div.fusion-layout-column > div.fusion-column-wrapper > div.fusion-title > h3.fusion-title-heading
ON AIR div.fusion-layout-column > div.fusion-column-wrapper > div.fusion-title > h3.fusion-title-heading
ON AIR div.fusion-layout-column > div.fusion-column-wrapper > div.fusion-title > h3.fusion-title-heading
NAVIGAZIONE div.fusion-columns > div.fusion-column > section#avada-vertical-menu-widget-10 > h4.widget-title
Reject all and Close div.cl-consent__inner > div.cl-consent-popup > div.cl-consent__close-wrap > button.cl-consent__close-btn
We care about your privacy div#cl-consent > div.cl-consent__inner > div.cl-consent-popup > h3.cl-consent__title
We and our partners store and/or access information on a device. Cookies, devic… div.cl-consent__inner > div.cl-consent-popup > div.cl-consent__descr > p.cl-consent-node-p
our partners div.cl-consent-popup > div.cl-consent__descr > p.cl-consent-node-p > a.cl-consent-local-link
With your consent, your data can be used for the following: Personalised advert… div.cl-consent__inner > div.cl-consent-popup > div.cl-consent__descr > p.cl-consent-node-p
Your personal data will be processed and information from your device (cookies,… div.cl-consent__inner > div.cl-consent-popup > div.cl-consent__descr > p.cl-consent-node-p
1747 partner(s) div.cl-consent-popup > div.cl-consent__descr > p.cl-consent-node-p > a.cl-consent-local-link
Privacy Policy div.cl-consent-popup > div.cl-consent__descr > p.cl-consent-node-p > a.cl-consent-node-a
Cookie Policy div.cl-consent-popup > div.cl-consent__descr > p.cl-consent-node-p > a.cl-consent-node-a

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
NAVIGAZIONE div.fusion-columns > div.fusion-column > section#avada-vertical-menu-widget-10 > h4.widget-title

These are opportunities to improve keyboard navigation in your application.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.fusion-builder-row > div.fusion-layout-column > div.fusion-column-wrapper > img.fusion-empty-dims-img-placeholder div.fusion-builder-row > div.fusion-layout-column > div.fusion-column-wrapper > img.fusion-empty-dims-img-placeholder
div.fusion-builder-row > div.fusion-layout-column > div.fusion-column-wrapper > img.fusion-empty-dims-img-placeholder div.fusion-builder-row > div.fusion-layout-column > div.fusion-column-wrapper > img.fusion-empty-dims-img-placeholder

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.fusion-header > div.fusion-row > div.fusion-logo > a.ap-logo div.fusion-header > div.fusion-row > div.fusion-logo > a.ap-logo

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

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
VISITA LAPRESSE.IT div.fusion-layout-column > div.fusion-column-wrapper > div.fusion-button-wrapper > a.fusion-button
VISITA OLYCOM.IT div.fusion-layout-column > div.fusion-column-wrapper > div.fusion-button-wrapper > a.fusion-button
○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>`
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Buttons have an accessible name
●Input buttons have discernible text.
●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 are distinguishable without relying on color.
●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.
●Skip links are focusable.
●Document has a main landmark.
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○Deprecated ARIA roles were not used
○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
○`[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
○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 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.
○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.
○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
Landmark Structure
12 landmarks
PASS
12 landmarks
Info::
<main> landmark present
Info::
7 <nav> landmark(s) found
Info::
All <nav> elements are properly labeled
Warning::
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
BANNER header NAV "Menu Secondario" MAIN CONTENTINFO footer

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
35 headings, 1 skip(s)
PASS
35 headings, 1 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 Da 30 anni, lasciamo parlare i fatti
  • H2 2.500 lanci al giorno e un flusso di news 7gg/7 – h24 no stop
  • H2 Agenzia di Stampa
  • H3 Ultime News:
  • H2 Agenzia di Stampa
  • H2 Fotografia
  • H3 Create a connection with arresting photography
  • H2 Premio Pulitzer Fotografia vincitrice per breaking news
  • H2 Premio Pulitzer Fotografia premiata 1965
  • H2 Premio Pulitzer Miglior fotografia di cronaca 2001
  • H2 Premio Pulitzer Fotografia vincitrice per breaking news
  • H2 In evidenza Foto
  • H2 Produzioni TV
  • H3 ON AIR
  • H2 Gianni Agnelli in arte l’Avvocato
  • H2 Sophia!
  • H2 The Royals – Amori a Corte
  • H2 Motor Trend Mag
  • H2 In evidenza Produzioni TV
  • H2 Video news
  • H3 ON AIR
  • H2 Spari contro Trump a un comizio in Pennsylvania, il momento in cui viene colpito
  • H2 Crollo a Scampia, i residenti: “Rabbia e tanto dolore”
  • H2 Parigi 2024: la torcia olimpica davanti al Moulin Rouge
  • H2 Valle d’Aosta, a Cervinia si scava nel fango dopo l’alluvione
  • H2 In evidenza Video News
  • H2 Radio News
  • H2 Ultime News
  • H2 Ufficio Stampa
  • H2 Ufficio Stampa
  • H2 Eventi
  • H2 Eventi
  • H4 NAVIGAZIONE skipped
  • H3 We care about your privacy
  • H3 Manage options

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

A+
Heading Text Quality
1 heading-text-quality issue(s) detected
PASS
1 heading-text-quality issue(s) detected
Info::
3 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: 3 all-caps heading(s)
A+
Form Input Types
6 form control(s) checked, no type mismatches
PASS
6 form control(s) checked, no type mismatches
Info::
No input-type mismatches detected
A+
Form Input Quality
6 form control(s) checked, no input-semantic issues
PASS
6 form control(s) checked, no input-semantic issues
Info::
All form input semantics look correct
A+
Mobile Keyboard & Autofill
No autofill-eligible form controls
PASS
No autofill-eligible form controls
Info::
No autofill-eligible form controls (no name/email/tel/address fields)
A+
Document Language
Lang attribute set to "it-IT"
PASS
Lang attribute set to "it-IT"
Info::
<html lang="it-IT"> is set and valid
Got: it-IT
A+
Tabindex Anti-Patterns
0 positive, 1 -1-on-focusable
PASS
0 positive, 1 -1-on-focusable
Info::
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.)
A
Iframe Accessibility
1/1 iframe(s) missing title; 0 placeholder(s)
PASS
1/1 iframe(s) missing title; 0 placeholder(s)
Warning::
<iframe> missing title attribute (src="")
WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.
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
Info::
All tap targets meet WCAG 2.5.5 (44x44px) sizing
A
404 Error Page
HTTP 404, custom page
PASS
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Navigation links present on 404 page
Info::
Homepage link present on 404 page
Info::
Search form present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title AP_RGB ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓
A+
PWA Depth
No PWA depth issues detected
PASS
No PWA depth issues detected
Info::
No PWA depth issues detected
A+
Mobile UX Depth
1 mobile-depth signal(s) detected
PASS
1 mobile-depth signal(s) detected
Info::
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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback