F · Critical issues

Page SEO Inspection

https://qayamsayani.com/
Crawled 12 Nov, 05:08 UTC (9 hr ago)
HTTP 403 5 KB 53 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 68% Complete
Primary focus: "noindex" is set via meta robots, so this page will not appear in search results. 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.

! 1i 10% · needs work
Live snippet simulation
Title width: 147px / 580px
Q Qayamsayani.com qayamsayani.com
Just a moment...

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 147px of 580px

The title is 16 characters. Short titles are fine, but there may be room to say more about what the page offers.

Rendered width

Desktop147px/ 580px
Mobile133px/ 920px

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

Crawling & indexing

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

✕ 2! 2i 2✓ 1267% · needs work
HTTP status HTTP 403

The page returns HTTP 403 rather than 200.

403 https://qayamsayani.com/
How to fix
How to fix
Restore the page or redirect the URL to a working equivalent.
Robots directives

"noindex" is set via meta robots, so this page will not appear in search results.

meta robots: noindex,nofollow
How to fix
How to fix
Remove the directive if the page is meant to be found in search.
Robots directives

"nofollow" is set via meta robots.

meta robots: noindex,nofollow
How to fix
How to fix
Confirm this restriction is intentional.
Canonical tag

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

How to fix
How to fix
<link rel="canonical" href="https://qayamsayani.com/">
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">
Missing pages (404) HTTP 403

A page that does not exist returns HTTP 403 rather than 404, which tells search engines something other than "gone".

https://qayamsayani.com/wrp-missing-4b6d6d8ceb answered HTTP 403
How to fix
How to fix
Return 404 for addresses that do not exist.
Redirect chain

The URL resolves without redirects.

Language

Language is declared as "en-us".

lang="en-us"
hreflang

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

Viewport

The viewport is configured for mobile.

width=device-width,initial-scale=1
Character encoding

The page declares UTF-8 encoding.

Mixed content

All resources load securely.

URL length 24 characters

The URL is 24 characters.

URL readability

The URL is clean and readable.

URL depth 0 levels deep

The page is 0 levels deep.

URL parameters

The URL has no query parameters.

robots.txt 3 KB

robots.txt is present and does not block crawling.

XML sitemap 4 URLs

A sitemap is published, listing 4 URLs.

Lists 4 URLs

www and https versions 3 checked

All 3 other spellings of this address redirect here in one permanent step.

Content & metadata

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

! 1i 3✓ 343% · needs work
Word count 38 Thin content
Headings 0 Little structure
H1 tags 0 None found
Text ratio 0.7% Text vs markup
Heading outline 0 headings

This page has no headings.

Content length 38 words

The page has roughly 38 words, too little for search engines to tell what it is about.

How to fix
How to fix
Expand the page to answer the questions a reader arrives with.
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">
Text-to-HTML ratio 0.7% text

Only 0.7% of the page is readable text; the rest is markup and script.

How to fix
How to fix
Move inline scripts and styles to external files, and remove unused markup.
H1 tag

The page has exactly one h1.

qayamsayani.com
Heading hierarchy

The heading outline descends in order.

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✓ 338% · needs work
AI crawlers 3/10 7 excluded
Readable without JS Yes Served complete
Identity None No structured data
Quotable signals 1/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.
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.
AI crawler access 10 checked

7 AI crawlers are excluded by robots.txt.

GPTBot (OpenAI training)
ClaudeBot (Anthropic training)
Claude-Web (live fetches)
Google-Extended (AI Overviews)
Applebot-Extended
Bytespider (TikTok)
CCBot (Common Crawl)
How to fix
How to fix
Intentional exclusions need no action. If it was not intentional, remove the Disallow rule for those user agents.
Live answer fetches

Claude-Web (live fetches), Google-Extended (AI Overviews) cannot fetch this page to answer a question about it.

Claude-Web (live fetches)
Google-Extended (AI Overviews)
How to fix
How to fix
These agents fetch a page when someone asks about it, rather than to train on it. Allowing them is what makes the page citable in an answer.
Attribution

Attribution signals present: privacy policy.

privacy policy

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.

llms.txt for AI agents

llms.txt is published, giving AI agents a curated map of the site.

Speed & delivery

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

✕ 1i 1✓ 1185% · 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 Poor
5.11s

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 Good
135ms

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 Needs work
2.27s

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.

TTFBNo data
n/a

Real-user response time

Target ≤ 800ms

Needs real-user data from Chrome UX Report

Time to first byte

Time to first byte is 53 ms.

Render-blocking resources 1 found

1 render-blocking resource in the head.

HTML size 5 KB

The HTML document is 5 KB.

Deprecated tags

No deprecated HTML tags are used.

Inline styles 3 found

3 inline style attributes.

Compression

The response is compressed with br.

Content-Encoding: br
Page weight 24 requests · 678 KB

The page loads 24 requests totalling 678 KB.

What loaded, by type

Type RequestsTransferred
script5of 2 declared333 KB
image2of 1 declared220 KB
font474 KB
stylesheet5of 0 declared24 KB
other618 KB
document29 KB

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

Third-party services 1 services · 178 KB

1 third-party service load on this page, adding 178 KB.

Third-party services

