vega.pe website review

18 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 1.1 s faster on a phone.

Google CDN costs a phone 2.3 s of main-thread work and 2.7 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.

vtexassets.com costs a phone 1.8 s of main-thread work and 4.1 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.

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

Reduce initial server response time. Google estimates savings of 1.6 s on a phone.

The HTML itself could arrive about 1.6 s sooner: redirects, a slow server response or missing compression delay everything after it.

Google Tag Manager costs a phone 1.4 s of main-thread work and 523 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.

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

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

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

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

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

2 files block the first paint until they finish downloading. Deferring or inlining them could save about 750 ms.

TikTok costs a phone 580 ms of main-thread work and 160 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.

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

Facebook costs a phone 301 ms of main-thread work and 228 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.

Your server takes 1.7 s to send the HTML. Google recommends under 600 ms; everything else waits for it.

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

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

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.

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

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

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

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

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

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

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

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

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

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

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

20 images 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' largest content (lcp) went from 3.2 s to 3.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 7.6 MB in 184 requests on a phone: images 3.3 MB (46), scripts 3.1 MB (67) and other files 735 KiB (52). Under 2 MB keeps phones on slow connections fast.

9 images are downloaded at several times the size a phone draws them, for example 389c8105-9776-4ad9-a4a1-0c33810ca03d___2feb30c99f8bc90ddfb88 at 6,946 px wide, shown at 374 px. Resized copies would save about 2.4 MB.

2 images weigh 1.4 MB together. On a phone connection a single image that size takes seconds.

14 images further down the page (2.9 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

5 images (1.8 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.16 g of CO₂e: 259.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

2 buttons have no accessible name, so screen readers announce just “button”.

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

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

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

Some list items are not inside a list.

Some lists contain elements other than list items, which screen readers announce wrongly.

All page content should be contained by landmarks: 12 elements on the page fail this check, rated moderate by axe-core.

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 on the page fails this check, rated moderate by axe-core.

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

2 form fields have no label, so screen readers announce an empty box and autofill guesses.

Headings skip levels (h1 → h3, h1 → h4 and h1 → h3), which makes the page harder to scan with a screen reader.

Elements with visible text labels do not have matching accessible names. (3 elements).

There are 4 <h1> headlines (“Tu mercado,”, “de casa” and “Equipa tu”). One clear main headline is easier for people and search engines.

Your meta description is 169 characters; Google truncates after about 160, so the end of your pitch is cut.

Structured data found (WebSite) but with 1 problem, for example “WebSite: missing name”.

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

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

The homepage links to 48 pages on vega.pe and 15 external pages.

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.

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

Your homepage links to https://www.vega.pe/tecnologia/televisores/hd-y-full-hd/nanocell/qled-y-neo-qled/ultra-hd, https://www.vega.pe/tecnologia/parlantes/qled-y-neo-qled/torres-de-sonido/ultra-hd/televiores and https://www.vega.pe/electrohogar/lavadora-y-lavaseca/refrigeradoras-y-frigobares, which answer with an error. Visitors hit a dead end and search engines drop them.

https://www.vega.pe/vegaentradas266 is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

/, https://www.vega.pe/supermercado and https://www.vega.pe/electro-y-hogar all use the title “Vega.pe| Muchas OFERTAS para tu NEGOCIO y HOGAR”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.vega.pe/bebidas-y-snacks, https://www.vega.pe/desayuno, https://www.vega.pe/vegaentradas266, https://www.vega.pe/supermercado and https://www.vega.pe/electro-y-hogar use the same meta description. A description written for each page earns more clicks.

https://www.vega.pe/electrohogar/electrodomesticos, https://www.vega.pe/tecnologia, https://www.vega.pe/vegaentradas266, https://www.vega.pe/supermercado, https://www.vega.pe/electro-y-hogar and https://www.vega.pe/tecnologia/telefonia and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.vega.pe/electro-y-hogar has 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.

https://www.vega.pe/tecnologia, https://www.vega.pe/vegaentradas266, https://www.vega.pe/supermercado and https://www.vega.pe/electro-y-hogar took over 3 s to send their HTML from our server.

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

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

3 errors were logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'register')”.

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

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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 347 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and Meta Pixel and 3 mores (measured from a US location before any click). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 27 cookies (measured from a US location before any click).

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