Website review, no card needed
ujalacygnus.com website review
Visit site (opens in a new tab)Reviewed 4 November 202644 issues · 92 checks
This review found 44 issues worth fixing on ujalacygnus.com, 19 of them high impact, across 92 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
73CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 2.3 s |
| May 23, 2026 | 2.3 s |
| May 30, 2026 | 2.3 s |
| Jun 6, 2026 | 2.3 s |
| Jun 13, 2026 | 2.3 s |
| Jun 20, 2026 | 2.3 s |
| Jun 27, 2026 | 2.4 s |
| Jul 4, 2026 | 2.4 s |
| Jul 11, 2026 | 2.4 s |
| Jul 18, 2026 | 2.4 s |
| Jul 25, 2026 | 2.4 s |
| Aug 1, 2026 | 2.4 s |
| Aug 8, 2026 | 2.5 s |
| Aug 15, 2026 | 2.5 s |
| Aug 22, 2026 | 2.4 s |
| Aug 29, 2026 | 2.4 s |
| Sep 5, 2026 | 2.4 s |
| Sep 12, 2026 | 2.4 s |
| Sep 19, 2026 | 2.4 s |
| Sep 26, 2026 | 2.4 s |
| Oct 3, 2026 | 2.4 s |
| Oct 10, 2026 | 2.5 s |
| Oct 17, 2026 | 2.6 s |
| Oct 24, 2026 | 3.1 s |
| Oct 31, 2026 | 4.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 133 ms |
| May 23, 2026 | 131 ms |
| May 30, 2026 | 134 ms |
| Jun 6, 2026 | 138 ms |
| Jun 13, 2026 | 142 ms |
| Jun 20, 2026 | 145 ms |
| Jun 27, 2026 | 143 ms |
| Jul 4, 2026 | 145 ms |
| Jul 11, 2026 | 147 ms |
| Jul 18, 2026 | 147 ms |
| Jul 25, 2026 | 148 ms |
| Aug 1, 2026 | 143 ms |
| Aug 8, 2026 | 142 ms |
| Aug 15, 2026 | 142 ms |
| Aug 22, 2026 | 144 ms |
| Aug 29, 2026 | 145 ms |
| Sep 5, 2026 | 147 ms |
| Sep 12, 2026 | 149 ms |
| Sep 19, 2026 | 146 ms |
| Sep 26, 2026 | 148 ms |
| Oct 3, 2026 | 145 ms |
| Oct 10, 2026 | 143 ms |
| Oct 17, 2026 | 143 ms |
| Oct 24, 2026 | 140 ms |
| Oct 31, 2026 | 140 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.9 s
4.3 s
5.8 s
7.2 s
8.7 s
10.1 s
11.5 s
Speed
Reduce unused JavaScript
5.8 s · 744 KiBAbout 744 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 5.8 s faster on a phone.
Render-blocking requests
3.6 s32 files block the first paint until they finish downloading. Deferring or inlining them could save about 3.6 s.
Use efficient cache lifetimes
1.4 s · 220 KiB7 files are served with short cache lifetimes, so returning visitors download them again (220 KiB).
Reduce unused CSS
1.2 s · 284 KiBAbout 284 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.2 s faster on a phone.
Mobile performance score: 48
48/100Your mobile performance score is 48. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 5.0 s
A phone's processor spends 5.0 s on main-thread work while loading, 2.8 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
3,263 HTML elements
The page has 3,263 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 (Google Tag Manager, Google CDN and Clarity and others), adding 1.5 MB and 995 ms of main-thread time.
Improve image delivery
600 ms · 181 KiB6 images could be 181 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 600 ms faster on a phone.
Google Tag Manager adds 401 ms
401 msGoogle Tag Manager costs a phone 401 ms of main-thread work and 512 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 303 ms
303 msGoogle CDN costs a phone 303 ms of main-thread work and 736 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.
Legacy JavaScript
250 ms · 34 KiBPolyfills for old browsers add 34 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 250 ms faster on a phone.
15 long tasks on the main thread
15 long tasks block the main thread while loading, the longest for 188 ms. During a long task the page ignores taps.
Minify JavaScript
12 KiB12 KiB could be saved by minifying JavaScript.
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.
1 checks passed
Server response: 544 ms
544 msYour server sent the HTML in 544 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.
Real-user LCP: 5.0 s
5.0 sReal visitors wait 5.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 6.5 s
6.5 sReal visitors see the first content after 6.5 s (75th percentile). Good is under 1.8 s.
First Contentful Paint: 10.1 s
10.1 sThe first text or image appears after 10.1 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 22.1 s
22.1 sYour largest element takes 22.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.
Speed Index: 20.6 s
20.6 sVisually, the page fills in at 20.6 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 22.5 s
22.5 sThe page becomes fully interactive after 22.5 s. Good is under 3.8 s.
Largest content (LCP) got 61% slower for real visitors
+61%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.3 s to 4.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user TTFB: 1.6 s
1.6 sReal visitors wait 1.6 s for your server to start answering (75th percentile). Good is under 800 ms.
Total Blocking Time: 327 ms
327 msScripts block taps and scrolling for 327 ms in total while the page loads. Good is under 200 ms.
4 images without width and height
4 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
+6%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 133 ms to 140 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Real-user INP: 150 ms
150 msReal visitors wait 150 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.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 3.5 MB in 139 requests
3.5 MBYour homepage downloads 3.5 MB in 139 requests on a phone: scripts 1.9 MB (50), images 569 KiB (17) and other files 368 KiB (27). Under 2 MB keeps phones on slow connections fast.
1 image in older formats
1 image (44 KiB) is 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.0 g of CO₂ per visit
1.00 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.00 g of CO₂e: 120.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
Unlabelled dropdowns
2 dropdowns have no label.
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
1 text element with low contrast
1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.
11 images without alt text
11 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (4 elements)
All page content should be contained by landmarks: 4 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 (2 elements)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 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.
53 links without text
53 visible links have no text or label, so screen readers cannot say where they go.
18 form fields without a label
18 form fields have no label, so screen readers announce an empty box and autofill guesses.
Alternative text of images should not be repeated as text (9 elements)
Alternative text of images should not be repeated as text: 9 elements on the page fail this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h2 → h5, h2 → h4 and h2 → h4), which makes the page harder to scan with a screen reader.
1 checks passed
49 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 59 WCAG 2.2 A/AA and best-practice rules on the phone render: 49 passed and 10 failed. 3 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 (70 characters)
Your title is 70 characters, so Google will cut it off around 60: “Best Superspeciality Hospitals in India | Advanced Care - Ujala Cygnus”.
22 links with vague text
22 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
Meta description is long (223 characters)
Your meta description is 223 characters; Google truncates after about 160, so the end of your pitch is cut.
288 internal links, 18 external
The homepage links to 288 pages on ujalacygnus.com and 18 external pages.
5 checks passed
Canonical URL set
The canonical URL is https://ujalacygnus.com/.
Structured data in place
Structured data found: BreadcrumbList, ImageObject, MedicalOrganization, WebPage 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://ujalacygnus.com/sitemap_index.xml.
AI search readiness
No llms.txt
There is no https://ujalacygnus.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: 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 (3,292 words), so crawlers that don't run JavaScript still read it.
Other pages
1 page without a meta description
https://ujalacygnus.com/case-studies has no meta description, so Google writes the search snippet from whatever text it finds.
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://ujalacygnus.com/hospitals/ujala-cygnus-noble-super-speciality-hospital-kanpur, whose canonical is https://ujalacygnus.com/hospitals/ujala-cygnus-noble-superspeciality-hospital-kanpur. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
1 page slow to respond
https://ujalacygnus.com/hospitals/ujala-cygnus-noble-super-speciality-hospital-kanpur took over 3 s to send its HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 133 found) and read each the way a search engine does.
5 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.
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
24 small tap targets
24 of 37 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 “$carousel.slick is not a function”.
2 distorted images
2 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
1 checks passed
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.
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,071 words of copy
The homepage carries about 1,071 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: “Book Appointment”.
5 calls to action
The homepage has 5 calls to action, for example “Call Now”, “Request Callback” and “Book Appointment”.
6 short forms
6 short forms (6 fields at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 6 customer or partner logos and 5 trust badges.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics and Microsoft Clarity.
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
5 trackers load before any consent
5Before 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.
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.
19 other companies contacted
Loading the homepage contacts 19 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 ujalacygnus.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 | Microsoft Clarity
- Hosting
- CtrlS
Company
- Headquarters
- New Delhi
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 44 issues on ujalacygnus.com, including 22 speed issues, 4 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.