Website review, no card needed
oasisindia.in website review
Visit site (opens in a new tab)Reviewed 26 October 202642 issues · 86 checks
This review found 42 issues worth fixing on oasisindia.in, 10 of them high impact, across 86 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
83BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 5.5 s |
| May 16, 2026 | 5.4 s |
| May 23, 2026 | 5.3 s |
| May 30, 2026 | 5.2 s |
| Jun 6, 2026 | 5.3 s |
| Jun 13, 2026 | 5.4 s |
| Jun 20, 2026 | 5.4 s |
| Jun 27, 2026 | 5.3 s |
| Jul 4, 2026 | 5.0 s |
| Jul 11, 2026 | 4.9 s |
| Jul 18, 2026 | 5.1 s |
| Jul 25, 2026 | 5.1 s |
| Aug 1, 2026 | 5.0 s |
| Aug 8, 2026 | 4.7 s |
| Aug 15, 2026 | 3.6 s |
| Aug 22, 2026 | 3.5 s |
| Aug 29, 2026 | 3.5 s |
| Sep 5, 2026 | 3.4 s |
| Sep 12, 2026 | 3.3 s |
| Sep 19, 2026 | 3.0 s |
| Sep 26, 2026 | 2.8 s |
| Oct 3, 2026 | 2.8 s |
| Oct 10, 2026 | 2.7 s |
| Oct 17, 2026 | 2.7 s |
| Oct 24, 2026 | 2.7 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 177 ms |
| May 16, 2026 | 178 ms |
| May 23, 2026 | 179 ms |
| May 30, 2026 | 181 ms |
| Jun 6, 2026 | 181 ms |
| Jun 13, 2026 | 180 ms |
| Jun 20, 2026 | 179 ms |
| Jun 27, 2026 | 178 ms |
| Jul 4, 2026 | 178 ms |
| Jul 11, 2026 | 180 ms |
| Jul 18, 2026 | 186 ms |
| Jul 25, 2026 | 185 ms |
| Aug 1, 2026 | 181 ms |
| Aug 8, 2026 | 175 ms |
| Aug 15, 2026 | 161 ms |
| Aug 22, 2026 | 159 ms |
| Aug 29, 2026 | 159 ms |
| Sep 5, 2026 | 162 ms |
| Sep 12, 2026 | 161 ms |
| Sep 19, 2026 | 160 ms |
| Sep 26, 2026 | 160 ms |
| Oct 3, 2026 | 157 ms |
| Oct 10, 2026 | 156 ms |
| Oct 17, 2026 | 153 ms |
| Oct 24, 2026 | 145 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
Speed
Improve image delivery
3.1 MB14 images could be 3.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Use efficient cache lifetimes
2.6 MB18 files are served with short cache lifetimes, so returning visitors download them again (2.6 MB).
Mobile performance score: 68
68/100Your mobile performance score is 68 (desktop: 56). Pages that score under 90 lose visitors before the first paint.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Facebook and WebEngage and others), adding 975 KiB and 891 ms of main-thread time.
Document request latency
950 msThe HTML itself could arrive about 950 ms sooner: redirects, a slow server response or missing compression delay everything after it.
Reduce initial server response time
940 msReduce initial server response time. Google estimates savings of 940 ms on a phone.
Google Tag Manager adds 545 ms
545 msGoogle Tag Manager costs a phone 545 ms of main-thread work and 521 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
335 KiBAbout 335 KiB of JavaScript is downloaded but never used on this page.
Main-thread work: 2.6 s
A phone's processor spends 2.6 s on main-thread work while loading, 1.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Server response: 1.0 s
1.0 sYour server takes 1.0 s to send the HTML. Google recommends under 600 ms; everything else waits for it.
11 long tasks on the main thread
11 long tasks block the main thread while loading, the longest for 244 ms. During a long task the page ignores taps.
Reduce unused CSS
150 ms · 70 KiBAbout 70 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.
Render-blocking requests
200 ms6 files block the first paint until they finish downloading. Deferring or inlining them could save about 200 ms.
Legacy JavaScript
48 KiBPolyfills for old browsers add 48 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
5 KiB5 KiB could be saved by minifying JavaScript.
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: 14.5 s
14.5 sThe page becomes fully interactive after 14.5 s. Good is under 3.8 s.
Speed Index: 8.7 s
8.7 sVisually, the page fills in at 8.7 s (Speed Index). Good is under 3.4 s.
Real-user TTFB: 1.1 s
1.1 sReal visitors wait 1.1 s for your server to start answering (75th percentile). Good is under 800 ms.
Total Blocking Time: 517 ms
517 msScripts block taps and scrolling for 517 ms in total while the page loads. Good is under 200 ms.
Largest Contentful Paint: 3.5 s
3.5 sYour largest element takes 3.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Slide 1”.
First Contentful Paint: 2.0 s
2.0 sThe first text or image appears after 2.0 s on a phone. Good is under 1.8 s.
6 images without width and height
6 images have no width and height attributes, so the layout jumps as each one loads.
7 checks passed
Real-user LCP: 1.9 s
1.9 sReal visitors wait 1.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 166 ms
166 msReal visitors wait 166 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.8 s
1.8 sReal visitors see the first content after 1.8 s (75th percentile). Good is under 1.8 s.
Tap response (INP) got 16% faster for real visitors
-16%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 177 ms to 145 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 50% faster for real visitors
-50%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 5.5 s to 2.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 5.1 MB in 129 requests
5.1 MBYour homepage downloads 5.1 MB in 129 requests on a phone: images 3.6 MB (41), scripts 1.2 MB (52) and fonts 121 KiB (3). Under 2 MB keeps phones on slow connections fast.
1 image over 500 KB
Understanding-the-Safe-Period-A-Guide-to-Natural-Family-Plan weighs 994 KiB. On a phone connection a single image that size takes seconds.
6 images far larger than shown
1.1 MB6 images are downloaded at several times the size a phone draws them, for example Understanding-the-Safe-Period-A-Guide-to-Natural-Family-Plan at 1,200 px wide, shown at 292 px. Resized copies would save about 1.1 MB.
6 images in older formats
6 images (2.3 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.
6 images below the first screen load straight away
6 images further down the page (2.3 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).
About 1.5 g of CO₂ per visit
1.46 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.46 g of CO₂e: 175.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
Hidden but focusable
31 elements hidden from screen readers can still receive keyboard focus.
22 text elements with low contrast
22 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Main landmark should not be contained in another landmark (1 element)
Main landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.
Document should not have more than one main landmark (1 element)
Document should not have more than one main landmark: 1 element on the page fails 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.
Headings skip levels
Headings skip levels (h1 → h4), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 25 images in the HTML carry an alt attribute.
45 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 51 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 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
Title is long (83 characters)
Your title is 83 characters, so Google will cut it off around 60: “Best IVF Centre in India: Fertility & IVF Clinic/Hospital Near Me | Oasis Fertility”.
Meta description is long (329 characters)
Your meta description is 329 characters; Google truncates after about 160, so the end of your pitch is cut.
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 X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
87 internal links, 3 external
The homepage links to 87 pages on oasisindia.in and 3 external pages.
5 checks passed
One H1 headline
Your main headline reads: “Welcome to Oasis Fertility”.
Canonical URL set
The canonical URL is https://oasisindia.in/.
Structured data in place
Structured data found: FAQPage.
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://oasisindia.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.
Some text only appears after JavaScript runs
33%The HTML your server sends has 369 of the 1,131 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.
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.
llms.txt published
The site publishes https://oasisindia.in/llms.txt (26 KiB, 2 links), a plain-text guide to the site for AI tools.
Other pages
3 pages point its canonical at the homepage
https://oasisindia.in/blog, https://oasisindia.in/international-patients/treatment-process and https://oasisindia.in/international-patients/financial-planning declare the homepage as their canonical URL, which tells Google they are copies of the homepage and keeps them out of search results. A site-wide template setting usually causes this.
3 pages share a title
/, https://oasisindia.in/international-patients/treatment-process and https://oasisindia.in/international-patients/financial-planning all use the title “Best IVF Centre in India: Fertility & IVF Clinic/Hospital Near Me | O…”. Search engines can't tell which page to show for a search, so each competes with the others.
2 pages share a meta description
https://oasisindia.in/international-patients/treatment-process and https://oasisindia.in/international-patients/financial-planning use the same meta description. A description written for each page earns more clicks.
1 page without an H1
https://oasisindia.in/blog has no <h1> headline, so visitors and search engines get no clear main topic.
4 pages slow to respond
https://oasisindia.in/fertility-treatments/laparoscopy, https://oasisindia.in/fertility-treatments/hysteroscopy, https://oasisindia.in/advanced-fertility-treatments/laser-assisted-hatching-lah and https://oasisindia.in/advanced-fertility-treatments/microfluidic-sperm-sorting took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 75 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.
Every page has a meta description
All 15 pages that loaded have a meta description.
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
8 small tap targets
8 of 25 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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,131 words of copy
The homepage carries about 1,131 words of visible text.
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Book Now” and “Call Now”.
4 calls to action
The homepage has 4 calls to action, for example “Where do I start?”, “Book consultationFREE” and “Book Now”.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics, Meta Pixel and Cloudflare Web Analytics.
Direct contact links
Visitors can reach you directly: 2 phone links and 0 email links.
Privacy and tracking
6 trackers load before any consent
6Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, LinkedIn Insight and Meta Pixel and 1 more (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.
9 cookies set on arrival
9Opening the homepage sets 9 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.
31 other companies contacted
Loading the homepage contacts 31 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 oasisindia.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
- Next.js
- 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 42 issues on oasisindia.in, including 18 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.