Website review, no card needed
youthindiafoundation.com website review
Visit site (opens in a new tab)Reviewed 4 November 202636 issues · 75 checks
This review found 36 issues worth fixing on youthindiafoundation.com, 9 of them high impact, across 75 checks. The most urgent: improve image delivery. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
67DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Jun 6, 2026 | 3.6 s |
| Jun 13, 2026 | 3.4 s |
| Jun 20, 2026 | 3.8 s |
| Jun 27, 2026 | 3.4 s |
| Jul 4, 2026 | 3.2 s |
| Jul 11, 2026 | 3.2 s |
| Jul 18, 2026 | 3.2 s |
| Jul 25, 2026 | 3.6 s |
| Aug 1, 2026 | 3.9 s |
| Oct 31, 2026 | 3.2 s |
Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.
One score from every part of this review. How it works
How it loaded on a phone
0.8 s
1.5 s
2.3 s
3.0 s
3.8 s
4.5 s
5.3 s
6.0 s
Speed
Improve image delivery
24.6 s · 20.8 MB17 images could be 20.8 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 24.6 s faster on a phone.
Mobile performance score: 59
59/100Your mobile performance score is 59. Pages that score under 90 lose visitors before the first paint.
3 long tasks on the main thread
3 long tasks block the main thread while loading, the longest for 406 ms. During a long task the page ignores taps.
Render-blocking requests
350 ms5 files block the first paint until they finish downloading. Deferring or inlining them could save about 350 ms.
Main-thread work: 2.9 s
A phone's processor spends 2.9 s on main-thread work while loading, 679 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Use efficient cache lifetimes
260 KiB8 files are served with short cache lifetimes, so returning visitors download them again (260 KiB).
Reduce unused JavaScript
150 ms · 116 KiBAbout 116 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.
Legacy JavaScript
150 ms · 28 KiBPolyfills for old browsers add 28 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Font display
150 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 150 ms).
8 third-party services on the page
8 third-party services load with your homepage (1000logos.net, britannica.com and wikimedia.org and others), adding 641 KiB and 0 ms of main-thread time.
Reduce unused CSS
50 ms · 11 KiBAbout 11 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 50 ms faster on a phone.
Minify CSS
20 ms · 2 KiB2 KiB could be saved by minifying CSS.
Chained critical requests
Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
1 checks passed
Server response: 2 ms
2 msYour server sent the HTML in 2 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 82.1 s
82.1 sYour largest element takes 82.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “img”.
Speed Index: 21.2 s
21.2 sVisually, the page fills in at 21.2 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 87.4 s
87.4 sThe page becomes fully interactive after 87.4 s. Good is under 3.8 s.
Total Blocking Time: 280 ms
280 msScripts block taps and scrolling for 280 ms in total while the page loads. Good is under 200 ms.
5 images without width and height
5 images have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) held steady for real visitors
+3%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 3.6 s to 3.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Not enough real-visitor data yet
Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.
2 checks passed
First Contentful Paint: 1.5 s
1.5 sThe first text or image appears after 1.5 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 25.7 MB in 84 requests
25.7 MBYour homepage downloads 25.7 MB in 84 requests on a phone: images 25.1 MB (37), scripts 296 KiB (23) and fonts 144 KiB (2). Under 2 MB keeps phones on slow connections fast.
11 images over 500 KB
11 images weigh 23.6 MB together. On a phone connection a single image that size takes seconds.
19 images far larger than shown
22.8 MB19 images are downloaded at several times the size a phone draws them, for example 1.jpg at 6,000 px wide, shown at 340 px. Resized copies would save about 22.8 MB.
18 images below the first screen load straight away
18 images further down the page (19.7 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
16 images in older formats
16 images (18.1 MB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.
About 7.3 g of CO₂ per visit
7.29 gBy the Sustainable Web Design model, a visit to your homepage emits about 7.29 g of CO₂e: 874.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
6 text elements with low contrast
6 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
4 tap targets too small
4 tap targets are too small or too close together to hit reliably with a finger.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
Headings skip levels
Headings skip levels (h1 → h3, h3 → h5 and h3 → h5), which makes the page harder to scan with a screen reader.
1 checks passed
Every image has alt text
All 33 images in the HTML carry an alt attribute.
SEO
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
Title is short (22 characters)
Your title is only 22 characters: “Youth India Foundation”. Between 30 and 65 characters leaves room to say what you do and for whom.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
No social preview image
No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
No XML sitemap
No XML sitemap at https://youthindiafoundation.com/sitemap.xml, so Google discovers your pages only by following links.
No robots.txt
There is no robots.txt at youthindiafoundation.com/robots.txt, the first file search crawlers ask for.
1 link crawlers can't follow
1 link has no real href, so search engines can't follow it.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
34 internal links, 10 external
The homepage links to 34 pages on youthindiafoundation.com and 10 external pages.
1 checks passed
One H1 headline
Your main headline reads: “A community for everyone to look beyond their own interests.”.
AI search readiness
No Organization structured data
There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.
No llms.txt
There is no https://youthindiafoundation.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.
2 checks passed
AI answer engines may read the site
There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading the site and cite it in answers.
Text is in the HTML
Your server sends the page's text in the HTML (843 words), so crawlers that don't run JavaScript still read it.
Other pages
14 pages share a title
/, https://youthindiafoundation.com/team, https://youthindiafoundation.com/portfolio, https://youthindiafoundation.com/contact, https://youthindiafoundation.com/states/project-01 and https://youthindiafoundation.com/states/project-02 and 8 others all use the title “Youth India Foundation”. Search engines can't tell which page to show for a search, so each competes with the others.
13 pages without a meta description
https://youthindiafoundation.com/team, https://youthindiafoundation.com/portfolio, https://youthindiafoundation.com/contact, https://youthindiafoundation.com/states/project-01, https://youthindiafoundation.com/states/project-02 and https://youthindiafoundation.com/states/project-03 and 7 others have no meta description, so Google writes the search snippet from whatever text it finds.
13 pages without an H1
https://youthindiafoundation.com/team, https://youthindiafoundation.com/portfolio, https://youthindiafoundation.com/contact, https://youthindiafoundation.com/states/project-01, https://youthindiafoundation.com/states/project-02 and https://youthindiafoundation.com/states/project-03 and 7 others have no <h1> headline, so visitors and search engines get no clear main topic.
2 pages with very little text
https://youthindiafoundation.com/portfolio and https://youthindiafoundation.com/contact have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.
13 internal pages checked
We fetched 13 pages linked from your homepage and read each the way a search engine does.
4 checks passed
Linked pages load
All 13 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 13 pages that loaded have a <title>.
Best practices
4 broken images
4 images failed to load on a phone, for example https://upload.wikimedia.org/wikipedia/commons/thumb/8/82/Dell_Logo.png/1200px-Dell_Logo.png.
14 small tap targets
14 of 25 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
5 distorted images
5 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
No risk reducer
No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.
About 1,218 words of copy
The homepage carries about 1,218 words of visible text.
5 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “JOIN US” and “CONTACT US”.
5 calls to action
The homepage has 5 calls to action, for example “Join Us”, “Contact Us” and “Subscribe”.
1 short form
A short form (1 field at most) is right on the homepage, asking for an email.
Social proof on the page
Social proof on the homepage: 8 customer or partner logos and “0 + Active Members”.
Direct contact links
Visitors can reach you directly: 0 phone links and 1 email link.
Privacy and tracking
No consent tool detected
No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.
20 other companies contacted
Loading the homepage contacts 20 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
Security, domain, email and software versions
The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at youthindiafoundation.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
- The footer still says © 2023.
Stack
- CMS
- WordPress
- Framework
- Next.js
- Hosting
- Vercel
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 36 issues on youthindiafoundation.com, including 11 speed issues, 8 SEO issues and 1 conversion gap. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.
- 28 research agents read your site, reviews, competitors, communities and public filings
- Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
- Competitor intelligence with battlecards for your closest rivals
- Ideal customer profile, buyer segments and buying-stage funnel
- Ranked channels, outreach sequences and content angles
- Live Reddit threads where buyers ask for what you sell, with draft replies
- Earned media and PR openings
- At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
- PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
- Refresh the playbook later to see what changed
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.