Website review, no card needed

velez.com.co logo

velez.com.co website review

Visit site (opens in a new tab)Reviewed 28 October 202647 issues · 87 checks

This review found 47 issues worth fixing on velez.com.co, 22 of them high impact, across 87 checks. The most urgent: use efficient cache lifetimes. 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
4.5 s4.0 sMay 9Oct 244.5 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20264.1 s
May 16, 20264.1 s
May 23, 20264.1 s
May 30, 20264.1 s
Jun 6, 20264.2 s
Jun 13, 20264.3 s
Jun 20, 20264.3 s
Jun 27, 20264.3 s
Jul 4, 20264.3 s
Jul 11, 20264.2 s
Jul 18, 20264.1 s
Jul 25, 20264.1 s
Aug 1, 20264.2 s
Aug 8, 20264.2 s
Aug 15, 20264.2 s
Aug 22, 20264.2 s
Aug 29, 20264.2 s
Sep 5, 20264.1 s
Sep 12, 20264.1 s
Sep 19, 20264.1 s
Sep 26, 20264.1 s
Oct 3, 20264.2 s
Oct 10, 20264.3 s
Oct 17, 20264.4 s
Oct 24, 20264.5 s
Real-visitor tap response (INP)75th percentile, phones
274 ms238 msMay 9Oct 24247 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026263 ms
May 16, 2026256 ms
May 23, 2026254 ms
May 30, 2026257 ms
Jun 6, 2026262 ms
Jun 13, 2026265 ms
Jun 20, 2026269 ms
Jun 27, 2026270 ms
Jul 4, 2026267 ms
Jul 11, 2026264 ms
Jul 18, 2026259 ms
Jul 25, 2026260 ms
Aug 1, 2026260 ms
Aug 8, 2026257 ms
Aug 15, 2026257 ms
Aug 22, 2026251 ms
Aug 29, 2026245 ms
Sep 5, 2026246 ms
Sep 12, 2026245 ms
Sep 19, 2026244 ms
Sep 26, 2026244 ms
Oct 3, 2026244 ms
Oct 10, 2026242 ms
Oct 17, 2026244 ms
Oct 24, 2026247 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 velez.com.co (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. velez.com.co at 1.0 s1.0 s
  2. velez.com.co at 1.9 s1.9 s
  3. velez.com.co at 2.9 s2.9 s
  4. velez.com.co at 3.8 s3.8 s
  5. velez.com.co at 4.8 s4.8 s
  6. velez.com.co at 5.7 s5.7 s
  7. velez.com.co at 6.7 s6.7 s
  8. velez.com.co at 7.6 s7.6 s

Speed

12 to fix33
  • Use efficient cache lifetimes

    13.1 s · 3.0 MB

    29 files are served with short cache lifetimes, so returning visitors download them again (3.0 MB).

  • Reduce unused JavaScript

    2.9 s · 916 KiB

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

  • Google Tag Manager adds 1.1 s

    1.1 s

    Google Tag Manager costs a phone 1.1 s of main-thread work and 953 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: 33

    33/100

    Your mobile performance score is 33 (desktop: 68). 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, 3.2 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, vtexassets.com and Insider and others), adding 4.1 MB and 2.6 s of main-thread time.

  • Reduce unused CSS

    950 ms · 199 KiB

    About 199 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 950 ms faster on a phone.

  • vtexassets.com adds 578 ms

    578 ms

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

  • Insider adds 394 ms

    394 ms

    Insider costs a phone 394 ms of main-thread work and 1.2 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.

  • Legacy JavaScript

    300 ms · 69 KiB

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

  • 17 long tasks on the main thread

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

  • Render-blocking requests

    300 ms

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

  • Improve image delivery

    52 KiB

    1 image could be 52 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Phones get a much slower page than desktops

    Desktop scores 68 but mobile only 33. 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.

  • Minify JavaScript

    4 KiB

    4 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 18 ms

    18 ms

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

Core Web Vitals

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

    0.61

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

  • Largest Contentful Paint: 28.9 s

    28.9 s

    Your largest element takes 28.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

  • Time to Interactive: 33.9 s

    33.9 s

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

  • Speed Index: 11.2 s

    11.2 s

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

  • First Contentful Paint: 4.4 s

    4.4 s

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

  • Total Blocking Time: 1.2 s

    1.2 s

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

  • Real-user INP: 274 ms

    274 ms

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

  • Real-user FCP: 2.0 s

    2.0 s

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

  • 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 263 ms to 247 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Largest content (LCP) held steady for real visitors

    +7%

    Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 4.1 s to 4.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

