multilit.com.br website review

73 files are served with short cache lifetimes, so returning visitors download them again (7.4 MB).

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

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

16 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.4 s.

Google Tag Manager costs a phone 1.2 s of main-thread work and 1.1 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

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

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

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

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

The page has 2,480 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

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

3 KiB could be saved by minifying CSS.

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

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

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 6.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.

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

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

Your largest element takes 26.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Quer ser um representante Multilit?”.

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

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

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

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

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

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 185 ms to 237 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 4.2 s to 5.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

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

Your homepage downloads 8.9 MB in 128 requests on a phone: images 7.1 MB (46), scripts 1.6 MB (40) and stylesheets 87 KiB (16). Under 2 MB keeps phones on slow connections fast.

6 images weigh 4.1 MB together. On a phone connection a single image that size takes seconds.

4 images are downloaded at several times the size a phone draws them, for example SITE-Banner-Garantia-10-anos.png at 1,920 px wide, shown at 390 px. Resized copies would save about 1.9 MB.

26 images (6.3 MB) 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.

3 images further down the page (845 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

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

Some list items are not inside a list.

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

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

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

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

9 visible links have no text or label, so screen readers cannot say where they go.

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

ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.

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

There is no <h1>, so neither visitors nor Google get a clear main headline.

Your title is only 21 characters: “Home - Grupo Multilit”. Between 30 and 65 characters leaves room to say what you do and for whom.

The homepage links to 250 pages on multilit.com.br and 14 external pages.

There is no https://multilit.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://multilit.com.br/categorias-produtos/acessorios-hidralicos and https://multilit.com.br/produto/acessorios-hidraulicos/prolongador-para-caixa-de-gordura have no meta description, so Google writes the search snippet from whatever text it finds.

https://multilit.com.br/produto/acessorios-hidraulicos/engate-flexivel-2 and https://multilit.com.br/produto/auto-servico/plug-pvc-2 use the same meta description. A description written for each page earns more clicks.

https://multilit.com.br/blog, https://multilit.com.br/lista-de-materiais, https://multilit.com.br/categorias-produtos/acessorios-hidralicos, https://multilit.com.br/produto/acessorios-hidraulicos/prolongador-para-caixa-de-gordura, https://multilit.com.br/produto/acessorios-hidraulicos/engate-flexivel-2 and https://multilit.com.br/produto/acessorios-hidraulicos/valvula and 1 other took over 3 s to send their HTML from our server.

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

2 errors were logged to the browser console while the page loaded, for example “Unexpected token '<'”.

3 images are displayed at the wrong aspect ratio, so they look 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 686 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, LinkedIn Insight and Meta Pixel and 1 more (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 15 cookies (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 25 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.