Semrush.com SEO Score & Performance Report

← Back to Home

https://semrush.com

Desktop

Mobile

Score Analysis

LIVE

71OF 100

Needs Work

SEO

Perf

Page Title

Checking your browser - reCAPTCHA

Google Search Preview|How your page appears in search results

SERP Score

Needs Work

semrush.com

https://semrush.com

Checking your browser - reCAPTCHA

No meta description found

Snippet Quality

Title Length33 chars

030–60 optimal90

Description Length0 chars

070–160 optimal240

Power Word

CTA

URL Readable

HTTPS

No Truncation

Recommendations2 found

infoTitle lacks CTR-boosting power words

Consider adding words like "free", "guide", "best" to improve click-through rate

criticalMissing meta description

Add <meta name="description" content="..."> with 150-160 chars

Performance Report|Google PageSpeed Insights

Lighthouse v13.0.1Mar 3, 2026, 12:15 PM

Status200OK

Load Time0.24sFAST

HTML Size21 KBOK

CompressionNoneOFF

HTTPSSecureSECURE

Render-Block10 scriptsFOUND

Needs Improvement

LCPGOOD

1.9 s

Largest Contentful Paint

FCPNEEDS WORK

1.9 s

First Contentful Paint

TBTPOOR

870 ms

Total Blocking Time

CLSGOOD

Cumulative Layout Shift

SIPOOR

6.9 s

Speed Index

TTFBGOOD

Root document took 10 ms

Time to First Byte

FIDNEEDS WORK

230 ms

First Input Delay

Page Load FilmstripVisual timeline of how your page renders

0.4s

0.8s

1.2s

1.6s

2.0s

2.3s

2.7s

3.1s

Issues Found8 found

criticalTotal Blocking Time: 870 ms (poor)high

How to fixBreak up long tasks, defer non-critical JavaScript, use web workers. Target < 200ms

What this meansTBT measures total time the main thread was blocked. It's a lab proxy for INP.

SEO ImpactHigh TBT means the page feels unresponsive. This directly impacts INP, a Core Web Vital.

warningSpeed Index: 6.9 s (poor)medium

How to fixOptimize critical rendering path, reduce main-thread work. Target < 3.4s

What this meansSpeed Index measures how quickly content is visually displayed during page load.

SEO ImpactA high Speed Index means the page appears to load slowly.

infoReduce unused JavaScript - Est savings of 549 KiB (potential savings: 549 KB)

How to fixReduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.

infoAvoid large layout shifts

How to fixThese are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due …

infoReduce JavaScript execution time - 2.0 s

How to fixConsider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time.

infoMinimize main-thread work - 2.4 s

How to fixConsider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread work

warningNo gzip/brotli compression

How to fixEnable gzip or brotli compression

warning10 render-blocking scripts in <head>

How to fixAdd async or defer to scripts

OpportunitiesPotential savings to improve load time

Reduce unused JavaScriptEst savings of 549 KiB

Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.

549 KB transferable

DiagnosticsAdditional performance insights

Avoid large layout shifts

These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due …

Reduce JavaScript execution time

Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time.

2.0 s

Minimize main-thread work

Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread work

2.4 s

Avoids enormous network payloads

Minify JavaScript

Optimize viewport for mobile

Metrics

Tasks

LCP breakdown

Diagnostics

Initial server response time was short

Improve image delivery

Network Requests

Optimize DOM size

Duplicated JavaScript

Script Treemap Data

Avoid long main-thread tasks

3rd parties

Legacy JavaScript

User Timing marks and measures

Network Round Trip Times

Forced reflow

Avoid multiple page redirects

Render blocking requests

Minify CSS

Resources Summary

Reduce unused CSS

Screenshot Thumbnails

Layout shift culprits

Image elements have explicit `width` and `height`

Final Screenshot

Cumulative Layout Shift

Document request latency

Heading Structure|Content hierarchy and heading tags

55 / 100

H1

ideal: 1

H2

ideal: 2+

H3

ideal: optional

H4

ideal: optional

Recommendations2

criticalMissing H1 tag

Add exactly one <h1> tag as the main heading

warningNo H2 tags found

Use H2 tags to structure your content sections

Structured Data|Schema markup, Open Graph and Twitter Cards

35 / 100

JSON-LD Schema

Not found

Open Graph

Not found

Twitter Cards

Not found

Microdata

Not found

Recommendations3

criticalNo JSON-LD structured data found

Add JSON-LD schema markup (e.g., WebPage, Organization, Article)

criticalMissing Open Graph tags: og:title, og:description, og:image, og:url, og:type

Add OG meta tags for social sharing

warningNo Twitter Card meta tags

Add twitter:card, twitter:title, twitter:description meta tags

Image Optimization|Alt text, lazy loading and dimensions

80 / 100

Total Images

Missing Alt Text

Missing Dimensions

Lazy Loaded

0 of 0 images

Recommendations1

