AuditMyLaunch
Sign inStart an audit

Illustrative report · not a customer audit

Example SaaS Website Audit Report

Explore a fictional, evidence-shaped report that shows how launch verdict, scope, sources, and prioritized findings fit together.

Example target
Fictional SaaS launch
Scope
18/25 pages · 4/5 customer journeys
Repository
Not requested
Human review
Not included

Launch decision

Critical blockers determine the verdict

The numerical readiness score supports prioritization. It cannot override a Critical launch blocker.

74/100
Supporting context

Readiness score

The score helps prioritize work but never changes the blocked verdict while Critical findings remain.

Fix before launch

Highest-impact example findings

Critical first
  1. Primary pricing CTA fails its contrast target/pricing · primary action · desktop and mobile
    Critical
  2. Signup completion breaks after email verification on mobileSignup journey · 390px viewport
    Critical
  3. Signup completion is not measuredSignup completion state
    Important
  4. Homepage value proposition is ambiguous for first-time visitors/ · hero
    Important

Illustrative coverage

Scope and all eight audit areas stay visible

Coverage labels what was and was not evaluated. It never implies certification or untested success.

18/25Pages in example scope
4/5Customer journeys in example scope
4Responsive profiles illustrated
8Audit areas represented
  • User journeysExample coverage shown
  • UX & conversionExample coverage shown
  • AccessibilityExample coverage shown
  • PerformanceExample coverage shown
  • Analytics & errorsExample coverage shown
  • SEO & discoverabilityExample coverage shown
  • Security basicsExample coverage shown
  • Responsive behaviorExample coverage shown

Prioritized findings

Website Audit Findings Ranked by Launch Impact

16 illustrative findings: 2 critical, 6 important, and 8 minor. Detection method and confidence remain visible for every finding.

Showing all 16 findings
2 Critical6 Important8 Minor
01Primary pricing CTA fails its contrast targetCritical

Observed evidence

Illustrative measured text/background contrast is 3.2:1 against a 4.5:1 target for this text size.

User and business impact

People with low vision may not identify the primary purchase action, blocking conversion and increasing accessibility risk.

Recommended change

Use a darker violet pairing and re-run the contrast check in every interactive state.

Reproducible steps

  1. Open the illustrative pricing page.
  2. Locate the primary Launch-plan action.
  3. Measure its text and background colors in default, hover, and focus states.
Back to launch verdict
Location
/pricing · primary action · desktop and mobile
Audit area
Accessibility
Viewport
1440px desktop and 390px mobile
Estimated effort
Low
Observed
Evidence source
Automated website checks
Confidence
High
02Signup completion breaks after email verification on mobileCritical

Observed evidence

The illustrative callback returns, then the mobile journey remains in a loading state instead of reaching completion.

User and business impact

New customers can verify their email but cannot complete signup on mobile, directly blocking acquisition on that journey.

Recommended change

Handle the session refresh explicitly, add a recoverable error, and repeat the complete mobile journey.

Reproducible steps

  1. Start account creation at the 390px responsive profile.
  2. Submit valid fictional test-account details and follow verification.
  3. Observe the post-verification loading state and captured console error.
Back to launch verdict
Location
Signup journey · 390px viewport
Audit area
User journeys
Viewport
390px mobile
Estimated effort
Medium
Observed
Evidence source
Automated browser journey
Confidence
High
03Signup completion is not measuredImportant

Observed evidence

No illustrative conversion event is observed after the expected completion state.

User and business impact

Launch teams cannot measure the primary conversion reliably or distinguish successful signup from journey drop-off.

Recommended change

Emit one documented completion event only after the account is confirmed.

Reproducible steps

  1. Open the browser event monitor.
  2. Complete the fictional signup journey.
  3. Confirm that no completion event appears after verification.
Location
Signup completion state
Audit area
Analytics & errors
Viewport
390px mobile and 1440px desktop
Estimated effort
Low
Observed
Evidence source
Automated website checks
Confidence
High
04Homepage value proposition is ambiguous for first-time visitorsImportant

Observed evidence

The illustrative hero does not identify its product category or intended audience until below the fold.

User and business impact

First-time visitors may not understand the product quickly enough to trust the primary action, reducing conversion clarity.

Recommended change

State the product, target team, and primary outcome in the initial hierarchy.

Reproducible steps

  1. Open the fictional homepage in a fresh browser context.
  2. Read only the initial viewport without interacting.
  3. Record where product category, audience, and outcome first become clear.
