Website review, no card needed
challenger.com.co website review
Visit site (opens in a new tab)Reviewed 26 October 202657 issues · 103 checks
This review found 57 issues worth fixing on challenger.com.co, 26 of them high impact, across 103 checks. The most urgent: reduce unused JavaScript. 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
49FClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 4.1 s |
| May 16, 2026 | 4.0 s |
| May 23, 2026 | 4.0 s |
| May 30, 2026 | 4.0 s |
| Jun 6, 2026 | 3.9 s |
| Jun 13, 2026 | 3.9 s |
| Jun 20, 2026 | 3.9 s |
| Jun 27, 2026 | 3.9 s |
| Jul 4, 2026 | 4.0 s |
| Jul 11, 2026 | 4.0 s |
| Jul 18, 2026 | 4.0 s |
| Jul 25, 2026 | 4.0 s |
| Aug 1, 2026 | 3.9 s |
| Aug 8, 2026 | 3.9 s |
| Aug 15, 2026 | 3.9 s |
| Aug 22, 2026 | 3.9 s |
| Aug 29, 2026 | 3.9 s |
| Sep 5, 2026 | 4.0 s |
| Sep 12, 2026 | 3.9 s |
| Sep 19, 2026 | 3.9 s |
| Sep 26, 2026 | 3.8 s |
| Oct 3, 2026 | 3.7 s |
| Oct 10, 2026 | 3.7 s |
| Oct 17, 2026 | 3.7 s |
| Oct 24, 2026 | 3.7 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 244 ms |
| May 16, 2026 | 234 ms |
| May 23, 2026 | 223 ms |
| May 30, 2026 | 220 ms |
| Jun 6, 2026 | 217 ms |
| Jun 13, 2026 | 218 ms |
| Jun 20, 2026 | 221 ms |
| Jun 27, 2026 | 224 ms |
| Jul 4, 2026 | 228 ms |
| Jul 11, 2026 | 231 ms |
| Jul 18, 2026 | 231 ms |
| Jul 25, 2026 | 229 ms |
| Aug 1, 2026 | 228 ms |
| Aug 8, 2026 | 225 ms |
| Aug 15, 2026 | 224 ms |
| Aug 22, 2026 | 222 ms |
| Aug 29, 2026 | 221 ms |
| Sep 5, 2026 | 227 ms |
| Sep 12, 2026 | 228 ms |
| Sep 19, 2026 | 230 ms |
| Sep 26, 2026 | 230 ms |
| Oct 3, 2026 | 228 ms |
| Oct 10, 2026 | 227 ms |
| Oct 17, 2026 | 227 ms |
| Oct 24, 2026 | 229 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.1 s
2.1 s
3.2 s
4.2 s
5.3 s
6.4 s
7.4 s
8.5 s
Speed
Reduce unused JavaScript
2.0 s · 1.6 MBAbout 1.6 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.0 s faster on a phone.
Render-blocking requests
2.5 s52 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.5 s.
Use efficient cache lifetimes
1.1 s · 368 KiB34 files are served with short cache lifetimes, so returning visitors download them again (368 KiB).
Mobile performance score: 6
6/100Your mobile performance score is 6 (desktop: 44). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 7.2 s
A phone's processor spends 7.2 s on main-thread work while loading, 4.1 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 (vtexassets.com, Google Tag Manager and Google CDN and others), adding 9.0 MB and 3.5 s of main-thread time.
Improve image delivery
300 ms · 1.5 MB17 images could be 1.5 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 300 ms faster on a phone.
vtexassets.com adds 970 ms
970 msvtexassets.com costs a phone 970 ms of main-thread work and 5.8 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 762 ms
762 msGoogle Tag Manager costs a phone 762 ms of main-thread work and 529 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.
Google CDN adds 518 ms
518 msGoogle CDN costs a phone 518 ms of main-thread work and 2.0 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.
TikTok adds 380 ms
380 msTikTok costs a phone 380 ms of main-thread work and 276 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.
Reduce unused CSS
300 ms · 62 KiBAbout 62 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.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 343 ms. During a long task the page ignores taps.
Facebook adds 298 ms
298 msFacebook costs a phone 298 ms of main-thread work and 259 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.
1,570 HTML elements
The page has 1,570 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Legacy JavaScript
200 ms · 56 KiBPolyfills for old browsers add 56 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 200 ms faster on a phone.
Minify JavaScript
150 ms · 7 KiB7 KiB could be saved by minifying JavaScript.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Phones get a much slower page than desktops
Desktop scores 44 but mobile only 6. A gap that wide usually means heavy scripts and images that hit phones hardest.
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: 23 ms
23 msYour server sent the HTML in 23 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 LCP: 4.1 s
4.1 sReal visitors wait 4.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.95
0.95For real visitors the layout shifts by 0.95 (75th percentile). Good is under 0.1.
Largest Contentful Paint: 17.6 s
17.6 sYour largest element takes 17.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “2”.
Time to Interactive: 22.6 s
22.6 sThe page becomes fully interactive after 22.6 s. Good is under 3.8 s.
Cumulative Layout Shift: 0.926
0.926The layout shifts by 0.926 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Speed Index: 11.0 s
11.0 sVisually, the page fills in at 11.0 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 2.0 s
2.0 sScripts block taps and scrolling for 2.0 s in total while the page loads. Good is under 200 ms.
First Contentful Paint: 3.9 s
3.9 sThe first text or image appears after 3.9 s on a phone. Good is under 1.8 s.
Real-user INP: 234 ms
234 msReal visitors wait 234 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
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: 1.1 s
1.1 sReal visitors wait 1.1 s for your server to start answering (75th percentile). Good is under 800 ms.
16 images without width and height
16 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
-5%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 244 ms to 229 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
1 checks passed
Largest content (LCP) got 10% faster for real visitors
-10%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 4.1 s to 3.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Images and page weight
Page weight: 7.9 MB in 234 requests
7.9 MBYour homepage downloads 7.9 MB in 234 requests on a phone: images 4.6 MB (57), scripts 2.4 MB (64) and other files 372 KiB (48). Under 2 MB keeps phones on slow connections fast.
1 image over 500 KB
8f6e8507-8be8-481b-9b5a-ebcfadce1c2f___b9b00ec30f012fa176525 weighs 725 KiB. On a phone connection a single image that size takes seconds.
8 images far larger than shown
1.1 MB8 images are downloaded at several times the size a phone draws them, for example 8f6e8507-8be8-481b-9b5a-ebcfadce1c2f___b9b00ec30f012fa176525 at 2,400 px wide, shown at 265 px. Resized copies would save about 1.1 MB.
9 images below the first screen load straight away
9 images further down the page (1.3 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
An image on the first screen is lazy-loaded
11241451-d5d4-4da5-9d2c-235e6d5bf425___8abf55cd83a5ca5a2f6c4 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).
About 2.2 g of CO₂ per visit
2.24 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.24 g of CO₂e: 269.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Accessibility
2 buttons without a name
2 buttons have no accessible name, so screen readers announce just “button”.
14 tap targets too small
14 tap targets are too small or too close together to hit reliably with a finger.
ARIA dialog and alertdialog nodes should have an accessible name (3 elements)
ARIA dialog and alertdialog nodes should have an accessible name: 3 elements on the page fail this check, rated serious by axe-core.
Hidden but focusable
3 elements hidden from screen readers can still receive keyboard focus.
All page content should be contained by landmarks (20 elements)
All page content should be contained by landmarks: 20 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 (2 elements)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 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.
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.
18 links without text
18 visible links have no text or label, so screen readers cannot say where they go.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
Alternative text of images should not be repeated as text (9 elements)
Alternative text of images should not be repeated as text: 9 elements on the page fail this check, rated minor by axe-core.
Headings should not be empty (4 elements)
Headings should not be empty: 4 elements on the page fail this check, rated minor by axe-core.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (2 elements).
2 checks passed
Every image has alt text
All 43 images in the HTML carry an alt attribute.
40 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 51 WCAG 2.2 A/AA and best-practice rules on the phone render: 40 passed and 11 failed. 2 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.
Structured data has 1 problem
Structured data found (ItemList, Organization and WebSite) but with 1 problem, for example “WebSite: missing name”.
76 internal links, 13 external
The homepage links to 76 pages on challenger.com.co and 13 external pages.
6 checks passed
Meta description: 141 characters
Your meta description is 141 characters: “Tienda oficial Challenger: neveras, lavadoras, estufas, televisores y más para tu hogar. Envío gratis y garantía de fáb…”.
Title: 49 characters
Your title is a healthy 49 characters: “Challenger | Tienda en línea de electrodomésticos”.
Canonical URL set
The canonical URL is https://www.challenger.com.co/.
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://www.challenger.com.co/sitemap.xml.
AI search readiness
No llms.txt
There is no https://www.challenger.com.co/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.
3 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 (394 words), so crawlers that don't run JavaScript still read it.
Other pages
4 pages without an H1
https://www.challenger.com.co/nuestras-tiendas, https://www.challenger.com.co/combos/combos-cocina, https://www.challenger.com.co/combos/combos-refrigeracion and https://www.challenger.com.co/combos/combos-tv-y-audio have no <h1> headline, so visitors and search engines get no clear main topic.
3 pages slow to respond
https://www.challenger.com.co/cocina/campanas, https://www.challenger.com.co/cocina/hornos and https://www.challenger.com.co/cocina/lavaplatos took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 62 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
1 broken image
1 image failed to load on a phone, for example https://www.challenger.com.co/.
23 small tap targets
23 of 78 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')”.
8 distorted images
8 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
Missing source maps
Large scripts ship without source maps.
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.
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
Local business without LocalBusiness data
Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.
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 form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
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 357 words of copy
The homepage carries about 357 words of visible text.
2 checks passed
Analytics in place
Analytics detected: Google Tag Manager, Meta Pixel, Hotjar and TikTok Pixel.
Phone number on the homepage
Your phone number is on the homepage.
Privacy and tracking
7 trackers load before any consent
7Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and Meta Pixel and 2 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.
22 cookies set on arrival
22Opening the homepage sets 22 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.
30 other companies contacted
Loading the homepage contacts 30 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 challenger.com.co, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- React
- Analytics
- Google Tag Manager | Hotjar
- Hosting
- Whg Dal
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 57 issues on challenger.com.co, including 28 speed issues, 2 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.