Website review, no card needed

briganti.com.ar logo

briganti.com.ar website review

Visit site (opens in a new tab)Reviewed 7 November 202633 issues · 83 checks

This review found 33 issues worth fixing on briganti.com.ar, 10 of them high impact, across 83 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
3.1 s2.6 sMay 16Oct 312.7 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20262.8 s
May 23, 20262.7 s
May 30, 20262.7 s
Jun 6, 20262.7 s
Jun 13, 20262.7 s
Jun 20, 20262.7 s
Jun 27, 20262.7 s
Jul 4, 20262.8 s
Jul 11, 20262.8 s
Jul 18, 20262.8 s
Jul 25, 20262.8 s
Aug 1, 20262.9 s
Aug 8, 20262.9 s
Aug 15, 20262.9 s
Aug 22, 20262.9 s
Aug 29, 20263.0 s
Sep 5, 20263.0 s
Sep 12, 20263.0 s
Sep 19, 20263.0 s
Sep 26, 20262.9 s
Oct 3, 20262.9 s
Oct 10, 20262.8 s
Oct 17, 20262.8 s
Oct 24, 20262.8 s
Oct 31, 20262.7 s
Real-visitor tap response (INP)75th percentile, phones
549 ms208 msMay 16Oct 31506 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026249 ms
May 23, 2026247 ms
May 30, 2026247 ms
Jun 6, 2026249 ms
Jun 13, 2026252 ms
Jun 20, 2026257 ms
Jun 27, 2026263 ms
Jul 4, 2026269 ms
Jul 11, 2026270 ms
Jul 18, 2026272 ms
Jul 25, 2026274 ms
Aug 1, 2026282 ms
Aug 8, 2026296 ms
Aug 15, 2026314 ms
Aug 22, 2026349 ms
Aug 29, 2026386 ms
Sep 5, 2026436 ms
Sep 12, 2026480 ms
Sep 19, 2026494 ms
Sep 26, 2026500 ms
Oct 3, 2026502 ms
Oct 10, 2026502 ms
Oct 17, 2026502 ms
Oct 24, 2026510 ms
Oct 31, 2026506 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 briganti.com.ar (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. briganti.com.ar at 0.4 s0.4 s
  2. briganti.com.ar at 0.8 s0.8 s
  3. briganti.com.ar at 1.1 s1.1 s
  4. briganti.com.ar at 1.5 s1.5 s
  5. briganti.com.ar at 1.9 s1.9 s
  6. briganti.com.ar at 2.3 s2.3 s
  7. briganti.com.ar at 2.6 s2.6 s
  8. briganti.com.ar at 3.0 s3.0 s

Speed

10 to fix60
  • Reduce unused JavaScript

    2.1 s · 357 KiB

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

  • Mobile performance score: 60

    60/100

    Your mobile performance score is 60. Pages that score under 90 lose visitors before the first paint.

  • Reduce unused CSS

    760 ms · 132 KiB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Shopify, bc-solutions.net and Judge.me and others), adding 983 KiB and 651 ms of main-thread time.

  • Use efficient cache lifetimes

    400 ms · 59 KiB

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

  • Render-blocking requests

    450 ms

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

  • Shopify adds 313 ms

    313 ms

    Shopify costs a phone 313 ms of main-thread work and 532 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.

  • Legacy JavaScript

    300 ms · 30 KiB

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

  • 2,415 HTML elements

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

  • Main-thread work: 2.3 s

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

  • Minify CSS

    140 ms · 47 KiB

    47 KiB could be saved by minifying CSS.

  • 8 long tasks on the main thread

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

  • Minify JavaScript

    150 ms · 3 KiB

    3 KiB could be saved by minifying JavaScript.

  • Improve image delivery

    50 ms · 7 KiB

    1 image could be 7 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 50 ms faster on a phone.

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

    15 ms

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

Core Web Vitals

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

  • Largest Contentful Paint: 11.8 s

    11.8 s

    Your largest element takes 11.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: 11.8 s

    11.8 s

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

  • Speed Index: 6.5 s

    6.5 s

    Visually, the page fills in at 6.5 s (Speed Index). Good is under 3.4 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.

  • Tap response (INP) got 105% slower for real visitors

    +105%

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

  • First Contentful Paint: 2.4 s

    2.4 s

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

  • Total Blocking Time: 288 ms

    288 ms

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

  • 4 images without width and height

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

  • Largest content (LCP) held steady for real visitors

    +1%

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

