myplace.com.br website review

Your mobile performance score is 73. Pages that score under 90 lose visitors before the first paint.

4 images could be 157 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 350 ms faster on a phone.

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

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

widde.io costs a phone 52 ms of main-thread work and 347 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.

8 third-party services load with your homepage (widde.io, Shopify and RD Station and others), adding 795 KiB and 178 ms of main-thread time.

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

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

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

About 41 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 long task block the main thread while loading, the longest for 50 ms. During a long task the page ignores taps.

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

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

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

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

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

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

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.4 s (Speed Index). Good is under 3.4 s.

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

Your homepage downloads 5.7 MB in 364 requests on a phone: media 2.2 MB (2), other files 1.3 MB (204) and images 1.0 MB (37). Under 2 MB keeps phones on slow connections fast.

banner_mobile_GLAM_28-10.jpg 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 1.60 g of CO₂e: 192.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

4 elements use ARIA attributes their role does not allow, which confuses screen readers.

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

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

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

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

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

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

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

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

Elements with visible text labels do not have matching accessible names. (1 element).

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

The homepage links to 188 pages on myplace.com.br and 19 external pages.

Your Organization JSON-LD is missing 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.

https://loja.myplace.com.br/pages/politica-de-pagamento has no <h1> headline, so visitors and search engines get no clear main topic.

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

7 of 31 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 “Failed to load resource: net::ERR_FAILED”.

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 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 150 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 Google Ads, Google Analytics, Google Tag Manager and Meta Pixel (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 16 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.