feitoparaelas.com.br website review

About 433 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.0 s faster on a phone.

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

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

8 third-party services load with your homepage (Google Tag Manager, vitals.app and Clarity and others), adding 765 KiB and 695 ms of main-thread time.

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

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

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

vitals.app costs a phone 230 ms of main-thread work and 411 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 59 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.

43 KiB could be saved by minifying JavaScript.

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

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

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

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

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.

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

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

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

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

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 2.0 MB in 108 requests on a phone: scripts 1.1 MB (53), other files 486 KiB (31) and fonts 173 KiB (6). Under 2 MB keeps phones on slow connections fast.

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

Delayed refresh under 20 hours must not be used: 1 element on the page fails this check, rated critical by axe-core.

2 images have no alt text, which hurts accessibility and image search.

1 element use ARIA attributes their role does not allow, which confuses screen readers.

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

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

Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

Your title is only 15 characters: “A MELHOR OFERTA”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

Structured data found (BreadcrumbList and Product) but with 2 problems, for example “Product: missing name”.

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

No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

Your <h1> is empty.

The homepage links to 41 pages on feitoparaelas.com.br and 3 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.

https://feitoparaelas.com.br/collections/semana-da-beleza/products/escova-alisadora-5-em-1-alisa-seca-hidrata-modela-e-anti-frizz-bivolt and https://feitoparaelas.com.br/products/escova-alisadora-5-em-1-alisa-seca-hidrata-modela-e-anti-frizz-bivolt all use the title “Escova Alisadora Santi Hair com Touca de Cetim + Frete Grátis”, and 2 other titles repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

https://feitoparaelas.com.br/collections/todos-os-produtos, https://feitoparaelas.com.br/apps/17TRACK and https://feitoparaelas.com.br/pages/rastreio have no meta description, so Google writes the search snippet from whatever text it finds.

https://feitoparaelas.com.br/collections/semana-da-beleza/products/escova-alisadora-5-em-1-alisa-seca-hidrata-modela-e-anti-frizz-bivolt and https://feitoparaelas.com.br/products/escova-alisadora-5-em-1-alisa-seca-hidrata-modela-e-anti-frizz-bivolt use the same meta description. A description written for each page earns more clicks.

Your homepage links to 6 pages by a URL that isn't their canonical one, for example https://feitoparaelas.com.br/apps/17TRACK, whose canonical is https://feitoparaelas.com.br/apps/17track. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://feitoparaelas.com.br/collections/semana-da-beleza, https://feitoparaelas.com.br/collections/semana-da-beleza/products/escova-alisadora-5-em-1-alisa-seca-hidrata-modela-e-anti-frizz-bivolt, https://feitoparaelas.com.br/collections/semana-da-beleza/products/escova-alisadora-e-modeladora-5-em-1-com-kit-beleza, https://feitoparaelas.com.br/collections/semana-da-beleza/products/escova-secadora-3-em-1-hair-styler%C2%AE, https://feitoparaelas.com.br/collections/semana-da-beleza/products/acompanhamento-mensal-capilar-exclusivo and https://feitoparaelas.com.br/products/escova-alisadora-5-em-1-alisa-seca-hidrata-modela-e-anti-frizz-bivolt and 2 others took over 3 s to send their HTML from our server.

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

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 429 ()”.

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

Social proof on the homepage: 10 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

The homepage has only about 10 words of visible text; thin pages give Google and first-time buyers little to go on.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

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