elo.com.br website review

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

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

About 663 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 510 ms faster on a phone.

8 third-party services load with your homepage (goadopt.io, TikTok and Google Tag Manager and others), adding 1.0 MB and 398 ms of main-thread time.

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

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

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

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

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

About 40 KiB of CSS is downloaded but never applied on this page.

1 image could be 19 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

Desktop scores 67 but mobile only 38. A gap that wide usually means heavy scripts and images that hit phones hardest.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

4 KiB could be saved by minifying CSS.

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.

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

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

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

Real visitors wait 265 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 261 ms to 324 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

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

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

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

Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 2.4 s to 2.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 2.5 MB in 132 requests on a phone: scripts 1.9 MB (33), other files 297 KiB (35) and fonts 176 KiB (5). Under 2 MB keeps phones on slow connections fast.

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

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

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.

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.

Your title is only 28 characters: “Elo | O cartão do brasileiro”. Between 30 and 65 characters leaves room to say what you do and for whom.

There are 6 <h1> headlines (“Com Elo,você tem mais”, “Pague com Elo e ganhe mais” and “Sua RotinaVale Mais”). One clear main headline is easier for people and search engines.

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

There is no robots.txt at elo.com.br/robots.txt, the first file search crawlers ask for.

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

The homepage links to 19 pages on elo.com.br and 9 external pages.

There is no /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.

/ and /sobre-elo all use the title “Elo | O cartão do brasileiro”. Search engines can't tell which page to show for a search, so each competes with the others.

/inovacao, /institucional/canais-de-contato, /aceitacao-internacional-elo, /participantes-arranjo and /consultoria have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 1 page by a URL that isn't its canonical one, for example /programa-use-elo, whose canonical is /mais-com-elo. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

/consultoria has no <h1> headline, so visitors and search engines get no clear main topic.

/institucional/canais-de-contato and /termos-e-regulamentos/aviso-de-privacidade have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

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

Large scripts ship without source maps.

1 link to other sites is dead, for example https://dev.elo.com.br/ (503).

Neither X-Frame-Options nor a CSP frame-ancestors policy is set, so any site can embed yours in a frame.

1 link go through two or more redirects, for example https://www.elo.com.br/programa-use-elo/.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

elo.com.br is registered until Dec 2026. Make sure auto-renew is on and the card on file is current.

elo.com.br's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

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: 8 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.

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

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

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