weasy.com.br website review

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

8 third-party services load with your homepage (Clarity, loox.io and Shopify and others), adding 634 KiB and 1.0 s of main-thread time.

Your mobile performance score is 76. Pages that score under 90 lose visitors before the first paint.

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

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

About 244 KiB of JavaScript is downloaded but never used on this page.

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

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

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

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

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

3 KiB could be saved by minifying CSS.

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

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

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

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

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

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

Your homepage downloads 2.9 MB in 325 requests on a phone: other files 1.1 MB (196), scripts 996 KiB (88) and images 562 KiB (16). Under 2 MB keeps phones on slow connections fast.

BANNER_4.webp 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).

4 images (279 KiB) 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 0.83 g of CO₂e: 99.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

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

1 visible link has no text or label, so screen readers cannot say where it goes.

Alternative text of images should not be repeated as text: 8 elements on the page fail this check, rated minor by axe-core.

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

Your <h1> is empty.

The homepage links to 112 pages on weasy.com.br and 10 external pages.

/products/weasy-food and /products/weasy-food-kit-degustacao all use the title “Weasy Food Adultos | Alimentação natural para cães”. Search engines can't tell which page to show for a search, so each competes with the others.

/collections/para-bag, /collections/cuidados and /collections/brinquedos have no meta description, so Google writes the search snippet from whatever text it finds.

/products/weasy-food and /products/weasy-food-kit-degustacao use the same meta description. A description written for each page earns more clicks.

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

5 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://api.reclameaqui.com.br/embed-raverified/hash/dzgtX3hBWi1iT0hLVWdreTp3ZWFzeQ==' fro…”.

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

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.

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

The page uses urgency cues (a countdown or limited-time wording).

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo 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 25 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 45 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.