Every Conversion Optimization Audit check

Visitors make stay-or-leave decisions within the first few seconds of landing on a page, and a primary CTA that requires scrolling to find loses that window entirely. When the hero section presents a headline and subheadline but no button, interested visitors have no immediate path to convert and bounce before they ever see the offer, directly suppressing top-of-funnel signup rates.

Why this severity: Critical because a missing above-fold CTA directly kills conversion at the single highest-intent moment in the visitor journey.

Mobile devices generate the majority of web traffic, and a conversion path that breaks on small viewports silently discards most potential signups. A CTA hidden by `hidden sm:flex`, a form container with a fixed 600px width that triggers horizontal scroll, or a sticky navigation bar that covers the submit button all render the funnel unusable for phone visitors — a failure that is invisible on the desktop preview the developer tests against.

Why this severity: Critical because a broken mobile path eliminates the majority of traffic from converting, regardless of desktop polish.

A CTA button that fails WCAG 2.2 SC 1.4.11 (Non-text Contrast, 3:1 minimum against adjacent background) and SC 1.4.3 (Text Contrast, 4.5:1 minimum for normal text) is invisible to users with low vision — and to many typical users on bright screens or in direct sunlight. Beyond accessibility compliance, contrast failure directly suppresses conversion: if the primary action doesn't visually demand attention, visitors scan past it. A low-contrast CTA is the single cheapest conversion kill in a marketing page.

Why this severity: High because a CTA that fails to register visually eliminates the conversion path for a measurable fraction of visitors, including users with visual impairments covered by WCAG 2.2.

Generic button copy like "Submit", "Click Here", or "Go" forces visitors to infer what happens next, and that split-second of ambiguity suppresses click-through. Specific, outcome-oriented copy ("Start Free Trial", "Book a 15-Min Demo", "Get the Free Guide") completes the sentence "I want to ___" in the visitor's mind and removes the cognitive friction that silently tanks conversion rates on otherwise well-designed pages.

Why this severity: Medium because weak CTA copy suppresses click-through but the conversion surface still functions mechanically.

Two equally-weighted filled buttons side-by-side force the visitor to compare them and decide which is the "right" path, and that micro-hesitation is enough to drive many visitors away entirely. Visual hierarchy — a solid primary button paired with an outline or ghost secondary — communicates the intended default action without words and eliminates choice paralysis at the hero, where attention is most fragile.

Why this severity: Low because the page still converts but secondary friction from choice paralysis blunts primary CTA performance.

Visitors who scroll past the hero are actively evaluating, and a long landing page that only offers a CTA in the hero forces them to scroll back up when they are finally ready to convert — a micro-friction that silently drops conversion rates. Repeated CTAs after testimonials or pricing sections meet intent at its peak, and a sticky header CTA keeps the conversion path permanently one click away during the scroll journey.

Why this severity: Low because conversion still works but the page misses peak-intent moments further down the scroll.

Social proof parked in a dedicated testimonials section far from the CTA arrives too late — the visitor has already decided whether to trust the offer by the time they scroll past the hero. A compact proof signal ("Trusted by 12,000+ teams · ★★★★★ 4.9 on G2") rendered directly under the primary button reduces the silent "is this real?" objection at the exact moment of decision and measurably lifts signup conversion.

Why this severity: High because proximity-free social proof fails to defuse purchase anxiety at the moment of conversion.

Visitors who have never heard of your product arrive with a silent "is this real and safe?" objection, and absent trust signals leave that question unanswered at the exact moment they are asked to hand over an email or credit card. Customer logos, SSL/Stripe payment badges, SOC 2 indicators, and press mentions each answer a different piece of that objection without requiring the visitor to ask, and their absence directly depresses conversion on pricing and signup surfaces.

Why this severity: High because missing trust signals leave core purchase objections unanswered at the pricing and signup surfaces.

