leveros.com.br website review

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

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

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

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

10 images could be 135 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 27 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.

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

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

3 third-party services load with your homepage (Google Fonts, mais.social and Cloudflare CDN), adding 7 KiB and 1 ms of main-thread time.

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 612 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

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

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

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

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

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

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

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

bc0fa47241dd430d5fb830cc5a407484.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).

3 images are downloaded at several times the size a phone draws them, for example bc0fa47241dd430d5fb830cc5a407484.webp at 1,920 px wide, shown at 390 px. Resized copies would save about 202 KiB.

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

36 elements hidden from screen readers can still receive keyboard focus.

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

Form elements should have a visible label: 2 elements on the page fail this check, rated serious by axe-core.

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

1 tap target is too small or too close together to hit reliably with a finger.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

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

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

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

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

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

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

No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

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

The homepage links to 194 pages on leveros.com.br and 34 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.leveros.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.leveros.com.br/pagina/fale-conosco, https://www.leveros.com.br/minha-conta and https://www.leveros.com.br/minha-conta/lista-desejo all use the title “Leveros”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.leveros.com.br/pagina/lojas-fisicas and https://www.leveros.com.br/pagina/politica-entrega have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.leveros.com.br/minha-conta and https://www.leveros.com.br/minha-conta/lista-desejo use the same meta description. A description written for each page earns more clicks.

Your homepage links to 4 pages by a URL that isn't their canonical one, for example https://www.leveros.com.br/pagina/lojas-fisicas, whose canonical is https://www.leveros.com.br/pagina/[email protected]. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.leveros.com.br/pagina/fale-conosco, https://www.leveros.com.br/minha-conta, https://www.leveros.com.br/minha-conta/lista-desejo, https://www.leveros.com.br/ar-condicionado/inverter, https://www.leveros.com.br/ar-condicionado/split and https://www.leveros.com.br/ar-condicionado/cassete and 5 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.leveros.com.br/minha-conta and https://www.leveros.com.br/minha-conta/lista-desejo 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 58 found) and read each the way a search engine does.

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

7 images are served at too low a resolution for sharp phone screens.

Large scripts ship without source maps.

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.

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

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