Location
/ · hero
Audit area
UX & conversion
Viewport
390px mobile and 1440px desktop
Estimated effort
Medium
Observed
Evidence source
AI-assisted review
Confidence
Medium-high
05One password-reset entry point returns a broken linkImportant

Observed evidence

The illustrative footer recovery link returns a 404 while the form link succeeds.

User and business impact

Locked-out customers can reach a dead end, increasing account abandonment and avoidable support demand.

Recommended change

Route both recovery entry points to the same working reset start page.

Reproducible steps

  1. Open the fictional sign-in page.
  2. Follow each visible password-recovery entry point.
  3. Compare the response status and final destination.
Location
/login · recovery link
Audit area
User journeys
Viewport
390px mobile, 768px tablet, and 1440px desktop
Estimated effort
Low
Observed
Evidence source
Automated browser journey
Confidence
High
06Consent rejection still records a marketing page viewImportant

Observed evidence

An illustrative marketing request is captured after optional tracking is rejected.

User and business impact

Recording optional analytics after rejection undermines user consent expectations and the reliability of analytics governance.

Recommended change

Gate optional analytics initialization on the stored consent decision.

Reproducible steps

  1. Open a fresh fictional marketing-page session.
  2. Reject optional tracking in the consent control.
  3. Inspect network requests made after the decision.
Location
Marketing pages · analytics
Audit area
Analytics & errors
Viewport
390px mobile, 768px tablet, and 1440px desktop
Estimated effort
Medium
Observed
Evidence source
Automated website checks
Confidence
High
07A slow contact submission has no pending feedbackImportant

Observed evidence

The illustrative submit action remains enabled while a delayed request is pending.

User and business impact

People may submit repeatedly or abandon the contact journey because they cannot tell whether the request is still processing.

Recommended change

Disable repeat submission and announce a clear pending state.

Reproducible steps

  1. Throttle the fictional contact request.
  2. Submit valid form values once.
  3. Observe the action and live status while the request is pending.
Location
/contact · submit action
Audit area
User journeys
Viewport
390px mobile, 768px tablet, and 1440px desktop
Estimated effort
Low
Observed
Evidence source
Automated browser journey
Confidence
High
08Mobile navigation does not return focus after dismissalImportant

Observed evidence

After illustrative Escape-key dismissal, focus moves to the document body.

User and business impact

Keyboard users lose their navigation position after dismissal, making the next intended action harder to reach reliably.

Recommended change

Close on Escape and restore focus to the control that opened the menu.

Reproducible steps

  1. Open the fictional navigation at the 390px profile.
  2. Move focus into the menu and press Escape.
  3. Inspect the active element after the menu closes.
Location
Global navigation · mobile
Audit area
Accessibility
Viewport
390px mobile
Estimated effort
Low
Observed
Evidence source
Automated browser journey
Confidence
High
09One secondary page skips a heading levelMinor

Observed evidence

The illustrative heading outline moves from level two to level four.

User and business impact

Screen-reader users receive a less predictable content hierarchy, increasing the effort required to understand the page.

Recommended change

Use a level-three heading for the nested feature group.

Reproducible steps

  1. Open the fictional features page.
  2. Capture the document heading outline.
  3. Compare the nested heading with its nearest parent section.
Location
/features · content hierarchy
Audit area
Accessibility
Viewport
390px mobile, 768px tablet, and 1440px desktop
Estimated effort
Low
Observed
Evidence source
Automated website checks
Confidence
High
10Footer link labels repeat without destination contextMinor

Observed evidence

Three illustrative links use the label “Learn more” for different destinations.

User and business impact

Ambiguous repeated labels make destinations harder to predict, increasing navigation mistakes for all users.

Recommended change

Name the destination or subject in each footer link.

Reproducible steps

  1. Navigate to the fictional page footer.
  2. List links and their accessible names.
  3. Compare repeated labels with their destinations.
Location
Global footer
Audit area
UX & conversion
Viewport
390px mobile and 1440px desktop
Estimated effort
Low
Observed
Evidence source
AI-assisted review
Confidence
Medium
11Equivalent trial actions use inconsistent labelsMinor

Observed evidence

Illustrative entry points use three labels for the same trial destination.

User and business impact

Inconsistent labels make equivalent signup actions appear different, adding hesitation at conversion points.

Recommended change

Use one primary label unless an action has a genuinely different result.

Reproducible steps

  1. List primary trial actions across the fictional pages.
  2. Compare each label and resolved destination.
  3. Mark labels that differ while destinations match.
Location
Homepage, pricing, and navigation
Audit area
UX & conversion
Viewport
390px mobile, 768px tablet, and 1440px desktop
Estimated effort
Low
Observed
Evidence source
AI-assisted review
Confidence
Medium
12Form help text is visually detached at tablet widthMinor

