lemoritz.com.br website review

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

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

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

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

8 third-party services load with your homepage (Google Tag Manager, rebuyengine.com and Clarity and others), adding 6.0 MB and 1.2 s of main-thread time.

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

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

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

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

rebuyengine.com costs a phone 167 ms of main-thread work and 300 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,525 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

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

About 72 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.

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

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

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.

Your largest element takes 18.2 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 21.9 s. Good is under 3.8 s.

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

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

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

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

Scripts block taps and scrolling for 559 ms 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 248 ms to 284 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 2.3 s to 2.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 7.7 MB in 407 requests on a phone: images 3.4 MB (50), scripts 2.1 MB (111) and other files 992 KiB (202). Under 2 MB keeps phones on slow connections fast.

8 images are downloaded at several times the size a phone draws them, for example Artboard_6_6c0df882-96d6-4b1e-9d27-4c63e3e7fee2.png at 1,080 px wide, shown at 163 px. Resized copies would save about 684 KiB.

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

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

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

Your title is only 20 characters: “Le Moritz – lemoritz”. Between 30 and 65 characters leaves room to say what you do and for whom.

Your meta description is only 62 characters: “Até quando vai usar maquiagem que não foi feita para sua pele?”. 70 to 160 characters is enough to sell the click.

Your <h1> is empty.

The homepage links to 30 pages on lemoritz.com.br and 1 external page.

https://lemoritz.com.br/collections/all, https://lemoritz.com.br/pages/monte-seu-kit, https://lemoritz.com.br/pages/quiz-descubra-o-seu-subtom-de-pele, https://lemoritz.com.br/pages/rastreio-2, https://lemoritz.com.br/pages/pagina-de-como-usar-os-produtos and https://lemoritz.com.br/pages/sobre-nos and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://lemoritz.com.br/pages/monte-seu-kit and https://lemoritz.com.br/pages/pagina-de-como-usar-os-produtos have no <h1> headline, so visitors and search engines get no clear main topic.

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

6 errors were logged to the browser console while the page loaded, for example “Cannot read properties of null (reading 'appendChild')”.

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 phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach 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 932 words of visible text.

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