Skip to content

Free website audit: speed, SEO and accessibility.

Enter a URL to get Google Lighthouse scores, Core Web Vitals for mobile and desktop, and the fixes that matter most, explained in plain English.

Any public page. We test it on mobile and desktop.

  • Free, no sign-up
  • Google PageSpeed Insights data
  • Results in under a minute

Sample report

example.com
  • 64
    Performance
  • 92
    Accessibility
  • 83
    Best practices
  • 100
    SEO

LCP

3.1 s

Needs work

INP

180 ms

Good

CLS

0.02

Good

Top fixes, in plain English

  1. HighDefer render-blocking CSS and scripts~1.2 s faster first paint
  2. MediumServe images as WebP or AVIF~240 KiB lighter

Illustrative example. Enter your URL to get your own scores, Core Web Vitals and fixes.

What we check

Four scores, and what each one means.

Every score runs from 0 to 100. Lighthouse colours them in three bands, and so do we.

  • 0-49 Poor
  • 50-89 Needs work
  • 90-100 Good

  • Performance

    How fast the page loads and becomes usable on a throttled phone or a desktop, weighted from LCP, Total Blocking Time, CLS, First Contentful Paint and Speed Index.

    Usually dragged down by

    Heavy images, render-blocking CSS and scripts, too much JavaScript, slow servers and third-party tags.

    Performance testing

  • Accessibility

    Automated checks (axe-core) for problems that block people using screen readers, keyboards or zoom: contrast, labels, alt text, names and structure.

    Usually dragged down by

    Low-contrast text, icon-only links and buttons, unlabeled form fields and skipped heading levels.

    Accessibility testing

  • Best practices

    Modern-web hygiene: HTTPS everywhere, no console errors, no deprecated browser APIs, correctly sized images and safe permission prompts.

    Usually dragged down by

    JavaScript errors, third-party cookies, mixed content and outdated libraries.

    Website maintenance

  • SEO

    Technical basics that let search engines crawl, understand and show the page: title, meta description, crawlable links, indexability, status code and alt text.

    Usually dragged down by

    Missing meta descriptions, noindex left on by mistake, JavaScript-only links and vague link text.

    SEO services

Core Web Vitals, explained.

Google's three user-experience metrics. A page passes when at least 75% of real visits are in the good range for all three, measured separately on mobile and desktop over the last 28 days.

  1. lcp

    Largest Contentful Paint

    Loading: when the biggest image or text block appears.

    Good
    ≤ 2.5 s
    Needs work
    2.5–4 s
    Poor
    > 4 s

  2. inp

    Interaction to Next Paint

    Responsiveness: how fast the page reacts to taps, clicks and keys.

    Good
    ≤ 200 ms
    Needs work
    200–500 ms
    Poor
    > 500 ms

  3. cls

    Cumulative Layout Shift

    Visual stability: how much content jumps while loading.

    Good
    ≤ 0.1
    Needs work
    0.1–0.25
    Poor
    > 0.25

Field data vs lab data

Field data comes from real Chrome users (the Chrome UX Report) and is what Google's page experience signals use. Lab data is one simulated load; it can't measure INP, so it reports Total Blocking Time instead, and it is best for finding causes.

fcp

First Contentful Paint

When anything first appears on screen.

Good ≤ 1.8 s · Poor > 3 s

ttfb

Time to First Byte

How quickly the server starts responding.

Good ≤ 0.8 s · Poor > 1.8 s

tbt

Total Blocking Time (lab)

Lab stand-in for INP: time the main thread is blocked during load.

Good ≤ 200 ms · Poor > 600 ms

From report to a faster, fairer site.

A score is a symptom. This is the order we work in when a client hands us an audit.

1. Start with what real users feel

If the report shows field data, fix whichever Core Web Vital fails there first; that is what visitors experience and what Google's page experience signals look at. Lab scores are for diagnosis. Our guide to improving LCP, INP and CLS walks through each one.

2. Make the HTML arrive fast

Everything waits for the first byte. Slow hosting, redirect chains and uncached server rendering show up as a poor TTFB and drag every other metric with them. Caching at a CDN and server-rendered or static pages, as in Next.js, usually fix this at the root.

3. Get the main image or headline on screen

