Website review, no card needed

balamdenim.com logo

balamdenim.com website review

Visit site (opens in a new tab)Reviewed 20 November 202647 issues · 91 checks

This review found 47 issues worth fixing on balamdenim.com, 17 of them high impact, across 91 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
1.8 s1.4 sMay 30Nov 141.5 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20261.6 s
Jun 6, 20261.6 s
Jun 13, 20261.5 s
Jun 20, 20261.5 s
Jun 27, 20261.6 s
Jul 4, 20261.6 s
Jul 11, 20261.6 s
Jul 18, 20261.7 s
Jul 25, 20261.7 s
Aug 1, 20261.7 s
Aug 8, 20261.7 s
Aug 15, 20261.7 s
Aug 22, 20261.7 s
Aug 29, 20261.8 s
Sep 5, 20261.7 s
Sep 12, 20261.7 s
Sep 19, 20261.7 s
Sep 26, 20261.7 s
Oct 3, 20261.8 s
Oct 10, 20261.7 s
Oct 17, 20261.7 s
Oct 24, 20261.6 s
Oct 31, 20261.6 s
Nov 7, 20261.5 s
Nov 14, 20261.5 s
Real-visitor tap response (INP)75th percentile, phones
218 ms150 msMay 30Nov 14205 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026178 ms
Jun 6, 2026171 ms
Jun 13, 2026163 ms
Jun 20, 2026158 ms
Jun 27, 2026159 ms
Jul 4, 2026160 ms
Jul 11, 2026159 ms
Jul 18, 2026169 ms
Jul 25, 2026166 ms
Aug 1, 2026169 ms
Aug 8, 2026178 ms
Aug 15, 2026177 ms
Aug 22, 2026185 ms
Aug 29, 2026185 ms
Sep 5, 2026176 ms
Sep 12, 2026178 ms
Sep 19, 2026178 ms
Sep 26, 2026190 ms
Oct 3, 2026207 ms
Oct 10, 2026209 ms
Oct 17, 2026210 ms
Oct 24, 2026210 ms
Oct 31, 2026202 ms
Nov 7, 2026207 ms
Nov 14, 2026205 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 balamdenim.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. balamdenim.com at 3.9 s3.9 s
  2. balamdenim.com at 7.9 s7.9 s
  3. balamdenim.com at 11.8 s11.8 s
  4. balamdenim.com at 15.7 s15.7 s
  5. balamdenim.com at 19.6 s19.6 s
  6. balamdenim.com at 23.6 s23.6 s
  7. balamdenim.com at 27.5 s27.5 s
  8. balamdenim.com at 31.4 s31.4 s

Speed

15 to fix53
  • Reduce unused JavaScript

    8.0 s · 1.4 MB

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

  • Use efficient cache lifetimes

    2.4 s · 488 KiB

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

  • Main-thread work: 6.2 s

    A phone's processor spends 6.2 s on main-thread work while loading, 3.0 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, Clarity and Shopify and others), adding 3.3 MB and 1.4 s of main-thread time.

  • Mobile performance score: 53

    53/100

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

  • Improve image delivery

    200 ms · 666 KiB

    17 images could be 666 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.

  • Reduce unused CSS

    750 ms · 90 KiB

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

  • Minify JavaScript

    450 ms · 68 KiB

    68 KiB could be saved by minifying JavaScript.

  • Google Tag Manager adds 375 ms

    375 ms

    Google Tag Manager costs a phone 375 ms of main-thread work and 798 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 · 68 KiB

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

  • Clarity adds 342 ms

    342 ms

    Clarity costs a phone 342 ms of main-thread work and 30 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.

  • Shopify adds 200 ms

    200 ms

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

  • 2,378 HTML elements

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

  • rebuyengine.com adds 139 ms

    139 ms

    rebuyengine.com costs a phone 139 ms of main-thread work and 536 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.

  • azurefd.net adds 47 ms

    47 ms

    azurefd.net costs a phone 47 ms of main-thread work and 323 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.

  • Render-blocking requests

    150 ms

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

  • 12 long tasks on the main thread

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

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

  • Minify CSS

    3 KiB

    3 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 8 ms

    8 ms

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

Core Web Vitals

