Free tool

Landing Page Analyzer

Check any landing page's speed, SEO, mobile experience and accessibility. Paste a URL. Get scored in seconds.

What is a landing page analyzer?

A landing page analyzer tests a live page and tells you what's holding it back. This free tool runs your page through Google Lighthouse, the engine behind PageSpeed Insights and Chrome DevTools, and gives you one score out of 100 for speed, SEO, best practices and accessibility, plus a short list of fixes in order of urgency.

Paste any public URL, choose mobile or desktop, and you get the overall score, a score for each category, Google's key speed measurements and 17 pass/fail checks, usually in under a minute.

How your landing page score is calculated

Lighthouse scores each of four categories from 0 to 100. Your overall score is a weighted average of the four, so speed and SEO count most.

4 categories, weighted100% total
  1. Speed30%
  2. SEO30%
  3. Best Practices25%
  4. Accessibility15%
30% of score

Speed

How fast the page loads and becomes usable, measured by Google Lighthouse on a simulated phone or desktop. Slow pages lose visitors before they read a word.

30% of score

SEO

Whether search engines can find, read and show your page: a title and meta description, crawlability, descriptive links, image alt text and a canonical URL.

25% of score

Best Practices

Trust and technical health: HTTPS, no JavaScript errors in the browser console, and modern, safe code.

15% of score

Accessibility

Whether everyone can read and use the page: text contrast, a clear heading order, labelled form fields, named buttons and a declared page language.

Landing page analyzer grades by overall score
GradeOverall scoreWhat it means
Grade A90–100Excellent. This page follows best practices.
Grade B80–89Good, but there's room to improve.
Grade C70–79Needs work. Several issues to fix.
Grade D50–69Poor. Major issues are hurting this page.
Grade F0–49Failing. This page needs significant fixes.

Grade A

Overall score90–100
What it meansExcellent. This page follows best practices.

Grade B

Overall score80–89
What it meansGood, but there's room to improve.

Grade C

Overall score70–79
What it meansNeeds work. Several issues to fix.

Grade D

Overall score50–69
What it meansPoor. Major issues are hurting this page.

Grade F

Overall score0–49
What it meansFailing. This page needs significant fixes.

What each check means, and how to fix it

Alongside the scores, your report runs 17 pass/fail checks in 4 groups. Here is every one, with the advice the report gives when it fails.

Landing page analyzer checks and how to fix them
CheckIf it fails
SEO
Has title tagAdd a descriptive <title> tag. This is what shows in browser tabs and Google search results.
Has meta descriptionAdd a meta description (120-160 characters). This is the preview text Google shows below your page title.
Page is crawlableYour page is blocked from search engines. Check your robots.txt and meta robots tags.
Links have descriptive textReplace generic link text like "click here" with descriptive text that tells users where the link goes.
Has canonical URLAdd a canonical URL to tell search engines which version of this page is the original.
Images have alt textAdd alt text to images. This helps SEO and makes your page accessible to screen readers.
Mobile
Has viewport meta tagAdd a viewport meta tag so your page scales correctly on mobile devices.
Font sizes are readableIncrease font sizes so text is readable without zooming on mobile devices. Use at least 16px for body text.
Tap targets are sized properlyMake buttons and links at least 48x48 pixels so they are easy to tap on touchscreens.
Trust
Uses HTTPSSwitch to HTTPS. Visitors see a "Not Secure" warning on HTTP pages, which kills trust and conversions.
No console errorsFix JavaScript errors on your page. Console errors can break functionality and hurt user experience.
No vulnerable librariesUpdate JavaScript libraries with known security vulnerabilities.
Accessibility
Heading hierarchy is correctFix your heading hierarchy. Use one H1, then H2s for sections, H3s for subsections. Don't skip levels.
Text has sufficient contrastIncrease contrast between text and background colors. Low contrast makes text hard to read.
Page language is setAdd a lang attribute to your HTML tag (e.g., lang="en") so browsers and screen readers know the page language.
Buttons have accessible namesAdd accessible names to buttons so screen readers can announce what each button does.
Form inputs have labelsAdd labels to form inputs so users know what information to enter in each field.

SEO

Has title tag

If it failsAdd a descriptive <title> tag. This is what shows in browser tabs and Google search results.

Has meta description

If it failsAdd a meta description (120-160 characters). This is the preview text Google shows below your page title.

Page is crawlable

If it failsYour page is blocked from search engines. Check your robots.txt and meta robots tags.

Links have descriptive text

If it failsReplace generic link text like "click here" with descriptive text that tells users where the link goes.

Has canonical URL

If it failsAdd a canonical URL to tell search engines which version of this page is the original.

Images have alt text

If it failsAdd alt text to images. This helps SEO and makes your page accessible to screen readers.

Mobile

Has viewport meta tag

If it failsAdd a viewport meta tag so your page scales correctly on mobile devices.

Font sizes are readable

If it failsIncrease font sizes so text is readable without zooming on mobile devices. Use at least 16px for body text.

Tap targets are sized properly

If it failsMake buttons and links at least 48x48 pixels so they are easy to tap on touchscreens.

Trust

Uses HTTPS

If it failsSwitch to HTTPS. Visitors see a "Not Secure" warning on HTTP pages, which kills trust and conversions.

No console errors

If it failsFix JavaScript errors on your page. Console errors can break functionality and hurt user experience.

No vulnerable libraries

If it failsUpdate JavaScript libraries with known security vulnerabilities.

Accessibility

Heading hierarchy is correct

