latina.pe website review

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

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

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

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

8 third-party services load with your homepage (Google/Doubleclick Ads, adkaora.space and Pubmatic and others), adding 3.0 MB and 2.1 s of main-thread time.

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

Google/Doubleclick Ads costs a phone 917 ms of main-thread work and 1.7 MB 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.

17 images could be 508 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.

adkaora.space costs a phone 236 ms of main-thread work and 372 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 225 ms of main-thread work and 325 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 184 ms. During a long task the page ignores taps.

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

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

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

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

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

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

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

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

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

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

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

Your homepage downloads 7.5 MB in 1,119 requests on a phone: scripts 3.5 MB (102), images 1.8 MB (308) and media 1.4 MB (1). Under 2 MB keeps phones on slow connections fast.

m_fb3e32340d9a44333dc2bc2b16842a2e0.png is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

6 images are downloaded at several times the size a phone draws them, for example m_fb3e32340d9a44333dc2bc2b16842a2e0.png at 1,279 px wide, shown at 350 px. Resized copies would save about 207 KiB.

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

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

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

1 frame has no title, so screen-reader users cannot tell what it contains.

All page content should be contained by landmarks: 3 elements on the page fail this check, rated moderate by axe-core.

Main landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

Document should not have more than one main landmark: 1 element on the page fails 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.

Alternative text of images should not be repeated as text: 45 elements on the page fail this check, rated minor by axe-core.

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

1 form field has no label, so screen readers announce an empty box and autofill guesses.

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

Your title is only 17 characters: “Latina Televisión”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

The homepage links to 94 pages on latina.pe and 24 external pages.

There is no https://www.latina.pe/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://www.latina.pe/vivo and https://www.latina.pe/vod declare the homepage as their canonical URL, which tells Google they are copies of the homepage and keeps them out of search results. A site-wide template setting usually causes this.

/, https://www.latina.pe/vivo and https://www.latina.pe/vod all use the title “Latina Televisión”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.latina.pe/programas/arriba-mi-gente-61824/cap-tulos-completos-22145893/1/637, https://www.latina.pe/programas/por-amor-a-mi-hijo/capitulos-completos/1/13 and https://www.latina.pe/programas/kpopverso/latina-noticias/1/8 have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.latina.pe/vivo and https://www.latina.pe/vod use the same meta description. A description written for each page earns more clicks.

https://www.latina.pe/vod, https://www.latina.pe/programas/yo-soy-43547, https://www.latina.pe/programas/yo-soy-43547/capitulos-completos-t2/2/9, https://www.latina.pe/programas/arriba-mi-gente-61824, https://www.latina.pe/programas/arriba-mi-gente-61824/cap-tulos-completos-22145893/1/637 and https://www.latina.pe/programas/valentina-valiente-51247 and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.latina.pe/programas/yo-soy-43547/capitulos-completos-t2/2/9, https://www.latina.pe/programas/arriba-mi-gente-61824/cap-tulos-completos-22145893/1/637, https://www.latina.pe/programas/valentina-valiente-51247/cap-tulos-completos-6570403/1/168, https://www.latina.pe/programas/las-vueltas-del-amor/capitulos-completos/1/56, https://www.latina.pe/programas/por-amor-a-mi-hijo/capitulos-completos/1/13 and https://www.latina.pe/programas/kpopverso/latina-noticias/1/8 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 15 pages linked from your homepage (of 62 found) and read each the way a search engine does.

55 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_SOCKET_NOT_CONNECTED”.

Chrome logged issues while loading the page (“Cookie”).

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

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