jacomar.com.br website review

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

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

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

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

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

ZenDesk costs a phone 245 ms of main-thread work and 413 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.

FontAwesome CDN costs a phone 0 ms of main-thread work and 303 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.

7 third-party services load with your homepage (ZenDesk, Google Tag Manager and Google Analytics and others), adding 974 KiB and 368 ms of main-thread time.

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

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

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

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

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.

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

Your largest element takes 10.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Campanha RH Atração Mini 1”.

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

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

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

56 images have no width and height attributes, so the layout jumps as each one loads.

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

Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 203 ms to 227 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 1.9 s to 2.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 5.2 MB in 106 requests on a phone: images 3.8 MB (41), scripts 790 KiB (31) and fonts 546 KiB (11). Under 2 MB keeps phones on slow connections fast.

9 images are downloaded at several times the size a phone draws them, for example original_907327273e9e21c11013931e815a7c9862773d.png at 2,750 px wide, shown at 281 px. Resized copies would save about 2.1 MB.

2 images weigh 1.4 MB together. On a phone connection a single image that size takes seconds.

15 images (3.6 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.

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

5 buttons have no accessible name, so screen readers announce just “button”.

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

1 element hidden from screen readers can still receive keyboard focus.

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.

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

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

Headings skip levels (h2 → h4 and h4 → h6), 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 structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

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

There is no robots.txt at jacomar.com.br/robots.txt, the first file search crawlers ask for.

10 links have no real href, so search engines can't follow them.

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

The homepage links to 31 pages on jacomar.com.br and 87 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 https://www.jacomar.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.jacomar.com.br/lojas, https://www.jacomar.com.br/sobre, https://www.jacomar.com.br/contato, https://www.jacomar.com.br/trabalhe, https://www.jacomar.com.br/blog/jacomar-60-anos-essa-historia-a-gente-conta-juntos and https://www.jacomar.com.br/blog and 2 others have no <title>, so Google invents the link text in results.

/ and https://www.jacomar.com.br/home all use the title “Supermercado Jacomar | Nossa Maior Oferta é o Respeito”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.jacomar.com.br/lojas, https://www.jacomar.com.br/sobre, https://www.jacomar.com.br/blog/categoria/imprensa, https://www.jacomar.com.br/contato, https://www.jacomar.com.br/trabalhe and https://www.jacomar.com.br/blog/jacomar-60-anos-essa-historia-a-gente-conta-juntos and 3 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.jacomar.com.br/home and https://www.jacomar.com.br/ofertas have no <h1> headline, so visitors and search engines get no clear main topic.

We fetched 13 pages linked from your homepage and read each the way a search engine does.

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 (Not Found)”.

6 images are served at too low a resolution for sharp phone screens.

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

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