Home FAQ New Contact About
Developer topics

Site speed and accessibility checks Lighthouse and more

Free tools with links, two step-by-step guides, Core Web Vitals targets, green Do cards and pink Do not cards, and fixes for common Lighthouse warnings. Test on mobile first and retest after every change.

Free speed and accessibility tools

14

Start with one speed tool and one accessibility tool. Run them on your live page, on mobile first.

PageSpeed Insights

Google's report for a URL, with real-user Core Web Vitals data when available and a Lighthouse test.

Free: Free

Visit PageSpeed Insights

Lighthouse

Built into Chrome DevTools. Audits performance, accessibility, best practices and SEO.

Free: Free, open source

Visit Lighthouse

WebPageTest

Detailed speed tests from different locations, devices and connections, with waterfall charts.

Free: Free tests, check limits

Visit WebPageTest

GTmetrix

Speed reports with history and a waterfall chart.

Free: Free account, limited tests

Visit GTmetrix

Google Search Console

Core Web Vitals report showing real-user results for groups of pages on your site.

Free: Free

Visit Search Console

sitespeed.io

Open-source tool to measure speed from the command line and track it over time.

Free: Free, open source

Visit sitespeed.io

WAVE

Shows accessibility errors and structure right on your page.

Free: Free web tool and extension

Visit WAVE

axe DevTools

Browser extension that scans a page for accessibility problems and explains each one.

Free: Free extension

Visit axe DevTools

Pa11y

Command-line accessibility checker you can run in your build.

Free: Free, open source

Visit Pa11y

WebAIM Contrast Checker

Check text and background colours against WCAG contrast ratios.

Free: Free

Visit Contrast Checker

NVDA

Free screen reader for Windows, for testing how your page sounds.

Free: Free, open source

Visit NVDA

Squoosh

Compress and convert images in the browser to cut page weight.

Free: Free, open source

Visit Squoosh

Guide: check your site speed

8 steps

Follow these steps after each change. Scores move a little between runs, so test three times and compare the trend.

1. Open PageSpeed Insights

Go to pagespeed.web.dev, paste your page address and press Analyze. Test the live site, not a local copy.

Free: Free

Open PageSpeed Insights

2. Read the mobile tab first

Most visitors use phones, and mobile tests are stricter. Check desktop after.

3. Know field data and lab data

Field data comes from real visitors and shows only for sites with enough traffic. Lab data is a test run from Lighthouse. A new site often has lab data only.

4. Check the three Core Web Vitals

Look at Largest Contentful Paint, Interaction to Next Paint and Cumulative Layout Shift. Aim for the Good range shown below.

5. Work through Opportunities and Diagnostics

Sort by estimated saving. Fix the largest items first: usually images, scripts and fonts.

6. Run Lighthouse in Chrome

Open your page in an Incognito window so extensions do not add noise. Press F12, open the Lighthouse tab, pick Mobile and the categories you want, then Analyze page load.

7. Test from a realistic location

In WebPageTest choose a test location near your visitors and a slower connection to see what real users on weaker networks see.

8. Retest and keep notes

After every change, run the test again. Write down the score and what you changed so you can undo changes that do not help.

Guide: check accessibility

8 steps

Automated tools find only part of the problems. Always finish with a keyboard test and a short screen reader check.

1. Run an automated scan

Open WAVE, paste your address, and fix every error first. Alerts need a human decision.

Free: Free

Open WAVE

2. Scan with Lighthouse or axe

Run the Accessibility category in Lighthouse and the axe DevTools extension. Compare results and fix what both report.

3. Test with the keyboard only

Put the mouse aside. Use Tab and Shift+Tab to move, Enter and Space to activate, and Esc to close things. You should always see where focus is, the order should make sense, and you should never get stuck.

4. Zoom to 200 percent

Zoom the browser to 200 percent and then narrow it to about 320 pixels wide. Content should reflow with no sideways scrolling and nothing cut off.

5. Check colour contrast

Use the WebAIM Contrast Checker. Normal text needs a ratio of at least 4.5 to 1, and large text and icons at least 3 to 1.

Open Contrast Checker

6. Listen with a screen reader

Try NVDA on Windows, VoiceOver on Mac and iPhone (Cmd+F5 on Mac) or TalkBack on Android. Check that headings, links, buttons and form fields are announced with clear names.

Get NVDA

7. Check the structure

Use WAVE's structure view to check heading order, landmarks, image alt text and form labels.

8. Fix, then test again

Re-run the tools and the keyboard test after changes. Ask someone who uses assistive technology to try the key flows if you can.

Core Web Vitals and score ranges

4

Google measures these three things for real visitors. Hit the Good range for at least 75 percent of visits.

Largest Contentful Paint (LCP)

How fast the biggest visible element loads. Good is 2.5 seconds or less. Poor is more than 4 seconds. Usually a hero image or heading.

