rimax.com.co website review

About 1.2 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.7 s faster on a phone.

vtexassets.com costs a phone 1.4 s of main-thread work and 3.8 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

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

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

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

8 third-party services load with your homepage (vtexassets.com, Google CDN and Google Tag Manager and others), adding 7.6 MB and 3.2 s of main-thread time.

52 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 450 ms faster on a phone.

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

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

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

Polyfills for old browsers add 145 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 550 ms faster on a phone.

Google Tag Manager costs a phone 492 ms of main-thread work and 538 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 54 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 290 ms faster on a phone.

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

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.

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 589 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

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

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

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

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

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

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

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

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

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

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

55 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 333 ms to 348 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.3 s to 3.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 7.7 MB in 304 requests on a phone: scripts 3.1 MB (87), images 2.6 MB (142) and other files 1.1 MB (59). Under 2 MB keeps phones on slow connections fast.

a059f868-0255-4ccc-8c74-f87afd57584e___5a7e11e2a5bcc6b4f9b2c 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).

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

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

1 button has no accessible name, so screen readers announce just “button”.

35 elements hidden from screen readers can still receive keyboard focus.

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

Documents must have <title> element to aid in navigation: 1 element on the page fails this check, rated serious by axe-core.

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

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 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.

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

1 visible link has no text or label, so screen readers cannot say where it goes.

Alternative text of images should not be repeated as text: 2 elements on the page fail this check, rated minor by axe-core.

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

Your page has no <title>, so Google has to invent the blue link in search results.

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

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

Structured data found (ItemList and WebSite) but with 1 problem, for example “WebSite: missing name”.

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 90 pages on rimax.com.co and 15 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.rimax.com.co/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.rimax.com.co/casa%20de%20perro is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://www.rimax.com.co/Materas and https://www.rimax.com.co/materas all use the title “Materas plásticas para jardín | Rimax - undefined”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.rimax.com.co/casa%20de%20perro has no meta description, so Google writes the search snippet from whatever text it finds.

https://www.rimax.com.co/Materas and https://www.rimax.com.co/materas use the same meta description. A description written for each page earns more clicks.

Your homepage links to 5 pages by a URL that isn't their canonical one, for example https://www.rimax.com.co/Muebles, whose canonical is https://www.rimax.com.co/muebles. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.rimax.com.co/Muebles, https://www.rimax.com.co/Organizacion, https://www.rimax.com.co/infantil, https://www.rimax.com.co/Mascotas, https://www.rimax.com.co/Materas and https://www.rimax.com.co/profesionales and 1 other took over 3 s to send their HTML from our server.

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

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

6 errors were logged to the browser console while the page loaded, for example “Unexpected identifier 'Warning'”.

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 phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

There is no form on the homepage, so every lead has to click through to another page first.

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

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