ventyfan.pl website review

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

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

8 third-party services load with your homepage (Shopify, recart.com and Clarity and others), adding 1.8 MB and 1.3 s of main-thread time.

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

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

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

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

recart.com costs a phone 281 ms of main-thread work and 222 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.

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

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

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

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

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

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

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

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

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

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

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 4.2 MB in 510 requests on a phone: scripts 1.7 MB (229), other files 1.1 MB (201) and images 901 KiB (34). Under 2 MB keeps phones on slow connections fast.

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

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

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

Your canonical URL points to ventyfan.com, not ventyfan.pl, so Google may credit that host instead.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

The homepage links to 46 pages on ventyfan.pl and 14 external pages.

A phone browser shows 2,402 words, but the HTML your server sends has only 510. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

https://ventyfan.pl/products/clip-fan and https://ventyfan.pl/products/venty-clip-fan-upsell all use the title “Venty Clip Fan: Rechargeable Clip-On Fan, 10-Hr Battery – VENTY”. Search engines can't tell which page to show for a search, so each competes with the others.

https://ventyfan.pl/pages/collab, https://ventyfan.pl/policies/shipping-policy and https://ventyfan.pl/policies/refund-policy have no meta description, so Google writes the search snippet from whatever text it finds.

https://ventyfan.pl/products/clip-fan and https://ventyfan.pl/products/venty-clip-fan-upsell use the same meta description. A description written for each page earns more clicks.

https://ventyfan.pl/pages/reviews, https://ventyfan.pl/pages/support, https://ventyfan.pl/pages/support-for-product and https://ventyfan.pl/pages/help-page have no <h1> headline, so visitors and search engines get no clear main topic.

We fetched 15 pages linked from your homepage (of 21 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.

5 errors were logged to the browser console while the page loaded, for example “Failed to fetch r.fetch (https://ventyfan.pl/web-pixels@43600932w1bbca933p2f8a9c65m024fd2f2/web-pixel-1622212857@31a2d5…”.

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

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

The homepage shows no opening hours. If customers visit or call, show when.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

The homepage carries about 2,402 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 5 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 41 cookies, 3 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 51 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.