titansaudi.com website review

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

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

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

8 third-party services load with your homepage (Google Tag Manager, Optanon and Clarity and others), adding 996 KiB and 1.3 s of main-thread time.

28 images could be 1.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.

6 files are served with short cache lifetimes, so returning visitors download them again (77 KiB).

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

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

Optanon costs a phone 324 ms of main-thread work and 214 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,899 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

10 files block the first paint until they finish downloading. Deferring or inlining them could save about 250 ms.

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

About 22 KiB of CSS is downloaded but never applied on this page.

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 16.3 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 17.3 s. Good is under 3.8 s.

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

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

Real visitors wait 231 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

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

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

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

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

Your homepage downloads 4.7 MB in 263 requests on a phone: images 2.6 MB (72), scripts 1.0 MB (49) and other files 806 KiB (106). Under 2 MB keeps phones on slow connections fast.

Titan_Automatics_banner_Mobile_webp.webp weighs 780 KiB. On a phone connection a single image that size takes seconds.

13 images (1.5 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.

Titan_Automatics_banner_Mobile_webp.webp is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

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

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

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

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

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

ARIA role should be appropriate for the element: 11 elements on the page fail this check, rated minor by axe-core.

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

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

Your title is 70 characters, so Google will cut it off around 60: “Shop Premium Watches for Men & Women - Titan Watches UAE – Titan Saudi”.

Your meta description is 224 characters; Google truncates after about 160, so the end of your pitch is cut.

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

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

Your <h1> is empty.

The homepage links to 182 pages on titansaudi.com and 4 external pages.

https://titansaudi.com/products/black-aviator-men-sunglasses-m062gr2 and https://titansaudi.com/products/black-aviator-men-sunglasses-m138bk3 all use the title “Black Aviator Men Sunglasses – Titan Saudi”. Search engines can't tell which page to show for a search, so each competes with the others.

https://titansaudi.com/collections/%D8%B1%D8%AC%D8%A7%D9%84%D9%8A, https://titansaudi.com/collections/%D9%86%D8%B3%D8%A7%D8%A6%D9%8A-1, https://titansaudi.com/products/black-navigator-rimmed-sunglasses-from-fastrack-m253gy11v, https://titansaudi.com/products/black-wayfarer-men-sunglasses-p413gr1p, https://titansaudi.com/collections/%D8%AC%D9%88%D9%84%D8%A9 and https://titansaudi.com/collections/rectangle and 3 others have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 6 pages by a URL that isn't their canonical one, for example https://titansaudi.com/collections/%D8%B1%D8%AC%D8%A7%D9%84%D9%8A, whose canonical is https://titansaudi.com/collections/%d8%b1%d8%ac%d8%a7%d9%84%d9%8a. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://titansaudi.com/collections/%D8%B1%D8%AC%D8%A7%D9%84%D9%8A, https://titansaudi.com/collections/%D9%86%D8%B3%D8%A7%D8%A6%D9%8A-1, https://titansaudi.com/products/black-aviator-men-sunglasses-m062gr2, https://titansaudi.com/products/black-navigator-rimmed-sunglasses-from-fastrack-m253gy11v, https://titansaudi.com/products/black-wayfarer-men-sunglasses-p413gr1p and https://titansaudi.com/products/gold-aviator-men-sunglasses-m165gr8p-57 and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

4 errors were logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'querySelector')”.

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

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 testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

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

The homepage has only about 56 words of visible text; thin pages give Google and first-time buyers little to go on.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

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

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

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