Website review, no card needed

onsports.com.ar logo

onsports.com.ar website review

Visit site (opens in a new tab)Reviewed 25 October 202650 issues · 87 checks

This review found 50 issues worth fixing on onsports.com.ar, 18 of them high impact, across 87 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
4.2 s2.5 sMay 2Oct 172.7 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20263.4 s
May 9, 20263.3 s
May 16, 20263.3 s
May 23, 20263.4 s
May 30, 20263.5 s
Jun 6, 20263.6 s
Jun 13, 20263.7 s
Jun 20, 20263.6 s
Jun 27, 20263.5 s
Jul 4, 20263.5 s
Jul 11, 20263.5 s
Jul 18, 20263.8 s
Jul 25, 20264.0 s
Aug 1, 20263.9 s
Aug 8, 20263.8 s
Aug 15, 20263.5 s
Aug 22, 20263.2 s
Aug 29, 20262.9 s
Sep 5, 20262.8 s
Sep 12, 20262.7 s
Sep 19, 20262.7 s
Sep 26, 20262.7 s
Oct 3, 20262.7 s
Oct 10, 20262.7 s
Oct 17, 20262.7 s
Real-visitor tap response (INP)75th percentile, phones
472 ms309 msMay 2Oct 17367 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026453 ms
May 9, 2026445 ms
May 16, 2026430 ms
May 23, 2026417 ms
May 30, 2026409 ms
Jun 6, 2026400 ms
Jun 13, 2026398 ms
Jun 20, 2026383 ms
Jun 27, 2026370 ms
Jul 4, 2026363 ms
Jul 11, 2026358 ms
Jul 18, 2026371 ms
Jul 25, 2026394 ms
Aug 1, 2026395 ms
Aug 8, 2026392 ms
Aug 15, 2026374 ms
Aug 22, 2026356 ms
Aug 29, 2026337 ms
Sep 5, 2026328 ms
Sep 12, 2026336 ms
Sep 19, 2026334 ms
Sep 26, 2026339 ms
Oct 3, 2026340 ms
Oct 10, 2026352 ms
Oct 17, 2026367 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 onsports.com.ar (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. onsports.com.ar at 0.8 s0.8 s
  2. onsports.com.ar at 1.6 s1.6 s
  3. onsports.com.ar at 2.4 s2.4 s
  4. onsports.com.ar at 3.2 s3.2 s
  5. onsports.com.ar at 4.0 s4.0 s
  6. onsports.com.ar at 4.8 s4.8 s
  7. onsports.com.ar at 5.6 s5.6 s
  8. onsports.com.ar at 6.4 s6.4 s

Speed

11 to fix49
  • Reduce unused JavaScript

    6.6 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 6.6 s faster on a phone.

  • Use efficient cache lifetimes

    1.5 s · 296 KiB

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

  • Mobile performance score: 49

    49/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google CDN, vtexassets.com and Google Tag Manager and others), adding 6.9 MB and 1.7 s of main-thread time.

  • Improve image delivery

    600 ms · 1.4 MB

    5 images could be 1.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 600 ms faster on a phone.

  • Google CDN adds 504 ms

    504 ms

    Google CDN costs a phone 504 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.

  • vtexassets.com adds 421 ms

    421 ms

    vtexassets.com costs a phone 421 ms of main-thread work and 3.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.

  • Reduce unused CSS

    600 ms · 51 KiB

    About 51 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.

  • Google Tag Manager adds 394 ms

    394 ms

    Google Tag Manager costs a phone 394 ms of main-thread work and 543 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 · 56 KiB

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

  • Main-thread work: 3.4 s

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

  • 16 long tasks on the main thread

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

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

    19 ms

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

Core Web Vitals

10 to fix33
  • 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 CLS: 0.67

    0.67

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

  • First Contentful Paint: 9.8 s

    9.8 s

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

  • Largest Contentful Paint: 25.1 s

    25.1 s

    Your largest element takes 25.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “adidas dia de la madre​”.

  • Time to Interactive: 27.1 s

    27.1 s

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

  • Speed Index: 15.0 s

    15.0 s

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

  • Real-user INP: 273 ms

    273 ms

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

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

  • Total Blocking Time: 289 ms

    289 ms

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

  • 14 images without width and height

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

5 checks passed
  • Real-user LCP: 2.2 s

    2.2 s

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

  • Real-user TTFB: 764 ms

    764 ms

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

  • Tap response (INP) got 20% faster for real visitors

    -20%

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

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

    -19%

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

  • Cumulative Layout Shift: 0.006

    0.006

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

Images and page weight

