raheja.com website review

10 files block the first paint until they finish downloading. Deferring or inlining them could save about 3.3 s.

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 1.1 s).

145 files are served with short cache lifetimes, so returning visitors download them again (28.1 MB).

107 images could be 17.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 250 ms faster on a phone.

8 third-party services load with your homepage (Google Tag Manager, Facebook and cloudfront.net and others), adding 1.0 MB and 916 ms of main-thread time.

Your mobile performance score is 63 (desktop: 67). Pages that score under 90 lose visitors before the first paint.

Google Tag Manager costs a phone 615 ms of main-thread work and 670 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.

About 94 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.

About 387 KiB of JavaScript is downloaded but never used on this page.

A phone's processor spends 3.8 s on main-thread work while loading, 1.0 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

The page has 2,563 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

10 long tasks block the main thread while loading, the longest for 245 ms. During a long task the page ignores taps.

41 KiB could be saved by minifying JavaScript.

14 KiB could be saved by minifying CSS.

Polyfills for old browsers add 12 KiB JavaScript that modern phones do not need.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

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.

The page becomes fully interactive after 29.1 s. Good is under 3.8 s.

Visually, the page fills in at 13.3 s (Speed Index). Good is under 3.4 s.

The first text or image appears after 3.1 s on a phone. Good is under 1.8 s.

Real visitors wait 2.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.

Real visitors see the first content after 2.1 s (75th percentile). Good is under 1.8 s.

Real visitors wait 1.2 s for your server to start answering (75th percentile). Good is under 800 ms.

Your largest element takes 4.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Raheja Developers is one of the largest Real Estate compani…”. Most of its time is element render delay (4.5 s).

Scripts block taps and scrolling for 394 ms in total while the page loads. Good is under 200 ms.

2 images have no width and height attributes, so the layout jumps as each one loads.

Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 116 ms to 142 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 1.9 s to 2.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 30.6 MB in 203 requests on a phone: images 27.3 MB (127), scripts 2.0 MB (32) and stylesheets 478 KiB (16). Under 2 MB keeps phones on slow connections fast.

10 images weigh 18.7 MB together. On a phone connection a single image that size takes seconds.

35 images are downloaded at several times the size a phone draws them, for example Aerial Night View (1)20260713152051.jpg at 4,200 px wide, shown at 340 px. Resized copies would save about 11.6 MB.

40 images (26.1 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.

37 images further down the page (19.7 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

By the Sustainable Web Design model, a visit to your homepage emits about 8.66 g of CO₂e: 1039.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

14 buttons have no accessible name, so screen readers announce just “button”.

Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

1 dropdown has no label.

31 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

6 tap targets are too small or too close together to hit reliably with a finger.

ARIA input fields must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

<html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

163 images have no alt text, which hurts accessibility and image search.

All page content should be contained by landmarks: 43 elements on the page fail this check, rated moderate by axe-core.

109 visible links have no text or label, so screen readers cannot say where they go.

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

11 form fields have no label, so screen readers announce an empty box and autofill guesses.

The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

ARIA role should be appropriate for the element: 8 elements on the page fail this check, rated minor by axe-core.

Elements marked as presentational should be consistently ignored: 8 elements on the page fail this check, rated minor by axe-core.

Headings skip levels (h2 → h5, h2 → h5 and h2 → h4), which makes the page harder to scan with a screen reader.

There are 2 <h1> headlines (“Legacy of Raheja” and “Leela Sky Villas By Raheja Developers: Space, Exc…”). One clear main headline is easier for people and search engines.

Your meta description is 179 characters; Google truncates after about 160, so the end of your pitch is cut.

5 links have no real href, so search engines can't follow them.

2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

The homepage links to 168 pages on raheja.com and 56 external pages.

There is no https://raheja.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.

https://raheja.com/projects/new-launch, https://raheja.com/residential, https://raheja.com/projects/ready-to-move-resdential, https://raheja.com/projects/resdential-under-construction, https://raheja.com/projects/plotted-developer and https://raheja.com/projects/affordable and 1 other declare the homepage as their canonical URL, which tells Google they are copies of the homepage and keeps them out of search results. A site-wide template setting usually causes this.

https://raheja.com/projects/new-launch, https://raheja.com/projects/ready-to-move-resdential, https://raheja.com/projects/resdential-under-construction, https://raheja.com/projects/plotted-developer, https://raheja.com/projects/affordable and https://raheja.com/projects/premium-projects all use the title “Raheja Project List”. Search engines can't tell which page to show for a search, so each competes with the others.

https://raheja.com/projects/new-launch, https://raheja.com/residential, https://raheja.com/projects/ready-to-move-resdential, https://raheja.com/projects/resdential-under-construction, https://raheja.com/projects/plotted-developer and https://raheja.com/projects/affordable and 1 other use the same meta description. A description written for each page earns more clicks.

https://raheja.com/company-overview.html, https://raheja.com/company-vision.html, https://raheja.com/company-logo.html, https://raheja.com/company-awards.html, https://raheja.com/ar-nayan-raheja.html and https://raheja.com/navin-m-raheja.html and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

We fetched 15 pages linked from your homepage (of 78 found) and read each the way a search engine does.

2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

There is no form on the homepage, so every lead has to click through to another page first.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 1,860 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager 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.

Opening the homepage sets 5 cookies (measured from a US location before any click).

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.

Loading the homepage contacts 21 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.