Website review, no card needed

alfa.com.co logo

alfa.com.co website review

Visit site (opens in a new tab)Reviewed 26 October 202645 issues · 84 checks

This review found 45 issues worth fixing on alfa.com.co, 14 of them high impact, across 84 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
3.9 s3.6 sMay 9Oct 243.8 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20263.8 s
May 16, 20263.6 s
May 23, 20263.6 s
May 30, 20263.7 s
Jun 6, 20263.7 s
Jun 13, 20263.7 s
Jun 20, 20263.6 s
Jun 27, 20263.7 s
Jul 4, 20263.7 s
Jul 11, 20263.7 s
Jul 18, 20263.7 s
Jul 25, 20263.7 s
Aug 1, 20263.7 s
Aug 8, 20263.7 s
Aug 15, 20263.8 s
Aug 22, 20263.8 s
Aug 29, 20263.9 s
Sep 5, 20263.9 s
Sep 12, 20263.8 s
Sep 19, 20263.8 s
Sep 26, 20263.7 s
Oct 3, 20263.8 s
Oct 10, 20263.8 s
Oct 17, 20263.8 s
Oct 24, 20263.8 s
Real-visitor tap response (INP)75th percentile, phones
457 ms354 msMay 9Oct 24366 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026445 ms
May 16, 2026432 ms
May 23, 2026417 ms
May 30, 2026400 ms
Jun 6, 2026396 ms
Jun 13, 2026395 ms
Jun 20, 2026404 ms
Jun 27, 2026418 ms
Jul 4, 2026417 ms
Jul 11, 2026410 ms
Jul 18, 2026404 ms
Jul 25, 2026400 ms
Aug 1, 2026398 ms
Aug 8, 2026401 ms
Aug 15, 2026404 ms
Aug 22, 2026400 ms
Aug 29, 2026404 ms
Sep 5, 2026406 ms
Sep 12, 2026399 ms
Sep 19, 2026400 ms
Sep 26, 2026399 ms
Oct 3, 2026394 ms
Oct 10, 2026391 ms
Oct 17, 2026378 ms
Oct 24, 2026366 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 alfa.com.co (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. alfa.com.co at 0.6 s0.6 s
  2. alfa.com.co at 1.3 s1.3 s
  3. alfa.com.co at 1.9 s1.9 s
  4. alfa.com.co at 2.6 s2.6 s
  5. alfa.com.co at 3.2 s3.2 s
  6. alfa.com.co at 3.9 s3.9 s
  7. alfa.com.co at 4.5 s4.5 s
  8. alfa.com.co at 5.2 s5.2 s

Speed

9 to fix52
  • Reduce unused JavaScript

    3.9 s · 671 KiB

    About 671 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.9 s faster on a phone.

  • Use efficient cache lifetimes

    1.7 s · 396 KiB

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

  • 8 third-party services on the page

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

  • Mobile performance score: 52

    52/100

    Your mobile performance score is 52. Pages that score under 90 lose visitors before the first paint.

  • Reduce unused CSS

    900 ms · 92 KiB

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

  • Google Tag Manager adds 455 ms

    455 ms

    Google Tag Manager costs a phone 455 ms of main-thread work and 680 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.

  • vtexassets.com adds 327 ms

    327 ms

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

  • Render-blocking requests

    300 ms

    1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 300 ms.

  • Main-thread work: 2.4 s

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

  • Legacy JavaScript

    150 ms · 103 KiB

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

  • Improve image delivery

    150 ms · 76 KiB

    2 images could be 76 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.

  • 8 long tasks on the main thread

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

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

    48 ms

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

Core Web Vitals

12 to fix0
  • 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.55

    0.55

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

  • Largest Contentful Paint: 24.1 s

    24.1 s

    Your largest element takes 24.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “¡Adelanta la renovación de tu terraza o patio! Pisos para e…”.

  • Time to Interactive: 24.2 s

    24.2 s

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

  • Speed Index: 9.4 s

    9.4 s

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

  • First Contentful Paint: 4.5 s

    4.5 s

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

  • Real-user LCP: 2.9 s

    2.9 s

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

  • Real-user INP: 246 ms

    246 ms

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

  • Real-user FCP: 2.7 s

    2.7 s

    Real visitors see the first content after 2.7 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 1.7 s

    1.7 s

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

  • Total Blocking Time: 272 ms

    272 ms

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

  • 9 images without width and height

    9 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-24, real Chrome visitors' largest content (lcp) went from 3.8 s to 3.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

2 checks passed
  • Tap response (INP) got 15% faster for real visitors

    -15%

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

1 to fix85
  • Page weight: 3.1 MB in 168 requests

    3.1 MB

    Your homepage downloads 3.1 MB in 168 requests on a phone: scripts 2.2 MB (71), other files 393 KiB (70) and HTML 170 KiB (1). Under 2 MB keeps phones on slow connections fast.

  • 1 image in older formats

    1 image (38 KiB) is 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.

  • About 0.9 g of CO₂ per visit

    0.87 g

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

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

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

7 to fixGoogle 8688
  • 7 text elements with low contrast

    7 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • Hidden but focusable

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

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

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

  • 6 links without text

    6 visible links have no text or label, so screen readers cannot say where they go.

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (1 element).

2 checks passed
  • Every image has alt text

    All 21 images in the HTML carry an alt attribute.

  • 30 automated accessibility rules passed

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

SEO

3 to fixGoogle 9291
  • 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.

  • 1 link crawlers can't follow

    1 link has no real href, so search engines can't follow it.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 30 internal links, 19 external

    The homepage links to 30 pages on alfa.com.co and 19 external pages.

6 checks passed
  • Meta description: 155 characters

    Your meta description is 155 characters: “Disfruta los mejores precios con Alfa hasta 50% OFF en nuestra tienda en línea. Todo para decorar y remodelar tu hogar …”.

  • One H1 headline

    Your main headline reads: “Descuentos Alfa”.

  • Title: 30 characters

    Your title is a healthy 30 characters: “Descuentos Alfa| Hasta 50% OFF”.

  • Canonical URL set

    The canonical URL is https://www.alfa.com.co/.

  • 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.alfa.com.co/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.

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.

  • llms.txt published

    The site publishes https://www.alfa.com.co/llms.txt (2 KiB, 0 links), a plain-text guide to the site for AI tools.

Other pages

5 to fix67
  • 4 pages without a title

    https://www.alfa.com.co/pisos, https://www.alfa.com.co/artesanos, https://www.alfa.com.co/outlet and https://www.alfa.com.co/exterior-por-completo have no <title>, so Google invents the link text in results.

  • 2 pages share a title

    / and https://www.alfa.com.co/ideas all use the title “Descuentos Alfa| Hasta 50% OFF”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 4 pages without a meta description

    https://www.alfa.com.co/pisos, https://www.alfa.com.co/artesanos, https://www.alfa.com.co/outlet and https://www.alfa.com.co/exterior-por-completo have no meta description, so Google writes the search snippet from whatever text it finds.

  • 3 pages share a meta description

    https://www.alfa.com.co/fitness, https://www.alfa.com.co/soluciones-institucionales and https://www.alfa.com.co/ideas use the same meta description. A description written for each page earns more clicks.

  • 7 pages without an H1

    https://www.alfa.com.co/pisos, https://www.alfa.com.co/artesanos, https://www.alfa.com.co/soluciones-institucionales, https://www.alfa.com.co/ideas, https://www.alfa.com.co/sostenibilidad and https://www.alfa.com.co/outlet and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.

  • 6 pages slow to respond

    https://www.alfa.com.co/artesanos, https://www.alfa.com.co/muebles, https://www.alfa.com.co/tecnologia, https://www.alfa.com.co/soluciones-institucionales, https://www.alfa.com.co/sostenibilidad and https://www.alfa.com.co/exterior-por-completo took over 3 s to send their HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 27 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.

  • Canonical URLs point to themselves

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

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

Best practices

1 to fixGoogle 9693
  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Cannot destructure property 'store' of '(intermediate value)' as it is undefined.”.

2 checks passed
  • Tap targets are thumb-sized

    8 of 8 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix33
  • 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.

  • 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 65 words

    The homepage has only about 65 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
  • 7 trackers load before any consent

    7

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

  • 38 cookies set on arrival

    38

    Opening the homepage sets 38 cookies, 2 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.

  • 42 other companies contacted

    Loading the homepage contacts 42 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 alfa.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
Hosting
AWS

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 45 issues on alfa.com.co, 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