rappi.com.br website review

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

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

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

About 1.2 MB of JavaScript is downloaded but never used on this page.

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

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

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

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

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

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

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

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

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

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

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

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

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

Your largest element takes 4.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Se você tem Rappi, você tem tudo.”.

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

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

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

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

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

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

Your homepage downloads 6.3 MB in 166 requests on a phone: scripts 3.5 MB (61), images 1.5 MB (9) and other files 1.2 MB (90). Under 2 MB keeps phones on slow connections fast.

turbo_r8_offer.png weighs 955 KiB. On a phone connection a single image that size takes seconds.

4 images are downloaded at several times the size a phone draws them, for example turbo_r8_offer.png at 1,200 px wide, shown at 60 px. Resized copies would save about 1.3 MB.

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

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

ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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.

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.

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

Structured data found (ItemList, Organization and WebSite) but with 1 problem, for example “ItemList: itemListElement is an empty list”.

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

Open Graph is missing og:title and og:description, so shared links fall back to guesses.

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

The homepage links to 46 pages on rappi.com.br and 35 external pages.

Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

There is no https://www.rappi.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.

robots.txt blocks GPTBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.

https://www.rappi.com.br/restaurantes/delivery/22793-ponto-da-esfiha, https://www.rappi.com.br/restaurantes/delivery/3369-ofner and https://www.rappi.com.br/restaurantes/delivery/169343-outback-steakhouse have no <title>, so Google invents the link text in results.

https://www.rappi.com.br/restaurantes/delivery/22793-ponto-da-esfiha, https://www.rappi.com.br/restaurantes/delivery/3369-ofner and https://www.rappi.com.br/restaurantes/delivery/169343-outback-steakhouse 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 https://www.rappi.com.br/restaurantes/delivery/1031-burger-king, whose canonical is https://www.rappi.com.br/restaurantes. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.rappi.com.br/restaurantes/delivery/22793-ponto-da-esfiha, https://www.rappi.com.br/restaurantes/delivery/3369-ofner and https://www.rappi.com.br/restaurantes/delivery/169343-outback-steakhouse have no <h1> headline, so visitors and search engines get no clear main topic.

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

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=112162293&tm=gtm002&Ver=2&mid=e09e8aa2-6c6f-4656-91d1-0165cd337019&bo=1&sid=8ba573a0d06d11f1b4d4475ceb3d5304&vid=8ba5f500d06d11f1aa4e67a8a44f6aa9&vids=1&msclkid=N&pi=9.

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

Large scripts ship without source maps.

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.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

The homepage has only about 219 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 Amplitude, Google Ads, Google Analytics, Google Tag Manager and Hotjar 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 33 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.