myfunzy.com website review

Shopify costs a phone 1.8 s of main-thread work and 991 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

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

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

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

8 third-party services load with your homepage (Shopify, Clarity and myfunzy.de and others), adding 1.5 MB and 2.3 s of main-thread time.

About 691 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 600 ms faster on a phone.

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

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

108 KiB could be saved by minifying CSS.

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

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

75 KiB could be saved by minifying JavaScript.

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

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

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.

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

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

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

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

Real visitors see the first content after 1.8 s (75th percentile). Good is under 1.8 s.

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

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

Your homepage downloads 3.9 MB in 352 requests on a phone: scripts 1.5 MB (94), other files 1.2 MB (190) and images 829 KiB (46). Under 2 MB keeps phones on slow connections fast.

9 images (364 KiB) are 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 (45 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 1.12 g of CO₂e: 134.0 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.

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

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

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

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

2 form fields have no label, so screen readers announce an empty box and autofill guesses.

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

The homepage links to 153 pages on myfunzy.com and 0 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.

The HTML your server sends has 984 of the 2,374 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.

https://myfunzy.com/collections/family-sofa-module and https://myfunzy.com/collections/bundles-sets have no meta description, so Google writes the search snippet from whatever text it finds.

https://myfunzy.com/products/funzy-spielsofa, https://myfunzy.com/products/funzy-hupfpolster, https://myfunzy.com/products/funzy-arches, https://myfunzy.com/collections/family-sofa-module, https://myfunzy.com/collections/spieltisch and https://myfunzy.com/products/donut and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://myfunzy.com/products/funzy-spielsofa, https://myfunzy.com/products/funzy-hupfpolster, https://myfunzy.com/products/funzy-arches, https://myfunzy.com/collections/family-sofa-module, https://myfunzy.com/products/donut and https://myfunzy.com/products/spieltisch-set and 5 others have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

https://myfunzy.com/products/family-funzy-sofa-cord-koala-grau and https://myfunzy.com/collections/alle-produkte took over 3 s to send their HTML from our server.

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

4 errors were logged to the browser console while the page loaded, for example “Failed to execute 'observe' on 'MutationObserver': parameter 1 is not of type 'Node'.”.

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

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

The page uses urgency cues (a countdown or limited-time wording).

Before a visitor clicks anything, the page loads Google Analytics, Klaviyo and Microsoft Clarity (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 5 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 31 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.