B · Fair

Page SEO Inspection

https://www.srirakshafoundation.org/
Crawled 16 Nov, 15:33 UTC (1 day ago)
HTTP 200 1 KB 114 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: Largest Contentful Paint is 4.7s (lab data), above the 2.5s target and in the poor range. 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.

✓ 2100% · excellent
Live snippet simulation
Title width: 543px / 580px
S Srirakshafoundation.org www.srirakshafoundation.org
Sri Raksha Foundation | Caring for Cows, Serving Our Elders

Sri Raksha Foundation supports cow welfare through its Gaushala and cares for senior citizens through its Old Age Home in Kolar Gold Fields, Karnataka.

Title tag 543px of 580px

The title length is well judged.

Rendered width

Desktop543px/ 580px
Mobile488px/ 920px

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

Meta description 151 characters

The meta description length is well judged.

Crawling & indexing

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

! 3i 2✓ 1372% · good
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.srirakshafoundation.org/">
Missing pages (404) HTTP 200

A page that does not exist returns HTTP 200. Search engines can index endless empty pages, and Search Console reports them as soft 404s.

https://www.srirakshafoundation.org/wrp-missing-1998809434 answered HTTP 200
How to fix
How to fix
Make the server or the application return a 404 status for unknown addresses. The not-found page can look the same; only the status code has to change.
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://srirakshafoundation.org/ answers HTTP 200 itself
http://www.srirakshafoundation.org/ answers HTTP 200 itself
http://srirakshafoundation.org/ answers HTTP 200 itself
How to fix
How to fix
Redirect every spelling (http and https, with and without www) to https://www.srirakshafoundation.org/ with a single 301.
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">
XML sitemap

A sitemap exists but robots.txt does not reference it, so crawlers must guess its location.

How to fix
How to fix
Sitemap: https://www.srirakshafoundation.org/sitemap.xml
HTTP status HTTP 200

The page returns 200 OK.

Redirect chain

The URL resolves without redirects.

Robots directives

No directive prevents indexing.

Language

Language is declared as "en".

lang="en"
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.0
Character encoding

The page declares UTF-8 encoding.

Mixed content

All resources load securely.

URL length 36 characters

The URL is 36 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 0 KB

robots.txt is present and does not block crawling.

XML sitemap 1 URLs

A sitemap is published, listing 1 URLs.

Lists 1 URLs

Content & metadata

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

i 3✓ 770% · good
Word count 348 Substantive
Headings 0 Little structure
H1 tags 0 None found
Text ratio 13.4% Text vs markup
Heading outline 0 headings

This page has no headings.

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">
Heading hierarchy

The heading outline skips levels (h1 → h3).

h1: Caring for Cows.Serving Our Elders.Building a Kinder Tomorrow.
    h3: Gaushala
    h3: Old Age Home
    h3: Support Our Work
    h3: Volunteer
  h2: Compassion that makes a difference
  h2: Your kindness can make a real difference.
  h2: Transparency matters
  h2: We would love to hear from you.
    h3: Send us a message
How to fix
How to fix
Descend one level at a time: h1, then h2, then h3.
H1 tag

The page has exactly one h1.

Caring for Cows.Serving Our Elders.Building a Kinder Tomorrow.
Content length 348 words

The page has roughly 348 words.

Text-to-HTML ratio 13.4% text

Text is 13.4% of the page source.

Table headers

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

Keyword placement

The page's prominent terms appear in its title, description or headings.

Where these terms appear

TermCountDensityTitleDescriptionHeadings
foundation72.67%✓✓✕
care72.67%✕✓✕
raksha51.91%✓✓✕
age51.91%✕✓✓
cows51.91%✓✕✓
Keyword repetition

No term is repeated unnaturally often.

Keyword cloud

The page's most frequent terms, from 262 words of content.

What this page is about

Term size reflects how often it appears. Density is not a ranking factor, this is a view of the page's subject, not a target to hit.

