Website review, no card needed
sevensport.com.ar website review
Visit site (opens in a new tab)Reviewed 3 November 202659 issues · 92 checks
This review found 59 issues worth fixing on sevensport.com.ar, 28 of them high impact, across 92 checks. The most urgent: improve image delivery. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
52FClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 5.6 s |
| May 23, 2026 | 5.6 s |
| May 30, 2026 | 5.4 s |
| Jun 6, 2026 | 5.2 s |
| Jun 13, 2026 | 4.8 s |
| Jun 20, 2026 | 4.7 s |
| Jun 27, 2026 | 5.0 s |
| Jul 4, 2026 | 5.4 s |
| Jul 11, 2026 | 5.7 s |
| Jul 18, 2026 | 5.9 s |
| Jul 25, 2026 | 5.9 s |
| Aug 1, 2026 | 5.8 s |
| Aug 8, 2026 | 5.8 s |
| Aug 15, 2026 | 5.8 s |
| Aug 22, 2026 | 5.9 s |
| Aug 29, 2026 | 6.0 s |
| Sep 5, 2026 | 6.2 s |
| Sep 12, 2026 | 6.3 s |
| Sep 19, 2026 | 6.4 s |
| Sep 26, 2026 | 6.3 s |
| Oct 3, 2026 | 6.0 s |
| Oct 10, 2026 | 5.8 s |
| Oct 17, 2026 | 5.7 s |
| Oct 24, 2026 | 5.7 s |
| Oct 31, 2026 | 5.9 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 462 ms |
| May 23, 2026 | 465 ms |
| May 30, 2026 | 475 ms |
| Jun 6, 2026 | 482 ms |
| Jun 13, 2026 | 509 ms |
| Jun 20, 2026 | 508 ms |
| Jun 27, 2026 | 500 ms |
| Jul 4, 2026 | 484 ms |
| Jul 11, 2026 | 465 ms |
| Jul 18, 2026 | 459 ms |
| Jul 25, 2026 | 459 ms |
| Aug 1, 2026 | 460 ms |
| Aug 8, 2026 | 457 ms |
| Aug 15, 2026 | 449 ms |
| Aug 22, 2026 | 442 ms |
| Aug 29, 2026 | 427 ms |
| Sep 5, 2026 | 413 ms |
| Sep 12, 2026 | 413 ms |
| Sep 19, 2026 | 419 ms |
| Sep 26, 2026 | 420 ms |
| Oct 3, 2026 | 430 ms |
| Oct 10, 2026 | 430 ms |
| Oct 17, 2026 | 420 ms |
| Oct 24, 2026 | 414 ms |
| Oct 31, 2026 | 398 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
How it loaded on a phone
1.4 s
2.9 s
4.3 s
5.7 s
7.2 s
8.6 s
10.0 s
11.5 s
Speed
Improve image delivery
5.0 s · 1.9 MB36 images could be 1.9 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 5.0 s faster on a phone.
Reduce unused JavaScript
1.2 s · 1.5 MBAbout 1.5 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.2 s faster on a phone.
vtexassets.com adds 1.1 s
1.1 svtexassets.com costs a phone 1.1 s of main-thread work and 7.3 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.
Render-blocking requests
1.4 s2 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.4 s.
ThreatMetrix adds 1.1 s
1.1 sThreatMetrix costs a phone 1.1 s of main-thread work and 266 KiB 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.
Mobile performance score: 17
17/100Your mobile performance score is 17. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 8.7 s
A phone's processor spends 8.7 s on main-thread work while loading, 5.8 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
3,289 HTML elements
The page has 3,289 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 (ThreatMetrix, vtexassets.com and Google Tag Manager and others), adding 11.5 MB and 3.4 s of main-thread time.
Use efficient cache lifetimes
900 ms · 895 KiB77 files are served with short cache lifetimes, so returning visitors download them again (895 KiB).
Google CDN adds 495 ms
495 msGoogle CDN costs a phone 495 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.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 620 ms. During a long task the page ignores taps.
Google Tag Manager adds 533 ms
533 msGoogle Tag Manager costs a phone 533 ms of main-thread work and 741 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
450 ms · 49 KiBPolyfills for old browsers add 49 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 450 ms faster on a phone.
Reduce unused CSS
300 ms · 78 KiBAbout 78 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 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 KiB4 KiB could be saved by minifying JavaScript.
1 checks passed
Server response: 93 ms
93 msYour server sent the HTML in 93 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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 INP: 595 ms
595 msReal visitors wait 595 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.82
0.82For real visitors the layout shifts by 0.82 (75th percentile). Good is under 0.1.
Largest Contentful Paint: 27.9 s
27.9 sYour largest element takes 27.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “adidas 30% OFF”.
Speed Index: 20.9 s
20.9 sVisually, the page fills in at 20.9 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 48.7 s
48.7 sThe page becomes fully interactive after 48.7 s. Good is under 3.8 s.
First Contentful Paint: 5.8 s
5.8 sThe first text or image appears after 5.8 s on a phone. Good is under 1.8 s.
Cumulative Layout Shift: 0.4
0.4The layout shifts by 0.4 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Total Blocking Time: 817 ms
817 msScripts block taps and scrolling for 817 ms in total while the page loads. Good is under 200 ms.
Real-user LCP: 2.8 s
2.8 sReal visitors wait 2.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 2.7 s
2.7 sReal visitors see the first content after 2.7 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 972 ms
972 msReal visitors wait 972 ms for your server to start answering (75th percentile). Good is under 800 ms.
25 images without width and height
25 images have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) held steady for real visitors
+3%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 5.6 s to 5.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
1 checks passed
Tap response (INP) got 12% faster for real visitors
-12%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 462 ms to 398 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Images and page weight
Page weight: 10.6 MB in 285 requests
10.6 MBYour homepage downloads 10.6 MB in 285 requests on a phone: scripts 3.4 MB (76), images 3.0 MB (108) and fonts 2.3 MB (7). Under 2 MB keeps phones on slow connections fast.
1 image over 500 KB
1a05b7b0-a1e2-4540-acd8-3144fdf2a9d6___349736859c8f5583686bc weighs 991 KiB. On a phone connection a single image that size takes seconds.
3 images far larger than shown
985 KiB3 images are downloaded at several times the size a phone draws them, for example 1a05b7b0-a1e2-4540-acd8-3144fdf2a9d6___349736859c8f5583686bc at 300 px wide, shown at 60 px. Resized copies would save about 985 KiB.
2 images in older formats
2 images (1.4 MB) 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.
14 images below the first screen load straight away
14 images further down the page (458 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 3.0 g of CO₂ per visit
3.01 gBy the Sustainable Web Design model, a visit to your homepage emits about 3.01 g of CO₂e: 361.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
2 buttons without a name
2 buttons have no accessible name, so screen readers announce just “button”.
10 tap targets too small
10 tap targets are too small or too close together to hit reliably with a finger.
2 text elements with low contrast
2 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
13 images without alt text
13 images have no alt text, which hurts accessibility and image search.
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.
19 links without text
19 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. (20 elements).
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. 5 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Title is short (11 characters)
Your title is only 11 characters: “Seven Sport”. Between 30 and 65 characters leaves room to say what you do and for whom.
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.
154 internal links, 3 external
The homepage links to 154 pages on sevensport.com.ar and 3 external pages.
4 checks passed
Meta description: 123 characters
Your meta description is 123 characters: “Aprovecha Nuestras Ofertas , Cuotas sin interés - Envíos a todo el país. Retira Gratis por sucursal. Compra Ahora on li…”.
Canonical URL set
The canonical URL is https://www.sevensport.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.sevensport.com.ar/sitemap.xml.
AI search readiness
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.sevensport.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 (630 words), so crawlers that don't run JavaScript still read it.
Other pages
4 linked pages are broken
Your homepage links to https://www.sevensport.com.ar/futbol/139, https://www.sevensport.com.ar/calzado/34/34-5/139, https://www.sevensport.com.ar/calzado/35/35-5/139 and https://www.sevensport.com.ar/calzado/36/36-5/139, which answer with an error. Visitors hit a dead end and search engines drop them.
1 linked page hidden from search
https://www.sevensport.com.ar/182 is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
4 pages share a title
/, https://www.sevensport.com.ar/promociones, https://www.sevensport.com.ar/sucursales and https://www.sevensport.com.ar/marcas all use the title “Seven Sport”. Search engines can't tell which page to show for a search, so each competes with the others.
9 pages share a meta description
https://www.sevensport.com.ar/promociones, https://www.sevensport.com.ar/sucursales, https://www.sevensport.com.ar/newin, https://www.sevensport.com.ar/ofertas, https://www.sevensport.com.ar/mujer and https://www.sevensport.com.ar/hombre and 3 others use the same meta description. A description written for each page earns more clicks.
3 pages without an H1
https://www.sevensport.com.ar/promociones, https://www.sevensport.com.ar/sucursales and https://www.sevensport.com.ar/marcas have no <h1> headline, so visitors and search engines get no clear main topic.
2 pages with very little text
https://www.sevensport.com.ar/sucursales and https://www.sevensport.com.ar/marcas 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.
2 pages slow to respond
https://www.sevensport.com.ar/puma and https://www.sevensport.com.ar/182 took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 58 found) 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 11 pages that loaded have a meta description.
Every page has a title
All 11 pages that loaded have a <title>.
Best practices
23 small tap targets
23 of 80 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “a[c] is not a function”.
3 distorted images
3 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
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 495 words of copy
The homepage carries about 495 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
6 trackers load before any consent
6Before 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.
25 cookies set on arrival
25Opening the homepage sets 25 cookies, 1 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.
39 other companies contacted
Loading the homepage contacts 39 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 sevensport.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
- Hosting
- AWS
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 59 issues on sevensport.com.ar, including 28 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.