Website review, no card needed
wockhardthospitals.com website review
Visit site (opens in a new tab)Reviewed 29 October 202653 issues · 98 checks
This review found 53 issues worth fixing on wockhardthospitals.com, 25 of them high impact, across 98 checks. The most urgent: reduce unused JavaScript. 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
68D- #109,920 of 125,363 reviewed websitesbeats 10%
- #65,375 of 70,165 online storesbeats 5%
- #2,475 of 2,942 WooCommerce storesbeats 12%
Closest competitors among WooCommerce stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 6.4 s |
| May 16, 2026 | 6.5 s |
| May 23, 2026 | 6.6 s |
| May 30, 2026 | 6.9 s |
| Jun 6, 2026 | 7.5 s |
| Jun 13, 2026 | 7.2 s |
| Jun 20, 2026 | 6.8 s |
| Jun 27, 2026 | 6.0 s |
| Jul 4, 2026 | 4.4 s |
| Jul 11, 2026 | 3.9 s |
| Jul 18, 2026 | 4.0 s |
| Jul 25, 2026 | 4.3 s |
| Aug 1, 2026 | 4.7 s |
| Aug 8, 2026 | 5.0 s |
| Aug 15, 2026 | 5.2 s |
| Aug 22, 2026 | 5.1 s |
| Aug 29, 2026 | 4.9 s |
| Sep 5, 2026 | 4.8 s |
| Sep 12, 2026 | 4.7 s |
| Sep 19, 2026 | 4.7 s |
| Sep 26, 2026 | 4.6 s |
| Oct 3, 2026 | 4.6 s |
| Oct 10, 2026 | 4.5 s |
| Oct 17, 2026 | 4.4 s |
| Oct 24, 2026 | 4.4 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 149 ms |
| May 16, 2026 | 156 ms |
| May 23, 2026 | 162 ms |
| May 30, 2026 | 161 ms |
| Jun 6, 2026 | 157 ms |
| Jun 13, 2026 | 148 ms |
| Jun 20, 2026 | 138 ms |
| Jun 27, 2026 | 131 ms |
| Jul 4, 2026 | 124 ms |
| Jul 11, 2026 | 120 ms |
| Jul 18, 2026 | 119 ms |
| Jul 25, 2026 | 120 ms |
| Aug 1, 2026 | 120 ms |
| Aug 8, 2026 | 120 ms |
| Aug 15, 2026 | 121 ms |
| Aug 22, 2026 | 123 ms |
| Aug 29, 2026 | 122 ms |
| Sep 5, 2026 | 124 ms |
| Sep 12, 2026 | 123 ms |
| Sep 19, 2026 | 123 ms |
| Sep 26, 2026 | 122 ms |
| Oct 3, 2026 | 122 ms |
| Oct 10, 2026 | 124 ms |
| Oct 17, 2026 | 124 ms |
| Oct 24, 2026 | 123 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
2.8 s
5.6 s
8.4 s
11.2 s
14.0 s
16.8 s
19.6 s
22.4 s
Speed
Reduce unused JavaScript
12.5 s · 3.5 MBAbout 3.5 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 12.5 s faster on a phone.
Render-blocking requests
8.2 s73 files block the first paint until they finish downloading. Deferring or inlining them could save about 8.2 s.
Reduce unused CSS
2.6 s · 535 KiBAbout 535 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 2.6 s faster on a phone.
Font display
2.6 sWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 2.6 s).
YouTube adds 1.4 s
1.4 sYouTube costs a phone 1.4 s of main-thread work and 2.9 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Main-thread work: 14.4 s
A phone's processor spends 14.4 s on main-thread work while loading, 4.8 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Mobile performance score: 20
20/100Your mobile performance score is 20. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
4,461 HTML elements
The page has 4,461 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
8 third-party services on the page
8 third-party services load with your homepage (YouTube, Google Tag Manager and Google CDN and others), adding 5.2 MB and 3.1 s of main-thread time.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 1.6 s. During a long task the page ignores taps.
Minify JavaScript
920 ms · 222 KiB222 KiB could be saved by minifying JavaScript.
Improve image delivery
300 ms · 792 KiB14 images could be 792 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 300 ms faster on a phone.
Use efficient cache lifetimes
250 ms · 612 KiB33 files are served with short cache lifetimes, so returning visitors download them again (612 KiB).
Google Tag Manager adds 674 ms
674 msGoogle Tag Manager costs a phone 674 ms of main-thread work and 810 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.
Google CDN adds 552 ms
552 msGoogle CDN costs a phone 552 ms of main-thread work and 773 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 initial server response time
621 msReduce initial server response time. Google estimates savings of 621 ms on a phone.
Document request latency
600 msThe HTML itself could arrive about 600 ms sooner: redirects, a slow server response or missing compression delay everything after it.
kenyt.ai adds 213 ms
213 mskenyt.ai costs a phone 213 ms of main-thread work and 405 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: 721 ms
721 msYour server takes 721 ms to send the HTML. Google recommends under 600 ms; everything else waits for it.
Minify CSS
150 ms · 5 KiB5 KiB could be saved by minifying CSS.
Legacy JavaScript
89 KiBPolyfills for old browsers add 89 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.
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: 5.9 s
5.9 sReal visitors wait 5.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 5.9 s
5.9 sReal visitors see the first content after 5.9 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 4.6 s
4.6 sReal visitors wait 4.6 s for your server to start answering (75th percentile). Good is under 800 ms.
Largest Contentful Paint: 35.7 s
35.7 sYour largest element takes 35.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Wockhardt Hospitals”.
Speed Index: 35.8 s
35.8 sVisually, the page fills in at 35.8 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 80.6 s
80.6 sThe page becomes fully interactive after 80.6 s. Good is under 3.8 s.
First Contentful Paint: 6.2 s
6.2 sThe first text or image appears after 6.2 s on a phone. Good is under 1.8 s.
Total Blocking Time: 2.7 s
2.7 sScripts block taps and scrolling for 2.7 s in total while the page loads. Good is under 200 ms.
Cumulative Layout Shift: 0.147
0.147The layout shifts by 0.147 while loading, so content jumps under the reader's thumb. Good is under 0.1.
4 checks passed
Real-user INP: 142 ms
142 msReal visitors wait 142 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.
Tap response (INP) got 19% faster for real visitors
-19%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 149 ms to 123 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 32% faster for real visitors
-32%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 6.4 s to 4.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Images and page weight
Page weight: 16.9 MB in 351 requests
16.9 MBYour homepage downloads 16.9 MB in 351 requests on a phone: images 7.8 MB (69), scripts 6.7 MB (123) and fonts 918 KiB (11). Under 2 MB keeps phones on slow connections fast.
6 images over 500 KB
6 images weigh 4.6 MB together. On a phone connection a single image that size takes seconds.
17 images in older formats
17 images (5.5 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 4.8 g of CO₂ per visit
4.80 gBy the Sustainable Web Design model, a visit to your homepage emits about 4.80 g of CO₂e: 575.9 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
Unlabelled dropdowns
5 dropdowns have no label.
Certain ARIA roles must contain particular children (2 elements)
Certain ARIA roles must contain particular children: 2 elements on the page fail this check, rated critical by axe-core.
12 text elements with low contrast
12 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Hidden but focusable
1 element hidden from screen readers can still receive keyboard focus.
22 images without alt text
22 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (19 elements)
All page content should be contained by landmarks: 19 elements on the page fail this check, rated moderate by axe-core.
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.
The skip-link target should exist and be focusable (1 element)
The skip-link target should exist and be focusable: 1 element on the page fails this check, rated moderate by axe-core.
25 links without text
25 visible links have no text or label, so screen readers cannot say where they go.
21 form fields without a label
21 form fields have no label, so screen readers announce an empty box and autofill guesses.
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.
Headings skip levels
Headings skip levels (h2 → h4, h2 → h4 and h2 → h5), which makes the page harder to scan with a screen reader.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (4 elements).
1 checks passed
51 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 62 WCAG 2.2 A/AA and best-practice rules on the phone render: 51 passed and 11 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Title is long (79 characters)
Your title is 79 characters, so Google will cut it off around 60: “Best Hospitals in India: Trusted Multispeciality Hospital | Wockhardt Hospitals”.
Meta description is long (238 characters)
Your meta description is 238 characters; Google truncates after about 160, so the end of your pitch is cut.
500 internal links, 49 external
The homepage links to 500 pages on wockhardthospitals.com and 49 external pages.
5 checks passed
Canonical URL set
The canonical URL is https://wockhardthospitals.com/.
Structured data in place
Structured data found: MedicalOrganization and WebPage.
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://wockhardthospitals.com/sitemap.xml.
AI search readiness
No llms.txt
There is no https://wockhardthospitals.com/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.
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.
Organization data: 5 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and description; contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (2,565 words), so crawlers that don't run JavaScript still read it.
Other pages
2 links to non-canonical URLs
Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://wockhardthospitals.com/mumbai, whose canonical is https://wockhardthospitals.com/south-bombay-mumbai-central. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
4 pages without an H1
https://wockhardthospitals.com/mumbai, https://wockhardthospitals.com/mira-road, https://wockhardthospitals.com/rajkot and https://wockhardthospitals.com/nagpur-multispeciality have no <h1> headline, so visitors and search engines get no clear main topic.
13 pages slow to respond
https://wockhardthospitals.com/contact-us, https://wockhardthospitals.com/mumbai, https://wockhardthospitals.com/mira-road, https://wockhardthospitals.com/rajkot, https://wockhardthospitals.com/nagpur-multispeciality and https://wockhardthospitals.com/speciality/aesthetic-plastic-surgery and 7 others took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 166 found) and read each the way a search engine does.
5 checks passed
Linked pages load
13 pages of 15 loaded without an error (the rest turned automated requests away).
Every page has a meta description
All 13 pages that loaded have a meta description.
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 13 pages that loaded have a <title>.
Best practices
11 small tap targets
11 of 35 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
5 third-party cookies
5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
5 JavaScript errors while loading
5 errors were logged to the browser console while the page loaded, for example “Access to font at 'https://www.wockhardthospitals.com/wp-content/uploads/elementor/google-fonts/fonts/roboto-kfo7cnqeu9…”.
1 distorted image
1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.
5 low-resolution images
5 images are served at too low a resolution for sharp phone screens.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 544 words of copy
The homepage carries about 544 words of visible text.
6 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “REQUEST AN APPOINTMENT” and “Call Now”.
71 calls to action
The homepage has 71 calls to action, for example “Contact Us”, “REQUEST AN APPOINTMENT” and “Book An Appointment”.
7 short forms
7 short forms (5 fields at most) are right on the homepage, asking for an email.
Social proof on the page
Social proof on the homepage: 16 testimonial or review blocks, 9 customer or partner logos and “1 + Patients”.
Analytics in place
Analytics detected: Google Tag Manager.
Direct contact links
Visitors can reach you directly: 10 phone links and 5 email links.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, LinkedIn Insight and Meta Pixel (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.
19 cookies set on arrival
19Opening the homepage sets 19 cookies, 1 of them by other companies (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.
24 other companies contacted
Loading the homepage contacts 24 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 wockhardthospitals.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
- E-commerce
- WooCommerce
- Analytics
- Google Tag Manager
- Hosting
- CtrlS
Company
- Founded
- 1989
- Headquarters
- Mumbai
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 53 issues on wockhardthospitals.com, including 29 speed issues and 3 SEO issues. 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.