8 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: 44.1 s

    44.1 s

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

  • Speed Index: 16.8 s

    16.8 s

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

  • Time to Interactive: 44.8 s

    44.8 s

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

  • Real-user INP: 201 ms

    201 ms

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

  • Total Blocking Time: 399 ms

    399 ms

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

  • First Contentful Paint: 2.3 s

    2.3 s

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

  • 3 images without width and height

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

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

    +18%

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

  • Largest content (LCP) held steady for real visitors

    -4%

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

5 checks passed
  • Real-user LCP: 1.6 s

    1.6 s

    Real visitors wait 1.6 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.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: 712 ms

    712 ms

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

  • 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

2 to fix69
  • Page weight: 8.0 MB in 580 requests

    8.0 MB

    Your homepage downloads 8.0 MB in 580 requests on a phone: scripts 3.3 MB (178), images 2.6 MB (63) and other files 1.5 MB (307). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    Banner_Movil_3x2_99188c60-cd8e-4a32-beda-b80c038ea430.jpg 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).

  • 2 images below the first screen load straight away

    2 images further down the page (47 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 2.3 g of CO₂ per visit

    2.27 g

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

2 checks passed
  • 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

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

  • 16 text elements with low contrast

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

  • Hidden but focusable

    3 elements hidden from screen readers can still receive keyboard focus.

  • Elements must only use permitted ARIA attributes (3 elements)

    Elements must only use permitted ARIA attributes: 3 elements on the page fail this check, rated serious by axe-core.

  • Malformed lists

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

  • Summary elements must have discernible text (1 element)

    Summary elements must have discernible text: 1 element on the page fails this check, rated serious by axe-core.

  • 8 images without alt text

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

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

  • 30 links without text

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

  • ARIA role should be appropriate for the element (1 element)

    ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.

1 checks passed
  • 49 automated accessibility rules passed

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

SEO

3 to fixGoogle 8584
  • Title is long (67 characters)

    Your title is 67 characters, so Google will cut it off around 60: “Balam Denim Wear | Jeans y Ropa Denim para Hombre y Mujer en México”.

  • No structured data

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

  • Meta description is long (213 characters)

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

  • 240 internal links, 20 external

    The homepage links to 240 pages on balamdenim.com and 20 external pages.

5 checks passed
  • One H1 headline

    Your main headline reads: “Balam Denim Wear”.

  • Canonical URL set

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

  • 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 https://balamdenim.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.

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

Other pages

2 to fix90
  • 10 pages without a meta description

    https://balamdenim.com/pages/form-b2b, https://balamdenim.com/collections/jeans-mujeres, https://balamdenim.com/collections/blusas-y-playeras, https://balamdenim.com/collections/shorts-oferta, https://balamdenim.com/collections/chamarras-sobrecamisas-mujeres and https://balamdenim.com/collections/ropa-comoda and 4 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 3 pages without an H1

    https://balamdenim.com/pages/pagos-y-devoluciones, https://balamdenim.com/pages/guia-de-tallas and https://balamdenim.com/pages/form-b2b have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

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

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

  • 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

1 to fixGoogle 9693
  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Line: 6, column: 43, Invalid escape sequence.”.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

  • Local business without LocalBusiness data

    Your homepage shows a map but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • Thin social proof

    Social proof on the homepage: a star rating. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • Phone number is not tap-to-call

    Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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

    The homepage carries about 395 words of visible text.

3 checks passed
  • 2 short forms

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

  • Analytics in place

    Analytics detected: Google Tag Manager and Microsoft Clarity.

  • Phone number on the homepage

    Your phone number is on the homepage.

Privacy and tracking

1 to fix
  • 8 trackers load before any consent

    8

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

  • 23 cookies set on arrival

    23

    Opening the homepage sets 23 cookies, 3 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.

  • 44 other companies contacted

    Loading the homepage contacts 44 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 balamdenim.com, 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 13 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Mercado Pago Antifraud Plus · Rebuy Personalization Engine · Klaviyo Email Marketing Sms · Inbox · Sc Easy 404 Ai Redirects · Embedany · Microsoft Clarity · Littledata The Data Layer · Mercadopago Pf App · Forms · Whatsapp Chat Button · webservice.expert · rebuyengine.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
jQuery
E-commerce
Shopify
Analytics
Google Tag Manager | Microsoft Clarity
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 47 issues on balamdenim.com, including 23 speed issues, 3 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