infoNo images found

Consider adding relevant images

Link Analysis|Internal, external and nofollow links

80 / 100

Total Links

Internal

0% of all links

External

100% of all links

Nofollow

Recommendations1

warningOnly 0 internal links found

Add more internal links to improve crawlability

Indexability|Robots, canonical and sitemap

85 / 100

Canonical URL

Set

https://www.google.com/recaptcha/challengepage

Noindex

Allowed

Robots.txt

Found

Sitemap

Found

https://semrush.com/sitemap.xml

Crawl Directives

Meta RobotsNot set

X-Robots-TagNot set

GooglebotNot set

NofollowNo — links followed

Canonicalhttps://www.google.com/recaptcha/challengepage

Page URLhttps://semrush.com

Recommendations2

warningCanonical points to a different domain

Verify this is intentional.

infoNo Sitemap reference in robots.txt

Add Sitemap: https://semrush.com/sitemap.xml to robots.txt

Content Structure|Content quality and semantic HTML

80 / 100

Word Count

373

Paragraphs

All good length

Lists

Words per Heading

373

Ideal: 100-300

Semantic HTML Elements

<main>

<nav>

Recommendations2

warningPoor content chunking (373 words/heading)

Add more headings to break content into digestible chunks (aim for 150-200 words per section)

warningFew semantic HTML5 elements used

Use <main>, <article>, <nav>, <header>, <footer>, <section>

AI Readability|How easily AI models can process your content

90 / 100

Reading Level

Fairly Easy

Moderately complex

Total Words

373

Sentences

Avg Sentence Length

8 words

Vocabulary Richness

40%

149 unique words

Recommendations1

infoFirst paragraph is too short for AI summarization

Make the first paragraph a comprehensive summary (30-50 words)

AI Citation Potential|How likely AI will quote your content

50 / 100

Named Entities

0% density

FAQ Patterns

No FAQ Schema

Citations

Lists & Tables

0 items, 0 tables

Recommendations6

warningLow entity density

Include more specific names, brands, places. AI uses entities for knowledge graph matching.

infoNo entities repeated 3+ times

Reinforce key entities by mentioning them multiple times

warningLow quoteability - few clear, citable statements

Add bold key statements, blockquotes, or clear definitions that AI can extract

warningNo FAQ-style content detected

Add question-and-answer sections with heading questions (H2/H3 with "?")

Content Freshness|Date signals and cache headers

75 / 100

Date Signals

None

No date signals found on page

Cache Control

Set

no-cache, no-store, max-age=0, must-revalidate

ETag

Not set

Date Signals

Last-Modified HeaderNot found

Published DateNot found

Modified DateNot found

Recommendations2

warningNo datePublished or dateModified in structured data

Add datePublished and dateModified to your JSON-LD schema.

infoNo date/time signals found anywhere on page

Add <time datetime="..."> elements or schema dates to help AI assess content freshness

Security Headers|HTTP security headers analysis

92 / 100

Content-Security-Policy

Prevents XSS and injection attacks

require-trusted-types-for 'script';report-uri /recaptcha/challengepage/_/RecaptchaChallengePageUi/cspreport script-src 'report-sample' 'nonce-XUsm-HBLnJTHij9cQ7mvXw' 'unsafe-inline';object-src 'none';base-uri www.google.com;report-uri /recaptcha/challengepage/_/RecaptchaChallengePageUi/cspreport;worker-src 'self'

SET

Strict-Transport-Security

Forces HTTPS connections

max-age=31536000

SET

X-Frame-Options

Prevents clickjacking attacks

SAMEORIGIN

SET

X-Content-Type-Options

Prevents MIME-type sniffing

nosniff

SET

Referrer-Policy

Controls referrer information

MISSING

Permissions-Policy

Controls browser features

ch-ua-arch=*, ch-ua-bitness=*, ch-ua-full-version=*, ch-ua-full-version-list=*, ch-ua-model=*, ch-ua-wow64=*, ch-ua-form-factors=*, ch-ua-platform=*, ch-ua-platform-version=*

SET

Recommendations2

infoHSTS should include subdomains

Add includeSubDomains to HSTS header

infoMissing Referrer-Policy header

Add Referrer-Policy header (e.g., strict-origin-when-cross-origin)

Trust Signals|Essential trust-building pages

75 / 100

Contact Page

MISSING

A contact page builds trust with visitors and search engines

About Page

MISSING

An about page establishes credibility and expertise

MISSING

Required for compliance and builds user trust

MISSING

Protects both the site owner and users

Recommendations2

warningMissing trust pages: contact, about, privacy, terms

Add links to Contact, About, Privacy Policy, and Terms pages.

infoNo author attribution found

Add author information via schema markup or rel="author" for E-E-A-T signals

Tech Stack|1 technologies detected

55 / 100

Frameworks1

🛠️

Prototype

Script signature

javascript

semrush.com SEO Analysis