riocenter.com.br website review

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

54 files are served with short cache lifetimes, so returning visitors download them again (1.0 MB).

Your mobile performance score is 73 (desktop: 82). Pages that score under 90 lose visitors before the first paint.

8 third-party services load with your homepage (Google Tag Manager, TikTok and Facebook and others), adding 2.1 MB and 714 ms of main-thread time.

1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 750 ms.

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

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

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

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

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

your-objectstorage.com costs a phone 0 ms of main-thread work and 848 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.

super1.com.br costs a phone 0 ms of main-thread work and 441 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.

45 KiB could be saved by minifying CSS.

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

29 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 1.9 s for your server to start answering (75th percentile). Good is under 800 ms.

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

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

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

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

Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 170 ms to 237 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

Your largest element takes 3.2 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 3.8 s (Speed Index). Good is under 3.4 s.

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

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

Your homepage downloads 4.5 MB in 103 requests on a phone: other files 2.1 MB (18), images 1.3 MB (65) and scripts 938 KiB (15). Under 2 MB keeps phones on slow connections fast.

aHR0cHM6Ly9yaW9jZW50ZXItZGV2LmhlbDEueW91ci1vYmplY3RzdG9yYWdl 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).

3 images are downloaded at several times the size a phone draws them, for example aHR0cHM6Ly9yaW9jZW50ZXItZGV2LmhlbDEueW91ci1vYmplY3RzdG9yYWdl at 1,080 px wide, shown at 173 px. Resized copies would save about 166 KiB.

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

1 element use ARIA attributes their role does not allow, which confuses screen readers.

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

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

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious 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.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

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

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

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

Your title is only 23 characters: “Rio Center — Rio Center”. Between 30 and 65 characters leaves room to say what you do and for whom.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

Your meta description is only 62 characters: “Moda para a toda família e produtos para o lar com excelência.”. 70 to 160 characters is enough to sell the click.

The homepage links to 468 pages on riocenter.com.br 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://riocenter.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://riocenter.com.br/busca, https://riocenter.com.br/d/feminino, https://riocenter.com.br/d/FEMININO/BASICOS, https://riocenter.com.br/d/FEMININO/BLAZERS_CASACOS_JAQUETAS, https://riocenter.com.br/d/FEMININO/BLUSAS_CAMISETAS and https://riocenter.com.br/d/FEMININO/VESTIDOS and 9 others 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://riocenter.com.br/busca, whose canonical is https://riocenter.com.br/s. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://riocenter.com.br/d/MASCULINO/CAMISETAS took over 3 s to send its HTML from our server.

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

10 images failed to load on a phone, for example https://riocenter-dev.hel1.your-objectstorage.com/images/products/seller_551/MALA-SESTINI-GRANDE-360-DELUXE_94e7d919-d8d6-46be-9c12-492552facf6f_medium.webp.

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_TUNNEL_CONNECTION_FAILED”.

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.

Your homepage shows a map 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.

Social proof on the homepage: 3 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

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 1,810 words of visible text.

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