Website review, no card needed

olivaclinic.com logo

olivaclinic.com website review

Visit site (opens in a new tab)Reviewed 28 October 202640 issues · 88 checks

This review found 40 issues worth fixing on olivaclinic.com, 12 of them high impact, across 88 checks. The most urgent: use efficient cache lifetimes. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
5.5 s3.6 sMay 9Oct 243.8 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20265.0 s
May 16, 20265.1 s
May 23, 20265.2 s
May 30, 20265.3 s
Jun 6, 20265.2 s
Jun 13, 20265.0 s
Jun 20, 20264.6 s
Jun 27, 20264.3 s
Jul 4, 20264.1 s
Jul 11, 20264.0 s
Jul 18, 20263.9 s
Jul 25, 20263.9 s
Aug 1, 20263.9 s
Aug 8, 20263.9 s
Aug 15, 20264.0 s
Aug 22, 20264.0 s
Aug 29, 20264.0 s
Sep 5, 20264.0 s
Sep 12, 20264.1 s
Sep 19, 20264.0 s
Sep 26, 20264.1 s
Oct 3, 20264.1 s
Oct 10, 20264.2 s
Oct 17, 20264.2 s
Oct 24, 20263.8 s
Real-visitor tap response (INP)75th percentile, phones
265 ms163 msMay 9Oct 24253 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026176 ms
May 16, 2026176 ms
May 23, 2026176 ms
May 30, 2026175 ms
Jun 6, 2026175 ms
Jun 13, 2026177 ms
Jun 20, 2026179 ms
Jun 27, 2026186 ms
Jul 4, 2026192 ms
Jul 11, 2026196 ms
Jul 18, 2026202 ms
Jul 25, 2026203 ms
Aug 1, 2026202 ms
Aug 8, 2026204 ms
Aug 15, 2026200 ms
Aug 22, 2026204 ms
Aug 29, 2026208 ms
Sep 5, 2026210 ms
Sep 12, 2026213 ms
Sep 19, 2026214 ms
Sep 26, 2026216 ms
Oct 3, 2026217 ms
Oct 10, 2026221 ms
Oct 17, 2026245 ms
Oct 24, 2026253 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

Full-page screenshot of olivaclinic.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. olivaclinic.com at 0.4 s0.4 s
  2. olivaclinic.com at 0.8 s0.8 s
  3. olivaclinic.com at 1.2 s1.2 s
  4. olivaclinic.com at 1.7 s1.7 s
  5. olivaclinic.com at 2.1 s2.1 s
  6. olivaclinic.com at 2.5 s2.5 s
  7. olivaclinic.com at 2.9 s2.9 s
  8. olivaclinic.com at 3.3 s3.3 s

Speed

13 to fix54
  • Use efficient cache lifetimes

    12.7 s · 3.0 MB

    34 files are served with short cache lifetimes, so returning visitors download them again (3.0 MB).

  • Reduce unused JavaScript

    2.5 s · 611 KiB

    About 611 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.5 s faster on a phone.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Facebook and Google CDN and others), adding 1.0 MB and 945 ms of main-thread time.

  • Mobile performance score: 54

    54/100

    Your mobile performance score is 54 (desktop: 51). Pages that score under 90 lose visitors before the first paint.

  • Document request latency

    550 ms

    The HTML itself could arrive about 550 ms sooner: redirects, a slow server response or missing compression delay everything after it.

  • Reduce initial server response time

    530 ms

    Reduce initial server response time. Google estimates savings of 530 ms on a phone.

  • Google Tag Manager adds 431 ms

    431 ms

    Google Tag Manager costs a phone 431 ms of main-thread work and 346 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.

  • Improve image delivery

    100 ms · 316 KiB

    2 images could be 316 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 100 ms faster on a phone.

  • 8 long tasks on the main thread

    8 long tasks block the main thread while loading, the longest for 261 ms. During a long task the page ignores taps.

  • 2,134 HTML elements

    The page has 2,134 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • Main-thread work: 2.1 s

    A phone's processor spends 2.1 s on main-thread work while loading, 1.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • Google CDN adds 148 ms

    148 ms

    Google CDN costs a phone 148 ms of main-thread work and 348 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.

  • Server response: 630 ms

    630 ms

    Your server takes 630 ms to send the HTML. Google recommends under 600 ms; everything else waits for it.

  • Reduce unused CSS

    28 KiB

    About 28 KiB of CSS is downloaded but never applied on this page.

  • Legacy JavaScript

    12 KiB

    Polyfills for old browsers add 12 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.

Core Web Vitals

9 to fix67
  • 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 TTFB: 1.9 s

    1.9 s

    Real visitors wait 1.9 s for your server to start answering (75th percentile). Good is under 800 ms.

  • Largest Contentful Paint: 21.6 s

    21.6 s

    Your largest element takes 21.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “uncompromised”.

  • Time to Interactive: 21.6 s

    21.6 s

    The page becomes fully interactive after 21.6 s. Good is under 3.8 s.

  • Total Blocking Time: 678 ms

    678 ms

    Scripts block taps and scrolling for 678 ms in total while the page loads. Good is under 200 ms.

  • Real-user LCP: 3.6 s

    3.6 s

    Real visitors wait 3.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Tap response (INP) got 41% slower for real visitors

    +41%

    Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 176 ms to 253 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Real-user FCP: 2.8 s

    2.8 s

    Real visitors see the first content after 2.8 s (75th percentile). Good is under 1.8 s.

  • Speed Index: 5.1 s

    5.1 s

    Visually, the page fills in at 5.1 s (Speed Index). Good is under 3.4 s.

