lejanbrand.com website review

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

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

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

19 images could be 1.9 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 650 ms faster on a phone.

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

8 third-party services load with your homepage (Clarity, Klaviyo and Shopify and others), adding 5.6 MB and 320 ms of main-thread time.

Shopify costs a phone 24 ms of main-thread work and 5.3 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 45 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.

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

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

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

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

9 KiB could be saved by minifying JavaScript.

8 KiB JavaScript is shipped twice across bundles.

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 10.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

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

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

Real visitors wait 3.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.

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

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

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

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

Your homepage downloads 11.2 MB in 309 requests on a phone: media 4.7 MB (2), images 4.2 MB (62) and other files 915 KiB (137). Under 2 MB keeps phones on slow connections fast.

1 image further down the page (179 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

35 tap targets are too small or too close together to hit reliably with a finger.

Scrollable region must have keyboard access: 2 elements on the page fail this check, rated serious by axe-core.

Inline text spacing must be adjustable with custom stylesheets: 1 element on the page fails this check, rated serious by axe-core.

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

Heading levels should only increase by one: 1 element on the page fails 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.

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

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

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

No XML sitemap at https://lejanbrand.com/sitemap.xml, so Google discovers your pages only by following links.

There is no robots.txt at lejanbrand.com/robots.txt, the first file search crawlers ask for.

2 links have no real href, so search engines can't follow them.

The homepage links to 130 pages on lejanbrand.com and 0 external pages.

There is no https://lejanbrand.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://lejanbrand.com/en-us/collections/lejan-broome, https://lejanbrand.com/en-us/collections/barefoot-for-women, https://lejanbrand.com/en-us/collections/barefoot-for-men and https://lejanbrand.com/en-us/collections/barefoot-shoes-kids have no <h1> headline, so visitors and search engines get no clear main topic.

https://lejanbrand.com/en-us/collections/lejan-broome, https://lejanbrand.com/en-us/collections/barefoot-for-women, https://lejanbrand.com/en-us/collections/barefoot-for-men and https://lejanbrand.com/en-us/collections/barefoot-shoes-kids 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 15 pages linked from your homepage (of 65 found) and read each the way a search engine does.

40 of 91 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_FAILED”.

Requests the notification permission on page load.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

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

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