Website review, no card needed

gruporivero.com logo

gruporivero.com website review

Visit site (opens in a new tab)Reviewed 25 October 202639 issues · 83 checks

This review found 39 issues worth fixing on gruporivero.com, 11 of them high impact, across 83 checks. The most urgent: render-blocking 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
3.4 s2.5 sMay 2Oct 172.6 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20263.3 s
May 9, 20263.3 s
May 16, 20263.3 s
May 23, 20263.2 s
May 30, 20263.1 s
Jun 6, 20263.0 s
Jun 13, 20263.0 s
Jun 20, 20263.1 s
Jun 27, 20263.1 s
Jul 4, 20263.1 s
Jul 11, 20263.0 s
Jul 18, 20262.8 s
Jul 25, 20262.9 s
Aug 1, 20262.9 s
Aug 8, 20262.9 s
Aug 15, 20262.9 s
Aug 22, 20262.8 s
Aug 29, 20262.8 s
Sep 5, 20262.8 s
Sep 12, 20262.7 s
Sep 19, 20262.7 s
Sep 26, 20262.7 s
Oct 3, 20262.6 s
Oct 10, 20262.6 s
Oct 17, 20262.6 s
Real-visitor tap response (INP)75th percentile, phones
309 ms289 msMay 2Oct 17294 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026299 ms
May 9, 2026304 ms
May 16, 2026302 ms
May 23, 2026304 ms
May 30, 2026298 ms
Jun 6, 2026295 ms
Jun 13, 2026297 ms
Jun 20, 2026291 ms
Jun 27, 2026293 ms
Jul 4, 2026300 ms
Jul 11, 2026297 ms
Jul 18, 2026299 ms
Jul 25, 2026303 ms
Aug 1, 2026304 ms
Aug 8, 2026305 ms
Aug 15, 2026307 ms
Aug 22, 2026303 ms
Aug 29, 2026298 ms
Sep 5, 2026302 ms
Sep 12, 2026300 ms
Sep 19, 2026305 ms
Sep 26, 2026300 ms
Oct 3, 2026298 ms
Oct 10, 2026297 ms
Oct 17, 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 gruporivero.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. gruporivero.com at 0.4 s0.4 s
  2. gruporivero.com at 0.8 s0.8 s
  3. gruporivero.com at 1.3 s1.3 s
  4. gruporivero.com at 1.7 s1.7 s
  5. gruporivero.com at 2.1 s2.1 s
  6. gruporivero.com at 2.5 s2.5 s
  7. gruporivero.com at 2.9 s2.9 s
  8. gruporivero.com at 3.4 s3.4 s

Speed

4 to fix68
  • Render-blocking requests

    1.4 s

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

  • Reduce unused JavaScript

    1.0 s · 163 KiB

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

  • Mobile performance score: 68

    68/100

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

  • Use efficient cache lifetimes

    300 ms · 141 KiB

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

  • 7 third-party services on the page

    7 third-party services load with your homepage (Google Tag Manager, TikTok and autogenius.io and others), adding 404 KiB and 358 ms of main-thread time.

  • Improve image delivery

    150 ms · 15 KiB

    1 image could be 15 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.

  • 4 long tasks on the main thread

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

  • Font display

    100 ms

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

  • Reduce unused CSS

    75 KiB

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

  • Phones get a much slower page than desktops

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

  • Legacy JavaScript

    9 KiB

    Polyfills for old browsers add 9 KiB JavaScript that modern phones do not need.

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

2 checks passed
  • Main-thread work: 0.7 s

    A phone's processor spends 0.7 s on main-thread work while loading, 379 ms of it running JavaScript. That is comfortably low.

  • Server response: 53 ms

    53 ms

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

Core Web Vitals

10 to fix0
  • 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: 7.7 s

    7.7 s

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

  • First Contentful Paint: 3.1 s

    3.1 s

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

  • Time to Interactive: 7.7 s

    7.7 s

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

  • Real-user LCP: 2.6 s

    2.6 s

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

  • Real-user INP: 296 ms

    296 ms

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

  • Real-user CLS: 0.13

    0.13

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

  • Real-user FCP: 1.9 s

    1.9 s

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

  • Speed Index: 3.4 s

    3.4 s

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

  • 4 images without width and height

    4 images have no width and height attributes, so the layout jumps as each one loads.

  • Tap response (INP) held steady for real visitors

    -2%

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

