vecol.com.co website review

12 images could be 2.9 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 11.8 s faster on a phone.

64 files block the first paint until they finish downloading. Deferring or inlining them could save about 3.8 s.

Your mobile performance score is 30. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

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

About 1.2 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.

8 third-party services load with your homepage (YouTube, landbot.io and Google Tag Manager and others), adding 2.6 MB and 1.1 s of main-thread time.

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

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

YouTube costs a phone 532 ms of main-thread work and 1,004 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.

landbot.io costs a phone 229 ms of main-thread work and 829 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.

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

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

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

11 KiB could be saved by minifying JavaScript.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

2 KiB could be saved by minifying CSS.

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 visitors wait 4.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.

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

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

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

Your largest element takes 22.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “INDICADORES DE INTERÉS”. Most of its time is element render delay (11.1 s).

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

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

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

The layout shifts by 0.257 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

1 image have no width and height attributes, so the layout jumps as each one loads.

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

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

Your homepage downloads 9.1 MB in 241 requests on a phone: images 4.6 MB (35), scripts 3.4 MB (96) and stylesheets 438 KiB (78). Under 2 MB keeps phones on slow connections fast.

IMAGEN_DEVIDEODEINICIO.png weighs 2.3 MB. On a phone connection a single image that size takes seconds.

7 images are downloaded at several times the size a phone draws them, for example IMAGEN_DEVIDEODEINICIO.png at 1,920 px wide, shown at 350 px. Resized copies would save about 2.4 MB.

11 images (4.1 MB) are 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.

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

12 tap targets are too small or too close together to hit reliably with a finger.

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

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

No meta description, so Google writes its own snippet from whatever text it finds.

Your title is only 14 characters: “Inicio - VECOL”. Between 30 and 65 characters leaves room to say what you do and for whom.

The homepage links to 100 pages on vecol.com.co and 25 external pages.

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

/ and https://www.vecol.com.co/en all use the title “Inicio - VECOL”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.vecol.com.co/en, https://www.vecol.com.co/informacion-general, https://www.vecol.com.co/trabaje-con-nosotros, https://www.vecol.com.co/informes-de-gestion, https://www.vecol.com.co/asamblea-accionistas and https://www.vecol.com.co/nuestro-sector and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.vecol.com.co/informacion-general, https://www.vecol.com.co/trabaje-con-nosotros, https://www.vecol.com.co/informes-de-gestion, https://www.vecol.com.co/asamblea-accionistas, https://www.vecol.com.co/nuestro-sector and https://www.vecol.com.co/equipo-y-modernizacion and 7 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.vecol.com.co/en, https://www.vecol.com.co/informacion-general, https://www.vecol.com.co/trabaje-con-nosotros, https://www.vecol.com.co/informes-de-gestion, https://www.vecol.com.co/asamblea-accionistas and https://www.vecol.com.co/nuestro-sector and 2 others took over 3 s to send their HTML from our server.

We fetched 15 pages linked from your homepage (of 53 found) and read each the way a search engine does.

1 image failed to load on a phone, for example https://upload.wikimedia.org/wikipedia/commons/thumb/3/3c/Download_on_the_App_Store_Badge.svg/1024px-Download_on_the_App_Store_Badge.svg.png.

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

5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

2 errors were logged to the browser console while the page loaded, for example “Unexpected token ','”.

1 image is served at too low a resolution for sharp phone screens.

Chrome logged issues while loading the page (“Cookie”).

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

Your homepage shows a map but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

Social proof on the homepage: 2 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

The homepage shows no opening hours. If customers visit or call, show when.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 568 words of visible text.

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

Opening the homepage sets 18 cookies, 1 of them by other companies (measured from a US location before any click).

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.

Loading the homepage contacts 21 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.