Website review, no card needed
rascal.com.br website review
Visit site (opens in a new tab)Reviewed 1 November 202623 issues · 70 checks
This review found 23 issues worth fixing on rascal.com.br, 5 of them high impact, across 70 checks. The most urgent: 11 text elements with low contrast. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
88BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 825 ms |
| May 16, 2026 | 831 ms |
| May 23, 2026 | 813 ms |
| May 30, 2026 | 818 ms |
| Jun 6, 2026 | 820 ms |
| Jun 13, 2026 | 810 ms |
| Jun 20, 2026 | 832 ms |
| Jun 27, 2026 | 821 ms |
| Jul 4, 2026 | 860 ms |
| Jul 11, 2026 | 870 ms |
| Jul 18, 2026 | 841 ms |
| Jul 25, 2026 | 854 ms |
| Aug 1, 2026 | 857 ms |
| Aug 8, 2026 | 853 ms |
| Aug 15, 2026 | 870 ms |
| Aug 22, 2026 | 861 ms |
| Aug 29, 2026 | 864 ms |
| Sep 5, 2026 | 877 ms |
| Sep 12, 2026 | 880 ms |
| Sep 19, 2026 | 934 ms |
| Sep 26, 2026 | 959 ms |
| Oct 3, 2026 | 994 ms |
| Oct 10, 2026 | 1.0 s |
| Oct 17, 2026 | 959 ms |
| Oct 24, 2026 | 929 ms |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 146 ms |
| May 16, 2026 | 146 ms |
| May 23, 2026 | 145 ms |
| May 30, 2026 | 144 ms |
| Jun 6, 2026 | 142 ms |
| Jun 13, 2026 | 143 ms |
| Jun 20, 2026 | 145 ms |
| Jun 27, 2026 | 146 ms |
| Jul 4, 2026 | 150 ms |
| Jul 11, 2026 | 153 ms |
| Jul 18, 2026 | 152 ms |
| Jul 25, 2026 | 154 ms |
| Aug 1, 2026 | 156 ms |
| Aug 8, 2026 | 159 ms |
| Aug 15, 2026 | 162 ms |
| Aug 22, 2026 | 166 ms |
| Aug 29, 2026 | 169 ms |
| Sep 5, 2026 | 174 ms |
| Sep 12, 2026 | 176 ms |
| Sep 19, 2026 | 180 ms |
| Sep 26, 2026 | 188 ms |
| Oct 3, 2026 | 195 ms |
| Oct 10, 2026 | 207 ms |
| Oct 17, 2026 | 209 ms |
| Oct 24, 2026 | 211 ms |
Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.
One score from every part of this review. How it works
How it loaded on a phone
0.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Render-blocking requests
850 ms1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 850 ms.
Reduce unused CSS
560 ms · 120 KiBAbout 120 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 560 ms faster on a phone.
Use efficient cache lifetimes
150 ms · 106 KiB9 files are served with short cache lifetimes, so returning visitors download them again (106 KiB).
Chained critical requests
Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.
3 checks passed
Mobile performance score: 99
99/100Your mobile performance score is 99. That is in Google's “good” band (90 and up).
Main-thread work: 0.3 s
A phone's processor spends 0.3 s on main-thread work while loading, 18 ms of it running JavaScript. That is comfortably low.
Server response: 157 ms
157 msYour server sent the HTML in 157 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Tap response (INP) got 44% slower for real visitors
+44%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 146 ms to 211 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 14% slower for real visitors
+14%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 0.8 s to 0.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
12 checks passed
Passes Core Web Vitals for real visitors
Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).
Real-user LCP: 0.9 s
0.9 sReal visitors wait 0.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 125 ms
125 msReal visitors wait 125 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.03
0.03For real visitors the layout shifts by 0.03 (75th percentile). Good is under 0.1.
Real-user FCP: 0.9 s
0.9 sReal visitors see the first content after 0.9 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 351 ms
351 msReal visitors wait 351 ms for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 1.6 s
1.6 sThe first text or image appears after 1.6 s, inside the 1.8 s “good” threshold.
Speed Index: 2.7 s
2.7 sVisually, the page fills in at 2.7 s (Speed Index), inside the 3.4 s “good” threshold.
Largest Contentful Paint: 1.6 s
1.6 sYour largest element renders in 1.6 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “Nós, do Ráscal, valorizamos as relações humanas e as histór…”.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Total Blocking Time: 0 ms
0 msScripts block the page for only 0 ms while loading. Good is under 200 ms.
Time to Interactive: 1.6 s
1.6 sThe page is fully interactive after 1.6 s.
Images and page weight
8 images in older formats
8 images (717 KiB) are 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.
About 0.3 g of CO₂ per visit
0.30 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.30 g of CO₂e: 36.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Page weight: 1.1 MB in 11 requests
1.1 MBYour homepage downloads 1.1 MB in 11 requests on a phone: images 719 KiB (5), fonts 214 KiB (3) and stylesheets 125 KiB (1). That is a lean page.
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
11 text elements with low contrast
11 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
All page content should be contained by landmarks (10 elements)
All page content should be contained by landmarks: 10 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 (1 element)
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.
5 links without text
5 visible links have no text or label, so screen readers cannot say where they go.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
2 checks passed
Every image has alt text
All 18 images in the HTML carry an alt attribute.
42 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 46 WCAG 2.2 A/AA and best-practice rules on the phone render: 42 passed and 4 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Meta description is long (228 characters)
Your meta description is 228 characters; Google truncates after about 160, so the end of your pitch is cut.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
51 internal links, 15 external
The homepage links to 51 pages on rascal.com.br and 15 external pages.
5 checks passed
Title: 32 characters
Your title is a healthy 32 characters: “Home Ráscal - Ráscal Restaurante”.
Canonical URL set
The canonical URL is https://www.rascal.com.br/.
Structured data in place
Structured data found: BreadcrumbList, Organization, WebPage and WebSite.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at https://www.rascal.com.br/sitemap_index.xml.
AI search readiness
4 checks passed
AI answer engines may read the site
Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.
Organization data: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (260 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.rascal.com.br/llms.txt (58 KiB, 48 links), a plain-text guide to the site for AI tools.
Other pages
3 linked pages hidden from search
https://www.rascal.com.br/30-anos-do-rascal, https://www.rascal.com.br/livro-nossos-almocos-de-familia and https://www.rascal.com.br/delivery are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.
2 pages share a title
https://www.rascal.com.br/30-anos-do-rascal and https://www.rascal.com.br/livro-nossos-almocos-de-familia all use the title “Ráscal: há 30 anos acolhendo gerações”. Search engines can't tell which page to show for a search, so each competes with the others.
3 pages without a meta description
https://www.rascal.com.br/restaurante/cardapio-e-bebidas-rascal-sao-paulo, https://www.rascal.com.br/restaurante/cardapio-e-bebidas-rascal-guarulhos and https://www.rascal.com.br/restaurante/cardapio-e-bebidas-rascal-rio-de-janeiro have no meta description, so Google writes the search snippet from whatever text it finds.
6 pages share a meta description
https://www.rascal.com.br/30-anos-do-rascal and https://www.rascal.com.br/livro-nossos-almocos-de-familia use the same meta description. A description written for each page earns more clicks.
9 pages without an H1
https://www.rascal.com.br/restaurante, https://www.rascal.com.br/30-anos-do-rascal, https://www.rascal.com.br/restaurante/cardapio-e-bebidas-rascal-sao-paulo, https://www.rascal.com.br/restaurante/cardapio-e-bebidas-rascal-guarulhos, https://www.rascal.com.br/restaurante/cardapio-e-bebidas-rascal-rio-de-janeiro and https://www.rascal.com.br/receitas and 3 others have no <h1> headline, so visitors and search engines get no clear main topic.
13 internal pages checked
We fetched 13 pages linked from your homepage and read each the way a search engine does.
3 checks passed
Linked pages load
All 13 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a title
All 13 pages that loaded have a <title>.
Best practices
9 small tap targets
9 of 17 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Access to fetch at 'https://gtm-54cj6mx-ythln.uc.r.appspot.com/g/collect?v=2&tid=G-RCC7HPKFJB>m=45je6at0h2v879477562z…”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No call to action on the first screen
On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.
No calls to action
We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
Only about 215 words
The homepage has only about 215 words of visible text; thin pages give Google and first-time buyers little to go on.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
No risk reducer
No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.
2 checks passed
Analytics in place
Analytics detected: Google Tag Manager and Google Analytics.
Direct contact links
Visitors can reach you directly: 0 phone links and 1 email link.
Privacy and tracking
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Meta 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.
23 cookies set on arrival
23Opening the homepage sets 23 cookies, 1 of them by other companies (measured from a US location before any click).
No consent tool detected
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.
23 other companies contacted
Loading the homepage contacts 23 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
Security, domain, email and software versions
The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at rascal.com.br, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- WordPress
- Framework
- jQuery
- Analytics
- Google Analytics | Google Tag Manager
- Hosting
- Hostinger
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 23 issues on rascal.com.br, including 3 speed issues, 3 SEO issues and 4 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.
- 28 research agents read your site, reviews, competitors, communities and public filings
- Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
- Competitor intelligence with battlecards for your closest rivals
- Ideal customer profile, buyer segments and buying-stage funnel
- Ranked channels, outreach sequences and content angles
- Live Reddit threads where buyers ask for what you sell, with draft replies
- Earned media and PR openings
- At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
- PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
- Refresh the playbook later to see what changed
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.