lnda.com website review

About 1.4 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 7.1 s faster on a phone.

Shopify costs a phone 4.9 s of main-thread work and 2.0 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

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

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

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

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

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

8 third-party services load with your homepage (Shopify, appstle.com and embedany.com and others), adding 3.1 MB and 6.1 s of main-thread time.

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

122 KiB could be saved by minifying JavaScript.

appstle.com costs a phone 642 ms of main-thread work and 103 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 165 ms of main-thread work and 545 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.

107 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 250 ms faster on a phone.

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

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

About 68 KiB of CSS is downloaded but never applied on this page.

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 could be saved by minifying CSS.

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

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

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

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

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

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 41.2 MB in 463 requests on a phone: media 33.4 MB (3), images 2.8 MB (59) and scripts 2.8 MB (185). Under 2 MB keeps phones on slow connections fast.

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

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

2 images have no alt text, which hurts accessibility and image search.

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

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

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

Your title is only 23 characters: “Linda Johansen Skincare”. Between 30 and 65 characters leaves room to say what you do and for whom.

There are 2 <h1> headlines (“” and “Livesending”). One clear main headline is easier for people and search engines.

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

Structured data found (BreadcrumbList, Organization and WebSite) but with 1 problem, for example “Organization: url points at a different host (https://lnda.no)”.

9 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

The homepage links to 146 pages on lnda.com and 7 external pages.

https://lnda.com/collections/all and https://lnda.com/policies/shipping-policy use the same meta description. A description written for each page earns more clicks.

https://lnda.com/collections/all, https://lnda.com/policies/shipping-policy, https://lnda.com/collections/lnda-lab, https://lnda.com/collections/cleansers-lab, https://lnda.com/collections/moisturizer-lab and https://lnda.com/collections/serum-lab and 6 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://lnda.com/collections/all, https://lnda.com/policies/shipping-policy, https://lnda.com/collections/lnda-lab and https://lnda.com/collections/cleansers-lab took over 3 s to send their HTML from our server.

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

4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

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 analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

The homepage has only about 25 words of visible text; thin pages give Google and first-time buyers little to go on.

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

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 16 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 45 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.