foundationcarerakshaagecowsgoldfieldskgfkarnatakaoldthroughkolarsrirakshafoundationhomecompassionsriseniorcitizensworksupportmakekindnesssupportingeverydonordonationinfoorgservingelderskindertomorrowcowgaushaladonateshelterlearnolderpeopledignity

AI & answer readiness

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

✕ 1i 4✓ 338% · needs work
AI crawlers 10/10 All allowed
Readable without JS No Needs JavaScript
Identity None No structured data
Quotable signals 1/4 Schema, date, author, answers
Content needs JavaScript

The page serves no text. All 348 words appear only after JavaScript runs.

served: 0 words
rendered: 348 words
How to fix
How to fix
Render this page on the server, or pre-render it at build time. Google will usually still index it, but answer engines and link previews read the served HTML and will see an empty page.
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.
llms.txt for AI agents

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

https://www.srirakshafoundation.org/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.
Attribution

Attribution signals present: contact page, about page.

contact page, about page

Extractable structure 348 words

348 words across 10 headings, 0 lists and 0 tables.

Entity identity

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

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✓ 1292% · 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
4.68s

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
0ms

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.54s

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 114 ms.

Render-blocking resources 1 found

1 render-blocking resource in the head.

HTML size 1 KB

The HTML document is 1 KB.

Deprecated tags

No deprecated HTML tags are used.

Inline styles 0 found

0 inline style attributes.

Compression

The response is compressed with zstd.

Content-Encoding: zstd
Page weight 14 requests · 1.5 MB

The page loads 14 requests totalling 1.5 MB.

What loaded, by type

Type RequestsTransferred
image6of 7 declared1.3 MB
script272 KB
font262 KB
stylesheet2of 1 declared9 KB
document11 KB
other11 KB

Of these, 4 requests (74 KB) come from third-party domains. The HTML declares 7 images but only 6 loaded, the rest are lazy-loaded and fetched when scrolled to.

Third-party services 2 services · 74 KB

2 third-party services load on this page, adding 74 KB.

Third-party services

Service TransferredMain thread
Google Fonts63 KBunder 1ms
Cloudflare10 KB9ms

0.0s of main-thread time

Browser caching 4 KB re-downloaded

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

Short cache lifetimes

FileCache lifetimeSize
static.cloudflareinsights.com/…823e78c4301a35b7e07294d873017920888140921d10 KB

Security

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

! 2i 7✓ 536% · needs work
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'
Email addresses in the page 1 found

1 email address is written into the page as plain text, where harvesting bots collect them for spam and phishing.

[email protected]
How to fix
How to fix
Use a contact form, or show the address through a script or as an image. If the address must stay, give it a strong spam filter.
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.
security.txt

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

https://www.srirakshafoundation.org/.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.
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 87 days left

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

87 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✓ 788% · good
DMARC policy

The DMARC policy for srirakshafoundation.org 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.

HTTP/3 HTTP/3

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

CDN Cloudflare

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

Domain expiry 292 days left

srirakshafoundation.org is registered until 5 Sep 2027 with GoDaddy.com, LLC.

292 days remaining
Domain age Under a year old

srirakshafoundation.org was registered on 5 Sep 2026, under a year ago. Age is not a ranking factor, but an established name is one buyers and partners look for.

IPv6

www.srirakshafoundation.org has an IPv6 address, so IPv6-only networks reach it directly.

SPF record

srirakshafoundation.org publishes an SPF record: v=spf1 include:zoho.in ~all

ads.txt

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

Links, media & schema

Links, images and structured data.

! 2i 1✓ 873% · good
Social share preview From this page's Open Graph tags
Image dimensions 7 found

7 images have no width and height, so the page shifts as they load (hurting CLS).

Shown as 6 unique sources; the counts show how often each repeats.