Interaction to Next Paint (INP)

How quickly the page responds after a tap or click. Good is 200 milliseconds or less. Poor is more than 500 milliseconds. Heavy JavaScript hurts it.

Cumulative Layout Shift (CLS)

How much the layout jumps while loading. Good is 0.1 or less. Poor is more than 0.25. Images without sizes and late-loading ads cause it.

Lighthouse score colours

90 to 100 is green (good), 50 to 89 is orange (needs improvement) and 0 to 49 is red (poor). A score is a guide, not the goal. Real visitor experience matters more.

Do: speed

8

Habits that make pages load faster.

Compress and resize images

Save images at the size they display, in WebP or AVIF where possible, and compress them.

Set width and height on images

This reserves space and prevents layout shift while images load.

Lazy-load images below the fold

Add loading="lazy" to images that are not visible at first.

Prioritise the main image

Make the hero image load early, for example with fetchpriority="high", and keep it small.

Use a CDN and caching

Serve files from a CDN and set long cache times for files that rarely change.

Defer non-critical JavaScript

Use defer on scripts and load only the code a page needs.

Limit fonts

Use one or two font families, only the weights you need, and font-display: swap.

Test on a mid-range phone

Check on a real phone or with throttling, not only on your fast computer.

Do not: speed

7

Common mistakes that slow pages down.

Do not lazy-load the hero image

It delays your Largest Contentful Paint. Lazy-load only images below the first screen.

Do not stack third-party scripts

Every chat widget, tracker and font loader adds delay. Keep only the ones you need.

Do not upload full-size camera photos

A 5 MB photo shown at 400 pixels wide wastes bandwidth.

Do not autoplay large videos

Use a poster image and load the video on demand.

Do not ship huge JavaScript bundles

Remove unused libraries and split code so each page loads less.

Do not block rendering

Avoid large render-blocking CSS and scripts in the head.

Do not trust one test

A single run on fast Wi-Fi can mislead. Test several times and on mobile.

Do: accessibility

8

Habits that make your site usable for everyone.

Use semantic HTML

Use header, nav, main, button and a for what they are. This gives keyboard and screen reader support for free.

Write useful alt text

Describe what the image shows or does. Use empty alt="" for purely decorative images.

Label every form field

Connect each input to a visible label. Show clear error messages next to the field.

Keep a visible focus style

Make sure the keyboard focus outline is easy to see on every button and link.

Keep headings in order

Use one h1, then h2 and h3 in order, so the page outline makes sense.

Set the page language

Add lang="en" (or your language) to the html tag.

Make touch targets big enough

Aim for about 44 by 44 pixels for buttons and links on phones.

Respect reduced motion

Turn animations down when the visitor has chosen prefers-reduced-motion.

Do not: accessibility

9

Common mistakes that shut people out.

Do not use colour alone

Do not mark errors or links with colour only. Add text, an icon or an underline.

Do not use a div as a button

A div with a click handler is not reachable by keyboard or announced as a button. Use button.

Do not remove the focus outline

Removing it without a clear replacement leaves keyboard users lost.

Do not use placeholders as labels

Placeholder text disappears while typing and often has low contrast.

Do not use images of text

They do not scale, cannot be read by screen readers and break in dark mode.

Do not write vague link text

"Click here" tells screen reader users nothing. Say where the link goes.

Do not block zoom

Never use user-scalable=no or a maximum scale in the viewport tag.

Do not autoplay audio or flashing content

Sound that starts by itself is disruptive, and flashing content can be harmful.

Do not rely only on automated tools

They catch only part of the problems. Test with a keyboard and a screen reader too.

Common Lighthouse warnings and how to fix them

12

Search for the exact warning name in your report, then use the fix.

Properly size images

Resize images to the size they display, and use srcset so phones download smaller files.

Serve images in next-gen formats

Convert JPEG and PNG to WebP or AVIF with a tool like Squoosh.

Eliminate render-blocking resources

Add defer to scripts, inline only the small critical CSS and load the rest later.

Reduce unused JavaScript

Remove libraries you do not use and load heavy code only on the pages that need it.

Image elements do not have explicit width and height

Add width and height attributes, or set an aspect ratio in CSS, to stop layout shifts.

Largest Contentful Paint element

Find the element named in the report, make it smaller, load it early and avoid lazy-loading it.

Links do not have a discernible name

Give every link readable text or an aria-label. This includes icon-only links.

Buttons do not have an accessible name

Add visible text or an aria-label to every button, including icon buttons.

Background and foreground colours do not have a sufficient contrast ratio

Darken the text or lighten the background until it reaches 4.5 to 1 for normal text.

Form elements do not have associated labels

Wrap the input in a label or connect them with for and id.

Document does not have a meta description

Add a meta name="description" tag with a short summary of the page.

Image elements do not have alt attributes

Add alt text to every image. Use an empty alt for decoration.