rech.com website review

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

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

The HTML itself could arrive about 900 ms sooner: redirects, a slow server response or missing compression delay everything after it.

Reduce initial server response time. Google estimates savings of 896 ms on a phone.

Your server takes 996 ms to send the HTML. Google recommends under 600 ms; everything else waits for it.

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

About 46 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.

2 third-party services load with your homepage (jQuery CDN and Google Fonts), adding 33 KiB and 47 ms of main-thread time.

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

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

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.51 (75th percentile). Good is under 0.1.

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

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

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

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

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

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

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

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

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

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

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

No meta description, so Google writes its own snippet from whatever text it finds.

There are 6 <h1> headlines (“Horizontina”, “Itajaí” and “Navegantes”). One clear main headline is easier for people and search engines.

The homepage links to 56 pages on rech.com and 30 external pages.

Your homepage links to /novo/lojas, which answers with an error. Visitors hit a dead end and search engines drop it.

/nossa-historia, /noticias, /relacao-com-investidores, /governanca and /politica-de-privacidade all use the title “Rech”. Search engines can't tell which page to show for a search, so each competes with the others.

/nossa-historia, /lojas, /produtos, /noticias, /filtro/linha-agricola and /filtro/linha-amarela and 5 others have no meta description, so Google writes the search snippet from whatever text it finds.

/nossa-historia and /filtro/motores have no <h1> headline, so visitors and search engines get no clear main topic.

/filtro/motores took over 3 s to send its HTML from our server.

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

10 of 22 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: the server responded with a status of 404 ()”.

1 image is 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.

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 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 shows no opening hours. If customers visit or call, show when.

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

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 2 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.