vnda.com.br website review

cloudfront.net costs a phone 2.0 s of main-thread work and 24.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.

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

Google Tag Manager costs a phone 1.1 s of main-thread work and 1.2 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 10.5 s on main-thread work while loading, 6.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

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

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

8 third-party services load with your homepage (cloudfront.net, Google Tag Manager and Facebook and others), adding 26.8 MB and 3.9 s of main-thread time.

4 images could be 402 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

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

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

The page has 1,871 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

Polyfills for old browsers add 55 KiB JavaScript that modern phones do not need.

About 54 KiB of CSS is downloaded but never applied on this page.

7 KiB could be saved by minifying CSS.

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

2 KiB JavaScript is shipped twice across bundles.

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 709 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

Your largest element takes 10.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Plataforma de Ecommerce da Olist (antiga Vnda) Customização…”.

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

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

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

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

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

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

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

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

Your homepage downloads 28.8 MB in 180 requests on a phone: media 24.0 MB (4), scripts 3.3 MB (66) and images 1.0 MB (45). Under 2 MB keeps phones on slow connections fast.

image 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).

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

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

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

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

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

Structured data found (Corporation, FAQPage, SoftwareApplication and WebPage) but with 1 problem, for example “SoftwareApplication: no offers (price) block”.

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

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

The homepage links to 59 pages on vnda.com.br and 13 external pages.

Your Organization JSON-LD is missing logo, sameAs (social profiles), 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.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://olist.com/sistema-erp/multiempresas, whose canonical is https://olist.com/sistema-erp/multiempresa. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

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

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=22020252&tm=gtm002&Ver=2&mid=a7bb5eaf-c7e8-4a43-9f19-04620bd7f1f5&bo=1&sid=5d204040d7db11f18a6cfd50d3c11293&vid=5d20ec30d7db11f1b4706fe8ade6c2fc&vids=1&msclkid=N&pi=91.

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

Large scripts ship without source maps.

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 testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

There is no form on the homepage, so every lead has to click through to another page first.

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 1,244 words of visible text.

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

Opening the homepage sets 20 cookies (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 31 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.