Hiding pricing behind a "Contact Sales" gate or omitting billing cycles creates real friction — visitors who cannot find a price point often leave rather than email a stranger to ask. Even a simple "From $29/month" anchor lets pricing-curious visitors self-qualify, reduces bounce from the pricing page, and improves the quality of inbound demo requests by filtering out visitors whose budgets do not match.

Why this severity: High because opaque pricing causes qualified visitors to bounce rather than initiate a sales conversation.

A testimonial attributed to "— Mike" or "Happy Customer" reads as either lazy or fabricated, and visitors discount it accordingly. Full attribution — name, role, and company — converts a testimonial from ambient copy into verifiable social proof a visitor can actually go check, and the specificity itself signals that the customer was real enough to stand behind the quote publicly.

Why this severity: Medium because weak attribution reduces testimonial credibility without breaking the conversion path mechanically.

Testimonials say "it worked for me," but case studies say "here is exactly how it worked, with numbers" — and for B2B buyers comparing vendors, a single quantified success story often moves the deal more than ten one-line quotes. A marketing site with customer logos but no linked stories leaves prospects guessing at outcomes, forcing them to book a demo just to ask the question a published case study would have already answered.

Why this severity: Low because case studies accelerate B2B conversion but their absence does not break the funnel itself.

Visitors hesitate to hand over an email address when they cannot see what happens next — they imagine spam, credit-card surprises, or a sales call. A single line of micro-copy next to the submit button ("No credit card required. Unsubscribe anytime.") answers that hesitation in place and measurably reduces form abandonment, whereas a privacy policy link buried in the footer does no work at the moment of decision.

Why this severity: Low because the form still functions but privacy-related hesitation quietly depresses completion rates.

Every additional required field on a signup form removes a measurable percentage of completions — a four-field form loses meaningfully more signups than an email-plus-password form, and a six-field form asking for phone number and team size before first login discards the majority of interested users. Worse, a "free trial" form that silently requires a credit card without prominent disclosure reads as a bait-and-switch and destroys trust at the exact moment you are trying to build it.

Why this severity: Critical because excess form fields and hidden credit-card gates directly reject the majority of interested signups.

A bare form with four input fields and a submit button reads as commitment when the visitor is still evaluating. Friction-reduction signals — OAuth buttons ("Continue with Google"), a "No credit card required" line, or a "Takes less than 2 minutes" note — each remove a specific concern without asking the visitor to do more work, and their presence compounds into meaningful lifts on signup completion rates, especially for first-time visitors with no prior brand trust.

Why this severity: High because a form with zero friction-reducers loses signups that a single OAuth button or reassurance line would have captured.

A top-of-form banner saying "There was an error" forces visitors to re-scan every field to find what went wrong, and many simply abandon instead. Inline errors rendered directly under the offending field tell the visitor exactly what to fix and where — a fundamental usability affordance that is also a WCAG 2.2 SC 3.3.1 (Error Identification) requirement for accessible form validation, meaning the absence of inline errors creates both a conversion drag and a compliance gap.

Why this severity: Medium because non-inline error feedback increases abandonment and fails WCAG 2.2 SC 3.3.1 but does not block submission outright.

Submit-only validation forces users to complete an entire form before learning they made a mistake on field one. Each round-trip error adds friction, and friction causes abandonment — especially on signup forms where a single bad email format can discard everything the user typed. Inline validation (blur or change) catches errors at the field level the moment the user leaves it, cutting abandonment on multi-field forms. This is purely a UX and conversion concern; client-side feedback is bypassable and never substitutes for server-side validation.

Why this severity: Medium because submit-only validation measurably increases form abandonment and degrades user experience, but does not expose a security vulnerability on its own.

Missing or incorrect `autocomplete` attributes force users to type information their browser or password manager already knows. Password managers rely on both the `name` attribute and `autocomplete` to distinguish `new-password` from `current-password` — without this signal, they may autofill the wrong credential, prefill nothing, or prompt users to save an incorrect entry. WCAG 2.2 SC 1.3.5 (Identify Input Purpose) requires programmatic purpose identification for common personal data fields. Autofill friction is disproportionately punishing on mobile, where typing is slower and error-prone.

