mayca.com website review

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

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

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

8 third-party services load with your homepage (Google Tag Manager, Facebook and survicate-cdn.com and others), adding 1.2 MB and 1.8 s of main-thread time.

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

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

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

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

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

Facebook costs a phone 260 ms of main-thread work and 225 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,781 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

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

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

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 19.1 s. Good is under 3.8 s.

Your largest element takes 7.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “E-Commerce Tenga acceso a nuestro portafolio y compre en lí…”.

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

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

Real visitors wait 232 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

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

The first text or image appears after 2.0 s on a phone. Good is under 1.8 s.

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

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

Your homepage downloads 2.2 MB in 326 requests on a phone: scripts 1.7 MB (248), stylesheets 179 KiB (5) and images 97 KiB (12). Under 2 MB keeps phones on slow connections fast.

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

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

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

Page should contain a level-one heading: 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.

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

Your title is only 29 characters: “Homepage - Mayca Food Service”. Between 30 and 65 characters leaves room to say what you do and for whom.

Your meta description is only 29 characters: “Homepage - Mayca Food Service”. 70 to 160 characters is enough to sell the click.

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

No XML sitemap at https://www.mayca.com/sitemap.xml, so Google discovers your pages only by following links.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 605 pages on mayca.com and 6 external pages.

https://www.mayca.com/purchaseorder/purchaseorder, https://www.mayca.com/customer/address, https://www.mayca.com/sales/order/history, https://www.mayca.com/negotiable_quote/quote, https://www.mayca.com/requisition_list/requisition/index and https://www.mayca.com/company all use the title “Inicio de sesión de cliente”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.mayca.com/stores, https://www.mayca.com/asesor/index/solicitar, https://www.mayca.com/contact, https://www.mayca.com/purchaseorder/purchaseorder, https://www.mayca.com/customer/address and https://www.mayca.com/sales/order/history and 3 others use the same meta description. A description written for each page earns more clicks.

https://www.mayca.com/food-service, https://www.mayca.com/franquicias, https://www.mayca.com/centro-gastronomico, https://www.mayca.com/trayectoria, https://www.mayca.com/mayca-plus and https://www.mayca.com/comprar have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

4 errors were logged to the browser console while the page loaded, for example “Sending form data to 'https://www.facebook.com/tr/' violates the following report-only Content Security Policy directiv…”.

Chrome logged issues while loading the page (“Content security policy”).

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

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

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