Website review, no card needed
ektaworld.com website review
Visit site (opens in a new tab)Reviewed 26 October 202652 issues · 104 checks
This review found 52 issues worth fixing on ektaworld.com, 27 of them high impact, across 104 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
67DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 2.1 s |
| May 16, 2026 | 2.2 s |
| May 23, 2026 | 2.2 s |
| May 30, 2026 | 2.4 s |
| Jun 6, 2026 | 2.4 s |
| Jun 13, 2026 | 2.5 s |
| Jun 20, 2026 | 2.4 s |
| Jun 27, 2026 | 2.4 s |
| Jul 4, 2026 | 2.5 s |
| Jul 11, 2026 | 2.3 s |
| Jul 18, 2026 | 2.4 s |
| Jul 25, 2026 | 2.5 s |
| Aug 1, 2026 | 2.4 s |
| Aug 8, 2026 | 2.4 s |
| Aug 15, 2026 | 2.3 s |
| Aug 22, 2026 | 2.1 s |
| Aug 29, 2026 | 2.2 s |
| Sep 5, 2026 | 2.2 s |
| Sep 12, 2026 | 2.4 s |
| Sep 19, 2026 | 2.4 s |
| Sep 26, 2026 | 2.3 s |
| Oct 3, 2026 | 2.3 s |
| Oct 10, 2026 | 2.2 s |
| Oct 17, 2026 | 2.3 s |
| Oct 24, 2026 | 2.3 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 103 ms |
| May 16, 2026 | 96 ms |
| May 23, 2026 | 96 ms |
| May 30, 2026 | 105 ms |
| Jun 6, 2026 | 106 ms |
| Jun 13, 2026 | 111 ms |
| Jun 20, 2026 | 109 ms |
| Jun 27, 2026 | 105 ms |
| Jul 4, 2026 | 106 ms |
| Jul 11, 2026 | 104 ms |
| Jul 18, 2026 | 109 ms |
| Jul 25, 2026 | 105 ms |
| Aug 1, 2026 | 100 ms |
| Aug 8, 2026 | 105 ms |
| Aug 15, 2026 | 102 ms |
| Aug 22, 2026 | 104 ms |
| Aug 29, 2026 | 102 ms |
| Sep 5, 2026 | 99 ms |
| Sep 12, 2026 | 97 ms |
| Sep 19, 2026 | 97 ms |
| Sep 26, 2026 | 102 ms |
| Oct 3, 2026 | 104 ms |
| Oct 10, 2026 | 103 ms |
| Oct 17, 2026 | 102 ms |
| Oct 24, 2026 | 100 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.6 s
3.2 s
4.7 s
6.3 s
7.9 s
9.5 s
11.1 s
12.7 s
Speed
Reduce unused JavaScript
24.9 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 24.9 s faster on a phone.
Use efficient cache lifetimes
20.4 s · 7.1 MB112 files are served with short cache lifetimes, so returning visitors download them again (7.1 MB).
Improve image delivery
11.7 s · 3.1 MB24 images could be 3.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 11.7 s faster on a phone.
Render-blocking requests
5.7 s14 files block the first paint until they finish downloading. Deferring or inlining them could save about 5.7 s.
Minify JavaScript
1.6 s · 398 KiB398 KiB could be saved by minifying JavaScript.
YouTube adds 1.5 s
1.5 sYouTube costs a phone 1.5 s of main-thread work and 3.8 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.
Reduce unused CSS
1.1 s · 333 KiBAbout 333 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.1 s faster on a phone.
Mobile performance score: 33
33/100Your mobile performance score is 33 (desktop: 30). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 5.9 s
A phone's processor spends 5.9 s on main-thread work while loading, 3.0 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 (YouTube, Google Tag Manager and kenyt.ai and others), adding 6.2 MB and 2.5 s of main-thread time.
Document request latency
750 ms · 76 KiBThe HTML itself could arrive about 750 ms sooner: redirects, a slow server response or missing compression delay everything after it.
Reduce initial server response time
736 msReduce initial server response time. Google estimates savings of 736 ms on a phone.
Google Tag Manager adds 433 ms
433 msGoogle Tag Manager costs a phone 433 ms of main-thread work and 774 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
450 ms · 37 KiBPolyfills for old browsers add 37 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 450 ms faster on a phone.
sell.do adds 170 ms
170 mssell.do costs a phone 170 ms of main-thread work and 842 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.
kenyt.ai adds 199 ms
199 mskenyt.ai costs a phone 199 ms of main-thread work and 398 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 127 ms
127 msGoogle CDN costs a phone 127 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: 836 ms
836 msYour server takes 836 ms to send the HTML. Google recommends under 600 ms; everything else waits for it.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 195 ms. During a long task the page ignores taps.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Minify CSS
10 KiB10 KiB could be saved by minifying CSS.
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 CLS: 0.62
0.62For real visitors the layout shifts by 0.62 (75th percentile). Good is under 0.1.
Largest Contentful Paint: 61.3 s
61.3 sYour largest element takes 61.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Speed Index: 25.0 s
25.0 sVisually, the page fills in at 25.0 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 69.0 s
69.0 sThe page becomes fully interactive after 69.0 s. Good is under 3.8 s.
First Contentful Paint: 6.3 s
6.3 sThe first text or image appears after 6.3 s on a phone. Good is under 1.8 s.
Total Blocking Time: 889 ms
889 msScripts block taps and scrolling for 889 ms in total while the page loads. Good is under 200 ms.
Real-user LCP: 3.3 s
3.3 sReal visitors wait 3.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 2.1 s
2.1 sReal visitors see the first content after 2.1 s (75th percentile). Good is under 1.8 s.
51 images without width and height
51 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
+2%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 103 ms to 100 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+5%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 2.1 s to 2.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
2 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.
Cumulative Layout Shift: 0.084
0.084The layout barely moves while loading (CLS 0.084, good is under 0.1).
Images and page weight
Page weight: 12.8 MB in 206 requests
12.8 MBYour homepage downloads 12.8 MB in 206 requests on a phone: scripts 5.8 MB (56), images 5.5 MB (68) and stylesheets 637 KiB (32). Under 2 MB keeps phones on slow connections fast.
4 images over 500 KB
4 images weigh 4.0 MB together. On a phone connection a single image that size takes seconds.
2 images far larger than shown
716 KiB2 images are downloaded at several times the size a phone draws them, for example banner_3.webp at 2,000 px wide, shown at 390 px. Resized copies would save about 716 KiB.
An image on the first screen is lazy-loaded
banner_3.webp 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).
14 images in older formats
14 images (927 KiB) 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.
14 images below the first screen load straight away
14 images further down the page (908 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 3.6 g of CO₂ per visit
3.64 gBy the Sustainable Web Design model, a visit to your homepage emits about 3.64 g of CO₂e: 436.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
Required ARIA attributes must be provided (2 elements)
Required ARIA attributes must be provided: 2 elements on the page fail this check, rated critical by axe-core.
ARIA attributes must conform to valid values (2 elements)
ARIA attributes must conform to valid values: 2 elements on the page fail this check, rated critical by axe-core.
Unlabelled dropdowns
2 dropdowns have no label.
4 text elements with low contrast
4 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
4 tap targets too small
4 tap targets are too small or too close together to hit reliably with a finger.
ARIA input fields must have an accessible name (2 elements)
ARIA input fields must have an accessible name: 2 elements on the page fail this check, rated serious by axe-core.
Interactive controls must not be nested (1 element)
Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.
All page content should be contained by landmarks (35 elements)
All page content should be contained by landmarks: 35 elements on the page fail this check, rated moderate by axe-core.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
31 links without text
31 visible links have no text or label, so screen readers cannot say where they go.
12 form fields without a label
12 form fields have no label, so screen readers announce an empty box and autofill guesses.
Headings skip levels
Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 85 images in the HTML carry an alt attribute.
43 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 56 WCAG 2.2 A/AA and best-practice rules on the phone render: 43 passed and 13 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
2 links with vague text
2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
65 internal links, 38 external
The homepage links to 65 pages on ektaworld.com and 38 external pages.
8 checks passed
Meta description: 130 characters
Your meta description is 130 characters: “Ekta World is the best real estate company in Mumbai, developing premium residential properties across the city for ove…”.
One H1 headline
Your main headline reads: “Ekta World Best Real Estate Company in Mumbai Since 1987”.
Title: 52 characters
Your title is a healthy 52 characters: “Best Real Estate Company in Mumbai 2026 | Ekta World”.
Canonical URL set
The canonical URL is https://www.ektaworld.com/.
Structured data in place
Structured data found: FAQPage, Organization and RealEstateAgent.
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.ektaworld.com/sitemap.xml.
AI search readiness
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: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (1,741 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.ektaworld.com/llms.txt (195 KiB, 94 links), a plain-text guide to the site for AI tools.
Other pages
2 pages with very little text
https://www.ektaworld.com/upcoming-projects.html and https://www.ektaworld.com/get-in-touch.html have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 25 found) and read each the way a search engine does.
7 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a meta description
All 15 pages that loaded have a meta description.
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
8 small tap targets
8 of 15 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.
6 JavaScript errors while loading
6 errors were logged to the browser console while the page loaded, for example “WOW is not defined”.
2 low-resolution images
2 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 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.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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,164 words of copy
The homepage carries about 1,164 words of visible text.
7 checks passed
2 calls to action
The homepage has 2 calls to action, for example “GET IN TOUCH”.
Social proof on the page
Social proof on the homepage: 4 testimonial or review blocks, 1 customer or partner logo and 12 trust badges.
Analytics in place
Analytics detected: Google Tag Manager and Google Analytics.
Direct contact links
Visitors can reach you directly: 1 phone link and 0 email links.
Opening hours shown
Your opening hours are on the homepage.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
LocalBusiness structured data
Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Google Tag Manager (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
5Opening the homepage sets 5 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.
20 other companies contacted
Loading the homepage contacts 20 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 ektaworld.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- jQuery
- Analytics
- Google Analytics | Google Tag Manager
- Hosting
- CtrlS
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 52 issues on ektaworld.com, including 28 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.