ullowine.com website review

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

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

8 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.1 s.

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

8 third-party services load with your homepage (Bold Commerce, shopapps.site and rechargecdn.com and others), adding 1.5 MB and 770 ms of main-thread time.

89 KiB could be saved by minifying JavaScript.

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

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

Bold Commerce costs a phone 197 ms of main-thread work and 349 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.

shopapps.site costs a phone 148 ms of main-thread work and 303 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.

rechargecdn.com costs a phone 127 ms of main-thread work and 298 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 45 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

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

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

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

1 KiB JavaScript is shipped twice across bundles.

Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

Your largest element takes 17.3 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 17.3 s. Good is under 3.8 s.

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

Real visitors wait 871 ms for your server to start answering (75th percentile). Good is under 800 ms.

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

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

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

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

Your homepage downloads 3.2 MB in 230 requests on a phone: scripts 1.8 MB (76), other files 797 KiB (117) and images 436 KiB (22). Under 2 MB keeps phones on slow connections fast.

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

3 elements hidden from screen readers can still receive keyboard focus.

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

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

Your title is 69 characters, so Google will cut it off around 60: “Üllo Wine Purifier | Remove Sulfites from Wine. Aerate. Enjoy. – Ullo”.

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

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

The homepage links to 118 pages on ullowine.com and 4 external pages.

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://ullowine.com/discount/BN2026 declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.

/ and https://ullowine.com/discount/BN2026 all use the title “Üllo Wine Purifier | Remove Sulfites from Wine. Aerate. Enjoy. – Ullo”. Search engines can't tell which page to show for a search, so each competes with the others.

https://ullowine.com/blogs/news/tagged/wine-purification and https://ullowine.com/blogs/news have no meta description, so Google writes the search snippet from whatever text it finds.

https://ullowine.com/pages/where-to-buy has no <h1> headline, so visitors and search engines get no clear main topic.

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

4 images failed to load on a phone, for example https://ullowine.com/.

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

Social proof on the homepage: 29 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

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.

There is no form on the homepage, so every lead has to click through to another page first.

The homepage carries about 542 words of visible text.

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