ramsons.com.br website review

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

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

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

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

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

8 third-party services load with your homepage (Google Tag Manager, cloudfront.net and Facebook and others), adding 4.0 MB and 1.7 s of main-thread time.

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

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

Google Tag Manager costs a phone 714 ms of main-thread work and 680 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 756 KiB of JavaScript is downloaded but never used on this page.

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

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

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

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

Real visitors wait 4.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.

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

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

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

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

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

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

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

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

14 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 207 ms to 217 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 3.4 s to 3.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 5.2 MB in 235 requests on a phone: images 2.9 MB (139), scripts 1.8 MB (34) and stylesheets 188 KiB (16). Under 2 MB keeps phones on slow connections fast.

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

3 images are downloaded at several times the size a phone draws them, for example lg-logo.png at 4,336 px wide, shown at 183 px. Resized copies would save about 220 KiB.

6 images (337 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.

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

ARIA attributes must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.

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

1 tap target is too small or too close together to hit reliably with a finger.

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

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

Heading levels should only increase by one: 1 element on the page fails 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.

The skip-link target should exist and be focusable: 1 element on the page fails this check, rated moderate by axe-core.

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

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

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

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

No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 1,084 pages on ramsons.com.br and 18 external pages.

There is no https://www.ramsons.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.ramsons.com.br/eletrodomesticos/refrigeradores and https://www.ramsons.com.br/eletrodomesticos/refrigeradores/frostfree4pfreezerembaixo all use the title “Refrigeradores: geladeiras frost free, frigobares e mais - Refrigerad…”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.ramsons.com.br/eletrodomesticos/refrigeradores and https://www.ramsons.com.br/eletrodomesticos/refrigeradores/frostfree4pfreezerembaixo use the same meta description. A description written for each page earns more clicks.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.ramsons.com.br/eletrodomesticos/refrigeradores/frostfree4pfreezerembaixo, whose canonical is https://www.ramsons.com.br/eletrodomesticos/refrigeradores. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

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

1 image failed to load on a phone, for example https://www.ramsons.com.br/Custom/Content/Themes/Base/assets/img/008-person.svg.

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

The page uses 1 deprecated browser API that will stop working in future browsers (“Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to…”).

2 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 ()”.

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

Social proof on the homepage: 4 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.

The homepage has only about 223 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 Analytics, Google Tag Manager 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 20 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.