lakai.com website review

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

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

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

About 43 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.

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

19 KiB could be saved by minifying CSS.

7 third-party services load with your homepage (omnisnippet1.com, Shopify and shop.app and others), adding 317 KiB and 98 ms of main-thread time.

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

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

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

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

5 KiB JavaScript is shipped twice across bundles.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

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 6.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Bastien Salabanzi jump over stairs”.

Real visitors wait 202 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

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

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

Your homepage downloads 6.5 MB in 193 requests on a phone: media 2.8 MB (1), images 2.5 MB (43) and other files 888 KiB (98). Under 2 MB keeps phones on slow connections fast.

lakai-telford-low-chris-joslin-black-white-lifestyle-4_ed6f4 weighs 704 KiB. On a phone connection a single image that size takes seconds.

8 images (1.2 MB) are 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.

4 images are downloaded at several times the size a phone draws them, for example lakai-evon-denim-dtc-main.webp at 900 px wide, shown at 173 px. Resized copies would save about 155 KiB.

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

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

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

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.

Alternative text of images should not be repeated as text: 2 elements on the page fail this check, rated minor by axe-core.

The homepage links to 462 pages on lakai.com and 4 external pages.

https://lakai.com/pages/team, https://lakai.com/pages/contact, https://lakai.com/policies/refund-policy and https://lakai.com/policies/privacy-policy have no meta description, so Google writes the search snippet from whatever text it finds.

https://lakai.com/collections/shoes, https://lakai.com/collections/apparel, https://lakai.com/collections/accessories, https://lakai.com/collections/sale and https://lakai.com/collections/evon-martinez use the same meta description. A description written for each page earns more clicks.

https://lakai.com/pages/team has no <h1> headline, so visitors and search engines get no clear main topic.

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

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

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.

Your longest form asks for 17 fields (0 required). Every extra field lowers completion.

The homepage carries about 1,082 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 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 15 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 21 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.