shebacoffee.com website review

3 images could be 268 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.0 s faster on a phone.

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

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

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

8 third-party services load with your homepage (Hotjar, Klaviyo and Shopify and others), adding 582 KiB and 193 ms of main-thread time.

1 long task block the main thread while loading, the longest for 91 ms. During a long task the page ignores taps.

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

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

3 KiB could be saved by minifying JavaScript.

2 KiB JavaScript is shipped twice across bundles.

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

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 2.0 MB in 193 requests on a phone: other files 746 KiB (84), scripts 599 KiB (85) and images 426 KiB (4). Under 2 MB keeps phones on slow connections fast.

Sheba-coffee---home-page.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).

1 image is downloaded at several times the size a phone draws it, for example ShebaCoffee_-_the_burthplace_of_coffee.png at 11,238 px wide, shown at 225 px. Resized copies would save about 161 KiB.

1 image (162 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 0.58 g of CO₂e: 69.1 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.

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

Links must have discernible text: 2 elements on the page fail this check, rated serious by axe-core.

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

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.

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

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

Your title is only 26 characters: “Sheba Coffee – ShebaCoffee”. Between 30 and 65 characters leaves room to say what you do and for whom.

Your meta description is only 37 characters: “Rare and Exquisite Speciality Coffees”. 70 to 160 characters is enough to sell the click.

There are 2 <h1> headlines (“Shop Sheba” and “Explore Sheba”). One clear main headline is easier for people and search engines.

The homepage links to 39 pages on shebacoffee.com and 12 external pages.

Your Organization JSON-LD is missing logo, sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

https://shebacoffee.com/pages/yemen and https://shebacoffee.com/pages/yemen-n all use the title “Yemen – ShebaCoffee”. Search engines can't tell which page to show for a search, so each competes with the others.

https://shebacoffee.com/pages/auction-2023, https://shebacoffee.com/collections/sheba-shop, https://shebacoffee.com/pages/yemen, https://shebacoffee.com/pages/ethiopia, https://shebacoffee.com/pages/annual-auctions and https://shebacoffee.com/pages/auction-2022-n and 6 others have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://shebacoffee.com/pages/yemen-n, whose canonical is https://shebacoffee.com/pages/yemen. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://shebacoffee.com/collections/sheba-shop, https://shebacoffee.com/pages/our-story and https://shebacoffee.com/pages/annual-auctions have no <h1> headline, so visitors and search engines get no clear main topic.

https://shebacoffee.com/pages/yemen-n, https://shebacoffee.com/policies/refund-policy and https://shebacoffee.com/policies/terms-of-service took over 3 s to send their HTML from our server.

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

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

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

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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 65 words of visible text; thin pages give Google and first-time buyers little to go on.

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 Analytics, Google Tag Manager, Hotjar, Klaviyo 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 (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 18 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.