yoli.com website review

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

43 files are served with short cache lifetimes, so returning visitors download them again (1.3 MB).

240 KiB could be saved by minifying JavaScript.

8 third-party services load with your homepage (nice-incontact.com, userway.org and fluid.app and others), adding 7.3 MB and 393 ms of main-thread time.

Your mobile performance score is 53 (desktop: 88). Pages that score under 90 lose visitors before the first paint.

imagekit.io costs a phone 0 ms of main-thread work and 4.2 MB 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.

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

fluid.app costs a phone 56 ms of main-thread work and 2.6 MB 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 files block the first paint until they finish downloading. Deferring or inlining them could save about 300 ms.

nice-incontact.com costs a phone 185 ms of main-thread work and 324 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.

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

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

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

7 KiB could be saved by minifying CSS.

Polyfills for old browsers add 11 KiB JavaScript that modern phones do not need.

Desktop scores 88 but mobile only 53. A gap that wide usually means heavy scripts and images that hit phones hardest.

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.

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.

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

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

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

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

For real visitors the layout shifts by 0.13 (75th percentile). Good is under 0.1.

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

Your homepage downloads 7.5 MB in 128 requests on a phone: media 3.5 MB (1), scripts 2.9 MB (51) and images 556 KiB (23). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example LWDVlc4RrU_n3awFVUeAC.jpg at 746 px wide, shown at 55 px. Resized copies would save about 58 KiB.

1 image (61 KiB) is 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.

1 image further down the page (43 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

1 frame has no title, so screen-reader users cannot tell what it contains.

1 image has no alt text, which hurts accessibility and image search.

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

1 form field has no label, so screen readers announce an empty box and autofill guesses.

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 title is only 4 characters: “Yoli”. Between 30 and 65 characters leaves room to say what you do and for whom.

Your meta description is only 10 characters: “Live Free.”. 70 to 160 characters is enough to sell the click.

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

The homepage links to 99 pages on yoli.com and 8 external pages.

/ and https://yoli.com/__fluid_affiliate_username__ all use the title “Yoli”. Search engines can't tell which page to show for a search, so each competes with the others.

Your homepage links to 13 pages by a URL that isn't their canonical one, for example https://yoli.com/__fluid_affiliate_username__/products/activation-pack, whose canonical is https://yoli.com/home/products/activation-pack. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://yoli.com/__fluid_affiliate_username__ and https://yoli.com/__fluid_affiliate_username__/products/cafetrim-552f6706-bdaa-45e1-a3d8-cca724474b0a use the same meta description. A description written for each page earns more clicks.

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

1 image failed to load on a phone, for example https://yoli.com/.

2 third-party cookies are 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: net::ERR_FAILED”.

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.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

The homepage carries about 559 words of visible text.

Opening the homepage sets 7 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 14 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.