maverickandwolf.com website review

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

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

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

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

Google Maps costs a phone 453 ms of main-thread work and 956 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.

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

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

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

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

About 24 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 240 ms faster on a phone.

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

1 image could be 14 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.

Polyfills for old browsers add 43 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 11.6 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 17.7 s. Good is under 3.8 s.

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

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

10 images have no width and height attributes, so the layout jumps as each one loads.

Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 101 ms to 104 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 1.5 s to 1.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 3.4 MB in 244 requests on a phone: scripts 1.9 MB (88), other files 820 KiB (124) and images 330 KiB (19). Under 2 MB keeps phones on slow connections fast.

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

2 frames have no title, so screen-reader users cannot tell what they contain.

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

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

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

Your title is only 15 characters: “Maverick & Wolf”. Between 30 and 65 characters leaves room to say what you do and for whom.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

There are 2 <h1> headlines (“Maverick & Wolf” and “Visit us in store”). One clear main headline is easier for people and search engines.

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

The homepage links to 174 pages on maverickandwolf.com and 7 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://maverickandwolf.com/collections/designer-glasses, https://maverickandwolf.com/collections/cartier-glasses, https://maverickandwolf.com/collections/chanel-glasses, https://maverickandwolf.com/pages/chrome-hearts, https://maverickandwolf.com/collections/dita-glasses and https://maverickandwolf.com/collections/gotti-glasses and 7 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://maverickandwolf.com/collections/chanel-glasses and https://maverickandwolf.com/pages/chrome-hearts have no <h1> headline, so visitors and search engines get no clear main topic.

https://maverickandwolf.com/pages/glasses-brands, https://maverickandwolf.com/collections/cartier-glasses, https://maverickandwolf.com/collections/chanel-glasses, https://maverickandwolf.com/collections/dita-glasses, https://maverickandwolf.com/collections/gotti-glasses and https://maverickandwolf.com/collections/linda-farrow-glasses and 2 others took over 3 s to send their HTML from our server.

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

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

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

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

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.

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

The homepage shows no opening hours. If customers visit or call, show when.

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, Heap and Klaviyo 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 (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 27 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.