ferriswheelpress.eu website review

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

YouTube costs a phone 2.5 s of main-thread work and 6.8 MB 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.

About 166 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.5 s faster on a phone.

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

Your mobile performance score is 31. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

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

8 third-party services load with your homepage (YouTube, Shopify and Google Tag Manager and others), adding 8.0 MB and 3.3 s of main-thread time.

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

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

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

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

Shopify costs a phone 213 ms of main-thread work and 522 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.

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

4 images could be 31 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.

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 41.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

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

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

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

Real visitors wait 3.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.

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

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

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

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

The layout shifts by 0.144 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

Your homepage downloads 12.2 MB in 374 requests on a phone: scripts 9.4 MB (110), other files 1.0 MB (193) and HTML 753 KiB (10). Under 2 MB keeps phones on slow connections fast.

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

1 button has no accessible name, so screen readers announce just “button”.

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

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

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

Some list items are not inside a list.

Some lists contain elements other than list items, which screen readers announce wrongly.

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

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

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

Your title is 85 characters, so Google will cut it off around 60: “Ferris Wheel Press — Premium Fountain Pens, Inks & Stationery — Ferris Wheel Press EU”.

There are 2 <h1> headlines (“Ferris Wheel Press EU” and “Ferris Wheel Press EU”). One clear main headline is easier for people and search engines.

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

1 link has no real href, so search engines can't follow it.

The homepage links to 289 pages on ferriswheelpress.eu and 11 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://ferriswheelpress.eu/collections/newest-releases, https://ferriswheelpress.eu/collections/festival-of-lights-collection, https://ferriswheelpress.eu/collections/vintage-photography-collection-vintage-vignettes, https://ferriswheelpress.eu/collections/treasures-box-collection, https://ferriswheelpress.eu/collections/25-years-of-magic-patronus-anniversary-collection and https://ferriswheelpress.eu/collections/the-masque-fountain-pen-ink-set and 6 others are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

https://ferriswheelpress.eu/collections/festival-of-lights-collection, https://ferriswheelpress.eu/collections/vintage-photography-collection-vintage-vignettes, https://ferriswheelpress.eu/collections/leather-stationery-collection, https://ferriswheelpress.eu/collections/licensed-products, https://ferriswheelpress.eu/collections/warner-bros-the-lord-of-the-rings-pen-ink-collection and https://ferriswheelpress.eu/collections/warner-bros-harry-potter-writing-collection and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://ferriswheelpress.eu/collections/treasures-box-collection, https://ferriswheelpress.eu/collections/25-years-of-magic-patronus-anniversary-collection and https://ferriswheelpress.eu/collections/the-masque-fountain-pen-ink-set use the same meta description. A description written for each page earns more clicks.

https://ferriswheelpress.eu/collections/newest-releases, https://ferriswheelpress.eu/collections/festival-of-lights-collection, https://ferriswheelpress.eu/collections/vintage-photography-collection-vintage-vignettes, https://ferriswheelpress.eu/collections/treasures-box-collection, https://ferriswheelpress.eu/collections/25-years-of-magic-patronus-anniversary-collection and https://ferriswheelpress.eu/collections/the-masque-fountain-pen-ink-set and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=97052208&tm=gtm002&Ver=2&mid=e75a323a-d97b-43ce-b378-3a9f61dc8fb9&bo=1&sid=8df91fa0dde011f1a14cb3fb31a26fcc&vid=8df949b0dde011f18087c1a0adc37658&vids=1&msclkid=N&pi=91.

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

6 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 ()”.

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

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 858 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 4 mores (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 32 cookies, 3 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 53 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.