epilot.mx website review

3 images could be 1.7 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

8 third-party services load with your homepage (Google Tag Manager, Shopify and Mailchimp and others), adding 704 KiB and 594 ms of main-thread time.

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

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

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

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

About 42 KiB of CSS is downloaded but never applied on this page.

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

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

3 KiB could be saved by minifying JavaScript.

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

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

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

GIF_EPILOT.gif weighs 17.3 MB. On a phone connection a single image that size takes seconds.

Your homepage downloads 16.7 MB in 238 requests on a phone: media 13.0 MB (3), images 2.0 MB (12) and scripts 880 KiB (119). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example GIF_EPILOT.gif at 1,198 px wide, shown at 390 px. Resized copies would save about 818 KiB.

1 image (17.3 MB) is 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 4.73 g of CO₂e: 568.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

5 images have no alt text, which hurts accessibility and image search.

All page content should be contained by landmarks: 2 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.

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

There are 3 <h1> headlines (“EPilot: Ecommerce Experts”, “GUIAMOS TU RUTA DIGITAL” and “PARA QUE TU MARCA CREZCA”). One clear main headline is easier for people and search engines.

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

The homepage links to 27 pages on epilot.mx and 1 external page.

Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

https://epilot.mx/customer_authentication/redirect has no <title>, so Google invents the link text in results.

https://epilot.mx/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://epilot.mx/en/pages/clientes, https://epilot.mx/en/blogs/news, https://epilot.mx/customer_authentication/redirect, https://epilot.mx/en/collections/all, https://epilot.mx/en/policies/refund-policy and https://epilot.mx/en/policies/privacy-policy and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

https://epilot.mx/en/pages/clientes and https://epilot.mx/customer_authentication/redirect have no <h1> headline, so visitors and search engines get no clear main topic.

https://epilot.mx/en/pages/contactanos has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

We fetched 8 pages linked from your homepage and read each the way a search engine does.

1 error was 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.

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

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