Website review, no card needed

casagrande.in logo

casagrande.in website review

Visit site (opens in a new tab)Reviewed 3 November 202660 issues · 105 checks

This review found 60 issues worth fixing on casagrande.in, 27 of them high impact, across 105 checks. The most urgent: reduce unused JavaScript. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
3.9 s2.6 sMay 16Oct 313.4 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20263.8 s
May 23, 20263.4 s
May 30, 20263.0 s
Jun 6, 20262.9 s
Jun 13, 20262.7 s
Jun 20, 20262.9 s
Jun 27, 20263.0 s
Jul 4, 20263.1 s
Jul 11, 20263.2 s
Jul 18, 20263.3 s
Jul 25, 20263.2 s
Aug 1, 20263.2 s
Aug 8, 20263.2 s
Aug 15, 20263.1 s
Aug 22, 20263.2 s
Aug 29, 20263.2 s
Sep 5, 20263.2 s
Sep 12, 20263.2 s
Sep 19, 20263.2 s
Sep 26, 20263.1 s
Oct 3, 20263.0 s
Oct 10, 20262.9 s
Oct 17, 20262.9 s
Oct 24, 20263.0 s
Oct 31, 20263.4 s
Real-visitor tap response (INP)75th percentile, phones
497 ms184 msMay 16Oct 31461 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026281 ms
May 23, 2026238 ms
May 30, 2026222 ms
Jun 6, 2026225 ms
Jun 13, 2026220 ms
Jun 20, 2026222 ms
Jun 27, 2026225 ms
Jul 4, 2026228 ms
Jul 11, 2026233 ms
Jul 18, 2026237 ms
Jul 25, 2026243 ms
Aug 1, 2026267 ms
Aug 8, 2026301 ms
Aug 15, 2026340 ms
Aug 22, 2026372 ms
Aug 29, 2026390 ms
Sep 5, 2026399 ms
Sep 12, 2026403 ms
Sep 19, 2026405 ms
Sep 26, 2026410 ms
Oct 3, 2026419 ms
Oct 10, 2026430 ms
Oct 17, 2026442 ms
Oct 24, 2026446 ms
Oct 31, 2026461 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

Full-page screenshot of casagrande.in (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. casagrande.in at 1.5 s1.5 s
  2. casagrande.in at 3.1 s3.1 s
  3. casagrande.in at 4.6 s4.6 s
  4. casagrande.in at 6.2 s6.2 s
  5. casagrande.in at 7.7 s7.7 s
  6. casagrande.in at 9.3 s9.3 s
  7. casagrande.in at 10.8 s10.8 s
  8. casagrande.in at 12.3 s12.3 s

Speed

15 to fix28
  • Reduce unused JavaScript

    13.3 s · 2.8 MB

    About 2.8 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 13.3 s faster on a phone.

  • Use efficient cache lifetimes

    2.7 s · 617 KiB

    28 files are served with short cache lifetimes, so returning visitors download them again (617 KiB).

  • Google Tag Manager adds 2.3 s

    2.3 s

    Google Tag Manager costs a phone 2.3 s of main-thread work and 3.9 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.

  • Render-blocking requests

    1.9 s

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

  • Reduce unused CSS

    1.0 s · 142 KiB

    About 142 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.0 s faster on a phone.

  • Mobile performance score: 28

    28/100

    Your mobile performance score is 28. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • Main-thread work: 8.0 s

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

  • Improve image delivery

    150 ms · 20.2 MB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Facebook and Google CDN and others), adding 6.1 MB and 3.6 s of main-thread time.

  • 20 long tasks on the main thread

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

  • Facebook adds 457 ms

    457 ms

    Facebook costs a phone 457 ms of main-thread work and 478 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 310 ms

    310 ms

    Google CDN costs a phone 310 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.

  • Legacy JavaScript

    300 ms · 39 KiB

    Polyfills for old browsers add 39 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 300 ms faster on a phone.

  • 2,701 HTML elements

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

  • livserv.in adds 115 ms

    115 ms

    livserv.in costs a phone 115 ms of main-thread work and 350 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.

  • Font display

    100 ms

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

  • Minify JavaScript

    17 KiB

    17 KiB could be saved by minifying JavaScript.

  • Minify CSS

    8 KiB

    8 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.

1 checks passed
  • Server response: 19 ms

    19 ms

    Your server sent the HTML in 19 ms, well inside Google's 600 ms guideline.

Core Web Vitals

12 to fix33
  • 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: 6.4 s

    6.4 s

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

  • Real-user INP: 616 ms

    616 ms

    Real visitors wait 616 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user FCP: 5.5 s

    5.5 s

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

  • Real-user TTFB: 5.2 s

    5.2 s

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

  • Largest Contentful Paint: 162.9 s

    162.9 s

    Your largest element takes 162.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “By using or accessing the website, you agree to the Disclai…”.

  • Speed Index: 32.7 s

    32.7 s

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

  • Time to Interactive: 164.9 s

    164.9 s

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

  • Total Blocking Time: 2.4 s

    2.4 s

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

  • First Contentful Paint: 4.3 s

    4.3 s

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

  • Tap response (INP) got 75% slower for real visitors

    +75%

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

  • 2 images without width and height

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