Most poor LCP scores come from a large hero image that is discovered late, lazy-loaded or uncompressed, or from web fonts hiding text. Reference it in the HTML, prioritise it, serve WebP or AVIF at the right size and let text render immediately.

4. Ship less JavaScript

Unused code, legacy polyfills and third-party tags block the main thread, which shows up as Total Blocking Time in the lab and slow INP in the field. Remove what you don't use, split bundles per page and load chat widgets and trackers after the page is usable.

5. Stop the page jumping

Layout shift is usually images and embeds without dimensions, late-loading banners and fonts that swap in at a different size. Reserving space fixes most of it.

6. Treat accessibility as more than a score

Automated tools catch only part of the real barriers, so a 100 is a floor, not a certificate. Keyboard, screen reader and zoom testing against WCAG finds the rest; our WCAG 2.2 testing checklist covers what to try by hand, and accessibility testing is a service we run.

7. Then the SEO basics

Unique titles and descriptions, crawlable links and indexable pages are the floor for technical SEO. Rankings still come from useful content and links; see our SEO services. If the platform itself is the bottleneck, a rebuild through website development may cost less than patching.

Website audit questions, answered

Something else on your mind? Ask a consultant and get a reply within one business day.

Is this website audit really free?

Yes. The scores, Core Web Vitals and the top fixes are free with no sign-up. If you want every fix listed and a printable version, leave your name and email and an engineer will follow up with notes. There is no obligation to hire us.

Where do the scores come from?

From Google PageSpeed Insights, which runs Lighthouse (the same engine as the Lighthouse panel in Chrome DevTools) on Google's servers and adds real-user data from the Chrome UX Report. We translate the results into plain English and rank the fixes. Our server only talks to Google's API; it never loads your site itself.

Why do my scores change every time I run the audit?

Lab tests are a single simulated load, so network conditions, server response time, ads and A/B tests can move the performance score by several points between runs. Accessibility, SEO and best-practice scores are more stable. Judge trends and the fixes list rather than one number, and rely on field data where it exists.

Why is my mobile score so much lower than desktop?

The mobile test emulates a mid-range phone with a slower CPU on a throttled mobile network, while desktop uses a fast connection and no CPU slowdown. JavaScript-heavy pages suffer most on mobile. Since most traffic is mobile and Google indexes the mobile version of pages, the mobile result is usually the one to prioritise.

What is the difference between field data and lab data?

Field data is how real Chrome users experienced your page over the last 28 days, reported at the 75th percentile. Lab data is one controlled test. Field data is what counts for Google's Core Web Vitals assessment; lab data helps you find the cause. Newer or low-traffic sites often have no field data yet.

What are good Core Web Vitals scores?

Google's thresholds are Largest Contentful Paint of 2.5 seconds or less, Interaction to Next Paint of 200 milliseconds or less and Cumulative Layout Shift of 0.1 or less, each measured at the 75th percentile of page visits. Poor starts above 4 seconds, 500 milliseconds and 0.25. Our Core Web Vitals guide explains how to fix each one.

Will a performance score of 100 improve my Google rankings?

Not by itself. Core Web Vitals are part of Google's page experience signals, but relevance and content quality matter far more. A faster site tends to convert better and keep visitors longer, which is the bigger reason to fix it. Chasing the last few lab points rarely pays off once real-user vitals pass.

If my accessibility score is 100, is my site WCAG compliant?

No. Automated checks can only detect part of the WCAG success criteria, such as contrast and missing labels. Keyboard navigation, focus order, screen reader announcements and meaningful alt text need manual testing. Laws such as the European Accessibility Act and the ADA are judged against real use, so a clean score is a start, not proof. See our accessibility testing service.

Which pages should I audit?

Start with the pages that earn money or traffic: the home page, your top landing pages from search or ads, a product or service template and the checkout or contact page. Templates matter most, because one fix to a template improves every page built on it.

Do you store my website or the results?

We don't keep audit results. The URL is sent to Google's PageSpeed Insights API to run the test and the results go straight back to your browser. We only receive the URL and score summary if you ask us to email the full report, and then only to reply to you, as described in our privacy policy.

Want an engineer to look deeper?

Automated audits find symptoms. Send us your site and a consultant replies within one business day with what to fix first and a rough estimate.

Book a free consultation+91-7302622997