Website review, no card needed

cvdirectomexico.com logo

cvdirectomexico.com website review

Visit site (opens in a new tab)Reviewed 28 October 202631 issues · 71 checks

This review found 31 issues worth fixing on cvdirectomexico.com, 11 of them high impact, across 71 checks. The most urgent: page weight: 11.8 MB in 234 requests. 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
2.5 s1.6 sMay 9Oct 242.1 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20261.7 s
May 16, 20261.8 s
May 23, 20261.9 s
May 30, 20262.0 s
Jun 6, 20262.0 s
Jun 13, 20262.1 s
Jun 20, 20262.1 s
Jun 27, 20262.1 s
Jul 4, 20262.0 s
Jul 11, 20262.0 s
Jul 18, 20262.0 s
Jul 25, 20262.2 s
Aug 1, 20262.3 s
Aug 8, 20262.4 s
Aug 15, 20262.4 s
Aug 22, 20262.4 s
Aug 29, 20262.4 s
Sep 5, 20262.3 s
Sep 12, 20262.2 s
Sep 19, 20262.1 s
Sep 26, 20262.0 s
Oct 3, 20262.0 s
Oct 10, 20262.0 s
Oct 17, 20262.1 s
Oct 24, 20262.1 s
Real-visitor tap response (INP)75th percentile, phones
382 ms278 msMay 9Oct 24294 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026317 ms
May 16, 2026314 ms
May 23, 2026323 ms
May 30, 2026327 ms
Jun 6, 2026334 ms
Jun 13, 2026346 ms
Jun 20, 2026355 ms
Jun 27, 2026363 ms
Jul 4, 2026370 ms
Jul 11, 2026350 ms
Jul 18, 2026335 ms
Jul 25, 2026315 ms
Aug 1, 2026294 ms
Aug 8, 2026292 ms
Aug 15, 2026290 ms
Aug 22, 2026292 ms
Aug 29, 2026295 ms
Sep 5, 2026297 ms
Sep 12, 2026299 ms
Sep 19, 2026301 ms
Sep 26, 2026304 ms
Oct 3, 2026308 ms
Oct 10, 2026309 ms
Oct 17, 2026301 ms
Oct 24, 2026294 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 cvdirectomexico.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. cvdirectomexico.com at 1.1 s1.1 s
  2. cvdirectomexico.com at 2.2 s2.2 s
  3. cvdirectomexico.com at 3.2 s3.2 s
  4. cvdirectomexico.com at 4.3 s4.3 s
  5. cvdirectomexico.com at 5.4 s5.4 s
  6. cvdirectomexico.com at 6.5 s6.5 s
  7. cvdirectomexico.com at 7.5 s7.5 s
  8. cvdirectomexico.com at 8.6 s8.6 s

Speed

5 to fix59
  • Main-thread work: 6.4 s

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

  • 3,905 HTML elements

    The page has 3,905 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • Mobile performance score: 59

    59/100

    Your mobile performance score is 59 (desktop: 90). Pages that score under 90 lose visitors before the first paint.

  • Render-blocking requests

    300 ms

    6 files block the first paint until they finish downloading. Deferring or inlining them could save about 300 ms.

  • 13 long tasks on the main thread

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

  • Improve image delivery

    150 ms · 122 KiB

    8 images could be 122 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.

  • Reduce unused JavaScript

    150 ms · 30 KiB

    About 30 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.

  • 3 third-party services on the page

    3 third-party services load with your homepage (Shopify, carthike.com and Vimeo), adding 101 KiB and 66 ms of main-thread time.

  • Use efficient cache lifetimes

    18 KiB

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

  • Reduce unused CSS

    11 KiB

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

  • Phones get a much slower page than desktops

    Desktop scores 90 but mobile only 59. A gap that wide usually means heavy scripts and images that hit phones hardest.

  • 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: 14 ms

    14 ms

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

Core Web Vitals

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

  • Real-user INP: 715 ms

    715 ms

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

  • Speed Index: 8.5 s

    8.5 s

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

  • Largest Contentful Paint: 4.8 s

    4.8 s

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

  • Time to Interactive: 6.7 s

    6.7 s

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

  • Total Blocking Time: 475 ms

    475 ms

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

  • First Contentful Paint: 2.6 s

    2.6 s

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

  • Tap response (INP) held steady for real visitors

    -6%

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

  • Largest content (LCP) got 19% slower for real visitors

    +19%

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

5 checks passed
  • Real-user LCP: 1.4 s

    1.4 s

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

  • Real-user CLS: 0.00

    0.00

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

  • Real-user FCP: 1.2 s

    1.2 s

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

  • Real-user TTFB: 699 ms

    699 ms

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

3 to fix53
  • Page weight: 11.8 MB in 234 requests

    11.8 MB

    Your homepage downloads 11.8 MB in 234 requests on a phone: media 8.7 MB (1), images 1.8 MB (73) and other files 758 KiB (94). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    Sofia_Deluxe_900x1224_5cb86fb6-e75c-4b7d-acdd-42f6ae2b8cc9.j 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).

  • 9 images in older formats

    9 images (501 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.

  • About 3.3 g of CO₂ per visit

    3.34 g

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

1 checks passed
  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

4 to fixGoogle 8894
  • 28 buttons without a name

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

  • 3 tap targets too small

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

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

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

  • 9 links without text

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

  • Headings skip levels

    Headings skip levels (h1 → h4), which makes the page harder to scan with a screen reader.

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (2 elements).

2 checks passed
  • Every image has alt text

    All 126 images in the HTML carry an alt attribute.

  • 48 automated accessibility rules passed

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

SEO

5 to fixGoogle 10076
  • Title is long (66 characters)

    Your title is 66 characters, so Google will cut it off around 60: “CV Directo | Tienda Oficial: Jade Cook, Power Legs, IBalance y más”.

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • 2 H1 headlines

    There are 2 <h1> headlines (“” and “Botas masajeadoras inalámbricas RevitaLegs by Pow…”). One clear main headline is easier for people and search engines.

  • Meta description is long (175 characters)

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

  • No social preview image

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

  • 188 internal links, 15 external

    The homepage links to 188 pages on cvdirectomexico.com and 15 external pages.

3 checks passed
  • Canonical URL set

    The canonical URL is https://cvdirectomexico.com/.

  • 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://cvdirectomexico.com/sitemap.xml.

AI search readiness

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

3 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 (2,488 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://cvdirectomexico.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

100
  • 15 internal pages checked

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

1 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

Best practices

1 to fixGoogle 9693
  • 2 JavaScript errors while loading

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

2 checks passed
  • Tap targets are thumb-sized

    170 of 197 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix50
  • 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.

  • Thin social proof

    Social proof on the homepage: 77 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

  • 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 1,216 words of copy

    The homepage carries about 1,216 words of visible text.

2 checks passed
  • 35 short forms

    35 short forms (4 fields at most) are right on the homepage, asking for an email.

  • Direct contact links

    Visitors can reach you directly: 7 phone links and 1 email link.

Privacy and tracking

1 to fix
  • 9 trackers load before any consent

    9

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

  • 16 cookies set on arrival

    16

    Opening the homepage sets 16 cookies (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.

  • 31 other companies contacted

    Loading the homepage contacts 31 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 cvdirectomexico.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
Tailwind CSS
E-commerce
Shopify
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 31 issues on cvdirectomexico.com, including 12 speed issues, 5 SEO issues and 4 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