Report loading
www.pagelensai.com
Preparing the full page inventory and screenshots.
Report loading
Preparing the full page inventory and screenshots.
Excellent
Health Score
Score by category
The headline health score combines page-level quality and site-wide repeat patterns, then stays anchored to the weakest visible category so it never looks worse than every category beneath it.
Section 01
PageLens AI maintains a premium technical foundation, yet critical accessibility failures and SEO truncation on subpages undermine its search visibility and user experience.
The platform demonstrates exceptional execution in its core design and performance architecture. A sophisticated visual hierarchy, driven by modern typography and a consistent dark/light mode-ready palette, establishes immediate brand authority. From an engineering standpoint, the site excels with optimized font loading strategies to prevent layout shifts and a robust implementation of Schema.org markup that provides rich context to search engines. Furthermore, the developer-centric approach on the /mcp page—utilizing literal code snippets—effectively validates the product's utility for its primary technical audience.
Significant friction points exist within the current deployment, most notably a high-priority accessibility failure on the /mcp desktop view where element color contrast falls below WCAG 2 AA thresholds. This is compounded by SEO inefficiencies; both titles and meta descriptions on subpages exceed character limits, causing critical information to be truncated in search results. On mobile, the user experience suffers from text-heavy hero sections that impede rapid scanning, alongside form inputs that lack visible text labels, relying instead on invisible aria-labels which disorient users with cognitive impairments.
There is a significant opportunity to broaden market appeal by evolving the content strategy beyond purely technical specifications. While the current focus on protocols like OAuth 2.1 serves developers, integrating high-level business value propositions—such as time savings and audit efficiency—captures decision-makers. Additionally, completing the social metadata suite with Open Graph images transforms unoptimized URL shares into high-impact visual previews across professional platforms.
5 highest-impact findings, ranked.
Ensure the contrast between foreground and background colors meets WCAG 2 AA minimum contrast ratio thresholds. Fix any of the following: Element has insufficient color contrast of 4.35 (foreground color: #71717b, background color: #000000, font size: 8.3pt (11px), font weight: normal). Expected contrast ratio of 4.5:1
How to fix: Element matching `.overflow-hidden.dark\:bg-zinc-900.bg-white:nth-child(1) > .bg-zinc-950.dark\:bg-black > .border-zinc-800.justify-between.py-2 > .text-\[11px\].text-zinc-500` has contrast ratio 4.35; WCAG AA requires 4.5:1. Increase the contrast between foreground and background colours (the Tailwind hint below proposes the next darker step in the same family if the offending class is a recognised palette utility). Reference: https://dequeuniversity.com/rules/axe/4.11/color-contrast?application=playwright Tailwind hint: replace `bg-zinc-900` (#18181b) with `bg-zinc-950` (#09090b, 19.9:1 vs white) — the next darker step in the same `zinc` family that passes WCAG AA (4.5:1). Tailwind hint: `bg-zinc-950` (#09090b) — no darker step in the `zinc` family passes 4.5:1 against white; switch to a different colour family or increase font weight to qualify as "large text" (3:1 threshold). Tailwind hint: replace `border-zinc-800` (#27272a) with `border-zinc-900` (#18181b, 17.72:1 vs white) — the next darker step in the same `zinc` family that passes WCAG AA (4.5:1).
On /mcp
Google truncates titles around 60 characters in search results. Anything beyond that is invisible on the SERP.
How to fix: Shorten the title to ≤60 characters, front-loading the most important keywords.
On /mcp
Google truncates snippet text around 160 characters. The trailing copy is invisible on the SERP and may make the snippet read awkwardly.
How to fix: Trim the description to ≤160 chars; keep the strongest hook in the first sentence.
On /mcp
Open Graph tags drive how the page appears when shared on Slack, LinkedIn, Facebook, WhatsApp, iMessage and most other platforms. Without them, shares fall back to the URL or a stripped preview.
How to fix: Add to <head>: <meta property="og:title" content="…"> <meta property="og:description" content="…"> <meta property="og:image" content="https://…/social-card.png">
On /mcp
The current copy focuses heavily on technical protocols (OAuth 2.1, PKCE, RFCs). While appropriate for the target audience, adding a single sentence about the business impact (e.s., 'Save hours of manual auditing') could increase appeal to broader stakeholders.
How to fix: Add a brief subheadline under the H1 that emphasizes the end-user benefit: 'Automate your SEO and accessibility audits directly within your favorite AI coding environment.'
On /mcp
