Website review, no card needed
superitalo.com.br website review
Visit site (opens in a new tab)Reviewed 1 November 202638 issues · 64 checks
This review found 38 issues worth fixing on superitalo.com.br, 13 of them high impact, across 64 checks. The most urgent: use efficient cache lifetimes. 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
67DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 2.4 s |
| May 16, 2026 | 2.3 s |
| May 23, 2026 | 2.3 s |
| May 30, 2026 | 2.4 s |
| Jun 6, 2026 | 2.3 s |
| Jun 13, 2026 | 2.3 s |
| Jun 20, 2026 | 2.4 s |
| Jun 27, 2026 | 2.5 s |
| Jul 4, 2026 | 2.6 s |
| Jul 11, 2026 | 2.5 s |
| Jul 18, 2026 | 2.5 s |
| Jul 25, 2026 | 2.5 s |
| Aug 1, 2026 | 2.5 s |
| Aug 8, 2026 | 2.5 s |
| Aug 15, 2026 | 2.5 s |
| Aug 22, 2026 | 2.6 s |
| Aug 29, 2026 | 2.7 s |
| Sep 5, 2026 | 2.8 s |
| Sep 12, 2026 | 2.9 s |
| Sep 19, 2026 | 2.9 s |
| Sep 26, 2026 | 2.9 s |
| Oct 3, 2026 | 3.0 s |
| Oct 10, 2026 | 3.0 s |
| Oct 17, 2026 | 2.9 s |
| Oct 24, 2026 | 3.4 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 171 ms |
| May 16, 2026 | 164 ms |
| May 23, 2026 | 164 ms |
| May 30, 2026 | 153 ms |
| Jun 6, 2026 | 152 ms |
| Jun 13, 2026 | 152 ms |
| Jun 20, 2026 | 152 ms |
| Jul 4, 2026 | 159 ms |
| Jul 11, 2026 | 161 ms |
| Jul 18, 2026 | 161 ms |
| Jul 25, 2026 | 163 ms |
| Aug 1, 2026 | 173 ms |
| Aug 8, 2026 | 179 ms |
| Aug 15, 2026 | 191 ms |
| Aug 22, 2026 | 190 ms |
| Aug 29, 2026 | 191 ms |
| Sep 5, 2026 | 194 ms |
| Sep 12, 2026 | 190 ms |
| Sep 19, 2026 | 187 ms |
| Sep 26, 2026 | 182 ms |
| Oct 3, 2026 | 190 ms |
| Oct 10, 2026 | 191 ms |
| Oct 17, 2026 | 223 ms |
| Oct 24, 2026 | 223 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.6 s
1.3 s
1.9 s
2.5 s
3.2 s
3.8 s
4.4 s
5.1 s
Speed
Use efficient cache lifetimes
3.3 s · 534 KiB16 files are served with short cache lifetimes, so returning visitors download them again (534 KiB).
Reduce unused JavaScript
1.6 s · 343 KiBAbout 343 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.6 s faster on a phone.
Render-blocking requests
1.3 s1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 1.3 s.
Mobile performance score: 67
67/100Your mobile performance score is 67. Pages that score under 90 lose visitors before the first paint.
Font display
700 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 700 ms).
Legacy JavaScript
450 ms · 47 KiBPolyfills for old browsers add 47 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 450 ms faster on a phone.
Reduce unused CSS
300 ms · 66 KiBAbout 66 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.
Google Tag Manager adds 167 ms
167 msGoogle Tag Manager costs a phone 167 ms of main-thread work and 405 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.
3 third-party services on the page
3 third-party services load with your homepage (Google Tag Manager, Facebook and Google Analytics), adding 632 KiB and 298 ms of main-thread time.
Minify CSS
150 ms · 13 KiB13 KiB could be saved by minifying CSS.
4 long tasks on the main thread
4 long tasks block the main thread while loading, the longest for 99 ms. During a long task the page ignores taps.
2 checks passed
Main-thread work: 0.6 s
A phone's processor spends 0.6 s on main-thread work while loading, 377 ms of it running JavaScript. That is comfortably low.
Server response: 1 ms
1 msYour server sent the HTML in 1 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Fails Core Web Vitals for real visitors
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.
Largest Contentful Paint: 9.4 s
9.4 sYour largest element takes 9.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Curitiba Cristo Rei”. Most of its time is element render delay (5.1 s).
Speed Index: 7.9 s
7.9 sVisually, the page fills in at 7.9 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 10.5 s
10.5 sThe page becomes fully interactive after 10.5 s. Good is under 3.8 s.
Real-user LCP: 3.6 s
3.6 sReal visitors wait 3.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Tap response (INP) got 33% slower for real visitors
+33%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 171 ms to 223 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 33% slower for real visitors
+33%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 2.4 s to 3.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user FCP: 2.6 s
2.6 sReal visitors see the first content after 2.6 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.5 s
1.5 sReal visitors wait 1.5 s for your server to start answering (75th percentile). Good is under 800 ms.
4 checks passed
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
First Contentful Paint: 0.8 s
0.8 sThe first text or image appears after 0.8 s, inside the 1.8 s “good” threshold.
Total Blocking Time: 59 ms
59 msScripts block the page for only 59 ms while loading. Good is under 200 ms.
Images and page weight
About 0.5 g of CO₂ per visit
0.46 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.46 g of CO₂e: 55.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Page weight: 1.6 MB in 33 requests
1.6 MBYour homepage downloads 1.6 MB in 33 requests on a phone: scripts 978 KiB (17), other files 610 KiB (12) and stylesheets 70 KiB (1). That is a lean page.
Accessibility
4 buttons without a name
4 buttons have no accessible name, so screen readers announce just “button”.
Interactive controls must not be nested (4 elements)
Interactive controls must not be nested: 4 elements on the page fail this check, rated serious by axe-core.
<html> element must have a lang attribute (1 element)
<html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
6 links without text
6 visible links have no text or label, so screen readers cannot say where they go.
No page language
The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.
Headings should not be empty (1 element)
Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.
1 checks passed
18 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 24 WCAG 2.2 A/AA and best-practice rules on the phone render: 18 passed and 6 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
4 H1 headlines
There are 4 <h1> headlines (“”, “Carregando...” and “escolhauma unidade”). One clear main headline is easier for people and search engines.
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
Meta description is long (447 characters)
Your meta description is 447 characters; Google truncates after about 160, so the end of your pitch is cut.
No XML sitemap
No XML sitemap at https://www.superitalo.com.br/sitemap.xml, so Google discovers your pages only by following links.
Only 2 internal links
The homepage links to only 2 pages on your own site, so visitors and crawlers find few routes into the rest of it.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.
3 checks passed
Title: 34 characters
Your title is a healthy 34 characters: “Ítalo Supermercados - Do Seu Jeito”.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
robots.txt in place
robots.txt is in place.
AI search readiness
No Organization structured data
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.
No llms.txt
There is no https://www.superitalo.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.
1 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.
Best practices
4 JavaScript errors while loading
4 errors were logged to the browser console while the page loaded, for example “Access to font at 'https://static.superitalo.com.br/static/fonts/isidora-alt-w00-semibold.ttf' from origin 'https://www…”.
2 checks passed
Tap targets are thumb-sized
30 of 30 tappable elements near the top are at least 24 px.
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.
No direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
Only about 57 words
The homepage has only about 57 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.
1 checks passed
Analytics in place
Analytics detected: Google Tag Manager and Google Analytics.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads 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.
3 cookies set on arrival
3Opening the homepage sets 3 cookies (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.
4 other companies contacted
Loading the homepage contacts 4 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 superitalo.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
- Framework
- Next.js
- Analytics
- Google Analytics | Google Tag Manager
- Hosting
- Zen Ecn
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 38 issues on superitalo.com.br, including 17 speed issues, 6 SEO issues and 5 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.