Why this severity: Low because the failure degrades UX and violates WCAG 2.2 SC 1.3.5 but does not create a direct security or data-loss risk.

A multi-step onboarding wizard with no progress indicator leaves users guessing whether they are on step two of four or step two of twelve, and that ambiguity drives abandonment that a single line of copy would prevent. Progress indicators set expectations, deliver a small sense of accomplishment as each step completes, and measurably reduce drop-off in conversion funnels — especially on mobile, where the remaining-steps question feels heavier under small viewports.

Why this severity: Low because multi-step abandonment rises without progress context but the flow still completes for committed users.

Without conversion event tracking, you cannot distinguish a high-performing landing page variant from a broken one, measure funnel drop-off, or justify any product decision with data. If an analytics library is installed but `.capture()` or `.track()` calls are absent from form submit handlers, you have the instrumentation overhead with none of the insight. ISO 25010:2011 reliability requires that quality-relevant behaviors be observable — a conversion funnel that is invisible to your analytics stack cannot be measured, improved, or debugged. Teams flying blind here routinely ship changes that hurt conversion and have no way to detect it.

Why this severity: Critical because the absence of conversion event tracking makes it impossible to measure product-market fit, optimize the funnel, or detect regressions in conversion rate after deploys.

Every additional 100ms of Largest Contentful Paint degrades conversion rate — Google's own data shows a 1-second LCP delay can reduce conversions by up to 7%. The most common source of above-fold slowness in Next.js marketing pages is a hero image loaded with default lazy behavior (which defers it) and synchronous third-party scripts blocking the render path. Render-blocking analytics, chat, and A/B testing scripts compound the problem because they delay the browser's ability to paint anything the user can interact with. ISO 25010:2011 performance-efficiency directly covers time-behavior under load.

Why this severity: High because above-fold load performance has a direct, measurable impact on conversion rate and is routinely the largest single contributor to poor Core Web Vitals scores on marketing pages.

Placeholder `href="#"` values, empty `onClick={() => {}}` handlers, and form submissions pointing at API routes that were never created are among the most common defects in AI-built projects — the surface looks finished but the conversion path is mechanically broken. Every dead CTA silently swallows interested visitors, and because the failure happens after the click, analytics often do not flag it until manual testing or a customer complaint surfaces the gap.

Why this severity: Medium because placeholder links and missing API routes silently abort conversions without any visible error to the visitor.

Conversion improvements compound over time only when they can be measured, and a codebase with hardcoded CTA copy, button colors, and form layouts has no way to isolate what actually moves the needle. Feature flags and A/B testing infrastructure let you ship variant hero copy, alternate pricing layouts, or different signup flows to subsets of traffic and read the results — without that scaffolding, every change is a guess and positive outcomes cannot be attributed to any specific decision.

Why this severity: Low because absent experimentation infrastructure blocks iterative conversion improvements without breaking the current funnel.

The moment a visitor moves their cursor toward the browser tab bar or the address bar is the last measurable window before they leave, and no exit-intent or abandonment-recovery mechanism means that moment passes silently with zero recovery attempt. A lightweight `mouseleave` listener coupled with a discount offer, extended-trial prompt, or content download converts a meaningful slice of would-be bounces into captured emails or delayed conversions at essentially zero engineering cost.

Why this severity: Low because exit-intent recovery captures incremental conversions but the baseline funnel functions without it.

A visitor who lands on a broken URL — a typo, a stale share, an expired campaign link — is a high-intent lost signal, and the framework-default 404 page shows a bare error with no path back into the site. A custom 404 with a link to the homepage, search, or the most common destinations recovers a meaningful share of these visitors and keeps them inside the funnel rather than punishing them with a dead-end for a mistake that was often not theirs.

Why this severity: Low because 404 recovery reclaims misrouted visitors but the main conversion path is unaffected.