moleqlar.com website review

About 843 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.5 s faster on a phone.

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

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

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

8 third-party services load with your homepage (Google Tag Manager, admetrics.events and Shopify and others), adding 1.8 MB and 1.3 s of main-thread time.

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

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

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

Google Tag Manager costs a phone 528 ms of main-thread work and 512 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.

About 63 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.

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

Klaviyo costs a phone 133 ms of main-thread work and 338 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.

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

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

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

18 KiB could be saved by minifying JavaScript.

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.

4 KiB could be saved by minifying CSS.

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

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

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

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

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

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

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

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.1 s to 2.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 5.0 MB in 347 requests on a phone: scripts 1.9 MB (119), images 1.8 MB (78) and other files 804 KiB (109). Under 2 MB keeps phones on slow connections fast.

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

1 image is downloaded at several times the size a phone draws it, for example zink_kapseln_5.jpg at 600 px wide, shown at 140 px. Resized copies would save about 32 KiB.

2 images (80 KiB) 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.

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

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

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

Some lists contain elements other than list items, which screen readers announce wrongly.

Summary elements must have discernible text: 1 element on the page fails this check, rated serious by axe-core.

All page content should be contained by landmarks: 33 elements on the page fail 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.

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

Elements with visible text labels do not have matching accessible names. (3 elements).

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

The homepage links to 280 pages on moleqlar.com and 20 external pages.

https://moleqlar.com/policies/refund-policy, https://moleqlar.com/policies/shipping-policy, https://moleqlar.com/pages/produkt-quiz and https://moleqlar.com/collections/all-in-one-essentials have no meta description, so Google writes the search snippet from whatever text it finds.

https://moleqlar.com/pages/produkt-quiz and https://moleqlar.com/collections/bundle have no <h1> headline, so visitors and search engines get no clear main topic.

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

4 images failed to load on a phone, for example https://bat.bing.com/action/0?ti=343046567&Ver=2&mid=b8b64068-f67e-4756-a2df-3756b862a350&bo=1&sid=fa0251a0db3811f18b8d2f5e82eba9f3&vid=fa0281e0db3811f1a4315da70e3456ce&vids=1&msclkid=N&pi=918639831&l.

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

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

1 image is served at too low a resolution for sharp phone screens.

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 customer or partner logo. 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 1,896 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 Tag Manager, Klaviyo, Meta Pixel and Microsoft Ads and 1 more (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 33 cookies, 4 of them by other companies (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.