Website review, no card needed
stayvista.com website review
Visit site (opens in a new tab)Reviewed 25 October 202640 issues · 90 checks
This review found 40 issues worth fixing on stayvista.com, 16 of them high impact, across 90 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
73CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 3.1 s |
| May 9, 2026 | 3.1 s |
| May 16, 2026 | 3.1 s |
| May 23, 2026 | 3.1 s |
| May 30, 2026 | 3.2 s |
| Jun 6, 2026 | 3.3 s |
| Jun 13, 2026 | 3.3 s |
| Jun 20, 2026 | 3.3 s |
| Jun 27, 2026 | 3.3 s |
| Jul 4, 2026 | 3.3 s |
| Jul 11, 2026 | 3.3 s |
| Jul 18, 2026 | 3.3 s |
| Jul 25, 2026 | 3.2 s |
| Aug 1, 2026 | 3.1 s |
| Aug 8, 2026 | 3.0 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 | 2.8 s |
| Sep 26, 2026 | 2.7 s |
| Oct 3, 2026 | 2.7 s |
| Oct 10, 2026 | 2.7 s |
| Oct 17, 2026 | 2.7 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 270 ms |
| May 9, 2026 | 269 ms |
| May 16, 2026 | 268 ms |
| May 23, 2026 | 269 ms |
| May 30, 2026 | 270 ms |
| Jun 6, 2026 | 271 ms |
| Jun 13, 2026 | 271 ms |
| Jun 20, 2026 | 270 ms |
| Jun 27, 2026 | 269 ms |
| Jul 4, 2026 | 267 ms |
| Jul 11, 2026 | 264 ms |
| Jul 18, 2026 | 262 ms |
| Jul 25, 2026 | 260 ms |
| Aug 1, 2026 | 259 ms |
| Aug 8, 2026 | 260 ms |
| Aug 15, 2026 | 260 ms |
| Aug 22, 2026 | 261 ms |
| Aug 29, 2026 | 262 ms |
| Sep 5, 2026 | 261 ms |
| Sep 12, 2026 | 260 ms |
| Sep 19, 2026 | 260 ms |
| Sep 26, 2026 | 259 ms |
| Oct 3, 2026 | 261 ms |
| Oct 10, 2026 | 264 ms |
| Oct 17, 2026 | 269 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.4 s
2.7 s
4.1 s
5.4 s
6.8 s
8.1 s
9.5 s
10.9 s
Speed
Improve image delivery
19.9 s · 6.3 MB64 images could be 6.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 19.9 s faster on a phone.
Use efficient cache lifetimes
2.1 s · 5.0 MB170 files are served with short cache lifetimes, so returning visitors download them again (5.0 MB).
Render-blocking requests
1.6 s5 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.6 s.
Mobile performance score: 39
39/100Your mobile performance score is 39 (desktop: 37). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 7.3 s
A phone's processor spends 7.3 s on main-thread work while loading, 3.5 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, Facebook and Clarity and others), adding 44.5 MB and 1.3 s of main-thread time.
vistarooms.com adds 0 ms
0 msvistarooms.com costs a phone 0 ms of main-thread work and 43.4 MB 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.
Google Tag Manager adds 899 ms
899 msGoogle Tag Manager costs a phone 899 ms of main-thread work and 724 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
150 ms · 758 KiBAbout 758 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.
Reduce unused CSS
460 ms · 83 KiBAbout 83 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 460 ms faster on a phone.
19 long tasks on the main thread
19 long tasks block the main thread while loading, the longest for 329 ms. During a long task the page ignores taps.
2,979 HTML elements
The page has 2,979 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Legacy JavaScript
26 KiBPolyfills for old browsers add 26 KiB JavaScript that modern phones do not need.
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: 467 ms
467 msYour server sent the HTML in 467 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.
Largest Contentful Paint: 32.6 s
32.6 sYour largest element takes 32.6 s to render on a phone. Google's threshold for “good” is 2.5 s.
Speed Index: 21.7 s
21.7 sVisually, the page fills in at 21.7 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 82.5 s
82.5 sThe page becomes fully interactive after 82.5 s. Good is under 3.8 s.
Total Blocking Time: 1.3 s
1.3 sScripts block taps and scrolling for 1.3 s in total while the page loads. Good is under 200 ms.
Real-user INP: 310 ms
310 msReal visitors wait 310 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.12
0.12For real visitors the layout shifts by 0.12 (75th percentile). Good is under 0.1.
First Contentful Paint: 1.8 s
1.8 sThe first text or image appears after 1.8 s on a phone. Good is under 1.8 s.
Tap response (INP) held steady for real visitors
-1%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 270 ms to 269 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 checks passed
Real-user LCP: 1.7 s
1.7 sReal visitors wait 1.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 1.2 s
1.2 sReal visitors see the first content after 1.2 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 469 ms
469 msReal visitors wait 469 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 13% faster for real visitors
-13%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 3.1 s to 2.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0.004
0.004The layout barely moves while loading (CLS 0.004, good is under 0.1).
Images and page weight
Page weight: 54.5 MB in 373 requests
54.5 MBYour homepage downloads 54.5 MB in 373 requests on a phone: media 33.1 MB (12), images 10.8 MB (174) and other files 6.9 MB (45). Under 2 MB keeps phones on slow connections fast.
7 images far larger than shown
4.8 MB7 images are downloaded at several times the size a phone draws them, for example pet-friendly-villas-1785318753.JPG at 6,016 px wide, shown at 190 px. Resized copies would save about 4.8 MB.
1 image over 500 KB
pet-friendly-villas-1785318753.JPG weighs 4.0 MB. On a phone connection a single image that size takes seconds.
25 images below the first screen load straight away
25 images further down the page (6.0 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
An image on the first screen is lazy-loaded
image is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).
18 images in older formats
18 images (998 KiB) 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 15.4 g of CO₂ per visit
15.44 gBy the Sustainable Web Design model, a visit to your homepage emits about 15.44 g of CO₂e: 1852.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
ARIA dialog and alertdialog nodes should have an accessible name (2 elements)
ARIA dialog and alertdialog nodes should have an accessible name: 2 elements on the page fail this check, rated serious by axe-core.
ARIA input fields must have an accessible name (2 elements)
ARIA input fields must have an accessible name: 2 elements on the page fail this check, rated serious by axe-core.
Scrollable region must have keyboard access (2 elements)
Scrollable region must have keyboard access: 2 elements on the page fail this check, rated serious by axe-core.
All page content should be contained by landmarks (12 elements)
All page content should be contained by landmarks: 12 elements on the page fail this check, rated moderate by axe-core.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
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.
2 form fields without a label
2 form fields have no label, so screen readers announce an empty box and autofill guesses.
2 checks passed
Every image has alt text
All 119 images in the HTML carry an alt attribute.
41 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 48 WCAG 2.2 A/AA and best-practice rules on the phone render: 41 passed and 7 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.
34 internal links, 5 external
The homepage links to 34 pages on stayvista.com and 5 external pages.
8 checks passed
Meta description: 141 characters
Your meta description is 141 characters: “Your search for a luxury villa, holiday home or homestay on rent is now over. Explore StayVista which manages 1200+ Hom…”.
One H1 headline
Your main headline reads: “Luxury Villas & Vacation Homes for Rent in India”.
Title: 47 characters
Your title is a healthy 47 characters: “StayVista: Top Luxury Villas & Vacation Rentals”.
Canonical URL set
The canonical URL is https://www.stayvista.com/.
Structured data in place
Structured data found: BreadcrumbList, LodgingBusiness, Organization and WebSite.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
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.stayvista.com/sitemap.xml.
AI search readiness
Parts of the site are closed to 2 AI crawlers
Your robots.txt lets ChatGPT search (OAI-SearchBot) and Perplexity (PerplexityBot) read the homepage but closes other sections to them, so answers about those pages can't cite you.
3 checks passed
Organization data: 5 of 6 facts
Your Organization JSON-LD gives name, url, sameAs (social profiles), description and contact details; logo would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (963 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.stayvista.com/llms.txt (9 KiB, 40 links), a plain-text guide to the site for AI tools.
Other pages
15 pages share a title
https://www.stayvista.com/collections/newly-launched-villas, https://www.stayvista.com/collections/pay-for-2-stay-for-3, https://www.stayvista.com/collections/pet-friendly-villas, https://www.stayvista.com/collections/workation-long-stays, https://www.stayvista.com/collections/private-pool-villas and https://www.stayvista.com/collections/romantic-villas and 9 others all use the title “Book Holiday Homes, Homestay & Luxury Villas on Rent | StayVista”. Search engines can't tell which page to show for a search, so each competes with the others.
15 pages share a meta description
https://www.stayvista.com/collections/newly-launched-villas, https://www.stayvista.com/collections/pay-for-2-stay-for-3, https://www.stayvista.com/collections/pet-friendly-villas, https://www.stayvista.com/collections/workation-long-stays, https://www.stayvista.com/collections/private-pool-villas and https://www.stayvista.com/collections/romantic-villas and 9 others use the same meta description. A description written for each page earns more clicks.
15 pages with very little text
https://www.stayvista.com/collections/newly-launched-villas, https://www.stayvista.com/collections/pay-for-2-stay-for-3, https://www.stayvista.com/collections/pet-friendly-villas, https://www.stayvista.com/collections/workation-long-stays, https://www.stayvista.com/collections/private-pool-villas and https://www.stayvista.com/collections/romantic-villas and 9 others 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.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 34 found) and read each the way a search engine does.
6 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.
Every page has a meta description
All 15 pages that loaded have a meta description.
Every page has an H1
Each page we checked has a main headline.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Minified React error #418; visit https://reactjs.org/docs/error-decoder.html?invariant=418 for the full message or use …”.
Missing source maps
Large scripts ship without source maps.
2 checks passed
Tap targets are thumb-sized
28 of 28 tappable elements near the top are at least 24 px.
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 opening hours
The homepage shows no opening hours. If customers visit or call, show when.
Phone number is not tap-to-call
Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
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 827 words of copy
The homepage carries about 827 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: “Download the StayVista app” and “Call Us”.
1 call to action
The homepage has 1 call to action, for example “Download Now”.
Social proof on the page
Social proof on the homepage: a star rating and 3 trust badges.
Phone number on the homepage
Your phone number is on the homepage.
LocalBusiness structured data
Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.
Privacy and tracking
7 trackers load before any consent
7Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, LinkedIn Insight and Meta Pixel and 2 mores (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.
7 cookies set on arrival
7Opening the homepage sets 7 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.
17 other companies contacted
Loading the homepage contacts 17 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 stayvista.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- Next.js
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 40 issues on stayvista.com, including 20 speed 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.