telerio.com.br website review

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

vtexassets.com costs a phone 3.5 s of main-thread work and 2.3 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.

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

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

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

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

20 images could be 363 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 600 ms faster on a phone.

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

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

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

plerdy.com costs a phone 490 ms of main-thread work and 73 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.

Facebook costs a phone 382 ms of main-thread work and 279 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.

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

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.

4 KiB could be saved by minifying JavaScript.

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

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

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

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

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

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

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

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

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

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

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

13 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-31, real Chrome visitors' largest content (lcp) went from 4.0 s to 4.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 4.2 MB in 542 requests on a phone: scripts 2.2 MB (64), HTML 967 KiB (1) and images 536 KiB (122). Under 2 MB keeps phones on slow connections fast.

7683948d-184a-4f5f-9344-894c2506291e___56ae1324901272d3b9589 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 90bf1eb0-4135-460c-ab32-7cdbbc0ff91f___124c18a60812177739c5b at 1,000 px wide, shown at 171 px. Resized copies would save about 156 KiB.

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

1 image (32 KiB) is 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.18 g of CO₂e: 141.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

224 buttons have no accessible name, so screen readers announce just “button”.

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

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

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

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

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

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

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

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

Your title is only 16 characters: “Telerio é do Rio”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

No XML sitemap at https://www.lojavazia.com.br/sitemap.xml, so Google discovers your pages only by following links.

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

The homepage links to 74 pages on telerio.com.br and 0 external pages.

A phone browser shows 4,603 words, but the HTML your server sends has only 1,240. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.

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

Your homepage links to https://www.telerio.com.br/471, which answers with an error. Visitors hit a dead end and search engines drop it.

https://www.telerio.com.br/ar-e-ventilacao/ar-condicionado, https://www.telerio.com.br/ar-e-ventilacao/ventiladores/ventilador-de-mesa, https://www.telerio.com.br/ar-e-ventilacao/ventiladores/ventilador-de-coluna, https://www.telerio.com.br/ar-e-ventilacao/ventiladores, https://www.telerio.com.br/eletrodomesticos and https://www.telerio.com.br/celulares-e-telefones/celular-e-smartphone and 7 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.telerio.com.br/ar-e-ventilacao/ventiladores/ventilador-de-mesa, https://www.telerio.com.br/ar-e-ventilacao/ventiladores/ventilador-de-coluna, https://www.telerio.com.br/ar-e-ventilacao/ventiladores, https://www.telerio.com.br/eletrodomesticos, https://www.telerio.com.br/celulares-e-telefones/celular-e-smartphone and https://www.telerio.com.br/eletroportateis and 2 others took over 3 s to send their HTML from our server.

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

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

2 errors were logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'register')”.

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

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 phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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 4,603 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, 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 21 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 31 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.