Website review, no card needed
leadsguru.in website review
Visit site (opens in a new tab)Reviewed 28 October 202649 issues · 90 checks
This review found 49 issues worth fixing on leadsguru.in, 18 of them high impact, across 90 checks. The most urgent: use efficient cache lifetimes. 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
70CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 5.7 s |
| May 16, 2026 | 5.6 s |
| May 23, 2026 | 5.7 s |
| May 30, 2026 | 5.6 s |
| Jun 6, 2026 | 5.7 s |
| Jun 13, 2026 | 5.7 s |
| Jun 20, 2026 | 5.7 s |
| Jun 27, 2026 | 5.7 s |
| Jul 4, 2026 | 5.3 s |
| Jul 11, 2026 | 4.8 s |
| Jul 18, 2026 | 4.2 s |
| Jul 25, 2026 | 3.6 s |
| Aug 1, 2026 | 3.2 s |
| Aug 8, 2026 | 3.1 s |
| Aug 15, 2026 | 3.0 s |
| Aug 22, 2026 | 3.0 s |
| Aug 29, 2026 | 3.0 s |
| Sep 5, 2026 | 3.0 s |
| Sep 12, 2026 | 3.0 s |
| Sep 19, 2026 | 3.0 s |
| Sep 26, 2026 | 3.0 s |
| Oct 3, 2026 | 3.1 s |
| Oct 10, 2026 | 3.1 s |
| Oct 17, 2026 | 3.2 s |
| Oct 24, 2026 | 3.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 149 ms |
| May 16, 2026 | 150 ms |
| May 23, 2026 | 149 ms |
| May 30, 2026 | 150 ms |
| Jun 6, 2026 | 148 ms |
| Jun 13, 2026 | 148 ms |
| Jun 20, 2026 | 148 ms |
| Jun 27, 2026 | 148 ms |
| Jul 4, 2026 | 147 ms |
| Jul 11, 2026 | 146 ms |
| Jul 18, 2026 | 145 ms |
| Jul 25, 2026 | 144 ms |
| Aug 1, 2026 | 144 ms |
| Aug 8, 2026 | 144 ms |
| Aug 15, 2026 | 145 ms |
| Aug 22, 2026 | 146 ms |
| Aug 29, 2026 | 148 ms |
| Sep 5, 2026 | 149 ms |
| Sep 12, 2026 | 149 ms |
| Sep 19, 2026 | 148 ms |
| Sep 26, 2026 | 147 ms |
| Oct 3, 2026 | 145 ms |
| Oct 10, 2026 | 145 ms |
| Oct 17, 2026 | 145 ms |
| Oct 24, 2026 | 144 ms |
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
1.0 s
2.0 s
3.0 s
4.0 s
5.0 s
6.0 s
7.0 s
8.0 s
Speed
Use efficient cache lifetimes
10.0 s · 9.1 MB99 files are served with short cache lifetimes, so returning visitors download them again (9.1 MB).
Render-blocking requests
5.0 s18 files block the first paint until they finish downloading. Deferring or inlining them could save about 5.0 s.
Improve image delivery
1.5 s · 2.8 MB42 images could be 2.8 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.5 s faster on a phone.
Font display
1.6 sWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 1.6 s).
Mobile performance score: 34
34/100Your mobile performance score is 34 (desktop: 63). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Reduce unused JavaScript
980 ms · 424 KiBAbout 424 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 980 ms faster on a phone.
6 third-party services on the page
6 third-party services load with your homepage (Google Tag Manager, Facebook and Hotjar and others), adding 907 KiB and 814 ms of main-thread time.
Reduce unused CSS
780 ms · 100 KiBAbout 100 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 780 ms faster on a phone.
Google Tag Manager adds 405 ms
405 msGoogle Tag Manager costs a phone 405 ms of main-thread work and 468 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Main-thread work: 3.0 s
A phone's processor spends 3.0 s on main-thread work while loading, 1.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Minify CSS
200 ms · 24 KiB24 KiB could be saved by minifying CSS.
11 long tasks on the main thread
11 long tasks block the main thread while loading, the longest for 158 ms. During a long task the page ignores taps.
Document request latency
72 KiBThe HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.
Legacy JavaScript
12 KiBPolyfills for old browsers add 12 KiB JavaScript that modern phones do not need.
Phones get a much slower page than desktops
Desktop scores 63 but mobile only 34. A gap that wide usually means heavy scripts and images that hit phones hardest.
Minify JavaScript
6 KiB6 KiB could be saved by minifying JavaScript.
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: 245 ms
245 msYour server sent the HTML in 245 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Fails Core Web Vitals for real visitors
Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.
Real-user LCP: 4.6 s
4.6 sReal visitors wait 4.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 5.1 s
5.1 sReal visitors see the first content after 5.1 s (75th percentile). Good is under 1.8 s.
Largest Contentful Paint: 15.1 s
15.1 sYour largest element takes 15.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Alternate Text”.
Speed Index: 11.8 s
11.8 sVisually, the page fills in at 11.8 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 15.1 s
15.1 sThe page becomes fully interactive after 15.1 s. Good is under 3.8 s.
First Contentful Paint: 3.9 s
3.9 sThe first text or image appears after 3.9 s on a phone. Good is under 1.8 s.
Real-user TTFB: 1.2 s
1.2 sReal visitors wait 1.2 s for your server to start answering (75th percentile). Good is under 800 ms.
Total Blocking Time: 577 ms
577 msScripts block taps and scrolling for 577 ms in total while the page loads. Good is under 200 ms.
Cumulative Layout Shift: 0.197
0.197The layout shifts by 0.197 while loading, so content jumps under the reader's thumb. Good is under 0.1.
3 images without width and height
3 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
-3%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 149 ms to 144 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Real-user INP: 148 ms
148 msReal visitors wait 148 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.03
0.03For real visitors the layout shifts by 0.03 (75th percentile). Good is under 0.1.
Largest content (LCP) got 43% faster for real visitors
-43%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 5.7 s to 3.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Images and page weight
Page weight: 9.9 MB in 118 requests
9.9 MBYour homepage downloads 9.9 MB in 118 requests on a phone: images 8.4 MB (65), scripts 908 KiB (22) and fonts 402 KiB (5). Under 2 MB keeps phones on slow connections fast.
4 images over 500 KB
4 images weigh 4.2 MB together. On a phone connection a single image that size takes seconds.
11 images in older formats
11 images (5.4 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.
29 images below the first screen load straight away
29 images further down the page (2.9 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
4 images far larger than shown
122 KiB4 images are downloaded at several times the size a phone draws them, for example 7a027f49-6756-47b1-82ed-378557e7787b_profile.webp at 1,036 px wide, shown at 318 px. Resized copies would save about 122 KiB.
About 2.8 g of CO₂ per visit
2.80 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.80 g of CO₂e: 336.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
7 text elements with low contrast
7 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
1 image without alt text
1 image has no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (13 elements)
All page content should be contained by landmarks: 13 elements on the page fail this check, rated moderate by axe-core.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
14 links without text
14 visible links have no text or label, so screen readers cannot say where they go.
ARIA role should be appropriate for the element (4 elements)
ARIA role should be appropriate for the element: 4 elements on the page fail this check, rated minor by axe-core.
Elements marked as presentational should be consistently ignored (4 elements)
Elements marked as presentational should be consistently ignored: 4 elements on the page fail this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h2 → h4, h2 → h5 and h2 → h4), which makes the page harder to scan with a screen reader.
1 checks passed
37 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 45 WCAG 2.2 A/AA and best-practice rules on the phone render: 37 passed and 8 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
124 links crawlers can't follow
124 links have no real href, so search engines can't follow them.
Title is long (66 characters)
Your title is 66 characters, so Google will cut it off around 60: “LeadsGuru: One-Stop-Platform for Top-Notch online courses in India”.
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:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
51 internal links, 14 external
The homepage links to 51 pages on leadsguru.in and 14 external pages.
3 checks passed
One H1 headline
Your main headline reads: “LeadsGuru Memberships”.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at https://www.leadsguru.in/sitemap.xml.
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://www.leadsguru.in/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
Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.
Text is in the HTML
Your server sends the page's text in the HTML (966 words), so crawlers that don't run JavaScript still read it.
Other pages
2 pages without a title
https://www.leadsguru.in/bundle/diamond-package and https://www.leadsguru.in/bundle/leadsguru-startup-package have no <title>, so Google invents the link text in results.
6 pages share a title
/, https://www.leadsguru.in/faq.aspx, https://www.leadsguru.in/privacy-policy.aspx, https://www.leadsguru.in/term-condition.aspx, https://www.leadsguru.in/cookie-policy.aspx and https://www.leadsguru.in/disclaimer.aspx all use the title “LeadsGuru: One-Stop-Platform for Top-Notch online courses in India”. Search engines can't tell which page to show for a search, so each competes with the others.
8 pages without a meta description
https://www.leadsguru.in/bundle/diamond-package, https://www.leadsguru.in/bundle/leadsguru-startup-package, https://www.leadsguru.in/kickstart-workshops.aspx, https://www.leadsguru.in/faq.aspx, https://www.leadsguru.in/privacy-policy.aspx and https://www.leadsguru.in/term-condition.aspx and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.
1 page without an H1
https://www.leadsguru.in/kickstart-workshops.aspx has no <h1> headline, so visitors and search engines get no clear main topic.
1 page with very little text
https://www.leadsguru.in/kickstart-workshops.aspx has 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.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 20 found) and read each the way a search engine does.
3 checks passed
Linked pages load
All 15 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.
Best practices
56 distorted images
56 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
7 small tap targets
7 of 23 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
2 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
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,194 words of copy
The homepage carries about 1,194 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: “Login / Signup”.
4 calls to action
The homepage has 4 calls to action, for example “Login / Signup”, “Subscribe Today” and “Contact”.
1 short form
A short form (0 fields at most) is right on the homepage.
Social proof on the page
Social proof on the homepage: 2 testimonial or review blocks and “140k+ Students”.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics, Meta Pixel, Microsoft Clarity and Hotjar.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Analytics, Google Tag Manager, Hotjar, Meta Pixel and Microsoft Clarity (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.
10 cookies set on arrival
10Opening the homepage sets 10 cookies (measured from a US location before any click).
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.
13 other companies contacted
Loading the homepage contacts 13 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
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 leadsguru.in, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- jQuery
- Analytics
- Google Analytics | Google Tag Manager | Hotjar | Microsoft Clarity
- Hosting
- NxtGen Datacenter & Cloud Technologies Pvt. Ltd.
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 49 issues on leadsguru.in, including 21 speed issues, 6 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.