Service TransferredMain thread
Google Tag Manager178 KB163ms

0.2s of main-thread time

Browser caching 0 KB re-downloaded

Cache lifetimes are long enough that a returning visitor re-downloads only 0 KB.

Short cache lifetimes

FileCache lifetimeSize
qayamsayani.com/email-decode.min.js2d1 KB

Security

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

! 1i 2✓ 1077% · good
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
Content Security Policy

The Content-Security-Policy allows unsafe-inline or unsafe-eval, which undermines much of its protection.

default-src 'none'; script-src 'nonce-luhrsBKXLNubfDrNjy5gHK' 'unsafe-eval' https://challenges.cloudflare.com; script-src-attr 'none'; style-src 'unsafe-inline…
How to fix
How to fix
Use nonces or hashes instead of unsafe-inline.
security.txt

No security.txt, so somebody who finds a vulnerability has no published way to tell you about it.

https://qayamsayani.com/.well-known/security.txt
How to fix
How to fix
Publish /.well-known/security.txt with a Contact: line (an email address or a form) and an Expires: date.
Email addresses in the page

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

MIME sniffing

MIME sniffing is disabled.

Clickjacking protection

The page is protected against framing.

Referrer policy

Referrer-Policy is "same-origin".

same-origin
Permissions policy

A Permissions-Policy limits which browser features the page and its embeds can use.

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 31 days left

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

31 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.

Server & domain

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

i 1✓ 686% · good
DMARC policy

The DMARC policy for qayamsayani.com is p=none, which collects reports but does not stop mail that spoofs the domain.

v=DMARC1; p=none; rua=mailto:[email protected]
How to fix
How to fix
Once the reports show only your own services sending, move to p=quarantine and then p=reject.
HTTP/2 HTTP/2

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

CDN Cloudflare

Served through Cloudflare, a CDN, so visitors get the page from a server near them.

Domain expiry 603 days left

qayamsayani.com is registered until 7 Jul 2028 with Cloudflare, Inc.

603 days remaining
Domain age Under a year old

qayamsayani.com was registered on 7 Jul 2026, under a year ago. Age is not a ranking factor, but an established name is one buyers and partners look for.

IPv6

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

SPF record

qayamsayani.com publishes an SPF record: v=spf1 include:_spf.mx.cloudflare.net ~all

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✓ 982% · good
Social share preview From this page's Open Graph tags
Image dimensions 1 found

1 image has no width and height, so the page shifts as they load (hurting CLS).

# / lineImage source
JS/favicon.ico<img src="/favicon.ico" class="_fc425d3f6c3beb39de6335d8" alt="Icon for qayamsayani.com">
How to fix
How to fix
<img src="…" width="800" height="600">, the browser reserves the space before decoding.
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 2 resources

0 internal and 2 external links.

0 internal, 2 external

0 internal, 2 external

Anchor text

Anchor text describes its destinations.

Link rel attributes

Outbound link rel attributes look appropriate.

In-page anchors

In-page anchors resolve to real targets.

Image alt text

All images carry an alt attribute.

Image formats

No heavy legacy image formats found.

Image loading

Image loading strategy looks sound.

Responsive images

Images are served responsively or are small enough not to need it.

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 "noindex" is set via meta robots, so this page will not appear in search results.
Remove the directive if the page is meant to be found in search.
quick fix
2
✕ Critical The page returns HTTP 403 rather than 200.
Restore the page or redirect the URL to a working equivalent.
moderate
3
✕ Critical Largest Contentful Paint is 5.1s (lab data), above the 2.5s target and in the poor range.
Optimise the hero image, remove render-blocking CSS and JS, and improve server response time.
moderate
4
! 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
5
! Recommended 1 image has no width and height, so the page shifts as they load (hurting CLS).
<img src="…" width="800" height="600">, the browser reserves the space before decoding.
quick fix
6
! Recommended "nofollow" is set via meta robots.
Confirm this restriction is intentional.
quick fix
7
! Recommended No canonical tag, so duplicate URLs may compete with each other.
<link rel="canonical" href="https://qayamsayani.com/">
quick fix
8
! 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
9
! Recommended The page has roughly 38 words, too little for search engines to tell what it is about.
Expand the page to answer the questions a reader arrives with.
involved
10
· Notice Claude-Web (live fetches), Google-Extended (AI Overviews) cannot fetch this page to answer a question about it.
These agents fetch a page when someone asks about it, rather than to train on it. Allowing them is what makes the page citable in an answer.
quick fix
11
· Notice The page publishes no date. Not expected on a page like this; worth adding if its content goes out of date.
<time datetime="2026-09-17">17 September 2026</time>, or datePublished in Article structured data.
quick fix
12
· Notice The page has no structured data, so it cannot qualify for rich results.
<script type="application/ld+json">{"@context":"https://schema.org","@type":"Article","headline":"…"}</script>
quick fix

Score breakdown

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

Indexability & Crawling39 checks · 10 issues
30
On-Page Content & Structure16 checks · 11 issues
66
Core Web Vitals13 checks · 2 issues
79
Schema & Rich Snippets1 checks · 1 issue
98
Media & Links10 checks · 1 issue
96
Overall scoreGrade F · 54/84 passed
30