Observed evidence

Illustrative help text appears closer to the next field than its own input.

User and business impact

Tablet users may associate guidance with the wrong field, increasing input errors and form completion effort.

Recommended change

Keep help and error copy inside the associated field group.

Reproducible steps

  1. Open the fictional contact form at 768px.
  2. Compare spacing above and below each help message.
  3. Verify which input each message appears to describe.
Location
/contact · 768px viewport
Audit area
Responsive behavior
Viewport
768px tablet
Estimated effort
Low
Observed
Evidence source
AI-assisted review
Confidence
Medium
13Two content images omit intrinsic dimensionsMinor

Observed evidence

The illustrative markup omits width and height for two visible card images.

User and business impact

Content can shift while images load, disrupting reading position and reducing perceived page stability.

Recommended change

Declare intrinsic dimensions and retain responsive sizing.

Reproducible steps

  1. Open the fictional resources page.
  2. Inspect visible article-card image markup.
  3. Record images without intrinsic width and height.
Location
/resources · article cards
Audit area
Performance
Viewport
390px mobile, 768px tablet, and 1440px desktop
Estimated effort
Low
Observed
Evidence source
Automated website checks
Confidence
High
14Newsletter error copy does not explain recoveryMinor

Observed evidence

The illustrative error says only “Something went wrong” after a timeout.

User and business impact

People cannot tell whether submission succeeded or retrying is safe, which can cause abandonment or duplicate attempts.

Recommended change

Explain that nothing was submitted and offer a retry.

Reproducible steps

  1. Throttle the fictional newsletter request until it times out.
  2. Submit a valid test email.
  3. Review the resulting error and available recovery action.
Location
Footer newsletter form
Audit area
UX & conversion
Viewport
390px mobile, 768px tablet, and 1440px desktop
Estimated effort
Low
Observed
Evidence source
AI-assisted review
Confidence
Medium
15One campaign link uses a mixed-case canonical pathMinor

Observed evidence

An illustrative campaign link first requests /Pricing before redirecting.

User and business impact

The extra redirect weakens canonical consistency and adds avoidable work for users, crawlers, and campaign measurement.

Recommended change

Generate the lowercase canonical destination directly.

Reproducible steps

  1. Open the fictional campaign entry point.
  2. Capture its initial requested path.
  3. Compare it with the final canonical destination.
Location
Campaign navigation
Audit area
SEO & discoverability
Viewport
390px mobile, 768px tablet, and 1440px desktop
Estimated effort
Low
Observed
Evidence source
Automated website checks
Confidence
High
16One tertiary action uses a weak focus indicatorMinor

Observed evidence

The illustrative focus outline differs from its background by less than the target.

User and business impact

Keyboard users may lose track of the active control, preventing reliable interaction with the tertiary action.

Recommended change

Apply the shared high-contrast focus token.

Reproducible steps

  1. Use the keyboard to reach the fictional tertiary action.
  2. Capture its focused state.
  3. Compare the indicator against adjacent colors.
Location
/resources · card action
Audit area
Accessibility
Viewport
1440px desktop keyboard
Estimated effort
Low
Observed
Evidence source
Automated website checks
Confidence
High

Passed checks

Website Audit Checks That Passed

These fictional checks illustrate evidence that needs no immediate action. They are not results from a customer website.

HTTPS and certificate validation

No mixed-content requests illustrated.

Primary navigation integrity

Primary destinations resolve in the example.

Authenticated dashboard access

The fictional test account reaches its dashboard.

robots.txt and sitemap

Both reference the expected illustrative host.

Core page metadata

High-priority example pages expose titles and descriptions.

Responsive media

Sampled images remain inside their responsive containers.

Methodology

Evidence sources remain separate

AI interpretation is not a deterministic measurement. Pure AI-assisted findings do not become Critical blockers.

01

Automated website checks

Reproducible rules and browser journeys capture technical, interaction, and responsive evidence.

02

AI-assisted review

Labelled interpretation can assess UX and messaging evidence without being presented as measurement.

03

Human expert review

Not included in this illustration and operationally separate from the automated audit.

Audit boundaries

Website Audit Exclusions

  • No repository access or source-code audit.
  • No native mobile-app audit.
  • No intrusive penetration or exploit testing.
  • No load, stress, or production-capacity certification.
  • No legal or regulatory compliance certification.
  • No human expert review was included.

Your deployed website

Start by mapping a real audit scope

Review candidate pages and customer journeys before any paid audit can begin.

Map my website freeCompare USD plans