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 InsightsFree 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.
Start with one speed tool and one accessibility tool. Run them on your live page, on mobile first.
Google's report for a URL, with real-user Core Web Vitals data when available and a Lighthouse test.
Free: Free
Visit PageSpeed InsightsBuilt into Chrome DevTools. Audits performance, accessibility, best practices and SEO.
Free: Free, open source
Visit LighthouseGoogle's guided checks with fix advice for your site.
Free: Free
Visit web.dev MeasureDetailed speed tests from different locations, devices and connections, with waterfall charts.
Free: Free tests, check limits
Visit WebPageTestSpeed reports with history and a waterfall chart.
Free: Free account, limited tests
Visit GTmetrixCore Web Vitals report showing real-user results for groups of pages on your site.
Free: Free
Visit Search ConsoleOpen-source tool to measure speed from the command line and track it over time.
Free: Free, open source
Visit sitespeed.ioShows accessibility errors and structure right on your page.
Free: Free web tool and extension
Visit WAVEBrowser extension that scans a page for accessibility problems and explains each one.
Free: Free extension
Visit axe DevToolsMicrosoft's free tool with automated checks and guided manual tests.
Free: Free, open source
Visit Accessibility InsightsCommand-line accessibility checker you can run in your build.
Free: Free, open source
Visit Pa11yCheck text and background colours against WCAG contrast ratios.
Free: Free
Visit Contrast CheckerFree screen reader for Windows, for testing how your page sounds.
Free: Free, open source
Visit NVDACompress and convert images in the browser to cut page weight.
Free: Free, open source
Visit SquooshFollow these steps after each change. Scores move a little between runs, so test three times and compare the trend.
Go to pagespeed.web.dev, paste your page address and press Analyze. Test the live site, not a local copy.
Free: Free
Open PageSpeed InsightsMost visitors use phones, and mobile tests are stricter. Check desktop after.
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.
Look at Largest Contentful Paint, Interaction to Next Paint and Cumulative Layout Shift. Aim for the Good range shown below.
Sort by estimated saving. Fix the largest items first: usually images, scripts and fonts.
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.
In WebPageTest choose a test location near your visitors and a slower connection to see what real users on weaker networks see.
After every change, run the test again. Write down the score and what you changed so you can undo changes that do not help.
Automated tools find only part of the problems. Always finish with a keyboard test and a short screen reader check.
Open WAVE, paste your address, and fix every error first. Alerts need a human decision.
Free: Free
Open WAVERun the Accessibility category in Lighthouse and the axe DevTools extension. Compare results and fix what both report.
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.
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.
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 CheckerTry 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 NVDAUse WAVE's structure view to check heading order, landmarks, image alt text and form labels.
Re-run the tools and the keyboard test after changes. Ask someone who uses assistive technology to try the key flows if you can.
Google measures these three things for real visitors. Hit the Good range for at least 75 percent of visits.
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.
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.
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.
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.
Habits that make pages load faster.
Save images at the size they display, in WebP or AVIF where possible, and compress them.
This reserves space and prevents layout shift while images load.
Add loading="lazy" to images that are not visible at first.
Make the hero image load early, for example with fetchpriority="high", and keep it small.
Serve files from a CDN and set long cache times for files that rarely change.
Use defer on scripts and load only the code a page needs.
Use one or two font families, only the weights you need, and font-display: swap.
Check on a real phone or with throttling, not only on your fast computer.
Common mistakes that slow pages down.
It delays your Largest Contentful Paint. Lazy-load only images below the first screen.
Every chat widget, tracker and font loader adds delay. Keep only the ones you need.
A 5 MB photo shown at 400 pixels wide wastes bandwidth.
Use a poster image and load the video on demand.
Remove unused libraries and split code so each page loads less.
Avoid large render-blocking CSS and scripts in the head.
A single run on fast Wi-Fi can mislead. Test several times and on mobile.
Habits that make your site usable for everyone.
Use header, nav, main, button and a for what they are. This gives keyboard and screen reader support for free.
Describe what the image shows or does. Use empty alt="" for purely decorative images.
Connect each input to a visible label. Show clear error messages next to the field.
Make sure the keyboard focus outline is easy to see on every button and link.
Use one h1, then h2 and h3 in order, so the page outline makes sense.
Add lang="en" (or your language) to the html tag.
Aim for about 44 by 44 pixels for buttons and links on phones.
Turn animations down when the visitor has chosen prefers-reduced-motion.
Common mistakes that shut people out.
Do not mark errors or links with colour only. Add text, an icon or an underline.
A div with a click handler is not reachable by keyboard or announced as a button. Use button.
Removing it without a clear replacement leaves keyboard users lost.
Placeholder text disappears while typing and often has low contrast.
They do not scale, cannot be read by screen readers and break in dark mode.
"Click here" tells screen reader users nothing. Say where the link goes.
Never use user-scalable=no or a maximum scale in the viewport tag.
Sound that starts by itself is disruptive, and flashing content can be harmful.
They catch only part of the problems. Test with a keyboard and a screen reader too.
Search for the exact warning name in your report, then use the fix.
Resize images to the size they display, and use srcset so phones download smaller files.
Convert JPEG and PNG to WebP or AVIF with a tool like Squoosh.
Add defer to scripts, inline only the small critical CSS and load the rest later.
Remove libraries you do not use and load heavy code only on the pages that need it.
Add width and height attributes, or set an aspect ratio in CSS, to stop layout shifts.
Find the element named in the report, make it smaller, load it early and avoid lazy-loading it.
Give every link readable text or an aria-label. This includes icon-only links.
Add visible text or an aria-label to every button, including icon buttons.
Darken the text or lighten the background until it reaches 4.5 to 1 for normal text.
Wrap the input in a label or connect them with for and id.
Add a meta name="description" tag with a short summary of the page.
Add alt text to every image. Use an empty alt for decoration.