Website review, no card needed
alkomprar.com website review
Visit site (opens in a new tab)Reviewed 19 October 202644 issues · 96 checks
This review found 44 issues worth fixing on alkomprar.com, 17 of them high impact, across 96 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
73CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Apr 25, 2026 | 4.0 s |
| May 2, 2026 | 4.0 s |
| May 9, 2026 | 4.1 s |
| May 16, 2026 | 4.1 s |
| May 23, 2026 | 4.1 s |
| May 30, 2026 | 4.1 s |
| Jun 6, 2026 | 4.1 s |
| Jun 13, 2026 | 4.1 s |
| Jun 20, 2026 | 4.1 s |
| Jun 27, 2026 | 4.1 s |
| Jul 4, 2026 | 4.1 s |
| Jul 11, 2026 | 4.1 s |
| Jul 18, 2026 | 4.0 s |
| Jul 25, 2026 | 4.0 s |
| Aug 1, 2026 | 4.0 s |
| Aug 8, 2026 | 4.0 s |
| Aug 15, 2026 | 4.1 s |
| Aug 22, 2026 | 4.2 s |
| Aug 29, 2026 | 4.2 s |
| Sep 5, 2026 | 4.1 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.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Apr 25, 2026 | 298 ms |
| May 2, 2026 | 296 ms |
| May 9, 2026 | 295 ms |
| May 16, 2026 | 295 ms |
| May 23, 2026 | 296 ms |
| May 30, 2026 | 299 ms |
| Jun 6, 2026 | 300 ms |
| Jun 13, 2026 | 299 ms |
| Jun 20, 2026 | 299 ms |
| Jun 27, 2026 | 301 ms |
| Jul 4, 2026 | 302 ms |
| Jul 11, 2026 | 305 ms |
| Jul 18, 2026 | 307 ms |
| Jul 25, 2026 | 308 ms |
| Aug 1, 2026 | 312 ms |
| Aug 8, 2026 | 319 ms |
| Aug 15, 2026 | 327 ms |
| Aug 22, 2026 | 333 ms |
| Aug 29, 2026 | 336 ms |
| Sep 5, 2026 | 336 ms |
| Sep 12, 2026 | 333 ms |
| Sep 19, 2026 | 331 ms |
| Sep 26, 2026 | 330 ms |
| Oct 3, 2026 | 334 ms |
| Oct 10, 2026 | 339 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.8 s
3.6 s
5.4 s
7.2 s
9.0 s
10.8 s
12.6 s
14.5 s
Speed
Reduce unused JavaScript
2.5 s · 633 KiBAbout 633 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.5 s faster on a phone.
Mobile performance score: 36
36/100Your mobile performance score is 36 (desktop: 50). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 5.8 s
A phone's processor spends 5.8 s on main-thread work while loading, 2.5 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
4,676 HTML elements
The page has 4,676 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 (Google Tag Manager, Facebook and TikTok and others), adding 1.7 MB and 1.7 s of main-thread time.
Google Tag Manager adds 877 ms
877 msGoogle Tag Manager costs a phone 877 ms of main-thread work and 709 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.
Use efficient cache lifetimes
650 ms · 269 KiB22 files are served with short cache lifetimes, so returning visitors download them again (269 KiB).
Reduce unused CSS
450 ms · 201 KiBAbout 201 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.
Render-blocking requests
550 ms3 files block the first paint until they finish downloading. Deferring or inlining them could save about 550 ms.
Facebook adds 304 ms
304 msFacebook costs a phone 304 ms of main-thread work and 225 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.
Improve image delivery
150 ms · 161 KiB22 images could be 161 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.
13 long tasks on the main thread
13 long tasks block the main thread while loading, the longest for 243 ms. During a long task the page ignores taps.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Legacy JavaScript
30 KiBPolyfills for old browsers add 30 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.
1 checks passed
Server response: 123 ms
123 msYour server sent the HTML in 123 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: 16.9 s
16.9 sYour largest element takes 16.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “OFERTAS ALKOMPRAR”.
First Contentful Paint: 6.7 s
6.7 sThe first text or image appears after 6.7 s on a phone. Good is under 1.8 s.
Time to Interactive: 20.6 s
20.6 sThe page becomes fully interactive after 20.6 s. Good is under 3.8 s.
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: 850 ms
850 msScripts block taps and scrolling for 850 ms in total while the page loads. Good is under 200 ms.
Real-user INP: 363 ms
363 msReal visitors wait 363 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
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.
Tap response (INP) got 13% slower for real visitors
+13%Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' tap response (inp) went from 298 ms to 339 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 checks passed
Real-user LCP: 2.2 s
2.2 sReal visitors wait 2.2 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.
Real-user FCP: 1.7 s
1.7 sReal visitors see the first content after 1.7 s (75th percentile). Good is under 1.8 s.
Largest content (LCP) got 17% faster for real visitors
-17%Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' largest content (lcp) went from 4.0 s to 3.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0.011
0.011The layout barely moves while loading (CLS 0.011, good is under 0.1).
Images and page weight
Page weight: 3.2 MB in 255 requests
3.2 MBYour homepage downloads 3.2 MB in 255 requests on a phone: scripts 1.8 MB (91), images 842 KiB (92) and other files 211 KiB (55). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
a3a5583798b24df99b2ace65121d027c.webp 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 0.9 g of CO₂ per visit
0.91 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.91 g of CO₂e: 109.0 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
ARIA roles used must conform to valid values (1 element)
ARIA roles used must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.
83 text elements with low contrast
83 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
6 tap targets too small
6 tap targets are too small or too close together to hit reliably with a finger.
Scrollable region must have keyboard access (1 element)
Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.
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.
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.
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.
19 links without text
19 visible links have no text or label, so screen readers cannot say where they go.
3 form fields without a label
3 form fields have no label, so screen readers announce an empty box and autofill guesses.
Headings skip levels
Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (5 elements).
2 checks passed
Every image has alt text
All 303 images in the HTML carry an alt attribute.
47 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 56 WCAG 2.2 A/AA and best-practice rules on the phone render: 47 passed and 9 failed. 5 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.
908 internal links, 29 external
The homepage links to 908 pages on alkomprar.com and 29 external pages.
6 checks passed
Meta description: 150 characters
Your meta description is 150 characters: “Aniversario Alkomprar: compra tecnología, electrodomésticos y celulares a cuotas con Crédito 20 Minutos, 100% en línea.…”.
One H1 headline
Your main headline reads: “Alkomprar.com”.
Title: 39 characters
Your title is a healthy 39 characters: “Alkomprar Tienda Online | Alkomprar.com”.
Canonical URL set
The canonical URL is https://www.alkomprar.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.alkomprar.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 (2,763 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.alkomprar.com/llms.txt (12 KiB, 51 links), a plain-text guide to the site for AI tools.
Other pages
2 pages share a title
https://www.alkomprar.com/ofertas-alkomprar/c/ofertas-alkomprar and https://www.alkomprar.com/ofertas all use the title “ofertas alkomprar”. Search engines can't tell which page to show for a search, so each competes with the others.
1 page without a meta description
https://www.alkomprar.com/sigue-tu-pedido has no meta description, so Google writes the search snippet from whatever text it finds.
2 pages share a meta description
https://www.alkomprar.com/como-comprar/preguntas-frecuentes and https://www.alkomprar.com/ofertas use the same meta description. A description written for each page earns more clicks.
2 links to non-canonical URLs
Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://www.alkomprar.com/celulares/telefonos-celulares/c/BI_101, whose canonical is https://www.alkomprar.com/celulares/smartphones/c/BI_101. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
15 pages without an H1
https://www.alkomprar.com/ofertas-alkomprar/c/ofertas-alkomprar, https://www.alkomprar.com/sigue-tu-pedido, https://www.alkomprar.com/nuestra-compania/tiendas, https://www.alkomprar.com/experiencias-blog, https://www.alkomprar.com/como-comprar/preguntas-frecuentes and https://www.alkomprar.com/ofertas and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.
5 pages with very little text
https://www.alkomprar.com/celulares/telefonos-celulares/c/BI_101, https://www.alkomprar.com/computadores-tablets/c/BI_COMP, https://www.alkomprar.com/videojuegos/c/BI_VIJU, https://www.alkomprar.com/camaras/c/BI_CAMA and https://www.alkomprar.com/casa-inteligente-domotica/c/BI_CAIN 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.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 115 found) and read each the way a search engine does.
3 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
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://bat.bing.com/action/0?ti=187110205&tm=gtm002&Ver=2&mid=6acf7432-dc84-4b31-8b58-2725cf2cba9e&bo=1&sid=2dfc2850cb5a11f192e0e7f94a64c464&vid=2dfc8fb0cb5a11f18ca469d81c1e1879&vids=1&msclkid=N&pi=9.
1 third-party cookie
1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.
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 'register')”.
1 low-resolution image
1 image is served at too low a resolution for sharp phone screens.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
2 checks passed
Tap targets are thumb-sized
41 of 47 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: 12 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 636 words of copy
The homepage carries about 636 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: 6 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
9 trackers load before any consent
9Before a visitor clicks anything, the page loads Criteo, Google Ads, Google Analytics, Google Tag Manager and Meta Pixel and 4 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.
24 cookies set on arrival
24Opening the homepage sets 24 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.
40 other companies contacted
Loading the homepage contacts 40 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 alkomprar.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 44 issues on alkomprar.com, including 18 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.