futurola.com website review

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

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

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

Klaviyo costs a phone 135 ms of main-thread work and 312 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.

8 third-party services load with your homepage (Klaviyo, Clarity and Shopify and others), adding 638 KiB and 257 ms of main-thread time.

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

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

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

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

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

2 images could be 22 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.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

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 “Futurola Dutch Crown Device, 1 1/4 size 84mm”.

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

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

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

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

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

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

16 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

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

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

There is no <h1>, so neither visitors nor Google get a clear main headline.

Your meta description is 286 characters; Google truncates after about 160, so the end of your pitch is cut.

3 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

The homepage links to 186 pages on futurola.com and 8 external pages.

https://futurola.com/policies/shipping-policy has no meta description, so Google writes the search snippet from whatever text it finds.

https://futurola.com/collections/pre-production-shredders and https://futurola.com/collections/shredder-parts have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

5 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_TUNNEL_CONNECTION_FAILED”.

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.

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.

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

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