Technical audit

Technical site audit: find what breaks before your visitors do

Speed, Core Web Vitals, crawlability, accessibility, security and console errors, measured on desktop and mobile and written in plain language. Every issue says how it affects you and what to ask your developer for.
Sign up free

Free signup, no card · 2 free CRO audits · The sample opens without signing up

LCP

3.8 s

Needs work

Target < 2.5 s

CLS

0.04

Good

Target < 0.1

INP

180 ms

Good

Target < 200 ms

Technical pass

mobile
  • LCP3.8 sHero image loads late
  • CLS0.04Layout holds still
  • INP180 msResponds quickly
  • Console3JavaScript errors
  • Requests8412 from third parties

01  What it checks

Six areas, one report

What blocks the machine before it gets a chance to block the person.

01

Speed and Core Web Vitals

LCP, CLS and INP from PageSpeed Insights and, where there is traffic, from real Chrome users.

02

Crawlability

robots.txt, sitemap, the HTML before JavaScript runs, structured data, and whether AI crawlers can read the site.

03

Accessibility

Contrast, labels, focus order, tap target sizes: what shuts visitors, and sales, out.

04

Security

HTTPS, security headers and mixed content that make the browser warn your visitors.

05

Errors and network

Console errors, failed requests and heavy third-party scripts.

06

Cookie banner

What loads before consent, and how much of the phone screen the banner covers.

02  In order of importance

Not every issue is equal

Issues are grouped in four tiers, so you know what to hand your developer this week.

Fix now2
  • Hero image loads in 3.8 s
  • Sitemap lists 404 pages
Fix soon3
  • 3 JavaScript errors
  • Buttons without labels
  • No Content-Security-Policy
Plan2
  • 12 third-party scripts
  • No Product schema

Sample report

See what it finds before the page even loads

On the KYMA demo store the report shows the Meta pixel sending data before consent and after "Deny", a 1 MB photo making mobile LCP 3.6 s and a script that breaks on phones, with what to ask your developer.
Sign up free

03  One issue, as written

What it is, how it affects you, what to do

What it is

The main image appears 3.8 seconds after the page opens on a phone. Google's target is under 2.5.

How it affects you

Visitors see a blank where the page should convince them, and Google counts it in rankings.

What to ask for

"Preload the hero image, serve it as WebP at screen width, and remove lazy-loading from it."

04  How it works

Measured like a visitor, written for a person

  1. 01

    Paste the URL

    No code access and no script.
  2. 02

    We measure on desktop and mobile

    Before and after cookie consent, with Google's data where it exists.
  3. 03

    You get the plan

    Issues in four tiers, each with a note for your developer.

Ready to check your own site?

Sign up free

05  Questions

Common questions

No. Every issue has a plain explanation, how it affects your visitors or your rankings, and a note you can send to your developer as it is.

See what costs you before the page even loads

Pick a plan and run it from your workspace. Or see a sample report first.