5 checks passed
  • Real-user INP: 188 ms

    188 ms

    Real visitors wait 188 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.01

    0.01

    For real visitors the layout shifts by 0.01 (75th percentile). Good is under 0.1.

  • Largest content (LCP) got 21% faster for real visitors

    -21%

    Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 5.0 s to 3.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • First Contentful Paint: 1.4 s

    1.4 s

    The first text or image appears after 1.4 s, inside the 1.8 s “good” threshold.

  • Cumulative Layout Shift: 0.002

    0.002

    The layout barely moves while loading (CLS 0.002, good is under 0.1).

Images and page weight

2 to fix60
  • Page weight: 4.0 MB in 54 requests

    4.0 MB

    Your homepage downloads 4.0 MB in 54 requests on a phone: images 2.6 MB (20), scripts 1.2 MB (20) and fonts 114 KiB (5). Under 2 MB keeps phones on slow connections fast.

  • 9 images in older formats

    9 images (2.6 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 1.1 g of CO₂ per visit

    1.14 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.14 g of CO₂e: 137.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

2 checks passed
  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

10 to fixGoogle 8388
  • Unlabelled dropdowns

    5 dropdowns have no label.

  • 13 text elements with low contrast

    13 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • 5 images without alt text

    5 images have no alt text, which hurts accessibility and image search.

  • All page content should be contained by landmarks (73 elements)

    All page content should be contained by landmarks: 73 elements on the page fail this check, rated moderate by axe-core.

  • 86 links without text

    86 visible links have no text or label, so screen readers cannot say where they go.

  • 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.

  • Alternative text of images should not be repeated as text (24 elements)

    Alternative text of images should not be repeated as text: 24 elements on the page fail this check, rated minor by axe-core.

  • 10 form fields without a label

    10 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • Headings should not be empty (6 elements)

    Headings should not be empty: 6 elements on the page fail this check, rated minor by axe-core.

  • Headings skip levels

    Headings skip levels (h2 → h6, h2 → h6 and h2 → h5), which makes the page harder to scan with a screen reader.

1 checks passed
  • 43 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 53 WCAG 2.2 A/AA and best-practice rules on the phone render: 43 passed and 10 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

1 to fixGoogle 9295
  • Meta description is long (267 characters)

    Your meta description is 267 characters; Google truncates after about 160, so the end of your pitch is cut.

  • 377 internal links, 9 external

    The homepage links to 377 pages on olivaclinic.com and 9 external pages.

7 checks passed
  • One H1 headline

    Your main headline reads: “Oliva Clinics: Where Medical Expertise Meets Aesthetic Care”.

  • Title: 61 characters

    Your title is a healthy 61 characters: “Oliva Skin, Hair & Body Clinic | Advanced Treatments in India”.

  • Canonical URL set

    The canonical URL is https://www.olivaclinic.com/.

  • Structured data in place

    Structured data found: MedicalOrganization, 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.olivaclinic.com/sitemap_index.xml.

AI search readiness

100
4 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.

  • Organization data: 6 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.

  • Text is in the HTML

    Your server sends the page's text in the HTML (2,195 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://www.olivaclinic.com/llms.txt (1 KiB, 0 links), a plain-text guide to the site for AI tools.

Other pages

3 to fix80
  • 1 page points its canonical at the homepage

    https://www.olivaclinic.com/ask-oliva declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.

  • 1 page without a meta description

    https://www.olivaclinic.com/ask-oliva has no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

    https://www.olivaclinic.com/ask-oliva has no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page slow to respond

    https://www.olivaclinic.com/ask-oliva took over 3 s to send its HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 130 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.

  • Titles are unique

    Every page we checked has its own title.

  • 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

Google 96100
3 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

    23 of 24 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix94
  • 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.

  • 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 370 words of copy

    The homepage carries about 370 words of visible text.

7 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Buy Products Online” and “Book Now”.

  • 8 calls to action

    The homepage has 8 calls to action, for example “Contact Us”, “Buy Products Online” and “Book Appointment”.

  • 4 short forms

    4 short forms (4 fields at most) are right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 8 testimonial or review blocks, 2 customer or partner logos, 1 trust badge and “Served 8,00,000+ happy clients”.

  • Analytics in place

    Analytics detected: Google Tag Manager and Google Analytics.

  • Direct contact links

    Visitors can reach you directly: 6 phone links and 1 email link.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

Privacy and tracking

1 to fix
  • 5 trackers load before any consent

    5

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, 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.

  • 5 cookies set on arrival

    5

    Opening the homepage sets 5 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.

  • 14 other companies contacted

    Loading the homepage contacts 14 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 olivaclinic.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
Hosting
AWS

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 olivaclinic.com, including 22 speed issues, 1 SEO issue 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25