D · Poor

Page SEO Inspection

https://blog.toolmasterpro.com/
Crawled 18 Nov, 20:14 UTC (1 hr ago)
HTTP 429 3 KB 82 ms TTFB
Download PDF

PDF export is a paid feature

A PDF of the full report, ready to send to a client or a colleague, comes with Basic at $19 a month and every plan above it, along with saved history. The report itself stays free to read.

See the plans
On-Page Checklist 58% Complete
Primary focus: The page returns HTTP 429 rather than 200. Fix now →
Filter:

Full diagnostics

Every check that ran, grouped by what it affects. Problems appear first in each group.

Meta Tags & Search Snippet Simulator

The tags that decide how this page is titled and described in search results.

! 1✓ 150% · fair
Live snippet simulation
Title width: 274px / 580px
B Blog.toolmasterpro.com blog.toolmasterpro.com
https://blog.toolmasterpro.com/

No meta description, Google will generate a snippet from the page.

Meta description

The page has no meta description, so search engines will improvise the snippet.

How to fix
How to fix
<meta name="description" content="A 120 to 160 character summary with a clear call to action.">
Title tag 274px of 580px

The title length is well judged.

Rendered width

Desktop274px/ 580px
Mobile247px/ 920px

Measured in Arial at the size Google renders result titles, accurate to within a fraction of a percent of a browser. Characters: 31.

Crawling & indexing

Whether search engines can reach, read and index this page at all.

✕ 1! 4i 3✓ 953% · needs work
HTTP status HTTP 429

The page returns HTTP 429 rather than 200.

429 https://www.google.com/sorry/index?continue=https://blog.toolmasterpro.com/&q=EgSl402-GImO-NcGIi3bxSJZsw5lHLhzDP5wCCTWvzJ6wLqjva_nMrXWA9v5xXHvc6DM9NVt0K_o8SQyAnJSWgFDYNz83qG9v5PV4gE
How to fix
How to fix
Restore the page or redirect the URL to a working equivalent.
Canonical tag

No canonical tag, so duplicate URLs may compete with each other.

How to fix
How to fix
<link rel="canonical" href="https://www.google.com/sorry/index?continue=https://blog.toolmasterpro.com/&q=EgSl402-GImO-NcGIi3bxSJZsw5lHLhzDP5wCCTWvzJ6wLqjva_nMrXWA9v5xXHvc6DM9NVt0K_o8SQyAnJSWgFDYNz83qG9v5PV4gE">
Language

The html element has no lang attribute, which affects both search targeting and screen readers.

How to fix
How to fix
<html lang="en">
Viewport

The viewport does not set width=device-width, so the layout may not adapt to the device.

initial-scale=1
How to fix
How to fix
<meta name="viewport" content="width=device-width, initial-scale=1">
www and https versions 3 found

3 other spellings of this address do not lead here, so search engines can treat them as separate pages and split the ranking between them.

https://google.com/sorry/index?continue=https://blog.toolmasterpro.com/&q=EgSl402-GImO-NcGIi3bxSJZsw5lHLhzDP5wCCTWvzJ6wLqjva_nMrXWA9v5xXHvc6DM9NVt0K_o8SQyAnJSWgFDYNz83qG9v5PV4gE answers HTTP 404 itself
http://www.google.com/sorry/index?continue=https://blog.toolmasterpro.com/&q=EgSl402-GImO-NcGIi3bxSJZsw5lHLhzDP5wCCTWvzJ6wLqjva_nMrXWA9v5xXHvc6DM9NVt0K_o8SQyAnJSWgFDYNz83qG9v5PV4gE answers HTTP 429 itself
http://google.com/sorry/index?continue=https://blog.toolmasterpro.com/&q=EgSl402-GImO-NcGIi3bxSJZsw5lHLhzDP5wCCTWvzJ6wLqjva_nMrXWA9v5xXHvc6DM9NVt0K_o8SQyAnJSWgFDYNz83qG9v5PV4gE answers HTTP 404 itself
How to fix
How to fix
Redirect every spelling (http and https, with and without www) to https://www.google.com/sorry/index?continue=https://blog.toolmasterpro.com/&q=EgSl402-GImO-NcGIi3bxSJZsw5lHLhzDP5wCCTWvzJ6wLqjva_nMrXWA9v5xXHvc6DM9NVt0K_o8SQyAnJSWgFDYNz83qG9v5PV4gE with a single 301.
Redirect chain 1 redirects

