Website review, no card needed
vestedfinance.com website review
Visit site (opens in a new tab)Reviewed 23 October 202631 issues · 88 checks
This review found 31 issues worth fixing on vestedfinance.com, 5 of them high impact, across 88 checks. The most urgent: fails Core Web Vitals for real visitors. 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
91AClosest competitors among SaaS websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 974 ms |
| May 9, 2026 | 955 ms |
| May 16, 2026 | 980 ms |
| May 23, 2026 | 1.0 s |
| May 30, 2026 | 1.1 s |
| Jun 6, 2026 | 2.3 s |
| Jun 13, 2026 | 4.5 s |
| Jun 20, 2026 | 4.8 s |
| Jun 27, 2026 | 5.2 s |
| Jul 4, 2026 | 4.5 s |
| Jul 11, 2026 | 2.4 s |
| Jul 18, 2026 | 1.8 s |
| Jul 25, 2026 | 2.1 s |
| Aug 1, 2026 | 2.8 s |
| Aug 8, 2026 | 3.2 s |
| Aug 15, 2026 | 3.3 s |
| Aug 22, 2026 | 3.4 s |
| Aug 29, 2026 | 3.5 s |
| Sep 5, 2026 | 4.3 s |
| Sep 12, 2026 | 6.8 s |
| Sep 19, 2026 | 7.0 s |
| Sep 26, 2026 | 6.9 s |
| Oct 3, 2026 | 6.8 s |
| Oct 10, 2026 | 5.8 s |
| Oct 17, 2026 | 5.7 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 112 ms |
| May 9, 2026 | 111 ms |
| May 16, 2026 | 109 ms |
| May 23, 2026 | 107 ms |
| May 30, 2026 | 107 ms |
| Jun 6, 2026 | 112 ms |
| Jun 13, 2026 | 118 ms |
| Jun 20, 2026 | 121 ms |
| Jun 27, 2026 | 127 ms |
| Jul 4, 2026 | 125 ms |
| Jul 11, 2026 | 122 ms |
| Jul 18, 2026 | 122 ms |
| Jul 25, 2026 | 121 ms |
| Aug 1, 2026 | 120 ms |
| Aug 8, 2026 | 123 ms |
| Aug 15, 2026 | 125 ms |
| Aug 22, 2026 | 129 ms |
| Aug 29, 2026 | 137 ms |
| Sep 5, 2026 | 140 ms |
| Sep 12, 2026 | 156 ms |
| Sep 19, 2026 | 149 ms |
| Sep 26, 2026 | 145 ms |
| Oct 3, 2026 | 144 ms |
| Oct 10, 2026 | 135 ms |
| Oct 17, 2026 | 141 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
0.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Main-thread work: 6.0 s
A phone's processor spends 6.0 s on main-thread work while loading, 2.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, reddit and Cloudflare CDN and others), adding 947 KiB and 1.1 s of main-thread time.
Mobile performance score: 86
86/100Your mobile performance score is 86 (desktop: 99). Pages that score under 90 lose visitors before the first paint.
Google Tag Manager adds 591 ms
591 msGoogle Tag Manager costs a phone 591 ms of main-thread work and 517 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.
reddit adds 392 ms
392 msreddit costs a phone 392 ms of main-thread work and 27 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.
Reduce unused JavaScript
258 KiBAbout 258 KiB of JavaScript is downloaded but never used on this page.
1,628 HTML elements
The page has 1,628 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Reduce unused CSS
270 ms · 34 KiBAbout 34 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 270 ms faster on a phone.
9 long tasks on the main thread
9 long tasks block the main thread while loading, the longest for 225 ms. During a long task the page ignores taps.
Improve image delivery
77 KiB2 images could be 77 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Use efficient cache lifetimes
33 KiB7 files are served with short cache lifetimes, so returning visitors download them again (33 KiB).
Legacy JavaScript
19 KiBPolyfills for old browsers add 19 KiB JavaScript that modern phones do not need.
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.
Minify JavaScript
4 KiB4 KiB could be saved by minifying JavaScript.
1 checks passed
Server response: 188 ms
188 msYour server sent the HTML in 188 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.
Time to Interactive: 11.8 s
11.8 sThe page becomes fully interactive after 11.8 s. Good is under 3.8 s.
Tap response (INP) got 24% slower for real visitors
+24%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 112 ms to 141 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 497% slower for real visitors
+497%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 1.0 s to 5.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user TTFB: 820 ms
820 msReal visitors wait 820 ms for your server to start answering (75th percentile). Good is under 800 ms.
Total Blocking Time: 444 ms
444 msScripts block taps and scrolling for 444 ms in total while the page loads. Good is under 200 ms.
Speed Index: 3.9 s
3.9 sVisually, the page fills in at 3.9 s (Speed Index). Good is under 3.4 s.
7 checks passed
Real-user LCP: 1.4 s
1.4 sReal visitors wait 1.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 109 ms
109 msReal visitors wait 109 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.09
0.09For real visitors the layout shifts by 0.09 (75th percentile). Good is under 0.1.
Real-user FCP: 1.4 s
1.4 sReal visitors see the first content after 1.4 s (75th percentile). Good is under 1.8 s.
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.055
0.055The layout barely moves while loading (CLS 0.055, good is under 0.1).
Largest Contentful Paint: 1.6 s
1.6 sYour largest element renders in 1.6 s on a phone, inside Google's 2.5 s “good” threshold.
Images and page weight
1 image far larger than shown
9 KiB1 image is downloaded at several times the size a phone draws it, for example easy-access-new-lite.png at 1,156 px wide, shown at 360 px. Resized copies would save about 9 KiB.
About 0.4 g of CO₂ per visit
0.39 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.39 g of CO₂e: 46.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Page weight: 1.4 MB in 109 requests
1.4 MBYour homepage downloads 1.4 MB in 109 requests on a phone: scripts 766 KiB (30), fonts 249 KiB (6) and images 134 KiB (6). That is a lean page.
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Accessibility
24 tap targets too small
24 tap targets are too small or too close together to hit reliably with a finger.
16 text elements with low contrast
16 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
Orphan list items
Some list items are not inside a list.
2 form fields without a label
2 form fields have no label, so screen readers announce an empty box and autofill guesses.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
Headings should not be empty (1 element)
Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.
Alternative text of images should not be repeated as text (1 element)
Alternative text of images should not be repeated as text: 1 element on the page fails this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h2 → h4 and h2 → h4), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 64 images in the HTML carry an alt attribute.
46 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 52 WCAG 2.2 A/AA and best-practice rules on the phone render: 46 passed and 6 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Meta description is long (217 characters)
Your meta description is 217 characters; Google truncates after about 160, so the end of your pitch is cut.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
1 link with vague text
1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.
274 internal links, 25 external
The homepage links to 274 pages on vestedfinance.com and 25 external pages.
6 checks passed
One H1 headline
Your main headline reads: “Investing in US stocks for NRIs”.
Title: 49 characters
Your title is a healthy 49 characters: “Investing in US Stocks and ETFs for NRIs | Vested”.
Canonical URL set
The canonical URL is https://vestedfinance.com/.
Structured data in place
Structured data found: BreadcrumbList, FAQPage, Organization, WebPage and WebSite.
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://vestedfinance.com/post-sitemap.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
3 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 (3,329 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://vestedfinance.com/llms.txt (17 KiB, 69 links), a plain-text guide to the site for AI tools.
Other pages
3 linked pages hidden from search
https://vestedfinance.com/india-equity-opportunities-fund, https://vestedfinance.com/raw/india-equity-opportunities-fund and https://vestedfinance.com/legal/etf-disclosure are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.
5 pages without a meta description
https://vestedfinance.com/in/globed, https://vestedfinance.com/become-a-partner, https://vestedfinance.com/blog/all, https://vestedfinance.com/india-equity-opportunities-fund and https://vestedfinance.com/raw/india-equity-opportunities-fund have no meta description, so Google writes the search snippet from whatever text it finds.
2 pages without an H1
https://vestedfinance.com/india-equity-opportunities-fund and https://vestedfinance.com/raw/india-equity-opportunities-fund have no <h1> headline, so visitors and search engines get no clear main topic.
1 page slow to respond
https://vestedfinance.com/blog/all took over 3 s to send its HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 197 found) and read each the way a search engine does.
4 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.
Titles are unique
Every page we checked has its own title.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
19 of 22 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Local business without LocalBusiness data
Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
About 2,163 words of copy
The homepage carries about 2,163 words of visible text.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
8 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Pricing” and “Sign up”.
12 calls to action
The homepage has 12 calls to action, for example “Pricing”, “Sign up” and “India Pricing”.
2 short forms
2 short forms (6 fields at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 9 testimonial or review blocks and 9 trust badges.
Analytics in place
Analytics detected: Google Tag Manager and Google Analytics.
Direct contact links
Visitors can reach you directly: 1 phone link and 3 email links.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Risk reducer mentioned
A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.
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.
4 other companies contacted
Loading the homepage contacts 4 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 vestedfinance.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- WordPress
- Framework
- jQuery
- Analytics
- Google Analytics | Google Tag Manager
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 31 issues on vestedfinance.com, including 14 speed issues, 3 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.