oliveole.com website review

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

4 images could be 2.0 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

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

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

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

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

8 third-party services load with your homepage (Klaviyo, POWr and Hexton and others), adding 291 KiB and 171 ms of main-thread time.

About 35 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 50 ms).

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

2 KiB could be saved by minifying JavaScript.

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.

For real visitors the layout shifts by 0.33 (75th percentile). Good is under 0.1.

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

The layout shifts by 0.315 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

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

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

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

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

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

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

Your homepage downloads 3.5 MB in 149 requests on a phone: images 2.2 MB (12), other files 704 KiB (77) and scripts 476 KiB (51). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example store_x800.png at 1,339 px wide, shown at 390 px. Resized copies would save about 36 KiB.

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

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

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

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

Your title is only 21 characters: “Olive Olé – Olive Ole”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

Your <h1> is empty.

The homepage links to 31 pages on oliveole.com and 4 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://oliveole.com/pages/size-guide, which answers with an error. Visitors hit a dead end and search engines drop it.

https://oliveole.com/pages/career, https://oliveole.com/policies/terms-of-service and https://oliveole.com/policies/privacy-policy have no meta description, so Google writes the search snippet from whatever text it finds.

https://oliveole.com/pages/career and https://oliveole.com/pages/contact-us have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

We fetched 8 pages linked from your homepage and read each the way a search engine does.

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

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.

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.

The homepage has only about 28 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 Ads, Google Analytics, Google Tag Manager, 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 10 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 23 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.