The URL redirects once before resolving, costing an extra round trip.

302 https://blog.toolmasterpro.com/
429 https://www.google.com/sorry/index?continue=https://blog.toolmasterpro.com/&q=EgSl402-GImO-NcGIi3bxSJZsw5lHLhzDP5wCCTWvzJ6wLqjva_nMrXWA9v5xXHvc6DM9NVt0K_o8SQyAnJSWgFDYNz83qG9v5PV4gE
How to fix
How to fix
Link to the final URL directly so visitors and crawlers skip the hop.
Favicon

No favicon is declared. Google shows one beside your result on mobile.

How to fix
How to fix
<link rel="icon" href="/favicon.svg" type="image/svg+xml">
URL length 181 characters

The URL is 181 characters, above the ~100 where results start truncating it.

https://www.google.com/sorry/index?continue=https://blog.toolmasterpro.com/&q=EgSl402-GImO-NcGIi3bxSJZsw5lHLhzDP5wCCTWvzJ6wLqjva_nMrXWA9v5xXHvc6DM9NVt0K_o8SQyAnJSWgFDYNz83qG9v5PV4gE
How to fix
How to fix
Shorten the path to the words that describe the page.
Robots directives

No directive prevents indexing.

hreflang

No hreflang annotations, which is correct for a single-language page.

Character encoding

The page declares UTF-8 encoding.

Mixed content

All resources load securely.

URL readability

The URL is clean and readable.

URL depth 2 levels deep

The page is 2 levels deep.

URL parameters 2 found

The URL carries 2 parameters.

robots.txt 7 KB

robots.txt is present and does not block crawling.

XML sitemap 23 URLs

A sitemap index is published, referencing 23 sitemaps.

Sitemap index referencing 23 sitemaps

Missing pages (404) HTTP 404

A page that does not exist returns HTTP 404, so search engines drop dead addresses.

Content & metadata

What the page says it is about, and how it reads.

✕ 1i 3✓ 233% · needs work
Word count 154 Thin content
Headings 0 Little structure
H1 tags 0 None found
Text ratio 19.6% Text vs markup
Heading outline 0 headings

This page has no headings.

H1 tag

The page has no h1, so its main subject is undeclared.

How to fix
How to fix
<h1>The page's primary subject</h1>
Open Graph tags

Open Graph tags are incomplete: og:title, og:description, og:image missing.

Open Graph tags

Tag Status
og:title✕Missing
og:description✕Missing
og:image✕Missing
og:url✓Present
og:type✓Present
How to fix
How to fix
<meta property="og:image" content="https://example.com/share-1200x630.jpg">
Twitter card

No twitter:card tag, so shared links render as a small preview.

How to fix
How to fix
<meta name="twitter:card" content="summary_large_image">
Content length 154 words

The page has roughly 154 words. Fine for a short page such as pricing or contact; a page meant to rank for a topic usually needs more.

How to fix
How to fix
Expand the page to answer the questions a reader arrives with.
Text-to-HTML ratio 19.6% text

Text is 19.6% of the page source.

Table headers

No data tables on this page, so there are no columns to label.

Keyword usage

The page has too little text for keyword analysis to mean anything.

AI & answer readiness

Whether answer engines and AI overviews can extract and trust this page.

