shaheengroup.com website review

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

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

About 802 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 5.8 s faster on a phone.

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

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

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

8 third-party services load with your homepage (Google CDN, Google Tag Manager and Other Google APIs/SDKs and others), adding 1.6 MB and 946 ms of main-thread time.

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

Google CDN costs a phone 436 ms of main-thread work and 734 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 Tag Manager costs a phone 432 ms of main-thread work and 643 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.

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

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

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.

Your largest element takes 47.5 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 20.7 s (Speed Index). Good is under 3.4 s.

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

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

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

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

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 13.6 MB in 195 requests on a phone: images 11.1 MB (107), scripts 1.7 MB (37) and other files 353 KiB (8). Under 2 MB keeps phones on slow connections fast.

31 images are downloaded at several times the size a phone draws them, for example teamwork.jpg at 1,600 px wide, shown at 158 px. Resized copies would save about 3.7 MB.

4 images weigh 2.4 MB together. On a phone connection a single image that size takes seconds.

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

40 images further down the page (6.8 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 3.84 g of CO₂e: 461.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

3 elements use ARIA attributes their role does not allow, which confuses screen readers.

Certain ARIA roles must contain particular children: 3 elements on the page fail this check, rated critical by axe-core.

ARIA attributes must conform to valid values: 3 elements on the page fail this check, rated critical by axe-core.

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

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

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

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

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

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

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

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

1 form field has no label, so screen readers announce an empty box and autofill guesses.

The page declares lang=“lang=”, which is not a usable language code, so screen readers and translation tools guess.

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

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

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.

Your title is 66 characters, so Google will cut it off around 60: “Shaheen Group Bahrain - HVAC, firefighting, GRC, & Solar Solutions”.

The homepage links to 90 pages on shaheengroup.com and 8 external pages.

Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

https://www.shaheengroup.com/about-us, https://www.shaheengroup.com/about-us/our-history, https://www.shaheengroup.com/about-us/ceo-chairman-message, https://www.shaheengroup.com/about-us/certifications, https://www.shaheengroup.com/about-us/company-profile and https://www.shaheengroup.com/about-us/our-people and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.shaheengroup.com/about-us/certifications and https://www.shaheengroup.com/about-us/quality-policy have no <h1> headline, so visitors and search engines get no clear main topic.

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

1 image failed to load on a phone, for example https://www.shaheengroup.com/.

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

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

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

Before a visitor clicks anything, the page loads 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 (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 11 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.