4 checks passed
  • Real-user TTFB: 499 ms

    499 ms

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

  • Largest content (LCP) got 20% faster for real visitors

    -20%

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

  • Total Blocking Time: 141 ms

    141 ms

    Scripts block the page for only 141 ms while loading. Good is under 200 ms.

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

1 to fix97
  • An image on the first screen is lazy-loaded

    f-movil-1.webp 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).

  • About 0.3 g of CO₂ per visit

    0.26 g

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

3 checks passed
  • Page weight: 930 KiB in 26 requests

    930 KiB

    Your homepage downloads 930 KiB in 26 requests on a phone: scripts 415 KiB (8), other files 311 KiB (12) and HTML 102 KiB (1). That is a lean page.

  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images are sized for phones

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

Accessibility

5 to fixGoogle 8489
  • ARIA attributes must conform to valid values (1 element)

    ARIA attributes must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.

  • 12 images without alt text

    12 images have no alt text, which hurts accessibility and image search.

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

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

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

  • Headings skip levels

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

1 checks passed
  • 28 automated accessibility rules passed

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

SEO

7 to fixGoogle 10067
  • Title is long (75 characters)

    Your title is 75 characters, so Google will cut it off around 60: “Grupo Rivero Chevrolet Nissan Monterrey - Agencia Autos Nuevos y Seminuevos”.

  • 10 H1 headlines

    There are 10 <h1> headlines (“DA CLIC EN TU MARCA FAVORITA”, “¡NADIE TE VA CUIDAR” and “COMO RIVERO!”). One clear main headline is easier for people and search engines.

  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

  • Meta description is long (252 characters)

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

  • Structured data has 1 problem

    Structured data found (AutoDealer, Organization and WebSite) but with 1 problem, for example “AutoDealer: url is not an absolute URL ("www.gruporivero.com")”.

  • No XML sitemap

    No XML sitemap at https://www.gruporivero.com/sitemap.xml, so Google discovers your pages only by following links.

  • No robots.txt

    There is no robots.txt at gruporivero.com/robots.txt, the first file search crawlers ask for.

  • 10 internal links, 5 external

    The homepage links to 10 pages on gruporivero.com and 5 external pages.

1 checks passed
  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

AI search readiness

100
  • No llms.txt

    There is no https://www.gruporivero.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

    There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading the site and cite it in answers.

  • Organization data: 6 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.

Other pages

4 to fix68
  • 2 pages without a title

    https://www.gruporivero.com/valua-tu-carro and https://www.gruporivero.com/servicios-de-taller have no <title>, so Google invents the link text in results.

  • 2 pages share a title

    //index.html and / all use the title “Grupo Rivero Chevrolet Nissan Monterrey - Agencia Autos Nuevos y Semi…”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 2 pages without a meta description

    https://www.gruporivero.com/valua-tu-carro and https://www.gruporivero.com/servicios-de-taller have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

    https://www.gruporivero.com/valua-tu-carro has no <h1> headline, so visitors and search engines get no clear main topic.

  • 4 pages with very little text

    /, https://www.gruporivero.com/catalogo/seminuevos, https://www.gruporivero.com/valua-tu-carro and https://www.gruporivero.com/servicios-de-taller 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.

  • 6 internal pages checked

    We fetched 6 pages linked from your homepage and read each the way a search engine does.

3 checks passed
  • Linked pages load

    All 6 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

Best practices

3 to fixGoogle 7788
  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to…”).

  • 4 JavaScript errors while loading

    4 errors were logged to the browser console while the page loaded, for example “Minified React error #418; visit https://reactjs.org/docs/error-decoder.html?invariant=418 for the full message or use …”.

  • 3 distorted images

    3 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

2 checks passed
  • Tap targets are thumb-sized

    5 of 6 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix67
  • 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: 14 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

  • Only about 23 words

    The homepage has only about 23 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 map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

5 checks passed
  • Analytics in place

    Analytics detected: Google Tag Manager and TikTok Pixel.

  • Direct contact links

    Visitors can reach you directly: 3 phone links and 0 email links.

  • Opening hours shown

    Your opening hours are on the homepage.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

  • LocalBusiness structured data

    Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.

Privacy and tracking

1 to fix
  • 5 trackers load before any consent

    5

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

  • 11 cookies set on arrival

    11

    Opening the homepage sets 11 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.

  • 17 other companies contacted

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

Upkeep, stack and company

  • The footer still says © 2025.

Stack

Framework
Gatsby
Analytics
Google Tag Manager

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 39 issues on gruporivero.com, including 14 speed issues, 7 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