i 5✓ 229% · needs work
AI crawlers 10/10 All allowed
Readable without JS Yes Served complete
Identity None No structured data
Quotable signals 0/4 Schema, date, author, answers
Answer readiness 0 found

No heading is followed by a concise 40 to 60 word answer, the shape featured snippets and AI overviews extract.

How to fix
How to fix
Open at least one section with a direct 40 to 60 word answer to the question its heading poses.
Content freshness

The page publishes no date. Not expected on a page like this; worth adding if its content goes out of date.

How to fix
How to fix
<time datetime="2026-09-17">17 September 2026</time>, or datePublished in Article structured data.
Attribution

Nothing on the page identifies who is behind it: no author, publisher, or about and contact links.

How to fix
How to fix
Add an author byline with Person structured data, and link to about and contact pages.
Answer schema

No structured data an answer engine can lift directly, such as FAQPage, HowTo or Article.

How to fix
How to fix
Mark up question-and-answer content as FAQPage, or step-by-step content as HowTo.
llms.txt for AI agents

No llms.txt. AI coding agents have no curated map of this site.

https://www.google.com/llms.txt returned nothing
How to fix
How to fix
A markdown file at /llms.txt listing your most useful pages with one-line descriptions. It does not affect how AI assistants cite you in answers, and nobody has shown that it does. What it helps is agents reading your documentation directly: Anthropic supports it, Perplexity uses it to choose pages, and Cursor, Continue and Cline navigate docs with it. Worth doing for a documentation or API site, and safe to skip otherwise.
Extractable structure

The page is too short to assess structure.

Entity identity

The page has no structured data, so there is no entity to check.

Readable without JavaScript

The page reads the same with and without JavaScript.

AI crawler access 10 checked

Every AI crawler checked is allowed to read this page.

Speed & delivery

What makes the page slow, and what the loading experience measures.

✕ 1! 2✓ 873% · needs work
Rendered page
The page as it rendered on a mobile viewport during the performance test
Mobile, measured
The page as it rendered on a desktop viewport
Desktop, measured
LCP Good
1.12s

Largest Contentful Paint

Target ≤ 2.5s

What this measures

How long until the largest thing on screen, usually the hero image, video or headline block, has finished rendering. It is a proxy for "when did this page feel loaded".

What moves it: Serve the hero image in a modern format at the size it is displayed, preload it, and remove render-blocking CSS and JavaScript ahead of it. A slow server response delays it too, so check TTFB first.

INP Needs work
425ms

Interaction to Next Paint

Target ≤ 200ms

What this measures

How long the page takes to respond visibly after a tap, click or key press, measured across every interaction, not just the first. High INP is what makes a page feel unresponsive even once it looks ready.

What moves it: Break up long JavaScript tasks so the main thread is free to respond, defer work that is not needed for the interaction, and avoid large re-renders on every event.

CLS Good
0

Cumulative Layout Shift

Target ≤ 0.1

What this measures

How much visible content jumps around while the page loads. This is what makes someone tap the wrong thing because a banner or image pushed the layout down underneath their finger.

What moves it: Give images and video explicit width and height so the browser reserves the space, reserve room for ads and embeds, and avoid inserting content above what is already on screen.

FCP Good
1.42s

First Contentful Paint

Target ≤ 1.8s

What this measures

How long until anything at all appears, the first text or image painted. It separates "the page starts slowly" from "the biggest element is slow": a fast FCP with a slow LCP points at the hero, while both slow points at the server.

What moves it: Cut render-blocking CSS and JavaScript in the head, inline the styles needed for the first screen, and improve the server response time.

TTFB Poor
3996ms

Real-user response time

Target ≤ 800ms

What this measures

How long real visitors waited for the first byte of the response, the 75th percentile across everyone who actually loaded the page, not a single test from one location.

What moves it: Cache the response at the edge, host closer to your visitors, and reduce the work done before the first byte is sent, database queries, template rendering and third-party calls.

