multiloja.com.br website review

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

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

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

39 images could be 1.3 MB 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.

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

Your mobile performance score is 54 (desktop: 75). Pages that score under 90 lose visitors before the first paint.

About 901 KiB of JavaScript is downloaded but never used on this page.

YouTube costs a phone 722 ms of main-thread work and 977 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.

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

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

Facebook costs a phone 307 ms of main-thread work and 281 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 187 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.

1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 150 ms.

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

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

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.

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

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

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

Real visitors wait 332 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-24, real Chrome visitors' tap response (inp) went from 196 ms to 248 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

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

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

Your homepage downloads 7.0 MB in 218 requests on a phone: images 4.2 MB (122), scripts 2.1 MB (39) and fonts 355 KiB (5). Under 2 MB keeps phones on slow connections fast.

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

9 images are downloaded at several times the size a phone draws them, for example Quarto-Modulado-Casal-10-Portas-3-Gavetas-Infinity-Moveis-Ca at 1,000 px wide, shown at 285 px. Resized copies would save about 180 KiB.

4 images further down the page (85 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 1.99 g of CO₂e: 238.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

Elements must only use permitted ARIA attributes: 7 elements on the page fail this check, rated serious by axe-core.

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

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

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

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

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

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

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

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

There are 2 <h1> headlines (“Os melhores produtos para você e sua casa com pre…” and “Os melhores produtos para você e sua casa com pre…”). One clear main headline is easier for people and search engines.

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

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

The homepage links to 147 pages on multiloja.com.br and 9 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.

The HTML your server sends has 656 of the 1,254 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.

There is no https://www.multiloja.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.multiloja.com.br/torra-torra has no <title>, so Google invents the link text in results.

/ and https://www.multiloja.com.br/wishlist all use the title “Multiloja: Móveis, Eletro, Portáteis e Mais! | Multiloja”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.multiloja.com.br/fecha-mes-outubro, https://www.multiloja.com.br/wishlist, https://www.multiloja.com.br/pronta-entrega, https://www.multiloja.com.br/torra-torra, https://www.multiloja.com.br/moveis/cozinha and https://www.multiloja.com.br/moveis/sala-de-estar and 3 others use the same meta description. A description written for each page earns more clicks.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.multiloja.com.br/fecha-mes-outubro, whose canonical is https://www.multiloja.com.br/fecha-mes-outubro?page=1. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.multiloja.com.br/fecha-mes-outubro, https://www.multiloja.com.br/wishlist, https://www.multiloja.com.br/pronta-entrega, https://www.multiloja.com.br/torra-torra, https://www.multiloja.com.br/moveis and https://www.multiloja.com.br/moveis/quarto and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

5 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://api.reclameaqui.com.br/embed-reputation/hash/Mjg0NjU6bXVsdGlsb2phLWxvamEtdmlydHVhb…”.

Chrome logged issues while loading the page (“Cookie”).

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.

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

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 1,254 words of visible text.

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