unitedseo.ae website review

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

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

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

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

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

24 images could be 4.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

Hubspot costs a phone 761 ms of main-thread work and 753 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.

Facebook costs a phone 266 ms of main-thread work and 307 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 262 ms of main-thread work and 334 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 2,066 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

Google CDN costs a phone 129 ms of main-thread work and 347 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.

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

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

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

6 KiB could be saved by minifying JavaScript.

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 20.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “STOP SEARCHING. YOU’VE FOUND THE TOP SEO DUBAI AGENCY”. Most of its time is element render delay (8.3 s).

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

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

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

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

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

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

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

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

41 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-17, real Chrome visitors' tap response (inp) went from 260 ms to 274 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 10.9 MB in 181 requests on a phone: images 8.3 MB (95), scripts 2.2 MB (34) and fonts 247 KiB (16). Under 2 MB keeps phones on slow connections fast.

5 images weigh 3.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 1764137770.png at 1,200 px wide, shown at 347 px. Resized copies would save about 1.6 MB.

30 images (6.6 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.

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

1 dropdown has no label.

8 tap targets are too small or too close together to hit reliably with a finger.

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

1 image has no alt text, which hurts accessibility and image search.

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

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

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

Headings should not be empty: 3 elements on the page fail this check, rated minor by axe-core.

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

There are 2 <h1> headlines (“STOP SEARCHING. YOU’VE FOUND THE TOP SEO DUBAI AG…” and “STOP SEARCHING. YOU’VE FOUND THE TOP SEO DUBAI AG…”). One clear main headline is easier for people and search engines.

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

The homepage links to 163 pages on unitedseo.ae and 7 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.

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

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

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

Your homepage shows a map but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

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

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, HubSpot and Meta Pixel and 1 more (measured from a US location before any click). A consent tool (HubSpot cookie banner) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 12 cookies (measured from a US location before any click).

Loading the homepage contacts 37 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.