Compression

The HTML is served uncompressed. Gzip or Brotli typically cuts it by 70%.

How to fix
How to fix
Enable Brotli or gzip compression for text responses.
Render-blocking resources 0 found

0 render-blocking resources in the head.

HTML size 3 KB

The HTML document is 3 KB.

Deprecated tags

No deprecated HTML tags are used.

Inline styles 11 found

11 inline style attributes.

Page weight 1 requests · 2 KB

The page loads 1 requests totalling 2 KB.

What loaded, by type

Type RequestsTransferred
document12 KB

Of these, 0 requests (0 KB) come from third-party domains.

Security

Transport security, reputation and the response headers that protect visitors.

! 2i 5✓ 750% · fair
HSTS

No Strict-Transport-Security header, so a first visit over HTTP can be intercepted before the redirect.

How to fix
How to fix
Strict-Transport-Security: max-age=31536000; includeSubDomains
Clickjacking protection

Nothing prevents this page being embedded in a frame, which allows clickjacking.

How to fix
How to fix
Content-Security-Policy: frame-ancestors 'self'
MIME sniffing

No X-Content-Type-Options header, so browsers may guess a resource type and execute it.

How to fix
How to fix
X-Content-Type-Options: nosniff
Referrer policy

No Referrer-Policy header, so full URLs may leak to third-party sites.

How to fix
How to fix
Referrer-Policy: strict-origin-when-cross-origin
Content Security Policy

No Content-Security-Policy, the main defence against cross-site scripting.

How to fix
How to fix
Content-Security-Policy: default-src 'self'
Permissions policy

No Permissions-Policy header, so any script or embed on the page may ask for the camera, microphone or location.

How to fix
How to fix
Permissions-Policy: camera=(), microphone=(), geolocation=()
TLS version

The server still accepts TLS 1.0 or 1.1, retired in 2021. No current browser uses them, so they serve only very old clients and attackers forcing a weaker connection.

How to fix
How to fix
Disable TLS 1.0 and 1.1 and keep 1.2 and 1.3. On a CDN this is usually a "minimum TLS version" setting.
Email addresses in the page

No email addresses are written into the page for harvesting bots to collect.

Cookie flags

The page sets no cookies, so there are none to expose.

Version disclosure

No software versions are disclosed in headers or the page.

TLS certificate 68 days left

The TLS certificate is valid for another 68 days, issued by Google Trust Services.

68 days remaining
Google Web Risk

Not listed by Google Web Risk for malware, phishing or unwanted software.

TLS version TLS 1.3

Connections use TLS 1.3.

security.txt

security.txt publishes a contact for reporting vulnerabilities.

Server & domain

The server and the domain behind the page: protocol, network, registration and email records.

✓ 8100% · excellent
HTTP/2 HTTP/2

Served over HTTP/2, which loads a page's files in parallel over one connection.

HTTP/3 HTTP/3

Announces HTTP/3, which browsers switch to on a later visit for faster connections on poor networks.

CDN

No CDN was detected in the response, so every visitor is served from the origin server. Fine for a local audience; a CDN helps a distant one.

Domain expiry 665 days left

google.com is registered until 14 Sep 2028 with MarkMonitor Inc.

665 days remaining
Domain age 29 years old

google.com was registered on 15 Sep 1997, 29 years ago. Age is not a ranking factor, but an established name is one buyers and partners look for.

IPv6

www.google.com has an IPv6 address, so IPv6-only networks reach it directly.

SPF record

google.com publishes an SPF record: v=spf1 include:_spf.google.com ~all

DMARC policy

google.com has a DMARC policy of reject.

ads.txt

No ad network loads on this page, so ads.txt is not needed.

Links, media & schema

Links, images and structured data.

! 1i 1✓ 467% · fair
Social share preview From this page's Open Graph tags
Anchor text 1 found

1 link use non-descriptive anchor text, which tells neither readers nor engines where it leads.

