Website review, no card needed
alkosto.com website review
Visit site (opens in a new tab)Reviewed 20 October 202650 issues · 98 checks
This review found 50 issues worth fixing on alkosto.com, 18 of them high impact, across 98 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
75CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 4.2 s |
| May 9, 2026 | 4.2 s |
| May 16, 2026 | 4.2 s |
| May 23, 2026 | 4.1 s |
| May 30, 2026 | 4.1 s |
| Jun 6, 2026 | 4.0 s |
| Jun 13, 2026 | 3.9 s |
| Jun 20, 2026 | 3.9 s |
| Jun 27, 2026 | 3.9 s |
| Jul 4, 2026 | 3.9 s |
| Jul 11, 2026 | 3.9 s |
| Jul 18, 2026 | 3.9 s |
| Jul 25, 2026 | 3.8 s |
| Aug 1, 2026 | 3.8 s |
| Aug 8, 2026 | 3.7 s |
| Aug 15, 2026 | 3.7 s |
| Aug 22, 2026 | 3.8 s |
| Aug 29, 2026 | 3.8 s |
| Sep 5, 2026 | 3.9 s |
| Sep 12, 2026 | 3.9 s |
| Sep 19, 2026 | 3.8 s |
| Sep 26, 2026 | 3.6 s |
| Oct 3, 2026 | 3.4 s |
| Oct 10, 2026 | 3.3 s |
| Oct 17, 2026 | 3.3 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 248 ms |
| May 9, 2026 | 247 ms |
| May 16, 2026 | 246 ms |
| May 23, 2026 | 247 ms |
| May 30, 2026 | 248 ms |
| Jun 6, 2026 | 248 ms |
| Jun 13, 2026 | 248 ms |
| Jun 20, 2026 | 248 ms |
| Jun 27, 2026 | 256 ms |
| Jul 4, 2026 | 267 ms |
| Jul 11, 2026 | 276 ms |
| Jul 18, 2026 | 281 ms |
| Jul 25, 2026 | 280 ms |
| Aug 1, 2026 | 281 ms |
| Aug 8, 2026 | 282 ms |
| Aug 15, 2026 | 286 ms |
| Aug 22, 2026 | 289 ms |
| Aug 29, 2026 | 291 ms |
| Sep 5, 2026 | 293 ms |
| Sep 12, 2026 | 294 ms |
| Sep 19, 2026 | 294 ms |
| Sep 26, 2026 | 293 ms |
| Oct 3, 2026 | 290 ms |
| Oct 10, 2026 | 289 ms |
| Oct 17, 2026 | 289 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
0.9 s
1.8 s
2.6 s
3.5 s
4.4 s
5.3 s
6.2 s
7.1 s
Speed
Reduce unused JavaScript
3.6 s · 1.2 MBAbout 1.2 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.6 s faster on a phone.
Google Tag Manager adds 1.2 s
1.2 sGoogle Tag Manager costs a phone 1.2 s of main-thread work and 1.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.
Mobile performance score: 37
37/100Your mobile performance score is 37. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
5,541 HTML elements
The page has 5,541 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Main-thread work: 5.4 s
A phone's processor spends 5.4 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, ContentSquare and Sirv and others), adding 3.4 MB and 2.3 s of main-thread time.
Use efficient cache lifetimes
950 ms · 376 KiB25 files are served with short cache lifetimes, so returning visitors download them again (376 KiB).
Reduce unused CSS
900 ms · 213 KiBAbout 213 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 900 ms faster on a phone.
Render-blocking requests
750 ms4 files block the first paint until they finish downloading. Deferring or inlining them could save about 750 ms.
Improve image delivery
250 ms · 299 KiB11 images could be 299 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 250 ms faster on a phone.
ContentSquare adds 440 ms
440 msContentSquare costs a phone 440 ms of main-thread work and 176 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.
Sirv adds 163 ms
163 msSirv costs a phone 163 ms of main-thread work and 639 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.
alkomprar.com adds 108 ms
108 msalkomprar.com costs a phone 108 ms of main-thread work and 430 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.
JSDelivr CDN adds 66 ms
66 msJSDelivr CDN costs a phone 66 ms of main-thread work and 337 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.
18 long tasks on the main thread
18 long tasks block the main thread while loading, the longest for 227 ms. During a long task the page ignores taps.
Legacy JavaScript
34 KiBPolyfills for old browsers add 34 KiB JavaScript that modern phones do not need.
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 JavaScript
5 KiB5 KiB could be saved by minifying JavaScript.
1 checks passed
Server response: 61 ms
61 msYour server sent the HTML in 61 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.
Largest Contentful Paint: 20.8 s
20.8 sYour largest element takes 20.8 s to render on a phone. Google's threshold for “good” is 2.5 s.
Time to Interactive: 29.8 s
29.8 sThe page becomes fully interactive after 29.8 s. Good is under 3.8 s.
First Contentful Paint: 6.5 s
6.5 sThe first text or image appears after 6.5 s on a phone. Good is under 1.8 s.
Speed Index: 11.3 s
11.3 sVisually, the page fills in at 11.3 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 808 ms
808 msScripts block taps and scrolling for 808 ms in total while the page loads. Good is under 200 ms.
Real-user INP: 316 ms
316 msReal visitors wait 316 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 1.9 s
1.9 sReal visitors see the first content after 1.9 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 994 ms
994 msReal visitors wait 994 ms for your server to start answering (75th percentile). Good is under 800 ms.
4 images without width and height
4 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) got 17% slower for real visitors
+17%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 248 ms to 289 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
4 checks passed
Real-user LCP: 2.3 s
2.3 sReal visitors wait 2.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.04
0.04For real visitors the layout shifts by 0.04 (75th percentile). Good is under 0.1.
Largest content (LCP) got 21% faster for real visitors
-21%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 4.2 s to 3.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 6.9 MB in 264 requests
6.9 MBYour homepage downloads 6.9 MB in 264 requests on a phone: scripts 2.9 MB (104), media 2.0 MB (7) and images 1.4 MB (95). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
placeholder.svg 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.0 g of CO₂ per visit
1.96 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.96 g of CO₂e: 235.3 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
79 text elements with low contrast
79 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
4 tap targets too small
4 tap targets are too small or too close together to hit reliably with a finger.
Elements must only use permitted ARIA attributes (1 element)
Elements must only use permitted ARIA attributes: 1 element on the page fails this check, rated serious by axe-core.
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
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.
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.
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
The skip-link target should exist and be focusable (1 element)
The skip-link target should exist and be focusable: 1 element on the page fails this check, rated moderate by axe-core.
ARIA role should be appropriate for the element (33 elements)
ARIA role should be appropriate for the element: 33 elements on the page fail this check, rated minor by axe-core.
3 form fields without a label
3 form fields have no label, so screen readers announce an empty box and autofill guesses.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
Alternative text of images should not be repeated as text (1 element)
Alternative text of images should not be repeated as text: 1 element on the page fails 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. (7 elements).
2 checks passed
Every image has alt text
All 195 images in the HTML carry an alt attribute.
50 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 60 WCAG 2.2 A/AA and best-practice rules on the phone render: 50 passed and 10 failed. 6 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Structured data has 2 problems
Structured data found (LocalBusiness, Organization and WebSite) but with 2 problems, for example “WebSite: missing name”.
No social preview image
No Open Graph image (also missing: og:title, og:description), 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.
1,050 internal links, 15 external
The homepage links to 1,050 pages on alkosto.com and 15 external pages.
6 checks passed
Meta description: 125 characters
Your meta description is 125 characters: “Ofertas en celulares, TV, neveras, lavadoras, portátiles, llantas y colchones. Participa por el 50% de tu compra. ¡Comp…”.
One H1 headline
Your main headline reads: “Orgullosamente Colombiano”.
Title: 47 characters
Your title is a healthy 47 characters: “Alkosto Hiperahorro | Orgullosamente Colombiano”.
Canonical URL set
The canonical URL is https://www.alkosto.com/.
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.alkosto.com/sitemap.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing logo, description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
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.
Text is in the HTML
Your server sends the page's text in the HTML (3,067 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.alkosto.com/llms.txt (13 KiB, 53 links), a plain-text guide to the site for AI tools.
Other pages
3 pages share a title
https://www.alkosto.com/ofertas/c/ofertas, https://www.alkosto.com/ofertas and https://www.alkosto.com/catalogos-ofertas-ciudades all use the title “Ofertas en Alkosto: Celulares, electrodomésticos, colchones, televiso…”. Search engines can't tell which page to show for a search, so each competes with the others.
3 pages share a meta description
https://www.alkosto.com/ofertas/c/ofertas, https://www.alkosto.com/ofertas and https://www.alkosto.com/catalogos-ofertas-ciudades use the same meta description. A description written for each page earns more clicks.
5 links to non-canonical URLs
Your homepage links to 5 pages by a URL that isn't their canonical one, for example https://www.alkosto.com/ofertas, whose canonical is https://www.alkosto.com/ofertas/c/ofertas. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
15 pages without an H1
https://www.alkosto.com/ofertas/c/ofertas, https://www.alkosto.com/sigue-tu-pedido, https://www.alkosto.com/nuestra-compania/tiendas, https://www.alkosto.com/preguntas-frecuentes, https://www.alkosto.com/ofertas and https://www.alkosto.com/catalogos-ofertas-ciudades and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.
5 pages slow to respond
https://www.alkosto.com/ofertas, https://www.alkosto.com/catalogos-ofertas-ciudades, https://www.alkosto.com/celulares/c/BI_CELU_ALKOS, https://www.alkosto.com/computadores-tablets/c/BI_COMP_ALKOS and https://www.alkosto.com/tv-video/c/BI_TVVI_ALKOS took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 108 found) and read each the way a search engine does.
4 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Every page has a meta description
All 15 pages that loaded have a meta description.
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
4 JavaScript errors while loading
4 errors were logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'controller')”.
2 checks passed
Tap targets are thumb-sized
53 of 61 tappable elements near the top are at least 24 px.
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: 21 trust badges. 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.
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 775 words of copy
The homepage carries about 775 words of visible text.
5 checks passed
9 short forms
9 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager.
Direct contact links
Visitors can reach you directly: 10 phone links and 1 email link.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
LocalBusiness structured data
Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and TikTok Pixel (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.
15 cookies set on arrival
15Opening the homepage sets 15 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.
27 other companies contacted
Loading the homepage contacts 27 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 alkosto.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- jQuery
- 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 alkosto.com, including 24 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.