marcoshoes.com website review

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

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

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

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

Shopify costs a phone 156 ms of main-thread work and 422 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 (Shopify, Klaviyo and nfcube.com and others), adding 753 KiB and 219 ms of main-thread time.

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

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

5 images could be 139 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

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

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

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

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

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

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

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

Your homepage downloads 8.1 MB in 341 requests on a phone: media 5.6 MB (3), other files 956 KiB (163) and scripts 713 KiB (133). Under 2 MB keeps phones on slow connections fast.

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

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

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

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

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

ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor 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.

Elements with visible text labels do not have matching accessible names. (2 elements).

Your title is only 26 characters: “Marco Shoes Official Store”. Between 30 and 65 characters leaves room to say what you do and for whom.

The homepage links to 202 pages on marcoshoes.com and 4 external pages.

https://marcoshoes.com/collections/botki and https://marcoshoes.com/collections/botki/sztyblety all use the title “Botki skórzane damskie | Marco Shoes”. Search engines can't tell which page to show for a search, so each competes with the others.

https://marcoshoes.com/pages/fw26-27-sentymenty, https://marcoshoes.com/collections/fw26-27-1-drop and https://marcoshoes.com/collections/all have no meta description, so Google writes the search snippet from whatever text it finds.

https://marcoshoes.com/collections/botki and https://marcoshoes.com/collections/botki/sztyblety use the same meta description. A description written for each page earns more clicks.

https://marcoshoes.com/pages/fw26-27-sentymenty, https://marcoshoes.com/collections/fw26-27-1-drop, https://marcoshoes.com/collections/all, https://marcoshoes.com/collections/botki, https://marcoshoes.com/collections/botki/sztyblety and https://marcoshoes.com/collections/kozaki 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 91 found) and read each the way a search engine does.

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

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.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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

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