mobonline.com.br website review

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

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

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

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

8 third-party services load with your homepage (vtexassets.com, Google Tag Manager and Facebook and others), adding 3.4 MB and 695 ms of main-thread time.

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

vtexassets.com costs a phone 296 ms of main-thread work and 2.7 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 169 ms of main-thread work and 346 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 66 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 47 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

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

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

4 KiB could be saved by minifying JavaScript.

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 17.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Frete grátis”.

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

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

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

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

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

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

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

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

9 images are downloaded at several times the size a phone draws them, for example 33422c25-38a9-4b6c-afb3-b3b80c07f975___af4e0b09dae97afb98d84 at 1,540 px wide, shown at 390 px. Resized copies would save about 1.1 MB.

33422c25-38a9-4b6c-afb3-b3b80c07f975___af4e0b09dae97afb98d84 weighs 512 KiB. On a phone connection a single image that size takes seconds.

Your homepage downloads 3.6 MB in 100 requests on a phone: images 1.9 MB (15), scripts 1.5 MB (54) and HTML 97 KiB (1). Under 2 MB keeps phones on slow connections fast.

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

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

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

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

All page content should be contained by landmarks: 3 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.

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

Your title is only 25 characters: “MOB Moda premium feminina”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

No Open Graph image, 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 123 pages on mobonline.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.

https://www.mobonline.com.br/roupas/vestidos/vestido-longo and https://www.mobonline.com.br/roupas/blusas/regatas have no <title>, so Google invents the link text in results.

https://www.mobonline.com.br/roupas/vestidos/vestido-longo and https://www.mobonline.com.br/roupas/blusas/regatas have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.mobonline.com.br/lp-india, https://www.mobonline.com.br/roupas/vestidos, https://www.mobonline.com.br/roupas/vestidos/vestido-midi, https://www.mobonline.com.br/roupas/vestidos/vestido-longo, https://www.mobonline.com.br/roupas/blusas and https://www.mobonline.com.br/roupas/blusas/manga-curta and 7 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.mobonline.com.br/roupas/vestidos/vestido-longo, https://www.mobonline.com.br/roupas/blusas/manga-longa, https://www.mobonline.com.br/roupas/blusas/t-shirts and https://www.mobonline.com.br/roupas/blusas/regatas took over 3 s to send their HTML from our server.

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

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

1 error was logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'register')”.

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 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 15 words of visible text; thin pages give Google and first-time buyers little to go on.

There is no form on the homepage, so every lead has to click through to another page first.

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 Google Ads, Google Analytics, Google Tag Manager, Hotjar 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 20 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.