fanelashop.gr website review

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

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

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

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

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

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

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

About 406 KiB of JavaScript is downloaded but never used on this page.

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

Google Tag Manager costs a phone 178 ms of main-thread work and 296 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.

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

About 33 KiB of CSS is downloaded but never applied on this page.

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.

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

Your largest element takes 4.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “mobilebanner_202627jersey.png__PID:e49528b1-3fd7-47f8-9ae0-…”.

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

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

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

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

Your homepage downloads 8.1 MB in 720 requests on a phone: images 4.6 MB (326), other files 1.6 MB (232) and scripts 1.5 MB (128). Under 2 MB keeps phones on slow connections fast.

fanelamou-offer-large-mobile.webp 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 (36 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 2.28 g of CO₂e: 274.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

Images must have alternative text: 1 element on the page fails this check, rated critical by axe-core.

Scrollable region must have keyboard access: 48 elements on the page fail this check, rated serious by axe-core.

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

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

Alternative text of images should not be repeated as text: 1 element on the page fails this check, rated minor by axe-core.

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

Your title is 66 characters, so Google will cut it off around 60: “Fanelamou - Τα καλύτερα ποδοσφαιρικά ρούχα και φανέλες στην Ελλάδα”.

There are 6 <h1> headlines (“Fanelamou”, “🔥Η ΚΑΛΎΤΕΡΗ ΠΟΔΟΣΦΑΙΡΙΚΉ ΦΑΝΈΛΑ!🔥” and “Δημοφιλείς Φανέλες”). One clear main headline is easier for people and search engines.

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

The homepage links to 132 pages on fanelashop.gr and 4 external pages.

https://fanelamou.com/collections/%CE%B1%CF%81%CE%B3%CE%B5%CE%BD%CF%84%CE%AF%CE%BD%CE%B7, https://fanelamou.com/collections/%CE%B2%CF%81%CE%B1%CE%B6%CE%B9%CE%BB%CE%AF%CE%B1, https://fanelamou.com/collections/%CE%B3%CE%B1%CE%BB%CE%BB%CE%AF%CE%B1, https://fanelamou.com/collections/%CE%B1%CE%B3%CE%B3%CE%BB%CE%AF%CE%B1, https://fanelamou.com/collections/%CE%B9%CF%83%CF%80%CE%B1%CE%BD%CE%AF%CE%B1 and https://fanelamou.com/collections/%CF%80%CE%BF%CF%81%CF%84%CE%BF%CE%B3%CE%B1%CE%BB%CE%AF%CE%B1 and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 8 pages by a URL that isn't their canonical one, for example https://fanelamou.com/collections/%CE%B1%CF%81%CE%B3%CE%B5%CE%BD%CF%84%CE%AF%CE%BD%CE%B7, whose canonical is https://fanelamou.com/collections/%ce%b1%cf%81%ce%b3%ce%b5%ce%bd%cf%84%ce%af%ce%bd%ce%b7. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://fanelamou.com/collections/liverpool, https://fanelamou.com/collections/arsenal, https://fanelamou.com/collections/chelsea, https://fanelamou.com/collections/manchester-city, https://fanelamou.com/collections/manchester-united and https://fanelamou.com/collections/barcelona have no <h1> headline, so visitors and search engines get no clear main topic.

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

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

Social proof on the homepage: 2 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

The homepage has only about 170 words of visible text; thin pages give Google and first-time buyers little to go on.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel 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 15 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 35 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.