Website review, no card needed
supermercadovioleta.com.br website review
Visit site (opens in a new tab)Reviewed 26 October 202647 issues · 80 checks
This review found 47 issues worth fixing on supermercadovioleta.com.br, 18 of them high impact, across 80 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
54FClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 6.8 s |
| May 16, 2026 | 6.7 s |
| May 23, 2026 | 6.7 s |
| May 30, 2026 | 6.5 s |
| Jun 6, 2026 | 6.4 s |
| Jun 13, 2026 | 6.3 s |
| Jun 20, 2026 | 6.4 s |
| Jun 27, 2026 | 6.5 s |
| Jul 4, 2026 | 6.4 s |
| Jul 11, 2026 | 6.6 s |
| Jul 18, 2026 | 6.7 s |
| Jul 25, 2026 | 6.6 s |
| Aug 1, 2026 | 6.7 s |
| Aug 8, 2026 | 6.7 s |
| Aug 15, 2026 | 7.3 s |
| Aug 22, 2026 | 7.2 s |
| Aug 29, 2026 | 7.0 s |
| Sep 5, 2026 | 6.9 s |
| Sep 12, 2026 | 6.3 s |
| Sep 19, 2026 | 6.2 s |
| Sep 26, 2026 | 6.2 s |
| Oct 3, 2026 | 6.1 s |
| Oct 10, 2026 | 6.1 s |
| Oct 17, 2026 | 6.0 s |
| Oct 24, 2026 | 5.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 361 ms |
| May 16, 2026 | 346 ms |
| May 23, 2026 | 332 ms |
| May 30, 2026 | 328 ms |
| Jun 6, 2026 | 333 ms |
| Jun 13, 2026 | 322 ms |
| Jun 20, 2026 | 306 ms |
| Jun 27, 2026 | 284 ms |
| Jul 4, 2026 | 278 ms |
| Jul 11, 2026 | 278 ms |
| Jul 18, 2026 | 282 ms |
| Jul 25, 2026 | 292 ms |
| Aug 1, 2026 | 293 ms |
| Aug 8, 2026 | 306 ms |
| Aug 15, 2026 | 309 ms |
| Aug 22, 2026 | 308 ms |
| Aug 29, 2026 | 305 ms |
| Sep 5, 2026 | 304 ms |
| Sep 12, 2026 | 307 ms |
| Sep 19, 2026 | 316 ms |
| Sep 26, 2026 | 318 ms |
| Oct 3, 2026 | 321 ms |
| Oct 10, 2026 | 321 ms |
| Oct 17, 2026 | 312 ms |
| Oct 24, 2026 | 317 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
1.2 s
2.4 s
3.6 s
4.8 s
6.0 s
7.2 s
8.4 s
9.6 s
Speed
Use efficient cache lifetimes
60.4 s · 12.5 MB180 files are served with short cache lifetimes, so returning visitors download them again (12.5 MB).
Improve image delivery
47.1 s · 9.9 MB54 images could be 9.9 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 47.1 s faster on a phone.
Reduce unused JavaScript
5.0 s · 709 KiBAbout 709 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 5.0 s faster on a phone.
Mobile performance score: 26
26/100Your mobile performance score is 26 (desktop: 39). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 7.1 s
A phone's processor spends 7.1 s on main-thread work while loading, 4.0 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, atendimen.to and Facebook and others), adding 1.4 MB and 1.6 s of main-thread time.
Google Tag Manager adds 777 ms
777 msGoogle Tag Manager costs a phone 777 ms of main-thread work and 532 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.
Render-blocking requests
600 ms3 files block the first paint until they finish downloading. Deferring or inlining them could save about 600 ms.
atendimen.to adds 529 ms
529 msatendimen.to costs a phone 529 ms of main-thread work and 604 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.
16 long tasks on the main thread
16 long tasks block the main thread while loading, the longest for 500 ms. During a long task the page ignores taps.
Facebook adds 319 ms
319 msFacebook costs a phone 319 ms of main-thread work and 225 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.
1,774 HTML elements
The page has 1,774 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Legacy JavaScript
26 KiBPolyfills for old browsers add 26 KiB JavaScript that modern phones do not need.
Reduce unused CSS
17 KiBAbout 17 KiB of CSS is downloaded but never applied on this page.
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.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
Minify JavaScript
2 KiB2 KiB could be saved by minifying JavaScript.
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.
Real-user LCP: 6.4 s
6.4 sReal visitors wait 6.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.32
0.32For real visitors the layout shifts by 0.32 (75th percentile). Good is under 0.1.
Largest Contentful Paint: 76.8 s
76.8 sYour largest element takes 76.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Banner imagem”.
Speed Index: 27.1 s
27.1 sVisually, the page fills in at 27.1 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 78.1 s
78.1 sThe page becomes fully interactive after 78.1 s. Good is under 3.8 s.
Total Blocking Time: 2.4 s
2.4 sScripts block taps and scrolling for 2.4 s in total while the page loads. Good is under 200 ms.
First Contentful Paint: 5.4 s
5.4 sThe first text or image appears after 5.4 s on a phone. Good is under 1.8 s.
Real-user INP: 332 ms
332 msReal visitors wait 332 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 2.1 s
2.1 sReal visitors see the first content after 2.1 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.1 s
1.1 sReal visitors wait 1.1 s for your server to start answering (75th percentile). Good is under 800 ms.
3 checks passed
Tap response (INP) got 11% faster for real visitors
-11%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 361 ms to 317 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 13% faster for real visitors
-13%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 6.8 s to 5.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0.064
0.064The layout barely moves while loading (CLS 0.064, good is under 0.1).
Images and page weight
Page weight: 18.9 MB in 251 requests
18.9 MBYour homepage downloads 18.9 MB in 251 requests on a phone: images 16.2 MB (59), scripts 1.9 MB (133) and HTML 591 KiB (3). Under 2 MB keeps phones on slow connections fast.
About 5.4 g of CO₂ per visit
5.37 gBy the Sustainable Web Design model, a visit to your homepage emits about 5.37 g of CO₂e: 644.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
[aria-*] attributes do not have valid values
[aria-*] attributes do not have valid values (10 elements).
All page content should be contained by landmarks (3 elements)
All page content should be contained by landmarks: 3 elements on the page fail this check, rated moderate by axe-core.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
The skip-link target should exist and be focusable (1 element)
The skip-link target should exist and be focusable: 1 element on the page fails this check, rated moderate by axe-core.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (5 elements).
1 checks passed
37 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 40 WCAG 2.2 A/AA and best-practice rules on the phone render: 37 passed and 3 failed. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (20 characters)
Your title is only 20 characters: “Supermercados Online”. Between 30 and 65 characters leaves room to say what you do and for whom.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
No social preview image
No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
No XML sitemap
No XML sitemap at https://www.violetaexpress.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 incomplete here.
3 checks passed
Meta description: 104 characters
Your meta description is 104 characters: “Supermercados Online – faça suas compras com praticidade e segurança. Entrega rápida e produtos frescos.”.
One H1 headline
Your main headline reads: “Supermercados Online – Loja Virtual”.
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.violetaexpress.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.
Other pages
3 pages share a title
/, https://www.violetaexpress.com.br/produtos and https://www.violetaexpress.com.br/contato all use the title “Supermercados Online”. Search engines can't tell which page to show for a search, so each competes with the others.
2 pages share a meta description
https://www.violetaexpress.com.br/produtos and https://www.violetaexpress.com.br/contato use the same meta description. A description written for each page earns more clicks.
2 pages with very little text
https://www.violetaexpress.com.br/produtos and https://www.violetaexpress.com.br/contato 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.
2 internal pages checked
We fetched 2 pages linked from your homepage and read each the way a search engine does.
6 checks passed
Linked pages load
All 2 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 meta description
All 2 pages that loaded have a meta description.
Every page has an H1
Each page we checked has a main headline.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 2 pages that loaded have a <title>.
Best practices
5 small tap targets
5 of 5 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
Deprecated browser APIs
The page uses 2 deprecated browser APIs that will stop working in future browsers (“Authorization will not be covered by the wildcard symbol (*) in CORS `Access-Control-Allow-Headers`…”).
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 403 ()”.
1 distorted image
1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.
Missing source maps
Large scripts ship without source maps.
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.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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 34 words
The homepage has only about 34 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.
Privacy and tracking
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.
1 checks passed
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
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 supermercadovioleta.com.br, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
- The footer still says © 2025.
Stack
- Hosting
- Equinix
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 47 issues on supermercadovioleta.com.br, including 23 speed issues, 6 SEO issues and 6 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.