zlaner.com website review

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

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

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

About 58 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 1,503 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

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

5 third-party services load with your homepage (9gtb.com, Shopify and gorgias.help and others), adding 690 KiB and 44 ms of main-thread time.

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

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

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

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

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

Visually, the page fills in at 4.1 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 66 ms to 70 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 2.6 MB in 261 requests on a phone: images 1.3 MB (116), other files 776 KiB (98) and scripts 294 KiB (38). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example ac.svg at 9,750 px wide, shown at 20 px. Resized copies would save about 121 KiB.

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

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

Scrollable region must have keyboard access: 3 elements on the page fail this check, rated serious by axe-core.

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

All page content should be contained by landmarks: 2 elements on the page fail this check, rated moderate by axe-core.

Contentinfo landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

Document should not have more than one contentinfo landmark: 1 element on the page fails 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.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

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

No meta description, so Google writes its own snippet from whatever text it finds.

There is no <h1>, so neither visitors nor Google get a clear main headline.

Your title is only 6 characters: “Zlaner”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

The homepage links to 42 pages on zlaner.com and 17 external pages.

https://zlaner.com/collections/all-products and https://zlaner.com/pages/help-center have no meta description, so Google writes the search snippet from whatever text it finds.

https://zlaner.com/pages/help-center and https://zlaner.com/pages/data-sharing-opt-out have no <h1> headline, so visitors and search engines get no clear main topic.

We fetched 12 pages linked from your homepage 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.

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 phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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

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

Before a visitor clicks anything, the page loads Google Tag Manager (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 8 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 12 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.