rawcoffee.ae website review

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

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

7 third-party services load with your homepage (Bold Commerce, Shopify and smile.io and others), adding 1.5 MB and 468 ms of main-thread time.

About 451 KiB of JavaScript is downloaded but never used on this page.

13 images could be 376 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

Bold Commerce costs a phone 222 ms of main-thread work and 484 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.

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

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

The page has 1,753 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

Shopify costs a phone 119 ms of main-thread work and 529 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.

smile.io costs a phone 71 ms of main-thread work and 361 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.

Polyfills for old browsers add 26 KiB JavaScript that modern phones do not need.

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

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

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

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

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

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

Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 104 ms to 96 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 1.7 s to 1.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 3.6 MB in 261 requests on a phone: images 1.2 MB (36), scripts 1.2 MB (72) and other files 839 KiB (113). Under 2 MB keeps phones on slow connections fast.

RAW-Coffee-Company_Mexican-Trifecta-Mobile-Banner.jpg 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).

3 images are downloaded at several times the size a phone draws them, for example RAWCoffeeCompany_BrandPillar_Local.png at 1,920 px wide, shown at 240 px. Resized copies would save about 203 KiB.

3 images further down the page (237 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

1 image (31 KiB) is 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.

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

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

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

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

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

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

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

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

Your title is 74 characters, so Google will cut it off around 60: “RAW Coffee Company | 100% Direct & Ethically Traded | Roasted in Dubai”.

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

Your <h1> is empty.

The homepage links to 98 pages on rawcoffee.ae and 20 external pages.

https://rawcoffeecompany.com/blogs/blogs, https://rawcoffeecompany.com/pages/our-cafe, https://rawcoffeecompany.com/collections/coffee, https://rawcoffeecompany.com/pages/manage-subscriptions, https://rawcoffeecompany.com/collections/cafe-goods and https://rawcoffeecompany.com/collections/milklab-non-dairy-milk and 7 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://rawcoffeecompany.com/pages/our-story, https://rawcoffeecompany.com/pages/our-cafe and https://rawcoffeecompany.com/pages/subscriptions have no <h1> headline, so visitors and search engines get no clear main topic.

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 410 ()”.

Chrome logged issues while loading the page (“Content security policy”).

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

The page uses urgency cues (a countdown or limited-time wording).

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 12 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 16 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.