marvinsmagic.com website review

Your mobile performance score is 83 (desktop: 80). Pages that score under 90 lose visitors before the first paint.

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

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

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

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

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

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

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

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

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

8 KiB could be saved by minifying JavaScript.

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

Polyfills for old browsers add 24 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.

3 KiB JavaScript is shipped twice across bundles.

2 KiB could be saved by minifying CSS.

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

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 first text or image appears after 2.4 s on a phone. Good is under 1.8 s.

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

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

Your homepage downloads 2.4 MB in 284 requests on a phone: scripts 1.1 MB (115), other files 697 KiB (93) and images 339 KiB (27). Under 2 MB keeps phones on slow connections fast.

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

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

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

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

1 tap target is too small or too close together to hit reliably with a finger.

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

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

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

The homepage links to 80 pages on marvinsmagic.com and 11 external pages.

https://www.marvinsmagic.com/pages/wishlist and https://www.marvinsmagic.com/en-us/pages/wishlist all use the title “Wishlist – Marvin's Magic Worldwide”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.marvinsmagic.com/pages/wishlist, https://www.marvinsmagic.com/en-us/pages/wishlist and https://www.marvinsmagic.com/en-us/blogs/style 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://www.marvinsmagic.com/pages/wishlist, whose canonical is https://www.marvinsmagic.com/en-us/pages/wishlist. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

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

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

1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://d19ayerf5ehaab.cloudfront.net/css/product-widget/style.css' from origin 'https://w…”.

Chrome logged issues while loading the page (“Cookie”).

Social proof on the homepage: 8 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

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

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

The homepage carries about 3,792 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 20 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 31 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.