Website review, no card needed
univision.com website review
Visit site (opens in a new tab)Reviewed 11 October 202636 issues · 88 checks
This review found 36 issues worth fixing on univision.com, 14 of them high impact, across 88 checks. The most urgent: mobile performance score: 48. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
79CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Apr 18, 2026 | 1.8 s |
| Apr 25, 2026 | 1.8 s |
| May 2, 2026 | 1.8 s |
| May 9, 2026 | 1.8 s |
| May 16, 2026 | 1.9 s |
| May 23, 2026 | 1.9 s |
| May 30, 2026 | 1.9 s |
| Jun 6, 2026 | 1.8 s |
| Jun 13, 2026 | 1.8 s |
| Jun 20, 2026 | 1.9 s |
| Jun 27, 2026 | 1.9 s |
| Jul 4, 2026 | 1.9 s |
| Jul 11, 2026 | 2.0 s |
| Jul 18, 2026 | 2.0 s |
| Jul 25, 2026 | 2.0 s |
| Aug 1, 2026 | 1.9 s |
| Aug 8, 2026 | 1.9 s |
| Aug 15, 2026 | 1.9 s |
| Aug 22, 2026 | 1.9 s |
| Aug 29, 2026 | 1.9 s |
| Sep 5, 2026 | 1.9 s |
| Sep 12, 2026 | 1.9 s |
| Sep 19, 2026 | 2.0 s |
| Sep 26, 2026 | 2.0 s |
| Oct 3, 2026 | 1.9 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Apr 18, 2026 | 202 ms |
| Apr 25, 2026 | 201 ms |
| May 2, 2026 | 202 ms |
| May 9, 2026 | 204 ms |
| May 16, 2026 | 206 ms |
| May 23, 2026 | 207 ms |
| May 30, 2026 | 208 ms |
| Jun 6, 2026 | 207 ms |
| Jun 13, 2026 | 206 ms |
| Jun 20, 2026 | 205 ms |
| Jun 27, 2026 | 204 ms |
| Jul 4, 2026 | 205 ms |
| Jul 11, 2026 | 201 ms |
| Jul 18, 2026 | 198 ms |
| Jul 25, 2026 | 196 ms |
| Aug 1, 2026 | 192 ms |
| Aug 8, 2026 | 191 ms |
| Aug 15, 2026 | 189 ms |
| Aug 22, 2026 | 184 ms |
| Aug 29, 2026 | 180 ms |
| Sep 5, 2026 | 183 ms |
| Sep 12, 2026 | 182 ms |
| Sep 19, 2026 | 184 ms |
| Sep 26, 2026 | 185 ms |
| Oct 3, 2026 | 182 ms |
Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.
One score from every part of this review. How it works
How it loaded on a phone
1.0 s
1.9 s
2.9 s
3.9 s
4.8 s
5.8 s
6.8 s
7.7 s
Speed
Mobile performance score: 48
48/100Your mobile performance score is 48 (desktop: 61). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 8.5 s
A phone's processor spends 8.5 s on main-thread work while loading, 4.8 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
5,255 HTML elements
The page has 5,255 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Google/Doubleclick Ads and Rubicon Project and others), adding 2.3 MB and 1.6 s of main-thread time.
Reduce unused JavaScript
300 ms · 965 KiBAbout 965 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.
Use efficient cache lifetimes
870 KiB99 files are served with short cache lifetimes, so returning visitors download them again (870 KiB).
Render-blocking requests
550 ms2 files block the first paint until they finish downloading. Deferring or inlining them could save about 550 ms.
Google Tag Manager adds 314 ms
314 msGoogle Tag Manager costs a phone 314 ms of main-thread work and 507 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/Doubleclick Ads adds 271 ms
271 msGoogle/Doubleclick Ads costs a phone 271 ms of main-thread work and 543 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.
Rubicon Project adds 254 ms
254 msRubicon Project costs a phone 254 ms of main-thread work and 259 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.
DoubleVerify adds 254 ms
254 msDoubleVerify costs a phone 254 ms of main-thread work and 207 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.
Optanon adds 108 ms
108 msOptanon costs a phone 108 ms of main-thread work and 368 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 on the main thread
20 long tasks block the main thread while loading, the longest for 242 ms. During a long task the page ignores taps.
Improve image delivery
200 KiB4 images could be 200 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Legacy JavaScript
90 KiBPolyfills for old browsers add 90 KiB JavaScript that modern phones do not need.
Reduce unused CSS
25 KiBAbout 25 KiB of CSS is downloaded but never applied on this page.
Chained critical requests
Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.
1 checks passed
Server response: 29 ms
29 msYour server sent the HTML in 29 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Fails Core Web Vitals for real visitors
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.
Speed Index: 18.9 s
18.9 sVisually, the page fills in at 18.9 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 56.4 s
56.4 sThe page becomes fully interactive after 56.4 s. Good is under 3.8 s.
Total Blocking Time: 901 ms
901 msScripts block taps and scrolling for 901 ms in total while the page loads. Good is under 200 ms.
Largest Contentful Paint: 4.4 s
4.4 sYour largest element takes 4.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Poco antes de tocar tierra, el núcleo del peligroso huracán…”.
First Contentful Paint: 3.0 s
3.0 sThe first text or image appears after 3.0 s on a phone. Good is under 1.8 s.
Real-user TTFB: 835 ms
835 msReal visitors wait 835 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) held steady for real visitors
-9%Over the last 25 four-week periods to 2026-10-03, real Chrome visitors' tap response (inp) went from 202 ms to 182 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+8%Over the last 25 four-week periods to 2026-10-03, real Chrome visitors' largest content (lcp) went from 1.8 s to 1.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 checks passed
Real-user LCP: 1.3 s
1.3 sReal visitors wait 1.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 145 ms
145 msReal visitors wait 145 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.08
0.08For real visitors the layout shifts by 0.08 (75th percentile). Good is under 0.1.
Real-user FCP: 1.3 s
1.3 sReal visitors see the first content after 1.3 s (75th percentile). Good is under 1.8 s.
Cumulative Layout Shift: 0.07
0.07The layout barely moves while loading (CLS 0.07, good is under 0.1).
Images and page weight
Page weight: 5.5 MB in 1,163 requests
5.5 MBYour homepage downloads 5.5 MB in 1,163 requests on a phone: scripts 3.2 MB (122), images 1.1 MB (350) and other files 587 KiB (554). Under 2 MB keeps phones on slow connections fast.
1 image in older formats
1 image (137 KiB) 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.
About 1.5 g of CO₂ per visit
1.55 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.55 g of CO₂e: 185.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
9 text elements with low contrast
9 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
2 tap targets too small
2 tap targets are too small or too close together to hit reliably with a finger.
Frames without titles
1 frame has no title, so screen-reader users cannot tell what it contains.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
All page content should be contained by landmarks (416 elements)
All page content should be contained by landmarks: 416 elements on the page fail this check, rated moderate by axe-core.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
27 links without text
27 visible links have no text or label, so screen readers cannot say where they go.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (1 element).
2 checks passed
Every image has alt text
All 300 images in the HTML carry an alt attribute.
37 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 45 WCAG 2.2 A/AA and best-practice rules on the phone render: 37 passed and 8 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (113 characters)
Your title is 113 characters, so Google will cut it off around 60: “Univision | Shows, Noticias, Entretenimiento, Deportes y Novelas - Champions League y Lig…”.
528 internal links, 116 external
The homepage links to 528 pages on univision.com and 116 external pages.
7 checks passed
Meta description: 111 characters
Your meta description is 111 characters: “La mejor cobertura en Noticias, Deportes y Entretenimiento. Lo mejor de nuestra programación de TV. | Univision”.
One H1 headline
Your main headline reads: “Univision | Shows, Noticias, Entretenimiento, Deportes y Novelas - Champions League y Liga MX en vivo | Univision”.
Canonical URL set
The canonical URL is https://www.univision.com/.
Structured data in place
Structured data found: BreadcrumbList.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at https://www.univision.com/sitemap.xml.
AI search readiness
No Organization structured data
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.
No llms.txt
There is no https://www.univision.com/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.
2 checks passed
AI answer engines may read the site
Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.
Text is in the HTML
Your server sends the page's text in the HTML (5,109 words), so crawlers that don't run JavaScript still read it.
Other pages
2 pages without an H1
https://www.univision.com/temas/iran and https://www.univision.com/temas/destino-2026 have no <h1> headline, so visitors and search engines get no clear main topic.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 156 found) and read each the way a search engine does.
6 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a meta description
All 15 pages that loaded have a meta description.
Titles are unique
Every page we checked has its own title.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
30 third-party cookies
30 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
24 small tap targets
24 of 75 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“The Topics API is deprecated and will be removed in a future release.”).
Browser-reported issues
Chrome logged issues while loading the page (“Mixed content”).
1 low-resolution image
1 image is served at too low a resolution for sharp phone screens.
2 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
No risk reducer
No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.
About 2,154 words of copy
The homepage carries about 2,154 words of visible text.
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “SHOP” and “🛍️ Shop Univision”.
2 calls to action
The homepage has 2 calls to action, for example “Shop” and “🛍️ Shop Univision”.
Social proof on the page
Social proof on the homepage: 102 customer or partner logos and 5 trust badges.
Analytics in place
Analytics detected: Google Tag Manager.
Privacy and tracking
1 tracker load before any consent
1Before a visitor clicks anything, the page loads Google Tag Manager (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.
4 other companies contacted
Loading the homepage contacts 4 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: OneTrust
A consent management tool (OneTrust) loads with the page.
Security, domain, email and software versions
The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at univision.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Go beyond the website
What your $25 Growth Playbook adds
This review found 36 issues on univision.com, including 19 speed issues, 1 SEO issue and 1 conversion gap. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.
- 28 research agents read your site, reviews, competitors, communities and public filings
- Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
- Competitor intelligence with battlecards for your closest rivals
- Ideal customer profile, buyer segments and buying-stage funnel
- Ranked channels, outreach sequences and content angles
- Live Reddit threads where buyers ask for what you sell, with draft replies
- Earned media and PR openings
- At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
- PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
- Refresh the playbook later to see what changed
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.