Website review, no card needed
ujaas.com website review
Visit site (opens in a new tab)Reviewed 31 October 202642 issues · 85 checks
This review found 42 issues worth fixing on ujaas.com, 17 of them high impact, across 85 checks. The most urgent: use efficient cache lifetimes. 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
69DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 10.2 s |
| May 16, 2026 | 11.1 s |
| May 23, 2026 | 12.8 s |
| May 30, 2026 | 10.8 s |
| Jun 6, 2026 | 11.0 s |
| Jun 13, 2026 | 9.7 s |
| Jun 20, 2026 | 8.4 s |
| Jun 27, 2026 | 7.6 s |
| Jul 4, 2026 | 9.3 s |
| Jul 11, 2026 | 10.1 s |
| Jul 18, 2026 | 11.2 s |
| Jul 25, 2026 | 9.1 s |
| Aug 1, 2026 | 8.0 s |
| Aug 8, 2026 | 10.6 s |
| Aug 15, 2026 | 10.6 s |
| Aug 22, 2026 | 10.7 s |
| Aug 29, 2026 | 11.8 s |
| Sep 5, 2026 | 9.9 s |
| Sep 12, 2026 | 8.1 s |
| Sep 19, 2026 | 8.0 s |
| Sep 26, 2026 | 6.9 s |
| Oct 3, 2026 | 7.9 s |
| Oct 10, 2026 | 7.9 s |
| Oct 17, 2026 | 8.6 s |
| Oct 24, 2026 | 9.0 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 127 ms |
| May 16, 2026 | 120 ms |
| May 23, 2026 | 118 ms |
| May 30, 2026 | 114 ms |
| Jun 6, 2026 | 101 ms |
| Jun 13, 2026 | 100 ms |
| Jun 20, 2026 | 121 ms |
| Jun 27, 2026 | 107 ms |
| Jul 4, 2026 | 103 ms |
| Jul 11, 2026 | 114 ms |
| Jul 18, 2026 | 116 ms |
| Jul 25, 2026 | 133 ms |
| Aug 1, 2026 | 137 ms |
| Aug 8, 2026 | 130 ms |
| Aug 15, 2026 | 133 ms |
| Aug 22, 2026 | 127 ms |
| Aug 29, 2026 | 129 ms |
| Sep 5, 2026 | 120 ms |
| Sep 12, 2026 | 110 ms |
| Sep 19, 2026 | 120 ms |
| Sep 26, 2026 | 137 ms |
| Oct 10, 2026 | 135 ms |
| Oct 17, 2026 | 135 ms |
| Oct 24, 2026 | 131 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
3.7 s
7.5 s
11.2 s
14.9 s
18.6 s
22.4 s
26.1 s
29.8 s
Speed
Use efficient cache lifetimes
8.0 s · 3.7 MB81 files are served with short cache lifetimes, so returning visitors download them again (3.7 MB).
Reduce unused JavaScript
9.8 s · 1.5 MBAbout 1.5 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 9.8 s faster on a phone.
Render-blocking requests
7.6 s27 files block the first paint until they finish downloading. Deferring or inlining them could save about 7.6 s.
Reduce unused CSS
2.7 s · 583 KiBAbout 583 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 2.7 s faster on a phone.
Font display
3.0 sWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 3.0 s).
Mobile performance score: 46
46/100Your mobile performance score is 46. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 4.8 s
A phone's processor spends 4.8 s on main-thread work while loading, 2.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 CDN, YouTube and Google Tag Manager and others), adding 2.9 MB and 1.3 s of main-thread time.
Document request latency
800 ms · 147 KiBThe HTML itself could arrive about 800 ms sooner: redirects, a slow server response or missing compression delay everything after it.
Improve image delivery
550 ms · 376 KiB23 images could be 376 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 550 ms faster on a phone.
Reduce initial server response time
810 msReduce initial server response time. Google estimates savings of 810 ms on a phone.
Google CDN adds 482 ms
482 msGoogle CDN costs a phone 482 ms of main-thread work and 1.1 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.
YouTube adds 424 ms
424 msYouTube costs a phone 424 ms of main-thread work and 984 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 Tag Manager adds 198 ms
198 msGoogle Tag Manager costs a phone 198 ms of main-thread work and 426 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.
1,626 HTML elements
The page has 1,626 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Server response: 910 ms
910 msYour server takes 910 ms to send the HTML. Google recommends under 600 ms; everything else waits for it.
Legacy JavaScript
150 ms · 23 KiBPolyfills for old browsers add 23 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
14 long tasks on the main thread
14 long tasks block the main thread while loading, the longest for 132 ms. During a long task the page ignores taps.
Minify JavaScript
15 KiB15 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.
Minify CSS
2 KiB2 KiB could be saved by minifying CSS.
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: 8.0 s
8.0 sReal visitors wait 8.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 9.6 s
9.6 sReal visitors see the first content after 9.6 s (75th percentile). Good is under 1.8 s.
First Contentful Paint: 8.4 s
8.4 sThe first text or image appears after 8.4 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 34.6 s
34.6 sYour largest element takes 34.6 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: 34.9 s
34.9 sVisually, the page fills in at 34.9 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 39.7 s
39.7 sThe page becomes fully interactive after 39.7 s. Good is under 3.8 s.
Real-user TTFB: 1.4 s
1.4 sReal visitors wait 1.4 s for your server to start answering (75th percentile). Good is under 800 ms.
Total Blocking Time: 359 ms
359 msScripts block taps and scrolling for 359 ms in total while the page loads. Good is under 200 ms.
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
+8%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 127 ms to 131 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
4 checks passed
Real-user INP: 135 ms
135 msReal visitors wait 135 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.
Largest content (LCP) got 17% faster for real visitors
-17%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 10.2 s to 9.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0.042
0.042The layout barely moves while loading (CLS 0.042, good is under 0.1).
Images and page weight
Page weight: 7.1 MB in 161 requests
7.1 MBYour homepage downloads 7.1 MB in 161 requests on a phone: scripts 3.1 MB (54), images 2.3 MB (51) and stylesheets 634 KiB (31). Under 2 MB keeps phones on slow connections fast.
About 2.0 g of CO₂ per visit
2.00 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.00 g of CO₂e: 240.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
2 images without alt text
2 images have no alt text, which hurts accessibility and image search.
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.
21 text elements with low contrast
21 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.
Frames without titles
1 frame has no title, so screen-reader users cannot tell what it contains.
Headings skip levels
Headings skip levels (h1 → h4), which makes the page harder to scan with a screen reader.
1 checks passed
5 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 7 WCAG 2.2 A/AA and best-practice rules on the phone render: 5 passed and 2 failed. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
4 H1 headlines
There are 4 <h1> headlines (“Providing turnkey solutions”, “Electricity Dep. of Daman & Diu” and “West Begal EPC Projects”). One clear main headline is easier for people and search engines.
Meta description is long (187 characters)
Your meta description is 187 characters; Google truncates after about 160, so the end of your pitch is cut.
2 links crawlers can't follow
2 links have no real href, so search engines can't follow them.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.
145 internal links, 66 external
The homepage links to 145 pages on ujaas.com and 66 external pages.
6 checks passed
Title: 61 characters
Your title is a healthy 61 characters: “Ujaas Energy Ltd. | Solar Power Plant | Solar Power Solutions”.
Canonical URL set
The canonical URL is https://www.ujaas.com/.
Structured data in place
Structured data found: 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.
XML sitemap found
Your XML sitemap is reachable at https://www.ujaas.com/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.
No llms.txt
There is no https://www.ujaas.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.
1 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.
Other pages
6 pages without a meta description
https://www.ujaas.com/who-we-are, https://www.ujaas.com/vision-and-misson, https://www.ujaas.com/chairmans-message, https://www.ujaas.com/board-of-directors, https://www.ujaas.com/our-team and https://www.ujaas.com/board-committee have no meta description, so Google writes the search snippet from whatever text it finds.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 60 found) and read each the way a search engine does.
6 checks passed
Linked pages load
6 pages of 15 loaded without an error (the rest turned automated requests away).
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
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 6 pages that loaded have a <title>.
Best practices
5 third-party cookies
5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
1 distorted image
1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
2 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No call to action on the first screen
On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.
Thin social proof
Social proof on the homepage: 17 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.
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,871 words of copy
The homepage carries about 1,871 words of visible text.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
4 checks passed
5 calls to action
The homepage has 5 calls to action, for example “Book Closure Notice”, “CONTACT US” and “Sign up”.
2 short forms
2 short forms (4 fields at most) are right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics and Meta Pixel.
Direct contact links
Visitors can reach you directly: 1 phone link and 0 email links.
Privacy and tracking
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.
1 other company contacted
Loading the homepage contacts 1 host run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
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 ujaas.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
- The footer still says © 2014.
Stack
- CMS
- WordPress
- Framework
- jQuery
- Analytics
- Google Analytics | Google Tag Manager
- Hosting
- Emaxglobal As Emax Global Media Pvt. Ltd
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 ujaas.com, including 26 speed issues, 3 SEO issues and 2 conversion gaps. 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.