3 checks passed
  • Real-user CLS: 0.10

    0.10

    For real visitors the layout shifts by 0.10 (75th percentile). Good is under 0.1.

  • Largest content (LCP) got 11% faster for real visitors

    -11%

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

  • Cumulative Layout Shift: 0.044

    0.044

    The layout barely moves while loading (CLS 0.044, good is under 0.1).

Images and page weight

6 to fix19
  • Page weight: 97.9 MB in 313 requests

    97.9 MB

    Your homepage downloads 97.9 MB in 313 requests on a phone: images 90.6 MB (102), scripts 6.1 MB (103) and other files 672 KiB (79). Under 2 MB keeps phones on slow connections fast.

  • 23 images over 500 KB

    23 images weigh 80.8 MB together. On a phone connection a single image that size takes seconds.

  • 26 images far larger than shown

    35.1 MB

    26 images are downloaded at several times the size a phone draws them, for example Standard.jpeg at 5,472 px wide, shown at 338 px. Resized copies would save about 35.1 MB.

  • 40 images in older formats

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

  • 20 images below the first screen load straight away

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

  • An image on the first screen is lazy-loaded

    PVF-Web-banner_750-x-600-RI.jpg 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).

  • About 27.8 g of CO₂ per visit

    27.76 g

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

Accessibility

14 to fixGoogle 7082
  • Unlabelled dropdowns

    1 dropdown has no label.

  • 36 text elements with low contrast

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

  • ARIA input fields must have an accessible name (8 elements)

    ARIA input fields must have an accessible name: 8 elements on the page fail this check, rated serious by axe-core.

  • Interactive controls must not be nested (3 elements)

    Interactive controls must not be nested: 3 elements on the page fail this check, rated serious by axe-core.

  • <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.

  • Scrollable region must have keyboard access (1 element)

    Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

  • 4 images without alt text

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

  • All page content should be contained by landmarks (29 elements)

    All page content should be contained by landmarks: 29 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.

  • 52 form fields without a label

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

  • 2 links without text

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

  • Hidden but focusable

    1 element hidden from screen readers can still receive keyboard focus.

  • No page language

    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 (4 elements)

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

  • Headings skip levels

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

1 checks passed
  • 44 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 57 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 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

4 to fixGoogle 8584
  • Title is long (72 characters)

    Your title is 72 characters, so Google will cut it off around 60: “Casagrand: Real Estate Developers in South India | Top Builders in India”.

  • Meta description is long (168 characters)

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

  • 12 links crawlers can't follow

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

  • No favicon declared

    No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

  • 263 internal links, 71 external

    The homepage links to 263 pages on casagrande.in and 71 external pages.

6 checks passed
  • One H1 headline

    Your main headline reads: “DISCLAIMER”.

  • Canonical URL set

    The canonical URL is https://www.casagrand.co.in/.

  • Structured data in place

    Structured data found: ItemList, Organization and VideoObject.

  • 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.casagrand.co.in/sitemap.xml.

AI search readiness

100
  • No llms.txt

    There is no https://www.casagrand.co.in/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 (2,215 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix88
  • 4 linked pages hidden from search

    https://www.casagrand.co.in/media/awards, https://www.casagrand.co.in/media/newsletter, https://www.casagrand.co.in/media/press-release and https://www.casagrand.co.in/media/videos are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

  • 2 pages without an H1

    https://www.casagrand.co.in/residential-projects and https://www.casagrand.co.in/media/press-release have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 181 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.

  • 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 a title

    All 15 pages that loaded have a <title>.

Best practices

4 to fixGoogle 6983
  • 6 small tap targets

    6 of 19 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to…”).

  • 6 JavaScript errors while loading

    6 errors were logged to the browser console while the page loaded, for example “$(...).modal is not a function”.

  • 1 distorted image

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

  • 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

2 to fix88
  • 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.

  • A 8-field form

    Your longest form asks for 8 fields (0 required). Every extra field lowers completion.

  • 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,574 words of copy

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

  • Urgency cues

    The page uses urgency cues (a countdown or limited-time wording).

6 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Enquire Now” and “Call Now”.

  • 7 calls to action

    The homepage has 7 calls to action, for example “Contact Us”, “CALL US” and “Rent Vs Buy”.

  • Social proof on the page

    Social proof on the homepage: 10 customer or partner logos, 14 trust badges and “55K+ Customers”.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics, Meta Pixel and LinkedIn Insight.

  • Direct contact links

    Visitors can reach you directly: 24 phone links and 0 email links.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

Privacy and tracking

1 to fix
  • 8 trackers load before any consent

    8

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, LinkedIn Insight and Meta Pixel and 3 mores (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.

  • 25 cookies set on arrival

    25

    Opening the homepage sets 25 cookies, 2 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.

  • 48 other companies contacted

    Loading the homepage contacts 48 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 casagrande.in, 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
Hosting
AWS

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 60 issues on casagrande.in, including 27 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25