# / lineImage source
JS/images/logo/receipt-logo.jpeg ×2<img src="/images/logo/receipt-logo.jpeg" alt="Sri Raksha Foundation logo">
JS/images/common/foundation-hero.jpeg<img class="hero-image" src="/images/common/foundation-hero.jpeg" alt="Sri Raksha Foundation care and service">
JS/images/gaushala/gaushala-program-card.jpeg<img src="/images/gaushala/gaushala-program-card.jpeg" alt="" loading="lazy">
JS/images/old-age-home/old-age-home-program-card.jpeg<img src="/images/old-age-home/old-age-home-program-card.jpeg" alt="" loading="lazy">
JS/images/common/foundation-support-program-card.jpeg<img src="/images/common/foundation-support-program-card.jpeg" alt="" loading="lazy">
JS/images/common/volunteer-program-card.jpeg<img src="/images/common/volunteer-program-card.jpeg" alt="" loading="lazy">
How to fix
How to fix
<img src="…" width="800" height="600">, the browser reserves the space before decoding.
Responsive images 7 found

7 large images are served at one fixed size, so phones download desktop-sized files.

Shown as 6 unique sources; the counts show how often each repeats.

# / lineImage source
JS/images/logo/receipt-logo.jpeg ×2<img src="/images/logo/receipt-logo.jpeg" alt="Sri Raksha Foundation logo">
JS/images/common/foundation-hero.jpeg<img class="hero-image" src="/images/common/foundation-hero.jpeg" alt="Sri Raksha Foundation care and service">
JS/images/gaushala/gaushala-program-card.jpeg<img src="/images/gaushala/gaushala-program-card.jpeg" alt="" loading="lazy">
JS/images/old-age-home/old-age-home-program-card.jpeg<img src="/images/old-age-home/old-age-home-program-card.jpeg" alt="" loading="lazy">
JS/images/common/foundation-support-program-card.jpeg<img src="/images/common/foundation-support-program-card.jpeg" alt="" loading="lazy">
JS/images/common/volunteer-program-card.jpeg<img src="/images/common/volunteer-program-card.jpeg" alt="" loading="lazy">
How to fix
How to fix
<img src="hero.jpg" srcset="hero-400.jpg 400w, hero-800.jpg 800w" sizes="(max-width: 600px) 400px, 800px">
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 26 resources

26 internal and 0 external links.

26 internal, 0 external

26 internal, 0 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.

Broken links 1 checked

All 1 checked link resolve.

What to fix first

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

1
✕ Critical Largest Contentful Paint is 4.7s (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
2
✕ Critical The page serves no text. All 348 words appear only after JavaScript runs.
Render this page on the server, or pre-render it at build time. Google will usually still index it, but answer engines and link previews read the served HTML and will see an empty page.
involved
3
! Recommended 7 images have 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
4
! 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.srirakshafoundation.org/ with a single 301.
quick fix
5
! Recommended No canonical tag, so duplicate URLs may compete with each other.
<link rel="canonical" href="https://www.srirakshafoundation.org/">
quick fix
6
! 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
7
! Recommended Nothing prevents this page being embedded in a frame, which allows clickjacking.
Content-Security-Policy: frame-ancestors 'self'
quick fix
8
! Recommended A page that does not exist returns HTTP 200. Search engines can index endless empty pages, and Search Console reports them as soft 404s.
Make the server or the application return a 404 status for unknown addresses. The not-found page can look the same; only the status code has to change.
quick fix
9
! Recommended 7 large images are served at one fixed size, so phones download desktop-sized files.
<img src="hero.jpg" srcset="hero-400.jpg 400w, hero-800.jpg 800w" sizes="(max-width: 600px) 400px, 800px">
moderate
10
· 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
11
· 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
12
· Notice No heading is followed by a concise 40 to 60 word answer, the shape featured snippets and AI overviews extract.
Open at least one section with a direct 40 to 60 word answer to the question its heading poses.
moderate

Score breakdown

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

Indexability & Crawling41 checks · 16 issues
47
On-Page Content & Structure19 checks · 7 issues
67
Core Web Vitals13 checks · 1 issue
82
Schema & Rich Snippets1 checks · 1 issue
98
Media & Links10 checks · 2 issues
91
Overall scoreGrade B · 57/87 passed
69