# / lineLink
#1 L27"Learn more" → //support.google.com/websearch/answer/86640<a href="//support.google.com/websearch/answer/86640">Learn more</a>
How to fix
How to fix
Describe the destination: "read our grinder guide" rather than "click here".
Structured data

The page has no structured data, so it cannot qualify for rich results.

How to fix
How to fix
<script type="application/ld+json">{"@context":"https://schema.org","@type":"Article","headline":"…"}</script>
Link distribution 3 resources

2 internal and 1 external links.

2 internal, 1 external

2 internal, 1 external

Link rel attributes

Outbound link rel attributes look appropriate.

In-page anchors

In-page anchors resolve to real targets.

Images

The page contains no images.

Broken links 2 checked

All 2 checked links resolve.

What to fix first

Ranked by impact against effort, the top of this list buys the most for the least work.

1
✕ Critical The page returns HTTP 429 rather than 200.
Restore the page or redirect the URL to a working equivalent.
moderate
2
✕ Critical The page has no h1, so its main subject is undeclared.
<h1>The page's primary subject</h1>
quick fix
3
✕ Critical Real users wait 3996ms for the first byte, above the 800ms target.
Cache at the edge, move hosting closer to visitors, or cut server work before the first byte.
moderate
4
! Recommended The viewport does not set width=device-width, so the layout may not adapt to the device.
<meta name="viewport" content="width=device-width, initial-scale=1">
quick fix
5
! Recommended The page has no meta description, so search engines will improvise the snippet.
<meta name="description" content="A 120 to 160 character summary with a clear call to action.">
quick fix
6
! Recommended The HTML is served uncompressed. Gzip or Brotli typically cuts it by 70%.
Enable Brotli or gzip compression for text responses.
quick fix
7
! Recommended 3 other spellings of this address do not lead here, so search engines can treat them as separate pages and split the ranking between them.
Redirect every spelling (http and https, with and without www) to https://www.google.com/sorry/index?continue=https://blog.toolmasterpro.com/&q=EgSl402-GImO-NcGIi3bxSJZsw5lHLhzDP5wCCTWvzJ6wLqjva_nMrXWA9v5xXHvc6DM9NVt0K_o8SQyAnJSWgFDYNz83qG9v5PV4gE with a single 301.
quick fix
8
! Recommended No canonical tag, so duplicate URLs may compete with each other.
<link rel="canonical" href="https://www.google.com/sorry/index?continue=https://blog.toolmasterpro.com/&q=EgSl402-GImO-NcGIi3bxSJZsw5lHLhzDP5wCCTWvzJ6wLqjva_nMrXWA9v5xXHvc6DM9NVt0K_o8SQyAnJSWgFDYNz83qG9v5PV4gE">
quick fix
9
! Recommended 1 link use non-descriptive anchor text, which tells neither readers nor engines where it leads.
Describe the destination: "read our grinder guide" rather than "click here".
quick fix
10
! Recommended No Strict-Transport-Security header, so a first visit over HTTP can be intercepted before the redirect.
Strict-Transport-Security: max-age=31536000; includeSubDomains
quick fix
11
! Recommended Nothing prevents this page being embedded in a frame, which allows clickjacking.
Content-Security-Policy: frame-ancestors 'self'
quick fix
12
! Recommended Interaction to Next Paint is 425ms (real-user data), above the 200ms target.
Break up long JavaScript tasks and defer work that is not needed for the first interaction.
involved

Score breakdown

How each area scored. Categories that could not be measured are excluded rather than counted as zero.

Indexability & Crawling40 checks · 16 issues
24
On-Page Content & Structure14 checks · 9 issues
48
Core Web Vitals11 checks · 3 issues
66
Schema & Rich Snippets1 checks · 1 issue
98
Media & Links5 checks · 1 issue
96
Overall scoreGrade D · 41/77 passed
35