Account

What new tool do you want?

Web & SEO

Landing Page Grader

Grade any landing page out of 100 — server speed, compression, HTTPS, title and meta description, headings, mobile viewport, content, alt text, calls to action and social tags — with specific fixes.

How to use

  1. 1Enter a landing page URL.
  2. 2See your score and every check grouped by area.
  3. 3Fix the red items, starting with speed, mobile and call to action.

Frequently asked questions

What's a good score?

85+ is strong. Most pages lose points for a missing meta description, social tags or image alt text — quick wins.

Does it measure Core Web Vitals?

No — it checks what's in the HTML and server response. Use Google PageSpeed Insights for field performance data.

Is the page loaded like a real visitor?

It fetches the HTML from our server without running JavaScript, like a search engine's first pass.

Why most pages lose points on the same handful of checks

The grader's own FAQ points out that most pages lose points for a missing meta description, missing social tags or missing image alt text — not because those are obscure requirements, but because they're the checks most commonly skipped when a page is built quickly or copied from a template without customizing its head section. That pattern is exactly why fixing the 'red' items first, rather than chasing a perfect 100, is the efficient path: a handful of straightforward fixes typically closes most of the gap on a freshly checked page.

Worked example: Landing Page Grader

A landing page scoring 72/100 might show green on HTTPS, headings and content length, but red on a missing meta description, no Open Graph image (meaning shared links on social media show no preview image), and three images without alt text — each a specific, independently fixable item rather than one vague 'needs improvement' score. Fixing the meta description and adding an og:image tag alone could realistically push the score from 72 into the mid-80s, since those are weighted as meaningful individual checks, not minor cosmetic points.

Why this grades the HTML response, not a rendered page

The grader fetches a page's raw HTML without executing JavaScript, deliberately mimicking a search engine's first crawl pass rather than a real visitor's fully-rendered experience — which is also explicitly why it doesn't measure Core Web Vitals or actual load performance the way Google PageSpeed Insights does. A page that relies heavily on client-side JavaScript to inject its title, meta tags or main content after the initial HTML loads could score poorly here even if it looks complete and polished to a human visitor in a browser, since the grader is checking what's present before any JavaScript runs.

Why checks are grouped, not just listed in one long pile

Every check carries a group label — speed, trust, SEO basics, mobile, content and conversion are typical buckets — and the results render as separate sections rather than one undifferentiated checklist. That grouping is what makes the 'fix red items, starting with speed, mobile and call to action' advice in the how-to actually actionable: a page owner can scan straight to the mobile section and see every mobile-specific failure together, instead of hunting through a flat list of forty items to figure out which ones are related.

What the three score bands actually mean in the UI

The score circle itself changes color at fixed thresholds — 85 and above renders green with the label 'Strong page,' 65 to 84 renders amber as 'Good, with room to improve,' and anything below 65 renders red as 'Needs work.' A page sitting at 64 and a page sitting at 20 both display the same red 'Needs work' badge, which is why the number itself (not just the color band) is worth tracking between re-checks — fixing the meta description and alt text might move a page from 64 to 78, crossing into the amber band, even though the headline label changes only when you cross a boundary.

Related tools

More: Web & SEO