yamamura.com.br website review

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

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

6 third-party services load with your homepage (cloudfront.net, Google CDN and Clarity and others), adding 1.6 MB and 501 ms of main-thread time.

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

cloudfront.net costs a phone 234 ms of main-thread work and 1.3 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.

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

11 images could be 287 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

Google CDN costs a phone 171 ms of main-thread work and 295 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 218 KiB of JavaScript is downloaded but never used on this page.

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

12 KiB could be saved by minifying CSS.

25 KiB could be saved by minifying JavaScript.

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

Desktop scores 95 but mobile only 69. A gap that wide usually means heavy scripts and images that hit phones hardest.

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.

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

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

Your largest element takes 4.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Aniversário Yamamura: Produtos com até 60% OFF”.

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

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

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

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

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

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

Your homepage downloads 2.1 MB in 67 requests on a phone: images 816 KiB (29), fonts 649 KiB (11) and scripts 509 KiB (12). Under 2 MB keeps phones on slow connections fast.

3690_banner639262030029960274.webp 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).

1 image is downloaded at several times the size a phone draws it, for example 3712_banner639262097043367421.webp at 1,400 px wide, shown at 350 px. Resized copies would save about 26 KiB.

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

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

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

Some lists contain elements other than list items, which screen readers announce wrongly.

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

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

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

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

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

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

The homepage links to 47 pages on yamamura.com.br and 4 external pages.

There is no https://www.yamamura.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.

Your homepage links to https://www.yamamura.com.br/%7B%7BUrl%7D%7D, https://www.yamamura.com.br/%7B%7BUrls.FullBaseUrl%7D%7Dpainel-do-cliente/pedidos, https://www.yamamura.com.br/%7B%7BUrls.FullBaseUrl%7D%7Dpainel-do-cliente/dados-cadastrais, https://www.yamamura.com.br/%7B%7BSignOut%7D%7D, https://www.yamamura.com.br/%7B%7BUrls.FullBaseUrl%7D%7Dlogin and https://www.yamamura.com.br/%7B%7BUrls.FullBaseUrl%7D%7Dcadastro, which answer with an error. Visitors hit a dead end and search engines drop them.

https://www.yamamura.com.br/Shopping/Banner/Click declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.

/ and https://www.yamamura.com.br/Shopping/Banner/Click all use the title “Yamamura: Lustres, Pendentes, Lâmpadas e tudo para iluminação”, 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.yamamura.com.br/ventilador-de-teto-led-retratil-96w-multitemperatura-aruba-p9384227-p25059 and https://www.yamamura.com.br/marcas/tualux have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.yamamura.com.br/abajur-vidro-resina-preto-multicores-vitra-p9339779-p23057 and //abajur-vidro-resina-preto-multicores-vitra-p9339779-p23057 use the same meta description. A description written for each page earns more clicks.

https://www.yamamura.com.br/Shopping/Banner/Click has no <h1> headline, so visitors and search engines get no clear main topic.

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

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

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.

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

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

The homepage shows no opening hours. If customers visit or call, show when.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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 404 words of visible text.

Before a visitor clicks anything, the page loads Google Analytics 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 7 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 13 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.