okaje.com website review

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

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

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

20 images could be 382 KiB 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.

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

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

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

8 third-party services load with your homepage (Google CDN, gravity-software.com and Shopify and others), adding 588 KiB and 401 ms of main-thread time.

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

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

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

9 KiB could be saved by minifying JavaScript.

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

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

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

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

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

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

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

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 3.4 MB in 212 requests on a phone: images 1.6 MB (37), other files 838 KiB (117) and scripts 795 KiB (40). Under 2 MB keeps phones on slow connections fast.

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

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

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children. (2 elements).

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

8 elements hidden from screen readers can still receive keyboard focus.

ARIA input fields do not have accessible names (3 elements).

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

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

ARIA toggle fields do not have accessible names (1 element).

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

Elements with role="none" or role="presentation" have conflicts (2 elements).

Your title is only 24 characters: “Okaje Building Materials”. 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.

Your meta description is only 53 characters: “Wood and veneer supplier founded in Dubai since 2017.”. 70 to 160 characters is enough to sell the click.

There are 8 <h1> headlines (“”, “WOOD IS GOOD” and “NATURAL VENEER”). One clear main headline is easier for people and search engines.

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

The homepage links to 125 pages on okaje.com and 9 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.

Your homepage links to https://www.okaje.com/pages/laminates, which answers with an error. Visitors hit a dead end and search engines drop it.

https://www.okaje.com/pages/catalogue-request, https://www.okaje.com/blogs/certification, https://www.okaje.com/collections/natural-veneer, https://www.okaje.com/collections/engineered-veneer, https://www.okaje.com/collections/laminates and https://www.okaje.com/collections/all have no meta description, so Google writes the search snippet from whatever text it finds.

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

2 errors were logged to the browser console during Google's test (“Failed to load resource: the server responded with a status of 404 (Not Found)”).

Social proof on the homepage: 7 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

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

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

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