trojan.ae website review

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

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

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

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

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

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

20 images could be 17.1 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 load with your homepage (YouTube, Google CDN and jQuery CDN and others), adding 1.9 MB and 1.2 s of main-thread time.

YouTube costs a phone 563 ms of main-thread work and 960 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 costs a phone 507 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.

A phone's processor spends 3.7 s on main-thread work while loading, 2.2 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 226 ms. During a long task the page ignores taps.

4 KiB could be saved by minifying JavaScript.

The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

19 KiB could be saved by minifying CSS.

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.

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

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

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

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

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

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

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

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

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

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

Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 99 ms to 107 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 3.3 s to 3.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 27.8 MB in 90 requests on a phone: images 24.9 MB (42), scripts 1.6 MB (16) and stylesheets 388 KiB (13). Under 2 MB keeps phones on slow connections fast.

12 images weigh 21.7 MB together. On a phone connection a single image that size takes seconds.

14 images are downloaded at several times the size a phone draws them, for example nWSYzrIYDaIRIkVWeaaR.png at 2,850 px wide, shown at 390 px. Resized copies would save about 10.7 MB.

29 images (24.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.

14 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 7.88 g of CO₂e: 945.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

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

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

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

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

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

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

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

Your title is only 26 characters: “TROJAN GENERAL CONTRACTING”. 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.

There are 5 <h1> headlines (“PIONEERS IN SUSTAINABLE DESIGN AND CONSTRUCTION”, “OUR POTENTIAL, AMBITION AND DETERMINATION HAVE NO…” and “BUILDING LONG-TERM RELATIONSHIPS BASED ON INTEGRI…”). One clear main headline is easier for people and search engines.

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.

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

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

5 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 117 pages on trojan.ae and 22 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://trojan.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.

/, https://trojan.ae/about/tgc-profile, https://trojan.ae/about/ceo-message, https://trojan.ae/about/vision-and-mission, https://trojan.ae/about/our-people and https://trojan.ae/about/awards-and-certifications and 10 others all use the title “TROJAN GENERAL CONTRACTING”. Search engines can't tell which page to show for a search, so each competes with the others.

https://trojan.ae/about/tgc-profile, https://trojan.ae/about/ceo-message, https://trojan.ae/about/vision-and-mission, https://trojan.ae/about/our-people, https://trojan.ae/about/awards-and-certifications and https://trojan.ae/projects and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://trojan.ae/projects, https://trojan.ae/esg-reports and https://trojan.ae/qhse/esg-report took over 3 s to send their HTML from our server.

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

20 of 47 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.

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

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

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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

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

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