Website review, no card needed

directv.com.ec logo

directv.com.ec website review

Visit site (opens in a new tab)Reviewed 19 October 202641 issues · 71 checks

This review found 41 issues worth fixing on directv.com.ec, 19 of them high impact, across 71 checks. The most urgent: use efficient cache lifetimes. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
6.5 s4.0 sMay 2Oct 174.6 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20264.6 s
May 9, 20265.2 s
May 16, 20266.2 s
May 23, 20266.2 s
May 30, 20266.2 s
Jun 6, 20266.1 s
Jun 13, 20265.5 s
Jun 20, 20265.4 s
Jun 27, 20265.3 s
Jul 4, 20265.1 s
Jul 11, 20265.5 s
Jul 18, 20265.5 s
Jul 25, 20265.2 s
Aug 1, 20264.8 s
Aug 8, 20264.4 s
Aug 15, 20264.3 s
Aug 22, 20264.4 s
Aug 29, 20264.5 s
Sep 5, 20264.7 s
Sep 12, 20264.8 s
Sep 19, 20264.8 s
Sep 26, 20264.8 s
Oct 3, 20264.7 s
Oct 10, 20264.7 s
Oct 17, 20264.6 s
Real-visitor tap response (INP)75th percentile, phones
398 ms319 msMay 2Oct 17354 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026328 ms
May 9, 2026333 ms
May 16, 2026346 ms
May 23, 2026356 ms
May 30, 2026363 ms
Jun 6, 2026370 ms
Jun 13, 2026366 ms
Jun 20, 2026364 ms
Jun 27, 2026362 ms
Jul 4, 2026365 ms
Jul 11, 2026374 ms
Jul 18, 2026382 ms
Jul 25, 2026389 ms
Aug 1, 2026386 ms
Aug 8, 2026386 ms
Aug 15, 2026386 ms
Aug 22, 2026383 ms
Aug 29, 2026377 ms
Sep 5, 2026374 ms
Sep 12, 2026371 ms
Sep 19, 2026371 ms
Sep 26, 2026371 ms
Oct 3, 2026366 ms
Oct 10, 2026360 ms
Oct 17, 2026354 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

Full-page screenshot of directv.com.ec (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. directv.com.ec at 1.1 s1.1 s
  2. directv.com.ec at 2.3 s2.3 s
  3. directv.com.ec at 3.4 s3.4 s
  4. directv.com.ec at 4.5 s4.5 s
  5. directv.com.ec at 5.6 s5.6 s
  6. directv.com.ec at 6.8 s6.8 s
  7. directv.com.ec at 7.9 s7.9 s
  8. directv.com.ec at 9.0 s9.0 s

Speed

12 to fix33
  • Use efficient cache lifetimes

    7.8 s · 3.6 MB

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

  • Reduce unused JavaScript

    3.0 s · 1.1 MB

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

  • Google Tag Manager adds 1.5 s

    1.5 s

    Google Tag Manager costs a phone 1.5 s of main-thread work and 1.0 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Render-blocking requests

    1.3 s

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

  • Reduce unused CSS

    1.1 s · 204 KiB

    About 204 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.1 s faster on a phone.

  • Mobile performance score: 33

    33/100

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

  • Main-thread work: 6.5 s

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

  • 8 third-party services on the page

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

  • Improve image delivery

    200 ms · 847 KiB

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

  • Facebook adds 572 ms

    572 ms

    Facebook costs a phone 572 ms of main-thread work and 335 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 488 ms. During a long task the page ignores taps.

  • Amazon Web Services adds 0 ms

    0 ms

    Amazon Web Services costs a phone 0 ms of main-thread work and 1.1 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.

  • Legacy JavaScript

    200 ms · 35 KiB

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

  • Font display

    100 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 ms).

  • 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.

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

1 checks passed
  • Server response: 34 ms

    34 ms

    Your server sent the HTML in 34 ms, well inside Google's 600 ms guideline.

Core Web Vitals

10 to fix33
  • 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.

  • Largest Contentful Paint: 13.8 s

    13.8 s

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

  • Time to Interactive: 31.8 s

    31.8 s

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

  • Speed Index: 14.4 s

    14.4 s

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

  • Total Blocking Time: 2.1 s

    2.1 s

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

  • Real-user LCP: 3.7 s

    3.7 s

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

  • Real-user INP: 383 ms

    383 ms

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

  • Real-user FCP: 1.8 s

    1.8 s

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

  • Real-user TTFB: 1.2 s

    1.2 s

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

  • First Contentful Paint: 2.9 s

    2.9 s

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

  • Tap response (INP) held steady for real visitors

    +8%

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

  • Largest content (LCP) held steady for real visitors

    -5%

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

2 checks passed
  • Real-user CLS: 0.01

    0.01

    For real visitors the layout shifts by 0.01 (75th percentile). Good is under 0.1.

  • Cumulative Layout Shift: 0.002

    0.002

    The layout barely moves while loading (CLS 0.002, good is under 0.1).

Images and page weight

1 to fix70
  • Page weight: 5.3 MB in 122 requests

    5.3 MB

    Your homepage downloads 5.3 MB in 122 requests on a phone: scripts 2.5 MB (31), images 1.9 MB (47) and fonts 528 KiB (6). Under 2 MB keeps phones on slow connections fast.

  • 1 image in older formats

    1 image (49 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.50 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.50 g of CO₂e: 180.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

6 to fixGoogle 9686
  • 5 text elements with low contrast

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

  • Scrollable region must have keyboard access (1 element)

    Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

  • All page content should be contained by landmarks (2 elements)

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

  • 20 tap targets too small

    20 tap targets are too small or too close together to hit reliably with a finger.

  • 1 form field without a label

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

1 checks passed
  • 23 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 27 WCAG 2.2 A/AA and best-practice rules on the phone render: 23 passed and 4 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

4 to fixGoogle 9279
  • No H1 headline

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

  • Title is long (67 characters)

    Your title is 67 characters, so Google will cut it off around 60: “DIRECTV Ecuador | Planes de TV, internet y plataformas de streaming”.

  • Only 0 internal links

    The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.

  • 1 link crawlers can't follow

    1 link has no real href, so search engines can't follow it.

6 checks passed
  • Meta description: 159 characters

    Your meta description is 159 characters: “Consulta la oferta de planes de TV, plataformas de streaming, internet por fibra óptica y contenidos de DIRECTV. La mej…”.

  • Canonical URL set

    The canonical URL is https://www.directvla.com/.

  • Structured data in place

    Structured data found: WebSite.

  • 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 http://www.directvla.com/sitemap.xml.

AI search readiness

1 to fix83
  • 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.directvla.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.

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

Best practices

1 to fixGoogle 9692
  • 4 JavaScript errors while loading

    4 errors were logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'getRegistration') https://www.directvla.com/ec:1:6815”.

  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix33
  • No call to action on the first screen

    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 calls to action

    We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • 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.

  • Only about 100 words

    The homepage has only about 100 words of visible text; thin pages give Google and first-time buyers little to go on.

  • 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.

1 checks passed
  • Analytics in place

    Analytics detected: Hotjar.

Privacy and tracking

1 to fix
  • 7 trackers load before any consent

    7

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and Meta Pixel and 2 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.

  • 40 cookies set on arrival

    40

    Opening the homepage sets 40 cookies, 26 of them by other companies (measured from a US location before any click).

  • No consent tool detected

    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.

  • 27 other companies contacted

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

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 directv.com.ec, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
Next.js
Analytics
Hotjar

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 41 issues on directv.com.ec, including 22 speed issues, 4 SEO issues and 5 conversion gaps. 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25