lolipop.ch website review

45 images could be 2.0 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.4 s faster on a phone.

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

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

About 169 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.

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

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

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

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

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

79 KiB JavaScript is shipped twice across bundles.

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

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

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.

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

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

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

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

Your homepage downloads 4.7 MB in 238 requests on a phone: images 3.0 MB (51), scripts 760 KiB (79) and other files 720 KiB (83). Under 2 MB keeps phones on slow connections fast.

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

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

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

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

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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

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

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

Structured data found (Organization, Product and WebSite) but with 1 problem, for example “WebSite: url is not an absolute URL ("www.lolipop.ch")”.

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

The homepage links to 260 pages on lolipop.ch and 5 external pages.

https://www.lolipop.ch/customer_authentication/redirect has no <title>, so Google invents the link text in results.

https://www.lolipop.ch/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://www.lolipop.ch/customer_authentication/redirect and https://www.lolipop.ch/collections/all have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.lolipop.ch/customer_authentication/redirect has no <h1> headline, so visitors and search engines get no clear main topic.

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

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.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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