oliveandjune.com website review

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

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

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

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

8 third-party services load with your homepage (Google Tag Manager, alia-prod.com and gotolstoy.com and others), adding 36.7 MB and 2.7 s of main-thread time.

Shopify costs a phone 392 ms of main-thread work and 34.6 MB 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.

About 1.3 MB of JavaScript is downloaded but never used on this page.

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

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

Google Tag Manager costs a phone 498 ms of main-thread work and 691 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.

alia-prod.com costs a phone 461 ms of main-thread work and 305 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.

gotolstoy.com costs a phone 439 ms of main-thread work and 347 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.

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

Amazon Web Services costs a phone 262 ms of main-thread work and 20 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.

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

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

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

40 KiB could be saved by minifying JavaScript.

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

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.

Your largest element takes 18.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Pile of Olive & June kids press-on nail packages on pink, d…”.

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

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

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

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

Real visitors see the first content after 1.8 s (75th percentile). Good is under 1.8 s.

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

Your homepage downloads 45.1 MB in 685 requests on a phone: media 33.3 MB (7), images 6.5 MB (145) and scripts 3.2 MB (279). Under 2 MB keeps phones on slow connections fast.

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

1 image (361 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 12.77 g of CO₂e: 1532.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

7 buttons have no accessible name, so screen readers announce just “button”.

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

Images must have alternative text: 1 element on the page fails this check, rated critical by axe-core.

Some list items are not inside a list.

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

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 elements on the page fail this check, rated moderate by axe-core.

Main landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

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

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

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

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

There are 3 <h1> headlines (“Olive and June”, “THE O&J Cabin” and “is Calling”). One clear main headline is easier for people and search engines.

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

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

The homepage links to 362 pages on oliveandjune.com and 0 external pages.

Your Organization JSON-LD is missing 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://oliveandjune.com/products/the-complete-system-6-polishes is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://oliveandjune.com/pages/the-gift-shop, https://oliveandjune.com/collections/the-system, https://oliveandjune.com/collections/best-seller, https://oliveandjune.com/pages/the-o-j-mani-system-lp, https://oliveandjune.com/pages/get-the-gel-system-builder-gel-kit and https://oliveandjune.com/pages/dip-manis-by-olive-and-june and 4 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://oliveandjune.com/collections/shop-new, https://oliveandjune.com/pages/the-gift-shop, https://oliveandjune.com/collections/the-system, https://oliveandjune.com/collections/best-seller, https://oliveandjune.com/pages/the-o-j-mani-system-lp and https://oliveandjune.com/pages/the-olive-and-june-gel-mani-system-lp and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 403 (Forbidden)”.

Social proof on the homepage: 25 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 1,892 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 Klaviyo (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 11 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 51 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.