Website review, no card needed

propertystation.in logo

propertystation.in website review

Visit site (opens in a new tab)Reviewed 22 October 202627 issues · 76 checks

This review found 27 issues worth fixing on propertystation.in, 8 of them high impact, across 76 checks. The most urgent: use efficient cache lifetimes. 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
2.1 s1.3 sMay 9Sep 121.8 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20261.5 s
May 16, 20261.4 s
May 23, 20261.4 s
May 30, 20261.5 s
Jun 6, 20261.6 s
Jun 13, 20261.7 s
Jun 20, 20261.8 s
Jun 27, 20261.9 s
Jul 4, 20262.0 s
Jul 11, 20262.0 s
Jul 18, 20261.9 s
Jul 25, 20261.9 s
Aug 1, 20261.9 s
Aug 8, 20261.9 s
Aug 15, 20261.9 s
Aug 22, 20261.9 s
Aug 29, 20261.7 s
Sep 5, 20261.7 s
Sep 12, 20261.8 s
Real-visitor tap response (INP)75th percentile, phones
189 ms112 msMay 16Sep 12125 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026147 ms
May 23, 2026148 ms
May 30, 2026160 ms
Jun 6, 2026160 ms
Jun 13, 2026180 ms
Jun 20, 2026169 ms
Jun 27, 2026143 ms
Jul 4, 2026147 ms
Jul 11, 2026155 ms
Jul 18, 2026161 ms
Jul 25, 2026155 ms
Aug 1, 2026151 ms
Aug 8, 2026136 ms
Aug 15, 2026127 ms
Aug 22, 2026132 ms
Aug 29, 2026121 ms
Sep 5, 2026125 ms
Sep 12, 2026125 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 propertystation.in (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. propertystation.in at 0.4 s0.4 s
  2. propertystation.in at 0.8 s0.8 s
  3. propertystation.in at 1.1 s1.1 s
  4. propertystation.in at 1.5 s1.5 s
  5. propertystation.in at 1.9 s1.9 s
  6. propertystation.in at 2.3 s2.3 s
  7. propertystation.in at 2.6 s2.6 s
  8. propertystation.in at 3.0 s3.0 s

Speed

5 to fix68
  • Use efficient cache lifetimes

    1.8 s · 1.2 MB

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

  • Improve image delivery

    900 ms · 8.0 MB

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

  • Mobile performance score: 68

    68/100

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

  • Reduce unused JavaScript

    300 ms · 405 KiB

    About 405 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.

  • 2,428 HTML elements

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

  • 7 third-party services on the page

    7 third-party services load with your homepage (firebaseapp.com, Other Google APIs/SDKs and Google CDN and others), adding 469 KiB and 70 ms of main-thread time.

  • Reduce unused CSS

    15 KiB

    About 15 KiB of CSS is downloaded but never applied on this page.

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

2 checks passed
  • Main-thread work: 0.8 s

    A phone's processor spends 0.8 s on main-thread work while loading, 145 ms of it running JavaScript. That is comfortably low.

  • Server response: 35 ms

    35 ms

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

Core Web Vitals

5 to fix67
  • Largest Contentful Paint: 18.4 s

    18.4 s

    Your largest element takes 18.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Luxury Residential Projects in Gurgaon - Explore New Launch…”.

  • Time to Interactive: 18.5 s

    18.5 s

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

  • First Contentful Paint: 3.2 s

    3.2 s

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

  • Largest content (LCP) got 23% slower for real visitors

    +23%

    Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 1.5 s to 1.8 s 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.

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

4 checks passed
  • Tap response (INP) got 15% faster for real visitors

    -15%

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

  • Speed Index: 3.4 s

    3.4 s

    Visually, the page fills in at 3.4 s (Speed Index), inside the 3.4 s “good” threshold.

  • Cumulative Layout Shift: 0.001

    0.001

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

  • Total Blocking Time: 0 ms

    0 ms

    Scripts block the page for only 0 ms while loading. Good is under 200 ms.

Images and page weight

3 to fix35
  • Page weight: 11.7 MB in 215 requests

    11.7 MB

    Your homepage downloads 11.7 MB in 215 requests on a phone: images 11.3 MB (194), scripts 209 KiB (12) and fonts 103 KiB (2). Under 2 MB keeps phones on slow connections fast.

  • 2 images over 500 KB

    2 images weigh 2.7 MB together. On a phone connection a single image that size takes seconds.

  • 3 images far larger than shown

    1.6 MB

    3 images are downloaded at several times the size a phone draws them, for example sobha-sector-63a.webp at 6,400 px wide, shown at 270 px. Resized copies would save about 1.6 MB.

  • 1 image below the first screen load straight away

    1 image further down the page (28 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 3.3 g of CO₂ per visit

    3.32 g

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

1 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

Accessibility

4 to fixGoogle 9595
  • All page content should be contained by landmarks (195 elements)

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

  • 5 form fields without a label

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

  • Elements with role="dialog" or role="alertdialog" do not have accessible names.

    Elements with role="dialog" or role="alertdialog" do not have accessible names. (1 element).

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 283 images in the HTML carry an alt attribute.

  • 34 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 37 WCAG 2.2 A/AA and best-practice rules on the phone render: 34 passed and 3 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

5 to fixGoogle 8384
  • Meta description is long (203 characters)

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

  • Structured data has 1 problem

    Structured data found (BreadcrumbList, FAQPage, LocalBusiness and Organization) but with 1 problem, for example “Organization: sameAs is an empty list”.

  • No robots.txt

    There is no robots.txt at propertystation.in/robots.txt, the first file search crawlers ask for.

  • 4 links crawlers can't follow

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

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

  • 164 internal links, 13 external

    The homepage links to 164 pages on propertystation.in and 13 external pages.

5 checks passed
  • One H1 headline

    Your main headline reads: “Property Station - Best Real Estate Consultant in Gurgaon | Zero Brokerage”.

  • Title: 65 characters

    Your title is a healthy 65 characters: “Property Station - Zero Brokerage Real Estate Consultant, Gurgaon”.

  • Canonical URL set

    The canonical URL is https://www.propertystation.in/.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.propertystation.in/sitemap.xml.

AI search readiness

100
  • No llms.txt

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

    There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading the site and cite it in answers.

  • Organization data: 4 of 6 facts

    Your Organization JSON-LD gives name, url, logo and contact details; sameAs (social profiles) and description would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (2,442 words), so crawlers that don't run JavaScript still read it.

Other pages

1 to fix95
  • 3 pages without a meta description

    https://www.propertystation.in/gurgaon, https://www.propertystation.in/pune and https://www.propertystation.in/blogs 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 78 found) and read each the way a search engine does.

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

  • 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

3 to fixGoogle 9276
  • 3 broken images

    3 images failed to load on a phone, for example https://www.propertystation.in/images/banner/home-desktop-cover-mobile-4.webp.

  • 171 distorted images

    171 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

  • 4 JavaScript errors while loading

    4 errors were logged to the browser console while the page loaded, for example “X-Frame-Options may only be set via an HTTP header sent along with a document. It may not be set inside <meta>.”.

2 checks passed
  • Tap targets are thumb-sized

    12 of 12 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix94
  • No analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • About 1,448 words of copy

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

8 checks passed
  • Clear next step on the first screen

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

  • 4 calls to action

    The homepage has 4 calls to action, for example “Contact Us”, “Let's Schedule a Call →” and “Call Now”.

  • 1 short form

    A short form (5 fields at most) is right on the homepage, asking for an email.

  • Social proof on the page

    Social proof on the homepage: 1 testimonial or review block and “5,000+ Clients”.

  • Direct contact links

    Visitors can reach you directly: 4 phone links and 1 email link.

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

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

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.

  • 8 other companies contacted

    Loading the homepage contacts 8 hosts 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 propertystation.in, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
Tailwind CSS

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 27 issues on propertystation.in, including 10 speed issues, 5 SEO issues 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

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