lapi.com.mx website review

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

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

13 images could be 669 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.1 s faster on a phone.

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

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

8 third-party services load with your homepage (Google Tag Manager, Google CDN and Facebook and others), adding 2.1 MB and 2.1 s of main-thread time.

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

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

1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 850 ms.

Google CDN costs a phone 707 ms of main-thread work and 765 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.

85 KiB could be saved by minifying CSS.

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

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

Your largest element takes 22.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “f1”.

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

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

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

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

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

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

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

Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 121 ms to 129 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

Your homepage downloads 7.2 MB in 107 requests on a phone: scripts 4.0 MB (30), images 1.2 MB (38) and stylesheets 1.1 MB (7). Under 2 MB keeps phones on slow connections fast.

image_mobile weighs 528 KiB. On a phone connection a single image that size takes seconds.

3 images (605 KiB) are 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 2.04 g of CO₂e: 244.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

4 images have 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.

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

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

Elements marked as presentational should be consistently ignored: 7 elements on the page fail this check, rated minor by axe-core.

Your title is only 23 characters: “Lapi Laboratorio Médico”. 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.

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

The homepage links to 38 pages on lapi.com.mx and 19 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.

There is no https://lapi.com.mx/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

https://lapi.com.mx/shop and https://lapi.com.mx/r/guD all use the title “Tienda Virtual | Lapi Laboratorio Médico”. Search engines can't tell which page to show for a search, so each competes with the others.

https://lapi.com.mx/servicios-queretaro, https://lapi.com.mx/promociones, https://lapi.com.mx/no-vas-sola and https://lapi.com.mx/genetica have no meta description, so Google writes the search snippet from whatever text it finds.

https://lapi.com.mx/shop and https://lapi.com.mx/r/guD use the same meta description. A description written for each page earns more clicks.

Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://lapi.com.mx/r/s6C, whose canonical is https://lapi.com.mx/basicosdetusalud. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://lapi.com.mx/no-vas-sola and https://lapi.com.mx/r/s6C have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

1 error was logged to the browser console while the page loaded, for example “Identifier 'animationSpeed' has already been declared”.

Large scripts ship without source maps.

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.

Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

Your longest form asks for 8 fields (7 required). Every extra field lowers completion.

The homepage has only about 213 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, LinkedIn Insight 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 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 24 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.