medialabla.com website review

76 files are served with short cache lifetimes, so returning visitors download them again (5.8 MB).

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

5 images could be 1.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 3.5 s faster on a phone.

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

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

A phone's processor spends 5.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 (Google CDN, Google Tag Manager and Facebook and others), adding 1.9 MB and 2.0 s of main-thread time.

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

Google Tag Manager costs a phone 546 ms of main-thread work and 504 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 314 ms. During a long task the page ignores taps.

Facebook costs a phone 280 ms of main-thread work and 220 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.

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

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

8 KiB could be saved by minifying JavaScript.

7 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 30.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Agencia de marketing digital medialab”.

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

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

The layout shifts by 0.83 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

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

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

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

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

28 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-10, real Chrome visitors' tap response (inp) went from 155 ms to 173 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

Your homepage downloads 7.9 MB in 129 requests on a phone: images 5.4 MB (40), scripts 1.9 MB (49) and other files 367 KiB (20). Under 2 MB keeps phones on slow connections fast.

6 images weigh 4.9 MB together. On a phone connection a single image that size takes seconds.

7 images further down the page (3.6 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

5 images (2.3 MB) 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.25 g of CO₂e: 270.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

4 buttons have no accessible name, so screen readers announce just “button”.

2 dropdowns have no label.

ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

Some list items are not inside a list.

1 image has no alt text, which hurts accessibility and image search.

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.

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

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

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

ARIA role should be appropriate for the element: 3 elements on the page fail this check, rated minor by axe-core.

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

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

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

The homepage links to 37 pages on medialabla.com and 5 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.

The HTML your server sends has 272 of the 457 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.

https://medialabla.com/inicio declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.

/ and https://medialabla.com/inicio all use the title “Agencia de Marketing Digital en Perú | Media Lab”. Search engines can't tell which page to show for a search, so each competes with the others.

https://medialabla.com/articulos and https://medialabla.com/articulos/como-construir-un-roadmap-de-ia-empresarial-estrategico have no meta description, so Google writes the search snippet from whatever text it finds.

https://medialabla.com/inicio, https://medialabla.com/servicios, https://medialabla.com/nosotros, https://medialabla.com/marketlab, https://medialabla.com/contactanos and https://medialabla.com/casos_exito/coco-y-lucas and 5 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://medialabla.com/articulos, https://medialabla.com/contactanos and https://medialabla.com/casos_exito/coco-y-lucas have 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 14 pages linked from your homepage and read each the way a search engine does.

3 errors were logged to the browser console while the page loaded, for example “Cannot read properties of null (reading 'scrollWidth')”.

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: 6 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.

Your longest form asks for 11 fields (10 required). Every extra field lowers completion.

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and LinkedIn Insight and 2 mores (measured from a US location before any click). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 5 cookies (measured from a US location before any click).

Loading the homepage contacts 25 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.