redemac.com.br website review

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

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

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

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

7 third-party services load with your homepage (Google Tag Manager, Google CDN and Other Google APIs/SDKs and others), adding 4.1 MB and 861 ms of main-thread time.

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

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

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

Google CDN costs a phone 402 ms of main-thread work and 742 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.

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

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

eloja360.digital costs a phone 0 ms of main-thread work and 2.8 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.

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 20.4 s. Good is under 3.8 s.

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

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

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

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

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

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

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

Real visitors see the first content after 1.9 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.

5 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 155 ms to 181 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 5.1 MB in 158 requests on a phone: images 2.8 MB (58), scripts 1.7 MB (75) and other files 360 KiB (11). Under 2 MB keeps phones on slow connections fast.

1bc7d8bb-9946-43e5-9af9-a82931bce09a.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).

12 images (890 KiB) 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.

6 images further down the page (585 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

5 images are downloaded at several times the size a phone draws them, for example bdabbf07-e65f-400a-87a4-740af2963f5c.jpg at 900 px wide, shown at 172 px. Resized copies would save about 202 KiB.

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

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

Main landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

Document should not have more than one main landmark: 1 element on the page fails this check, rated moderate by axe-core.

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

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

Elements with visible text labels do not have matching accessible names. (3 elements).

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

Your title is only 7 characters: “REDEMAC”. Between 30 and 65 characters leaves room to say what you do and for whom.

Your meta description is only 29 characters: “Bem-vindo à nossa loja online”. 70 to 160 characters is enough to sell the click.

The homepage links to 164 pages on redemac.com.br and 8 external pages.

Your robots.txt shuts out ChatGPT (ChatGPT-User) and Perplexity (PerplexityBot). These fetch pages to answer people's questions and cite the source, so your site can't be quoted or linked in those answers.

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://redemac.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.

robots.txt blocks GPTBot, Google-Extended, Applebot-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers.

https://redemac.com.br/pesquisa has no <title>, so Google invents the link text in results.

https://redemac.com.br/pesquisa has no meta description, so Google writes the search snippet from whatever text it finds.

https://redemac.com.br/orcamento, https://redemac.com.br/produto/tramontina-abracadeira-34-cinza, https://redemac.com.br/produto/kit-paraf-phillips-5x80mm-c4-pcs, https://redemac.com.br/produto/pluvial-aquapluv-abracadeira-88mm-branca-tigre, https://redemac.com.br/produto/kit-paraf-phillips-6x60mm-c4-pcs and https://redemac.com.br/produto/jardim-engate-rapido-12-herc and 6 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://redemac.com.br/produto/pluvial-aquapluv-abracadeira-88mm-branca-tigre, https://redemac.com.br/produto/jardim-engate-rapido-12-herc, https://redemac.com.br/produto/fio-solido-600-mm, https://redemac.com.br/produto/caixa-luz-plastica-4-x-4-octogonal-krona and https://redemac.com.br/produto/mangueira-multiuso-38-3mm have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

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

5 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

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 phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach 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 1,041 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 12 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.