Website review, no card needed
hiranandani.com website review
Visit site (opens in a new tab)Reviewed 1 November 202641 issues · 93 checks
This review found 41 issues worth fixing on hiranandani.com, 12 of them high impact, across 93 checks. The most urgent: render-blocking requests. 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
66DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 2.7 s |
| May 16, 2026 | 2.6 s |
| May 23, 2026 | 2.7 s |
| May 30, 2026 | 2.5 s |
| Jun 6, 2026 | 2.3 s |
| Jun 13, 2026 | 2.5 s |
| Jun 20, 2026 | 2.3 s |
| Jun 27, 2026 | 2.7 s |
| Jul 4, 2026 | 2.3 s |
| Jul 11, 2026 | 2.4 s |
| Jul 18, 2026 | 3.0 s |
| Jul 25, 2026 | 2.7 s |
| Aug 1, 2026 | 3.0 s |
| Aug 8, 2026 | 2.9 s |
| Aug 15, 2026 | 2.4 s |
| Aug 22, 2026 | 2.2 s |
| Aug 29, 2026 | 2.3 s |
| Sep 12, 2026 | 2.5 s |
| Sep 19, 2026 | 2.3 s |
| Oct 17, 2026 | 2.5 s |
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
0.9 s
1.7 s
2.6 s
3.5 s
4.4 s
5.2 s
6.1 s
7.0 s
Speed
Render-blocking requests
2.5 s20 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.5 s.
Mobile performance score: 63
63/100Your mobile performance score is 63. Pages that score under 90 lose visitors before the first paint.
Google Tag Manager adds 350 ms
350 msGoogle Tag Manager costs a phone 350 ms of main-thread work and 638 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 unused JavaScript
335 KiBAbout 335 KiB of JavaScript is downloaded but never used on this page.
Improve image delivery
263 KiB6 images could be 263 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Google Analytics and Google/Doubleclick Ads and others), adding 752 KiB and 395 ms of main-thread time.
Reduce unused CSS
150 ms · 31 KiBAbout 31 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.
5 long tasks on the main thread
5 long tasks block the main thread while loading, the longest for 137 ms. During a long task the page ignores taps.
Document request latency
68 KiBThe HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.
Minify JavaScript
17 KiB17 KiB could be saved by minifying JavaScript.
Use efficient cache lifetimes
16 KiB2 files are served with short cache lifetimes, so returning visitors download them again (16 KiB).
Legacy JavaScript
8 KiBPolyfills for old browsers add 8 KiB JavaScript that modern phones do not need.
Minify CSS
8 KiB8 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.
2 checks passed
Main-thread work: 1.8 s
A phone's processor spends 1.8 s on main-thread work while loading, 674 ms of it running JavaScript. That is comfortably low.
Server response: 541 ms
541 msYour server sent the HTML in 541 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.
Speed Index: 12.9 s
12.9 sVisually, the page fills in at 12.9 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 9.6 s
9.6 sThe page becomes fully interactive after 9.6 s. Good is under 3.8 s.
Cumulative Layout Shift: 0.33
0.33The layout shifts by 0.33 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Real-user LCP: 2.6 s
2.6 sReal visitors wait 2.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.18
0.18For real visitors the layout shifts by 0.18 (75th percentile). Good is under 0.1.
First Contentful Paint: 2.9 s
2.9 sThe first text or image appears after 2.9 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 2.9 s
2.9 sYour largest element takes 2.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Established in 1978, Hiranandani Group is one of the most p…”. Most of its time is element render delay (3.3 s).
12 images without width and height
12 images have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) held steady for real visitors
-8%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 2.7 s to 2.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Real-user FCP: 1.6 s
1.6 sReal visitors see the first content after 1.6 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 797 ms
797 msReal visitors wait 797 ms for your server to start answering (75th percentile). Good is under 800 ms.
Total Blocking Time: 148 ms
148 msScripts block the page for only 148 ms while loading. Good is under 200 ms.
Images and page weight
2 images over 500 KB
2 images weigh 1.2 MB together. On a phone connection a single image that size takes seconds.
Page weight: 3.7 MB in 84 requests
3.7 MBYour homepage downloads 3.7 MB in 84 requests on a phone: images 2.2 MB (26), scripts 1.1 MB (33) and fonts 180 KiB (5). Under 2 MB keeps phones on slow connections fast.
5 images in older formats
5 images (1.4 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.
3 images far larger than shown
223 KiB3 images are downloaded at several times the size a phone draws them, for example rentals.png at 2,133 px wide, shown at 50 px. Resized copies would save about 223 KiB.
3 images below the first screen load straight away
3 images further down the page (231 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 1.1 g of CO₂ per visit
1.05 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.05 g of CO₂e: 126.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
ARIA attributes must conform to valid values (1 element)
ARIA attributes must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
Unlabelled dropdowns
1 dropdown has no label.
54 text elements with low contrast
54 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
<html> element must have a lang attribute (1 element)
<html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.
7 images without alt text
7 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (14 elements)
All page content should be contained by landmarks: 14 elements on the page fail this check, rated moderate by axe-core.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
24 form fields without a label
24 form fields have no label, so screen readers announce an empty box and autofill guesses.
11 links without text
11 visible links have no text or label, so screen readers cannot say where they go.
No page language
The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.
Headings skip levels
Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.
1 checks passed
41 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 51 WCAG 2.2 A/AA and best-practice rules on the phone render: 41 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
Title is long (73 characters)
Your title is 73 characters, so Google will cut it off around 60: “Hiranandani Group | Top Real Estate Builders & Developers in Mumbai India”.
Structured data has 1 problem
Structured data found (Corporation and HomeAndConstructionBusiness) but with 1 problem, for example “ld+json block 2 is not valid JSON (Bad control character in string literal in JSON at position )”.
1 link crawlers can't follow
1 link has no real href, so search engines can't follow it.
1 link with vague text
1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.
Open Graph partly set
Open Graph is missing og:title and og:description, so shared links fall back to guesses.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
98 internal links, 12 external
The homepage links to 98 pages on hiranandani.com and 12 external pages.
5 checks passed
Meta description: 157 characters
Your meta description is 157 characters: “Hiranandani Group is one of the Top Real Estate Builders in Mumbai. The group is considered to be synonymous with quali…”.
One H1 headline
Your main headline reads: “About HIRANANDANI”.
Canonical URL set
The canonical URL is https://www.hiranandani.com/.
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.hiranandani.com/sitemap.xml.
AI search readiness
No llms.txt
There is no https://hiranandani.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 (613 words), so crawlers that don't run JavaScript still read it.
Other pages
2 pages share a title
https://hiranandani.com/media-press-release.aspx and https://hiranandani.com/referral.aspx all use the title “Hiranandani: Home”. Search engines can't tell which page to show for a search, so each competes with the others.
4 pages without a meta description
https://hiranandani.com/newsletter, https://hiranandani.com/media-press-release.aspx, https://hiranandani.com/referral.aspx and https://hiranandani.com/channel-partners.html have no meta description, so Google writes the search snippet from whatever text it finds.
3 pages without an H1
https://hiranandani.com/newsletter, https://hiranandani.com/referral.aspx and https://hiranandani.com/channel-partners.html have no <h1> headline, so visitors and search engines get no clear main topic.
1 page with very little text
https://hiranandani.com/newsletter has 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 55 found) and read each the way a search engine does.
4 checks passed
Linked pages load
14 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.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 14 pages that loaded have a <title>.
Best practices
11 small tap targets
11 of 31 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 “Failed to load resource: the server responded with a status of 404 ()”.
1 low-resolution image
1 image is served at too low a resolution for sharp phone screens.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Thin social proof
Social proof on the homepage: 1 customer or partner logo. Pairing it with named testimonials or customer logos makes it far more convincing.
A 24-field form
Your longest form asks for 24 fields (0 required). Every extra field lowers completion.
Phone number is not tap-to-call
Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.
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 473 words of copy
The homepage carries about 473 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: “CONTACT” and “LEARN MORE”.
7 calls to action
The homepage has 7 calls to action, for example “CONTACT”, “LEARN MORE” and “Contact”.
Analytics in place
Analytics detected: Google Tag Manager and Google Analytics.
Opening hours shown
Your opening hours are on the homepage.
Phone number on the homepage
Your phone number is on the homepage.
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 (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.
11 other companies contacted
Loading the homepage contacts 11 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 hiranandani.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
- Irinn Netranex As In Netranex Technologies India Private Limited
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 41 issues on hiranandani.com, including 14 speed issues, 4 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.