2 to fix50
  • Page weight: 5.4 MB in 125 requests

    5.4 MB

    Your homepage downloads 5.4 MB in 125 requests on a phone: scripts 2.6 MB (55), images 1.5 MB (23) and other files 714 KiB (35). Under 2 MB keeps phones on slow connections fast.

  • 4 images far larger than shown

    1,012 KiB

    4 images are downloaded at several times the size a phone draws them, for example 1bf52ec5-7697-4817-a936-ff849d06e25c___8191cb86b485fa12ef26c at 1,080 px wide, shown at 178 px. Resized copies would save about 1,012 KiB.

  • About 1.5 g of CO₂ per visit

    1.54 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.54 g of CO₂e: 184.7 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 load when needed

    Images below the first screen wait until the visitor scrolls to them.

Accessibility

9 to fixGoogle 8186
  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

  • Hidden but focusable

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

  • 2 tap targets too small

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

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

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

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

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

  • 3 links without text

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

2 checks passed
  • Every image has alt text

    All 15 images in the HTML carry an alt attribute.

  • 33 automated accessibility rules passed

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

SEO

3 to fixGoogle 10083
  • No H1 headline

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

  • Structured data has 1 problem

    Structured data found (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.

  • 19 internal links, 2 external

    The homepage links to 19 pages on onsports.com.ar and 2 external pages.

5 checks passed
  • Meta description: 124 characters

    Your meta description is 124 characters: “Equipate en ON Sports con adidas, Puma y Nike. Aprovechá 3 cuotas sin interés y envíos gratis a todo el país. ¡Comprá a…”.

  • Title: 62 characters

    Your title is a healthy 62 characters: “ON Sports: Zapatillas y Ropa Deportiva en 3 Cuotas Sin Interés”.

  • Canonical URL set

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

AI search readiness

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

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

Other pages

5 to fix55
  • 3 linked pages are broken

    Your homepage links to https://www.onsports.com.ar/adidas/adidas-originals/adidas-sport-inspired/adidas-sportswear, https://www.onsports.com.ar/botines/adidas/adidas-originals/adidas-sport-inspired/adidas-sportswear and https://www.onsports.com.ar/adidas-originals/adidas-sportswear/adidas-sport-inspired/adidas, which answer with an error. Visitors hit a dead end and search engines drop them.

  • 4 linked pages hidden from search

    https://www.onsports.com.ar/hombre, https://www.onsports.com.ar/mujer, https://www.onsports.com.ar/ni%C3%B1os and https://www.onsports.com.ar/141 are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

  • 5 pages share a title

    /, https://www.onsports.com.ar/preguntas-frecuentes, https://www.onsports.com.ar/sucursales, https://www.onsports.com.ar/landing-futbol and https://www.onsports.com.ar/metodos-de-pago all use the title “ON Sports: Zapatillas y Ropa Deportiva en 3 Cuotas Sin Interés”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 10 pages share a meta description

    https://www.onsports.com.ar/preguntas-frecuentes, https://www.onsports.com.ar/sucursales, https://www.onsports.com.ar/novedades, https://www.onsports.com.ar/hombre, https://www.onsports.com.ar/mujer and https://www.onsports.com.ar/ni%C3%B1os and 4 others use the same meta description. A description written for each page earns more clicks.

  • 4 pages without an H1

    https://www.onsports.com.ar/preguntas-frecuentes, https://www.onsports.com.ar/sucursales, https://www.onsports.com.ar/landing-futbol and https://www.onsports.com.ar/metodos-de-pago have no <h1> headline, so visitors and search engines get no clear main topic.

  • 2 pages with very little text

    https://www.onsports.com.ar/sucursales and https://www.onsports.com.ar/metodos-de-pago 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.

  • 13 internal pages checked

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

3 checks passed
  • Canonical URLs point to themselves

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

  • Every page has a meta description

    All 10 pages that loaded have a meta description.

  • Every page has a title

    All 10 pages that loaded have a <title>.

Best practices

3 to fixGoogle 8885
  • 12 small tap targets

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

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'register')”.

  • 2 distorted images

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

  • 1 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix42
  • 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: 3 customer or partner logos. 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.

  • Only about 9 words

    The homepage has only about 9 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 risk reducer

    No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

1 checks passed
  • Analytics in place

    Analytics detected: Google Tag Manager and Meta Pixel.

Privacy and tracking

1 to fix
  • 6 trackers load before any consent

    6

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

  • 28 other companies contacted

    Loading the homepage contacts 28 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 onsports.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 50 issues on onsports.com.ar, including 21 speed issues, 3 SEO issues and 5 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