vixbrasil.com website review

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

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

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

About 780 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 750 ms faster on a phone.

8 third-party services load with your homepage (Facebook, TikTok and goadopt.io and others), adding 1.3 MB and 1.3 s of main-thread time.

6 images could be 682 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 700 ms faster on a phone.

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

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

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

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

TikTok costs a phone 254 ms of main-thread work and 156 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 2,373 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

Shopify costs a phone 87 ms of main-thread work and 404 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.

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

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.

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

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

Your largest element takes 11.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Reproduzir ou pausar vídeo”.

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

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

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

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

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

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

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

Your homepage downloads 17.5 MB in 265 requests on a phone: media 12.1 MB (1), scripts 2.1 MB (67) and images 2.0 MB (47). Under 2 MB keeps phones on slow connections fast.

vix-paula-hermanny-moda-praia-banner-principal-resort-27-mob 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).

2 images further down the page (264 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

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

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

Elements must only use permitted ARIA attributes: 1 element on the page fails this check, rated serious by axe-core.

1 image has no alt text, which hurts accessibility and image search.

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

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.

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

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

There is no <h1>, so neither visitors nor Google get a clear main headline.

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

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

Open Graph is missing og:title and og:description, so shared links fall back to guesses.

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

The homepage links to 319 pages on vixbrasil.com and 29 external pages.

https://www.vixbrasil.com/pages/catalogo-colecao-resort-27 and https://www.vixbrasil.com/pages/catalogo-colaboracao use the same meta description. A description written for each page earns more clicks.

https://www.vixbrasil.com/collections/new-in, https://www.vixbrasil.com/pages/catalogo-colecao-resort-27, https://www.vixbrasil.com/pages/catalogo-colaboracao, https://www.vixbrasil.com/collections/praia, https://www.vixbrasil.com/collections/biquinis-tops and https://www.vixbrasil.com/collections/maios and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.vixbrasil.com/collections/new-in, https://www.vixbrasil.com/collections/praia, https://www.vixbrasil.com/collections/biquinis-tops, https://www.vixbrasil.com/collections/maios, https://www.vixbrasil.com/collections/saidas-de-praia and https://www.vixbrasil.com/collections/calcinha-brazilian and 3 others 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.

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

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

1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

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

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.

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

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

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

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

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

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

Before a visitor clicks anything, the page loads Criteo, Google Ads, Google Analytics, Google Tag Manager and Meta Pixel and 3 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 32 cookies, 2 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 44 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.