5 checks passed
  • Real-user INP: 194 ms

    194 ms

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

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

    1.5 s

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

  • Real-user TTFB: 633 ms

    633 ms

    Real visitors wait 633 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

100
  • About 0.5 g of CO₂ per visit

    0.46 g

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

4 checks passed
  • Page weight: 1.6 MB in 110 requests

    1.6 MB

    Your homepage downloads 1.6 MB in 110 requests on a phone: scripts 935 KiB (54), other files 218 KiB (24) and stylesheets 195 KiB (22). That is a lean page.

  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • 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

8 to fixGoogle 7989
  • 20 text elements with low contrast

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

  • 12 tap targets too small

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

  • 3 images without alt text

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

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

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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

  • 20 links without text

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

  • Malformed lists

    Some lists contain elements other than list items, which screen readers announce wrongly.

1 checks passed
  • 43 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: 43 passed and 7 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

2 to fixGoogle 9286
  • No H1 headline

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

  • Structured data has 5 problems

    Structured data found (Organization) but with 5 problems, for example “Organization: logo is not an absolute URL ("//briganti.com.ar/cdn/shop/files/Logo_200_ac691b63-597a…”.

  • Open Graph partly set

    Open Graph is missing og:title and og:description, so shared links fall back to guesses.

  • 250 internal links, 11 external

    The homepage links to 250 pages on briganti.com.ar and 11 external pages.

5 checks passed
  • Meta description: 154 characters

    Your meta description is 154 characters: “ENVÍO GRATIS y 6 CUOTAS SIN INTERES | Descubre las últimas tendencias en zapatos, botas, mocasines, sandalias, zapatill…”.

  • Title: 33 characters

    Your title is a healthy 33 characters: “Briganti - Calzados y moda online”.

  • Canonical URL set

    The canonical URL is https://briganti.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://briganti.com.ar/sitemap.xml.

AI search readiness

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

  • Organization data: 5 of 6 facts

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

  • Text is in the HTML

    Your server sends the page's text in the HTML (779 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

1 to fix95
  • 9 pages without an H1

    https://briganti.com.ar/collections/mujer-calzado-botas-y-borcegos, https://briganti.com.ar/collections/mujer-bota-cana-alta, https://briganti.com.ar/collections/mujer-calzado-zapatilla, https://briganti.com.ar/collections/mujer-calzado-mocasin, https://briganti.com.ar/collections/mujer-calzado-zapato and https://briganti.com.ar/collections/mujer-calzado-chatita and 3 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 7 pages with very little text

    https://briganti.com.ar/collections/mujer-calzado-botas-y-borcegos, https://briganti.com.ar/collections/mujer-bota-cana-alta, https://briganti.com.ar/collections/mujer-calzado-zapatilla, https://briganti.com.ar/collections/mujer-calzado-mocasin, https://briganti.com.ar/collections/mujer-calzado-zapato and https://briganti.com.ar/collections/mujer-calzado-sandalias-y-chinelas and 1 other 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 126 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

Google 100100
3 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 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 analytics detected

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

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

    The homepage carries about 257 words of visible text.

3 checks passed
  • 1 call to action

    The homepage has 1 call to action, for example “Sign Up”.

  • 6 short forms

    6 short forms (1 field at most) are right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 20 testimonial or review blocks and 1 trust badge.

Privacy and tracking

  • 5 cookies set on arrival

    5

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

  • 9 other companies contacted

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

1 checks passed
  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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

Apps on your store

Your storefront loads 14 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Boost Ai Search Filter · Meteor Mega Menu · Judge Me Reviews · Optis Product Options · Ordersify Restocked Alerts · Bacon Menu · Deco Theme App Extension · Selleasy · Ordersify Bis · Deco Labels Badges · Cowlendar · cloudfront.net · nofraud.com · kiwisizing.com

Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info

Upkeep, stack and company

Stack

Framework
React
E-commerce
Shopify
Hosting
Cloudflare

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 33 issues on briganti.com.ar, including 19 speed issues, 2 SEO issues and 3 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