mobly.com.br website review

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

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

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

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

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

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

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

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

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

About 253 KiB of CSS is downloaded but never applied on this page.

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

15 KiB could be saved by minifying CSS.

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

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

For real visitors the layout shifts by 0.26 (75th percentile). Good is under 0.1.

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

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

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

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

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

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

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

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

1 image 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' tap response (inp) went from 360 ms to 347 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 3.7 s to 3.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 7.0 MB in 273 requests on a phone: images 2.7 MB (122), scripts 2.5 MB (67) and HTML 1.4 MB (4). Under 2 MB keeps phones on slow connections fast.

slider-mobile.png weighs 619 KiB. 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 slider-mobile.png at 1,656 px wide, shown at 390 px. Resized copies would save about 591 KiB.

7 images (1.4 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.

slider-mobile.png 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).

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

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

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

Links must have discernible text: 7 elements on the page fail this check, rated serious by axe-core.

ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.

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

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

Headings skip levels (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.

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

Structured data found (WebSite) but with 1 problem, for example “WebSite: missing name”.

The homepage links to 464 pages on mobly.com.br and 0 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.

There is no /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.

/auto-atendimento, /moveis/sofas, /moveis/sofas-camas, /moveis/poltronas-sala, /moveis/racks-paineis-estantes-home-theater and /moveis/guarda-roupas and 9 others have no <title>, so Google invents the link text in results.

/auto-atendimento, /moveis/sofas, /moveis/sofas-camas, /moveis/poltronas-sala, /moveis/racks-paineis-estantes-home-theater and /moveis/guarda-roupas and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

/auto-atendimento, /moveis/sofas, /moveis/sofas-camas, /moveis/poltronas-sala, /moveis/racks-paineis-estantes-home-theater and /moveis/guarda-roupas and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

/moveis/guarda-roupas, /moveis/comodas, /moveis/mesas-cabeceira and /infantil/moveis-infantis took over 3 s to send their HTML from our server.

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

2 images failed to load on a phone, for example https://xuojhr.mobly.com.br/g/uids?pld=PcBNjy2sNs32P93OwTyID5mvfE-Lgg2JraiL5KanUDgZP8ZziPiZi0eUQcKAJCP6wlGS3esFXEH2soLXCHWrVeFDFMp24XeOEoM8k25Jr_44hh0tR4HBJSOLr-hnJjKz8eEdE-gB4nj1annhGmNpq8wO3G2XqSRXM.

1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

6 errors were logged to the browser console while the page loaded, for example “Uncaught Error: Minified React error #418; visit https://react.dev/errors/418?args[]=HTML&args[]= for the full message …”.

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

1 image is served at too low a resolution for sharp phone screens.

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

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.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

The homepage has only about 94 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.

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