If it failsFix your heading hierarchy. Use one H1, then H2s for sections, H3s for subsections. Don't skip levels.

Text has sufficient contrast

If it failsIncrease contrast between text and background colors. Low contrast makes text hard to read.

Page language is set

If it failsAdd a lang attribute to your HTML tag (e.g., lang="en") so browsers and screen readers know the page language.

Buttons have accessible names

If it failsAdd accessible names to buttons so screen readers can announce what each button does.

Form inputs have labels

If it failsAdd labels to form inputs so users know what information to enter in each field.

If Google's Lighthouse doesn't report a check for your page, the report leaves it out rather than guessing.

Page speed measurements explained

The report shows Google's key speed measurements, each marked good, needs work or poor using these thresholds.

Page speed measurements and the thresholds the analyzer uses
MeasurementWhat it measuresGoodNeeds workPoor
Largest Contentful Paint (LCP)When the biggest thing on screen (usually the hero image or headline) has loaded.Up to 2.5 s2.5 s to 4 sOver 4 s
Cumulative Layout Shift (CLS)How much the layout jumps around while the page loads. Lower is better.Up to 0.10.1 to 0.25Over 0.25
Total Blocking Time (TBT)How long scripts stop the page from responding to taps and clicks while it loads.Up to 200 ms200 ms to 600 msOver 600 ms
First Contentful Paint (FCP)When the first text or image appears.Up to 1.8 s1.8 s to 3 sOver 3 s
Speed IndexHow quickly the visible part of the page fills in.Up to 3.4 s3.4 s to 5.8 sOver 5.8 s
Time to InteractiveWhen the page is fully ready to respond to the visitor.Up to 3.8 s3.8 s to 7.3 sOver 7.3 s

Largest Contentful Paint (LCP)

What it measuresWhen the biggest thing on screen (usually the hero image or headline) has loaded.
GoodUp to 2.5 s
Needs work2.5 s to 4 s
PoorOver 4 s

Cumulative Layout Shift (CLS)

What it measuresHow much the layout jumps around while the page loads. Lower is better.
GoodUp to 0.1
Needs work0.1 to 0.25
PoorOver 0.25

Total Blocking Time (TBT)

What it measuresHow long scripts stop the page from responding to taps and clicks while it loads.
GoodUp to 200 ms
Needs work200 ms to 600 ms
PoorOver 600 ms

First Contentful Paint (FCP)

What it measuresWhen the first text or image appears.
GoodUp to 1.8 s
Needs work1.8 s to 3 s
PoorOver 3 s

Speed Index

What it measuresHow quickly the visible part of the page fills in.
GoodUp to 3.4 s
Needs work3.4 s to 5.8 s
PoorOver 5.8 s

Time to Interactive

What it measuresWhen the page is fully ready to respond to the visitor.
GoodUp to 3.8 s
Needs work3.8 s to 7.3 s
PoorOver 7.3 s

What to fix first

Your report lists up to six fixes, most urgent first: any speed measurement in the red, then failing checks. These 4 failures are always marked critical, because each one can stop a page from being found, trusted or used on a phone:

  1. Missing title tag. Search results and browser tabs show nothing useful.
  2. Blocked from search engines. Google can't index the page, so it can't be found.
  3. No mobile viewport tag. The page won't fit a phone screen.
  4. Not on HTTPS. Browsers warn visitors the page is not secure.

Then work through slow images and heavy scripts, which drive most speed problems. For the full playbook, read our landing page best practices. Sharpen the words with the free headline analyzer and CTA generator, or start from a landing page templatethat's built to load fast and work on phones.

Frequently Asked Questions

A score of 90 or above (grade A) means your page follows best practices across speed, SEO, mobile, and accessibility. 80 to 89 (grade B) is good with room to improve, and 70 to 79 (grade C) needs work. Below 70 means there are significant issues hurting your page's ability to convert visitors.

Yes, completely free. No signup required. Enter your URL and get your results instantly. We use Google's Lighthouse engine (the same technology behind Chrome DevTools) to analyze your page.

Your overall score is a weighted average of four category scores: Performance (30%), SEO (30%), Best Practices (25%), and Accessibility (15%). Each category is scored 0-100 by Google Lighthouse, then combined into your overall grade.

Mobile and desktop use different simulated devices and network speeds. Mobile tests simulate a mid-range phone on a slower connection, so performance scores are typically lower. Since most visitors browse on phones, we default to mobile analysis.

Start with the top recommendations in your report. The biggest wins usually come from improving page speed (compress images, reduce JavaScript), adding missing SEO elements (meta description, alt text), and fixing mobile usability issues (tap target sizes, font sizes). A landing page builder like Leadpages handles most of these automatically.

PageSpeed Insights leads with the Performance score alone. This analyzer combines four Lighthouse categories (speed, SEO, best practices and accessibility) into one weighted score, so the two numbers measure different things. Lighthouse results also vary a little from run to run, so expect small differences between tests.

They are three of Google's key speed measurements. Largest Contentful Paint (LCP) is when the main content has loaded; aim for 2.5 seconds or less. Cumulative Layout Shift (CLS) measures how much the layout jumps while loading; aim for 0.1 or less. Total Blocking Time (TBT) is how long scripts block taps and clicks; aim for 200 milliseconds or less.

Yes, any page that is publicly available on the web. Google's servers load the page to test it, so pages behind a login, on a staging server or on a private network can't be analyzed.

Next step

Ready for a page that scores higher?

Describe your campaign and Leadpages builds a fast, mobile-ready landing page, already set up to convert.