officeoneuae.com website review

Your mobile performance score is 64. Pages that score under 90 lose visitors before the first paint.

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

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

About 361 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 270 ms faster on a phone.

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

Bold Commerce costs a phone 277 ms of main-thread work and 454 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,580 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

8 third-party services load with your homepage (Bold Commerce, Google Tag Manager and Shopify and others), adding 902 KiB and 449 ms of main-thread time.

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

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

38 KiB could be saved by minifying JavaScript.

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

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

Your largest element takes 5.4 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 10.9 s. Good is under 3.8 s.

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

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

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

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

Your homepage downloads 2.2 MB in 209 requests on a phone: scripts 837 KiB (43), other files 734 KiB (91) and images 415 KiB (59). Under 2 MB keeps phones on slow connections fast.

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

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

1 button has no accessible name, so screen readers announce just “button”.

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

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

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

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.

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

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

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

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

The homepage links to 551 pages on officeoneuae.com and 7 external pages.

https://www.officeoneuae.com/collections/ballpoint-pens and https://www.officeoneuae.com/collections/fountain-pens-ink have no meta description, so Google writes the search snippet from whatever text it finds.

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

1 error was logged to the browser console while the page loaded, for example “Invalid left-hand side in assignment”.

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

The homepage carries about 1,082 words of visible text.

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