wastramodaintima.com.br website review

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

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

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

8 third-party services load with your homepage (Google Tag Manager, Google CDN and Facebook and others), adding 3.3 MB and 516 ms of main-thread time.

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

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

Google Tag Manager costs a phone 384 ms of main-thread work and 661 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.

dooca.store costs a phone 11 ms of main-thread work and 2.3 MB 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.

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

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

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

Polyfills for old browsers add 11 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.

4 KiB could be saved by minifying JavaScript.

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.

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

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

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

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

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

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

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

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

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

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

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

8 images are downloaded at several times the size a phone draws them, for example projeto-site-wastra-650-x-900-mm-v2gmy.png at 2,457 px wide, shown at 390 px. Resized copies would save about 952 KiB.

Your homepage downloads 3.4 MB in 82 requests on a phone: images 2.3 MB (40), scripts 857 KiB (19) and fonts 169 KiB (5). Under 2 MB keeps phones on slow connections fast.

projeto-site-wastra-650-x-900-mm-v2gmy.png 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 0.97 g of CO₂e: 116.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”.

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

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

Links must have discernible text: 1 element on the page fails this check, rated serious by axe-core.

Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.

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

Heading levels should only increase by one: 1 element on the page fails this check, rated moderate by axe-core.

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

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

Your title is only 16 characters: “Wastra Underwear”. Between 30 and 65 characters leaves room to say what you do and for whom.

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

2 links have no real href, so search engines can't follow them.

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 54 pages on wastramodaintima.com.br and 7 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.

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

https://www.wastraunderwear.com.br/conta and https://www.wastraunderwear.com.br/carrinho have no <title>, so Google invents the link text in results.

/ and https://www.wastraunderwear.com.br/produtos all use the title “Wastra Underwear”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.wastraunderwear.com.br/conta and https://www.wastraunderwear.com.br/carrinho have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.wastraunderwear.com.br/conta and https://www.wastraunderwear.com.br/carrinho have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.wastraunderwear.com.br/kit-calcinha-levanta-bumbum/branco-preto-rose and https://www.wastraunderwear.com.br/conjunto-sexy-naty-cinta-liga/vermelho took over 3 s to send their HTML from our server.

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

5 images failed to load on a phone, for example https://assets.cloud.dooca.store/theme/assets/img/dc-payment/itau-color.svg.

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

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.

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.

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 317 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 11 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 15 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.