Website review, no card needed

bringeri.com.ar logo

bringeri.com.ar website review

Visit site (opens in a new tab)Reviewed 19 October 202652 issues · 89 checks

This review found 52 issues worth fixing on bringeri.com.ar, 24 of them high impact, across 89 checks. The most urgent: reduce unused JavaScript. 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
9.2 s3.0 sApr 25Oct 108.4 s
Show as table
DateReal-visitor load time (LCP)
Apr 25, 20264.1 s
May 2, 20264.0 s
May 9, 20263.9 s
May 16, 20263.8 s
May 23, 20263.8 s
May 30, 20263.7 s
Jun 6, 20263.8 s
Jun 13, 20264.0 s
Jun 20, 20264.2 s
Jun 27, 20264.2 s
Jul 4, 20264.7 s
Jul 11, 20265.7 s
Jul 18, 20266.5 s
Jul 25, 20267.6 s
Aug 1, 20267.9 s
Aug 8, 20268.0 s
Aug 15, 20268.2 s
Aug 22, 20268.3 s
Aug 29, 20268.4 s
Sep 5, 20268.5 s
Sep 12, 20268.5 s
Sep 19, 20268.5 s
Sep 26, 20268.5 s
Oct 3, 20268.4 s
Oct 10, 20268.4 s
Real-visitor tap response (INP)75th percentile, phones
663 ms158 msApr 25Oct 10231 ms
Show as table
DateReal-visitor tap response (INP)
Apr 25, 2026495 ms
May 2, 2026489 ms
May 9, 2026483 ms
May 16, 2026481 ms
May 23, 2026484 ms
May 30, 2026502 ms
Jun 6, 2026536 ms
Jun 13, 2026594 ms
Jun 20, 2026605 ms
Jun 27, 2026577 ms
Jul 4, 2026482 ms
Jul 11, 2026365 ms
Jul 18, 2026289 ms
Jul 25, 2026243 ms
Aug 1, 2026229 ms
Aug 8, 2026225 ms
Aug 15, 2026222 ms
Aug 22, 2026217 ms
Aug 29, 2026216 ms
Sep 5, 2026221 ms
Sep 12, 2026225 ms
Sep 19, 2026229 ms
Sep 26, 2026230 ms
Oct 3, 2026233 ms
Oct 10, 2026231 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 bringeri.com.ar (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. bringeri.com.ar at 1.3 s1.3 s
  2. bringeri.com.ar at 2.6 s2.6 s
  3. bringeri.com.ar at 4.0 s4.0 s
  4. bringeri.com.ar at 5.3 s5.3 s
  5. bringeri.com.ar at 6.6 s6.6 s
  6. bringeri.com.ar at 7.9 s7.9 s
  7. bringeri.com.ar at 9.3 s9.3 s
  8. bringeri.com.ar at 10.6 s10.6 s

Speed

13 to fix5
  • Reduce unused JavaScript

    5.5 s · 1.3 MB

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

  • vtexassets.com adds 1.5 s

    1.5 s

    vtexassets.com costs a phone 1.5 s of main-thread work and 2.8 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.

  • Use efficient cache lifetimes

    1.3 s · 539 KiB

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

  • Main-thread work: 11.2 s

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

  • Mobile performance score: 5

    5/100

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

  • 4,063 HTML elements

    The page has 4,063 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 (vtexassets.com, Google CDN and Google Tag Manager and others), adding 6.9 MB and 3.7 s of main-thread time.

  • Google CDN adds 814 ms

    814 ms

    Google CDN costs a phone 814 ms of main-thread work and 2.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.

  • Google Tag Manager adds 812 ms

    812 ms

    Google Tag Manager costs a phone 812 ms of main-thread work and 896 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.

  • Improve image delivery

    150 ms · 594 KiB

    27 images could be 594 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 CSS

    600 ms · 84 KiB

    About 84 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 600 ms faster on a phone.

  • Legacy JavaScript

    300 ms · 47 KiB

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

  • 20 long tasks on the main thread

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

  • Font display

    250 ms

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

  • Render-blocking requests

    150 ms

    1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 150 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.

  • Minify JavaScript

    4 KiB

    4 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 37 ms

    37 ms

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

Core Web Vitals

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

  • Real-user LCP: 6.0 s

    6.0 s

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

  • Real-user INP: 1.1 s

    1.1 s

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

  • Real-user CLS: 0.70

    0.70

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

  • Real-user FCP: 3.8 s

    3.8 s

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

  • First Contentful Paint: 12.6 s

    12.6 s

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

  • Largest Contentful Paint: 22.7 s

    22.7 s

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

  • Speed Index: 20.5 s

    20.5 s

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

  • Time to Interactive: 34.5 s

    34.5 s

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

  • Cumulative Layout Shift: 0.716

    0.716

    The layout shifts by 0.716 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • Total Blocking Time: 1.8 s

    1.8 s

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

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

    +107%

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

  • Real-user TTFB: 1.3 s

    1.3 s

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

  • 18 images without width and height

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

1 checks passed
  • Tap response (INP) got 53% faster for real visitors

    -53%

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

Images and page weight

2 to fix60
  • Page weight: 6.2 MB in 257 requests

    6.2 MB

    Your homepage downloads 6.2 MB in 257 requests on a phone: scripts 3.2 MB (69), fonts 936 KiB (12) and images 840 KiB (63). Under 2 MB keeps phones on slow connections fast.

  • 2 images far larger than shown

    39 KiB

    2 images are downloaded at several times the size a phone draws them, for example 180851-500-auto at 500 px wide, shown at 144 px. Resized copies would save about 39 KiB.

  • 6 images in older formats

    6 images (285 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.

  • 1 image below the first screen load straight away

    1 image further down the page (50 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 1.8 g of CO₂ per visit

    1.76 g

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

Accessibility

7 to fixGoogle 8490
  • 2 buttons without a name

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

  • 21 text elements with low contrast

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

  • 18 tap targets too small

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

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

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

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    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.

  • 5 links without text

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

  • 2 form fields without a label

    2 form fields have 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. (9 elements).

2 checks passed
  • Every image has alt text

    All 93 images in the HTML carry an alt attribute.

  • 44 automated accessibility rules passed

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

SEO

4 to fixGoogle 10078
  • No H1 headline

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

  • Meta description is long (165 characters)

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

  • Structured data has 1 problem

    Structured data found (ItemList and WebSite) but with 1 problem, for example “WebSite: missing name”.

  • No social preview image

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

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 108 internal links, 1 external

    The homepage links to 108 pages on bringeri.com.ar and 1 external page.

4 checks passed
  • Title: 63 characters

    Your title is a healthy 63 characters: “Bringeri, Tienda de Electro, Tecnología y Hogar al mejor precio”.

  • Canonical URL set

    The canonical URL is https://www.bringeri.com.ar/.

  • 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.bringeri.com.ar/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.

  • No llms.txt

    There is no https://www.bringeri.com.ar/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 (956 words), so crawlers that don't run JavaScript still read it.

Other pages

4 to fix79
  • 3 linked pages hidden from search

    https://www.bringeri.com.ar/291, https://www.bringeri.com.ar/138 and https://www.bringeri.com.ar/293 are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

  • 3 pages share a title

    /, https://www.bringeri.com.ar/promociones-bancarias and https://www.bringeri.com.ar/Sucursales all use the title “Bringeri, Tienda de Electro, Tecnología y Hogar al mejor precio”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 5 pages share a meta description

    https://www.bringeri.com.ar/291, https://www.bringeri.com.ar/138, https://www.bringeri.com.ar/293, https://www.bringeri.com.ar/promociones-bancarias and https://www.bringeri.com.ar/Sucursales use the same meta description. A description written for each page earns more clicks.

  • 14 pages without an H1

    https://www.bringeri.com.ar/291, https://www.bringeri.com.ar/138, https://www.bringeri.com.ar/293, https://www.bringeri.com.ar/tecnologia/tv--y-accesorios/tv, https://www.bringeri.com.ar/climatizacion/calefaccion and https://www.bringeri.com.ar/tecnologia/celulares and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 2 pages with very little text

    https://www.bringeri.com.ar/promociones-bancarias and https://www.bringeri.com.ar/Sucursales 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.

  • 15 internal pages checked

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

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

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9287
  • 22 small tap targets

    22 of 95 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Uncaught (in promise) p: OneSignal: This app ID does not match any existing app. Double check your app ID.”.

  • Requests the geolocation permission on page load

    Requests the geolocation permission on page load.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

  • 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 757 words of copy

    The homepage carries about 757 words of visible text.

  • Urgency cues

    The page uses urgency cues (a countdown or limited-time wording).

1 checks passed
  • Analytics in place

    Analytics detected: Google Tag Manager and Meta Pixel.

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 Microsoft Clarity (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.

  • 20 cookies set on arrival

    20

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

  • 35 other companies contacted

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

Upkeep, stack and company

Stack

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 52 issues on bringeri.com.ar, including 27 speed issues, 4 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