suncityprojects.com website review

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

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

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

Your mobile performance score is 56. Pages that score under 90 lose visitors before the first paint.

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

9 images could be 329 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 400 ms faster on a phone.

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

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

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

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

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

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

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

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

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.

3 KiB could be saved by minifying JavaScript.

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

Your largest element takes 9.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

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

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

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

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

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.

Your homepage downloads 57.0 MB in 156 requests on a phone: media 42.3 MB (6), images 11.7 MB (72) and scripts 2.0 MB (36). Under 2 MB keeps phones on slow connections fast.

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

18 images are downloaded at several times the size a phone draws them, for example 1760357889723-suncity-antara.jpg at 2,000 px wide, shown at 354 px. Resized copies would save about 3.4 MB.

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

4 images (2.8 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.

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

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

3 dropdowns have no label.

ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

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

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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

1 visible link has no text or label, so screen readers cannot say where it goes.

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

Your title is only 16 characters: “Suncity Projects”. Between 30 and 65 characters leaves room to say what you do and for whom.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

Your meta description is only 42 characters: “Suncity Projects - Real Estate Development”. 70 to 160 characters is enough to sell the click.

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

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

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 47 pages on suncityprojects.com and 16 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

There is no https://suncityprojects.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://suncityprojects.com/projects, https://suncityprojects.com/about-us, https://suncityprojects.com/nri-corner, https://suncityprojects.com/in-the-news and https://suncityprojects.com/press-release and 9 others all use the title “Suncity Projects”. Search engines can't tell which page to show for a search, so each competes with the others.

https://suncityprojects.com/projects, https://suncityprojects.com/about-us, https://suncityprojects.com/nri-corner, https://suncityprojects.com/in-the-news, https://suncityprojects.com/press-release and https://suncityprojects.com/events and 8 others use the same meta description. A description written for each page earns more clicks.

https://suncityprojects.com/projects, https://suncityprojects.com/in-the-news, https://suncityprojects.com/press-release, https://suncityprojects.com/events, https://suncityprojects.com/awards and https://suncityprojects.com/blogs and 5 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://suncityprojects.com/projects, https://suncityprojects.com/events, https://suncityprojects.com/blogs, https://suncityprojects.com/construction-updates and https://suncityprojects.com/projects/suncity-anantam 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.

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

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

Social proof on the homepage: 53 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

The homepage carries about 2,014 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Clarity (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 6 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 20 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.