marcodalmaso.com website review

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

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

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

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

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

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

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

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

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

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

tidio.co costs a phone 121 ms of main-thread work and 515 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.

azurefd.net costs a phone 75 ms of main-thread work and 329 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 (235 KiB).

1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 100 ms.

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

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

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.

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

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

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

Real visitors wait 886 ms for your server to start answering (75th percentile). Good is under 800 ms.

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

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

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

Your homepage downloads 4.9 MB in 172 requests on a phone: images 2.4 MB (38), scripts 1.9 MB (88) and fonts 223 KiB (4). Under 2 MB keeps phones on slow connections fast.

3 images weigh 1.7 MB together. On a phone connection a single image that size takes seconds.

6 images (2.2 MB) 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.

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

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

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

Interactive controls must not be nested: 2 elements on the page fail this check, rated serious by axe-core.

1 image has no alt text, which hurts accessibility and image search.

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

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

Structured data found (BlogPosting, ItemList, OnlineStore and WebSite) but with 2 problems, for example “BlogPosting: missing datePublished”.

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

The homepage links to 311 pages on marcodalmaso.com and 8 external pages.

https://marcodalmaso.com/collections/best-sellers, https://marcodalmaso.com/collections/beaded-necklaces-bracelets, https://marcodalmaso.com/collections/fall-edit, https://marcodalmaso.com/blogs/craft-edit and https://marcodalmaso.com/pages/international-customers have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://marcodalmaso.com/pages/international-customers, whose canonical is https://marcodalmaso.com/pages/support-center. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://marcodalmaso.com/collections/best-sellers, https://marcodalmaso.com/collections/beaded-necklaces-bracelets, https://marcodalmaso.com/collections/mixed-metals, https://marcodalmaso.com/collections/fall-edit, https://marcodalmaso.com/pages/gift-guide and https://marcodalmaso.com/pages/about-us and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://marcodalmaso.com/collections/best-sellers, https://marcodalmaso.com/collections/beaded-necklaces-bracelets, https://marcodalmaso.com/collections/mixed-metals, https://marcodalmaso.com/collections/fall-edit, https://marcodalmaso.com/pages/gift-guide and https://marcodalmaso.com/pages/about-us and 2 others took over 3 s to send their HTML from our server.

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

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

3 errors were logged to the browser console while the page loaded, for example “c.Shopify.loadFeatures is not a function”.

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.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

Social proof on the homepage: 1 trust badge. 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 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 627 words of visible text.

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