joola.it website review

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

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

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

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

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

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

gsitrix.com costs a phone 491 ms of main-thread work and 60 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.

Shopify costs a phone 286 ms of main-thread work and 715 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 326 KiB of JavaScript is downloaded but never used on this page.

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

Klaviyo costs a phone 143 ms of main-thread work and 315 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 39 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.

5 KiB could be saved by minifying JavaScript.

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

17 files are served with short cache lifetimes, so returning visitors download them again (51 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.

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 page becomes fully interactive after 26.4 s. Good is under 3.8 s.

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

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

Real visitors wait 211 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

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

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

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

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

Your homepage downloads 18.0 MB in 570 requests on a phone: media 10.8 MB (1), other files 2.9 MB (228) and images 2.2 MB (114). Under 2 MB keeps phones on slow connections fast.

Tyson_McGuffin_3063a322-21bc-43bf-a10f-408ad80db12c.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

1 image (80 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.

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

1 element use ARIA attributes their role does not allow, which confuses screen readers.

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

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

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

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

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

1 visible link has no text or label, so screen readers cannot say where it goes.

Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

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

Elements with visible text labels do not have matching accessible names. (1 element).

Structured data found (BreadcrumbList, Organization and WebSite) but with 2 problems, for example “Organization: url points at a different host (https://joola.de)”.

The homepage links to 310 pages on joola.it and 30 external pages.

https://joola.it/collections/professionale and https://joola.it/collections/rack-per-hobby have no meta description, so Google writes the search snippet from whatever text it finds.

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

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

8 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

The page uses 1 deprecated browser API that will stop working in future browsers (“Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to…”).

2 errors were 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”).

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 762 words of visible text.

Before a visitor clicks anything, the page loads Hotjar and Klaviyo (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 10 cookies, 1 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 33 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.