cscec.ae website review

9 images could be 2.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 11.2 s faster on a phone.

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

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

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

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

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

6 third-party services load with your homepage (YouTube, Google Tag Manager and Google Analytics and others), adding 2.2 MB and 722 ms of main-thread time.

YouTube costs a phone 628 ms of main-thread work and 1.9 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.

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

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

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

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

Polyfills for old browsers add 9 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.

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

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

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

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

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

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

The layout shifts by 0.331 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

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

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

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

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

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

Your homepage downloads 15.8 MB in 360 requests on a phone: images 13.0 MB (196), scripts 2.2 MB (121) and stylesheets 232 KiB (18). Under 2 MB keeps phones on slow connections fast.

39 images (3.7 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 4.49 g of CO₂e: 538.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

Document should not have more than one contentinfo landmark: 1 element on the page fails this check, rated moderate by axe-core.

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

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

No meta description, so Google writes its own snippet from whatever text it finds.

There is no <h1>, so neither visitors nor Google get a clear main headline.

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

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

Your title is 81 characters, so Google will cut it off around 60: “China State Construction Middle East – Leading Investment and Construction Groups”.

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

No XML sitemap at https://www.cscec.ae/sitemap.xml, so Google discovers your pages only by following links.

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 220 pages on cscec.ae and 0 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://www.cscec.ae/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.

Your homepage links to https://www.cscec.ae/contact-suppliers, https://www.cscec.ae/china-state-construction-engineering-career-section, https://www.cscec.ae/jobs, https://www.cscec.ae/contact-general-inquiry/contact-general and https://www.cscec.ae/cscec-me-won-the-infrastructure-contractor-of-the-year-award-and-offsite-construction-project-of-the-year, which answer with an error. Visitors hit a dead end and search engines drop them.

https://www.cscec.ae/about-china-state-construction-middle-east-2, https://www.cscec.ae/china-construction-middle-east-company-awards, https://www.cscec.ae/china-construction-middle-east-project-awards, https://www.cscec.ae/about-china-state-construction-middle-east-2/china-state-construction-middle-east-capabilities, https://www.cscec.ae/about-china-state-construction-middle-east-2/china-state-construction-middle-east-sustainability-3 and https://www.cscec.ae/about-china-state-construction-middle-east-2/china-state-construction-middle-east-community and 4 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.cscec.ae/about-china-state-construction-middle-east-2, https://www.cscec.ae/about-china-state-construction-middle-east-2/china-state-construction-middle-east-capabilities, https://www.cscec.ae/about-china-state-construction-middle-east-2/china-state-construction-middle-east-sustainability-3, https://www.cscec.ae/about-china-state-construction-middle-east-2/china-state-construction-middle-east-community, https://www.cscec.ae/china-state-construction-news and https://www.cscec.ae/china-state-construction-media have no <h1> headline, so visitors and search engines get no clear main topic.

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

3 images failed to load on a phone, for example https://www.cscec.ae/.

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

5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 500 ()”.

Chrome logged issues while loading the page (“Cookie”).

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

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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 7,073 words of visible text.

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

Opening the homepage sets 5 cookies, 1 of them by other companies (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 12 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.