maryachi.com website review

About 1.0 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 6.4 s faster on a phone.

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

Your mobile performance score is 35. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

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

8 third-party services load with your homepage (PayPal, Shopify and vitals.app and others), adding 2.4 MB and 1.9 s of main-thread time.

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

PayPal costs a phone 692 ms of main-thread work and 671 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 445 ms of main-thread work and 855 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.

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

vitals.app costs a phone 346 ms of main-thread work and 420 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,832 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

Polyfills for old browsers add 41 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

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

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

6 KiB could be saved by minifying CSS.

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.

Your largest element takes 16.6 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 7.0 s on a phone. Good is under 1.8 s.

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

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

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

Real visitors wait 3.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.

Real visitors see the first content after 2.3 s (75th percentile). Good is under 1.8 s.

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

Your homepage downloads 4.4 MB in 432 requests on a phone: scripts 2.0 MB (183), other files 1,012 KiB (191) and images 618 KiB (28). Under 2 MB keeps phones on slow connections fast.

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

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

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

ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails 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: 6 elements on the page fail this check, rated moderate by axe-core.

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.

5 visible links have no text or label, so screen readers cannot say where they go.

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

Your title is 69 characters, so Google will cut it off around 60: “Playeras, Accesorios y Regalos 100% Mexicanos y originales | MaryAchi”.

There are 3 <h1> headlines (“MaryAchi”, “Más Amor, Menos Odio” and “Chido| Sticker Pack”). One clear main headline is easier for people and search engines.

3 links have no real href, so search engines can't follow them.

The homepage links to 67 pages on maryachi.com and 9 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://www.maryachi.com/es-us/collections/playeras-1, https://www.maryachi.com/es-us/collections/tanktops-mujer, https://www.maryachi.com/es-us/collections/tanktops-hombre, https://www.maryachi.com/es-us/collections/sudaderas, https://www.maryachi.com/es-us/collections/toallas and https://www.maryachi.com/es-us/collections/chucherias and 2 others 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.maryachi.com/es-us/collections/tazas/Taza+Tazas, whose canonical is https://www.maryachi.com/es-us/collections/tazas/taza+tazas. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.maryachi.com/es-us/collections/toallas has no <h1> headline, so visitors and search engines get no clear main topic.

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

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.

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

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

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