pearlwax.de website review

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

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 600 ms).

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

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

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

8 third-party services load with your homepage (Shopify, Snapchat and rechargecdn.com and others), adding 1,015 KiB and 334 ms of main-thread time.

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

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

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

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

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

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

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

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

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 2.6 MB in 243 requests on a phone: scripts 1.1 MB (77), other files 785 KiB (103) and images 394 KiB (30). Under 2 MB keeps phones on slow connections fast.

Pearlwax-banner-1080x1080_ENG_750x.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 0.73 g of CO₂e: 87.7 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.

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

1 visible link has no text or label, so screen readers cannot say where it goes.

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

Elements with visible text labels do not have matching accessible names. (1 element).

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

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

Your <h1> is empty.

The homepage links to 56 pages on pearlwax.de and 9 external pages.

https://pearlwax.de/collections/starterkits and https://pearlwax.de/collections/startpakete all use the title “Perlwachs-Verpackungslösungen – Entdecken Sie die große Auswahl”. Search engines can't tell which page to show for a search, so each competes with the others.

https://pearlwax.de/pages/pearlwax-quiz-1 has no meta description, so Google writes the search snippet from whatever text it finds.

https://pearlwax.de/collections/starterkits and https://pearlwax.de/collections/startpakete use the same meta description. A description written for each page earns more clicks.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://pearlwax.de/collections/starterkits, whose canonical is https://pearlwax.de/collections/startpakete. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://pearlwax.de/pages/guide and https://pearlwax.de/pages/faq have no <h1> headline, so visitors and search engines get no clear main topic.

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

1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

Chrome logged issues while loading the page (“Cookie”).

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

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

Before a visitor clicks anything, the page loads Klaviyo and Snap 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 4 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 25 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.