julep.com website review

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

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

About 202 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.2 s faster on a phone.

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

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

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

8 third-party services load with your homepage (Shopify, Google Tag Manager and Klaviyo and others), adding 1.5 MB and 809 ms of main-thread time.

Polyfills for old browsers add 52 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 450 ms faster on a phone.

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

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

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

Klaviyo costs a phone 121 ms of main-thread work and 400 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.

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

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

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

3 KiB JavaScript is shipped twice across bundles.

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

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

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

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

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

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

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

Your homepage downloads 4.2 MB in 427 requests on a phone: scripts 1.9 MB (175), other files 992 KiB (169) and images 787 KiB (36). Under 2 MB keeps phones on slow connections fast.

Julep_ES101_Model_khaki_green_shimmer.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).

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

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

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

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

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

1 element has a tabindex above 0, which scrambles the keyboard order.

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

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

Your <h1> is empty.

The homepage links to 125 pages on julep.com and 11 external pages.

There is no https://www.julep.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

https://www.julep.com/products/eyeshadow-10-creme-to-powder-eyeshadow-stick has no <h1> headline, so visitors and search engines get no clear main topic.

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

1 image failed to load on a phone, for example https://www.julep.com/.

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

6 errors were logged to the browser console while the page loaded, for example “Cannot read properties of null (reading 'addEventListener')”.

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

Before a visitor clicks anything, the page loads Amplitude, Google Ads, Google Analytics, Google Tag Manager and Klaviyo and 3 mores (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 38 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 51 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.