3 checks passed
  • Real-user LCP: 2.5 s

    2.5 s

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

  • Real-user TTFB: 713 ms

    713 ms

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

  • Cumulative Layout Shift: 0.002

    0.002

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

Images and page weight

1 to fix70
  • Page weight: 6.9 MB in 211 requests

    6.9 MB

    Your homepage downloads 6.9 MB in 211 requests on a phone: scripts 2.6 MB (73), media 2.4 MB (1) and fonts 990 KiB (4). Under 2 MB keeps phones on slow connections fast.

  • About 2.0 g of CO₂ per visit

    1.96 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.96 g of CO₂e: 235.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

3 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • 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 8589
  • 4 tap targets too small

    4 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 (1 element)

    ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

  • Interactive controls must not be nested (1 element)

    Interactive controls must not be nested: 1 element on the page fails this check, rated serious 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.

  • 8 links without text

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

  • Alternative text of images should not be repeated as text (4 elements)

    Alternative text of images should not be repeated as text: 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. (1 element).

2 checks passed
  • Every image has alt text

    All 16 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 47 WCAG 2.2 A/AA and best-practice rules on the phone render: 40 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

3 to fixGoogle 10086
  • Title is long (69 characters)

    Your title is 69 characters, so Google will cut it off around 60: “Sitio oficial de ropa, zapatos y accesorios en cuero | Vélez Colombia”.

  • 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.

  • No X (Twitter) card tag

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

  • 22 internal links, 0 external

    The homepage links to 22 pages on velez.com.co and 0 external pages.

5 checks passed
  • Meta description: 151 characters

    Your meta description is 151 characters: “Viste con elegancia y estilo. Conoce los exclusivos productos de la tienda online de ropa, zapatos y accesorios en cuer…”.

  • One H1 headline

    Your main headline reads: “Tienda online de ropa, zapatos y accesorios en cuero Vélez”.

  • Canonical URL set

    The canonical URL is https://www.velez.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.velez.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.

  • No llms.txt

    There is no https://www.velez.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.

1 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.

Other pages

5 to fix67
  • 1 page without a title

    https://www.velez.com.co/mujer/zapatos has no <title>, so Google invents the link text in results.

  • 4 pages share 2 titles

    https://www.velez.com.co/bowling-1041040-12/p and https://www.velez.com.co/bowling-1041040-23/p all use the title “Bowling | Vélez”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

  • 2 pages without a meta description

    https://www.velez.com.co/mujer/zapatos and https://www.velez.com.co/artesanalidad have no meta description, so Google writes the search snippet from whatever text it finds.

  • 4 pages share a meta description

    https://www.velez.com.co/bowling-1041040-12/p and https://www.velez.com.co/bowling-1041040-23/p use the same meta description. A description written for each page earns more clicks.

  • 6 pages without an H1

    https://www.velez.com.co/outlet/zapatos, https://www.velez.com.co/lo-nuevo/mujer, https://www.velez.com.co/lo-nuevo/hombre, https://www.velez.com.co/iconos/mujer, https://www.velez.com.co/jbalvin and https://www.velez.com.co/mujer/zapatos have no <h1> headline, so visitors and search engines get no clear main topic.

  • 4 pages with very little text

    https://www.velez.com.co/outlet/zapatos, https://www.velez.com.co/lo-nuevo/mujer, https://www.velez.com.co/lo-nuevo/hombre and https://www.velez.com.co/iconos/mujer 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.velez.com.co/mujer/zapatos/botas-y-botines and https://www.velez.com.co/mujer/accesorios took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

3 to fixGoogle 9671
  • 4 broken images

    4 images failed to load on a phone, for example https://bat.bing.com/action/0?ti=187246765&tm=gtm002&Ver=2&mid=fca2f0f9-66c9-4004-82fc-a511b5437ae2&bo=1&sid=c74927c0d30411f1b733818ba0053236&vid=c7494d80d30411f19164c58defaab6bc&vids=1&msclkid=N&pi=9.

  • 8 small tap targets

    8 of 30 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 6 JavaScript errors while loading

    6 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

1 checks passed
  • 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 94 words

    The homepage has only about 94 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, Google Analytics and Meta Pixel.

Privacy and tracking

1 to fix
  • 9 trackers load before any consent

    9

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, LinkedIn Insight 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.

  • 30 cookies set on arrival

    30

    Opening the homepage sets 30 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.

  • 54 other companies contacted

    Loading the homepage contacts 54 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 velez.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 Analytics | Google Tag Manager
Hosting
AWS

Company

Founded
1986
Headquarters
Medellín

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 47 issues on velez.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