Pay-as-you-go pricing No subscriptions (for now)

Run reports when you need them.

Create an account and generate your first report for free — no card details required. After that, it’s a  simple £14.99 per report. Subscriptions are coming soon for teams and heavier usage.

Free first report (no card)
£14.99 / report

Pay only when you run a report. No recurring billing. No surprises.

Pay-as-you-go

Includes all core modules available in your account.

  • Free first report when you register —  no card required.
  • £14.99 per report after the free one —  pay only when you generate.
  • Secure checkout — processed by a trusted payment provider (e.g., Stripe). We don’t store card details.
  • Clear policies — privacy, refunds and complaints routes are visible and easy to find.

How the free report works: register, choose a module, run a report — you won’t be asked for payment details until you choose to generate your second report.

Subscriptions

Coming soon

We’re building subscriptions for teams and frequent usage (e.g., monthly report bundles, central billing, and team access).

Trust & transparency

UK support
  • Human support via email and contact form.

  • Security-first with HTTPS and best-practice handling of credentials.

  • Data privacy: we don’t sell personal data.

Questions before buying? Email  info@braynex.io  or call  +44 75 2397 9877

Full example report (On-Page Audit)

Example On-Page Audit report (illustrative only).

This is a full end-to-end example so visitors can see structure and depth. The exact sections, metrics, and wording can differ depending on your website and configuration.

!
This is a sample report, not a promise.

The layout below is representative. Your real report will vary based on site size, templates, technologies, crawl results, and available datasets at the time of analysis.

Braynex — On-Page Audit

https://example.co.uk/blog/how-to-start-running/

Fetched08 Feb 2026, 14:12 OverallGoodHTTPSEnabledConfidenceMedium

Key strengths

Secure baseline
Strength

HTTPS enabled with no mixed content detected across checked templates.

Mobile-ready layout
Strength

Viewport configured correctly and text is readable; tap targets meet minimum sizing on most pages.

Indexing signals
Strength

Pages are indexable; robots rules are consistent; internal links are descriptive and crawl-friendly.

Stable layout
Strength

Very low layout shift across the sample run (CLS close to zero).

Key weaknesses

Slow LCP on mobile
Weakness

Largest Contentful Paint is slower than ideal for blog templates due to hero image and third-party scripts.

Third-party weight
Weakness

Third-party scripts account for a large share of transfer and contribute to main-thread blocking.

Meta coverage gaps
Weakness

Some templates show missing or duplicated meta descriptions, reducing snippet quality.

Accessibility flags
Weakness

Contrast and ARIA landmark issues detected on navigation and footer components.

Lighthouse category scores

Scores shown here are sample-only and will vary by page, device, network and run conditions.

Performance
74 / 100
Accessibility
92 / 100
Best Practices
81 / 100
SEO
95 / 100

Data quality

A quick view of data reliability signals (sample).

Runtime errors:NoRecommendation:sufficient_for_decisionsChecked templates: 6Crawl pages: 50

Performance & Core Web Vitals

A sample “at-a-glance” panel of key performance metrics.

LCP
needs work
3,950 ms
Largest Contentful Paint (mobile)
TTI
slow
7,820 ms
Time to Interactive (mobile)
TBT
moderate
360 ms
Total Blocking Time
CLS
good
0.005
Cumulative Layout Shift
Requests
33
Total network requests
Total transfer
860 KiB
Total bytes transferred
Third-party bytes
735 KiB
Third-party share (sample)
Server TTFB
420 ms
Time to first byte

Mobile readiness

Example signals that influence mobile UX perception.

Viewport:width=device-width, initial-scale=1Text legibility:100% ≥ 12pxTouch targets:sufficientPWA:unavailable

Technical hygiene

Sample technical findings, grouped into common optimization buckets.

Unused JS
182 KiB
Potential reduction from trimming bundles
Unused CSS
64 KiB
Potential reduction from critical CSS
Offscreen image savings
2.3 KiB
Lazy-loading opportunities
Legacy JS
14 KiB
Modern bundle / differential serving
HTTP/2
Yes
Connection protocol
Redirects
0
Redirect chains detected
Cache TTL warnings
Yes
Some assets are short-cached
Third-party cookie
Detected
Example privacy signal

Accessibility signals

Example “flag” indicators (your real report may include different items).

Color contrast:flaggedARIA roles:flaggedMain landmark:missing on templateForm labels:partial coverage

Issues

A sample issues list showing severity, source, and evidence style.

SeveritySourceImpactEvidenceApplies to
moderateLighthouse: seo/meta-descriptionMissing meta description reduces snippet quality and potential CTR.Audit “meta-description” flagged on two templates; description absent or duplicated.https://example.co.uk/blog/how-to-start-running/
moderateLighthouse: performance/unminified-jsExtra JS bytes increase parse/execute time and main-thread blocking.Bundled scripts include unused modules; long tasks appear during hydration.https://example.co.uk/blog/
highAccessibility: contrastLow contrast can make text difficult to read for users and may impact compliance.Footer links and secondary buttons fall below contrast threshold in dark mode.https://example.co.uk/blog/how-to-start-running/
moderateBest practices: third-party cookiesPrivacy and trust concern for users; may require consent handling.A third-party cookie is set by embedded analytics/tag manager scripts.https://example.co.uk/blog/how-to-start-running/
lowImages: missing dimensionsUnsized images can increase layout shift risk and reduce perceived stability.Some inline images lack width/height attributes on category pages.https://example.co.uk/blog/category/training/

Opportunities

Example opportunities with rationale and estimated impact formatting.

Reduce unused JavaScript
Performance
Large unused JS increases parse/execute time and contributes to main-thread blocking on mobile devices.
Estimated savings Bytes: 180 KiB • Time: ~180 ms
Optimize LCP element
Core Web Vitals
Hero image can be prioritized and served in a modern format to improve LCP and perceived load speed.
Estimated savings LCP: ~350–650 ms (scenario-dependent)
Improve meta description coverage
SEO
Unique descriptions help create clearer snippets and reduce duplication across templated pages.
Estimated savings N/A (SEO quality signal)

Prioritized actions

Example action list to show how execution steps may be presented.

Add unique meta descriptions to key templates
Difficulty: low
ReasonMissing/duplicated meta descriptions detected on blog and category templates.
BenefitStronger snippets and clearer topical context; potential CTR uplift.
Defer / remove non-critical third-party scripts
Difficulty: medium
ReasonThird-party bundles contribute to long tasks and slower TTI.
BenefitReduced main-thread time and better mobile responsiveness.
Fix contrast + landmark issues
Difficulty: medium
ReasonContrast failures and missing main landmark flagged in accessibility checks.
BenefitBetter usability, fewer accessibility flags, stronger trust signals.
Set explicit dimensions for templated images
Difficulty: low
ReasonSome images lack width/height attributes.
BenefitReduced layout shift risk and improved perceived stability.
Ready to try it?

Run your first report free — no card required.

Create an account, generate one report, and see the output quality before you pay anything.