Website review, no card needed
vitafor.com.br website review
Visit site (opens in a new tab)Reviewed 18 November 202652 issues · 95 checks
This review found 52 issues worth fixing on vitafor.com.br, 21 of them high impact, across 95 checks. The most urgent: reduce unused JavaScript. 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
66DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 3.0 s |
| Jun 6, 2026 | 3.1 s |
| Jun 13, 2026 | 3.2 s |
| Jun 20, 2026 | 3.4 s |
| Jun 27, 2026 | 3.5 s |
| Jul 4, 2026 | 3.5 s |
| Jul 11, 2026 | 3.5 s |
| Jul 18, 2026 | 3.5 s |
| Jul 25, 2026 | 3.4 s |
| Aug 1, 2026 | 3.3 s |
| Aug 8, 2026 | 3.1 s |
| Aug 15, 2026 | 2.9 s |
| Aug 22, 2026 | 2.8 s |
| Aug 29, 2026 | 2.7 s |
| Sep 5, 2026 | 2.7 s |
| Sep 12, 2026 | 2.7 s |
| Sep 19, 2026 | 2.7 s |
| Sep 26, 2026 | 2.7 s |
| Oct 3, 2026 | 2.7 s |
| Oct 10, 2026 | 2.8 s |
| Oct 17, 2026 | 2.8 s |
| Oct 24, 2026 | 2.8 s |
| Oct 31, 2026 | 2.8 s |
| Nov 7, 2026 | 2.8 s |
| Nov 14, 2026 | 2.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 205 ms |
| Jun 6, 2026 | 210 ms |
| Jun 13, 2026 | 214 ms |
| Jun 20, 2026 | 219 ms |
| Jun 27, 2026 | 224 ms |
| Jul 4, 2026 | 229 ms |
| Jul 11, 2026 | 229 ms |
| Jul 18, 2026 | 224 ms |
| Jul 25, 2026 | 220 ms |
| Aug 1, 2026 | 220 ms |
| Aug 8, 2026 | 230 ms |
| Aug 15, 2026 | 248 ms |
| Aug 22, 2026 | 262 ms |
| Aug 29, 2026 | 264 ms |
| Sep 5, 2026 | 262 ms |
| Sep 12, 2026 | 254 ms |
| Sep 19, 2026 | 250 ms |
| Sep 26, 2026 | 248 ms |
| Oct 3, 2026 | 247 ms |
| Oct 10, 2026 | 245 ms |
| Oct 17, 2026 | 246 ms |
| Oct 24, 2026 | 252 ms |
| Oct 31, 2026 | 252 ms |
| Nov 7, 2026 | 250 ms |
| Nov 14, 2026 | 245 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.2 s
1.8 s
2.4 s
3.0 s
3.6 s
4.2 s
4.8 s
Speed
Reduce unused JavaScript
2.1 s · 893 KiBAbout 893 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.1 s faster on a phone.
Render-blocking requests
1.1 s5 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.1 s.
Mobile performance score: 46
46/100Your mobile performance score is 46. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 4.3 s
A phone's processor spends 4.3 s on main-thread work while loading, 2.7 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 (vtexassets.com, Google Tag Manager and Freshchat and others), adding 3.7 MB and 1.9 s of main-thread time.
Use efficient cache lifetimes
800 ms · 598 KiB48 files are served with short cache lifetimes, so returning visitors download them again (598 KiB).
vtexassets.com adds 859 ms
859 msvtexassets.com costs a phone 859 ms of main-thread work and 1.7 MB 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.
Google Tag Manager adds 448 ms
448 msGoogle Tag Manager costs a phone 448 ms of main-thread work and 691 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.
Legacy JavaScript
350 ms · 56 KiBPolyfills for old browsers add 56 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 350 ms faster on a phone.
Freshchat adds 307 ms
307 msFreshchat costs a phone 307 ms of main-thread work and 843 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.
Reduce unused CSS
300 ms · 80 KiBAbout 80 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.
Improve image delivery
283 KiB14 images could be 283 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
1,741 HTML elements
The page has 1,741 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
16 long tasks on the main thread
16 long tasks block the main thread while loading, the longest for 159 ms. During a long task the page ignores taps.
Minify JavaScript
25 KiB25 KiB could be saved by minifying JavaScript.
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.
1 checks passed
Server response: 53 ms
53 msYour server sent the HTML in 53 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: 16.2 s
16.2 sYour largest element takes 16.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 26.2 s
26.2 sThe page becomes fully interactive after 26.2 s. Good is under 3.8 s.
Speed Index: 9.1 s
9.1 sVisually, the page fills in at 9.1 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 4.1 s
4.1 sThe first text or image appears after 4.1 s on a phone. Good is under 1.8 s.
Real-user LCP: 2.5 s
2.5 sReal visitors wait 2.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 280 ms
280 msReal visitors wait 280 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 2.4 s
2.4 sReal visitors see the first content after 2.4 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 997 ms
997 msReal visitors wait 997 ms for your server to start answering (75th percentile). Good is under 800 ms.
Total Blocking Time: 489 ms
489 msScripts block taps and scrolling for 489 ms in total while the page loads. Good is under 200 ms.
12 images without width and height
12 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) got 19% slower for real visitors
+19%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 205 ms to 245 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-9%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 3.0 s to 2.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
2 checks passed
Real-user CLS: 0.04
0.04For real visitors the layout shifts by 0.04 (75th percentile). Good is under 0.1.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 4.0 MB in 394 requests
4.0 MBYour homepage downloads 4.0 MB in 394 requests on a phone: scripts 2.7 MB (68), images 575 KiB (60) and other files 441 KiB (251). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
865a47bb-0141-452d-b47b-185b7c20725a___34997ea91c1a2c4b00e6f is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).
3 images in older formats
3 images (106 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.
4 images below the first screen load straight away
4 images further down the page (184 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 1.1 g of CO₂ per visit
1.14 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.14 g of CO₂e: 136.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
18 tap targets too small
18 tap targets are too small or too close together to hit reliably with a finger.
ARIA commands must have an accessible name (6 elements)
ARIA commands must have an accessible name: 6 elements on the page fail this check, rated serious by axe-core.
Hidden but focusable
6 elements hidden from screen readers can still receive keyboard focus.
1 text element with low contrast
1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.
Scrollable region must have keyboard access (1 element)
Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.
1 image without alt text
1 image has no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (25 elements)
All page content should be contained by landmarks: 25 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 (9 elements)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 9 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.
19 links without text
19 visible links have no text or label, so screen readers cannot say where they go.
4 form fields without a label
4 form fields have no label, so screen readers announce an empty box and autofill guesses.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (3 elements).
1 checks passed
42 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 54 WCAG 2.2 A/AA and best-practice rules on the phone render: 42 passed and 12 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Meta description is long (161 characters)
Your meta description is 161 characters; Google truncates after about 160, so the end of your pitch is cut.
Structured data has 1 problem
Structured data found (WebSite) but with 1 problem, for example “WebSite: missing name”.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
109 internal links, 19 external
The homepage links to 109 pages on vitafor.com.br and 19 external pages.
5 checks passed
One H1 headline
Your main headline reads: “Os Mais Vendidos”.
Title: 57 characters
Your title is a healthy 57 characters: “Vitafor: Suplementos Nutricionais de Qualidade Comprovada”.
Canonical URL set
The canonical URL is https://www.vitafor.com.br/.
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.vitafor.com.br/sitemap.xml.
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.vitafor.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.
2 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.
Text is in the HTML
Your server sends the page's text in the HTML (760 words), so crawlers that don't run JavaScript still read it.
Other pages
3 linked pages hidden from search
https://www.vitafor.com.br/381, https://www.vitafor.com.br/172 and https://www.vitafor.com.br/382 are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.
8 pages share a meta description
https://www.vitafor.com.br/381, https://www.vitafor.com.br/172, https://www.vitafor.com.br/achocolatado-adocantes-e-cha, https://www.vitafor.com.br/acessorios, https://www.vitafor.com.br/alimentos and https://www.vitafor.com.br/382 and 2 others use the same meta description. A description written for each page earns more clicks.
2 pages without an H1
https://www.vitafor.com.br/quem-somos and https://www.vitafor.com.br/fitzei have no <h1> headline, so visitors and search engines get no clear main topic.
1 page slow to respond
https://www.vitafor.com.br/hospitalar took over 3 s to send its HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 92 found) and read each the way a search engine does.
5 checks passed
Linked pages load
All 15 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 15 pages that loaded have a meta description.
Titles are unique
Every page we checked has its own title.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
1 broken image
1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=187210625&tm=gtm002&Ver=2&mid=f14179ef-a54b-4c51-baa9-6db298f820e5&bo=1&sid=b5645160e2f111f1a3274be9927ecb4a&vid=b5648af0e2f111f19bce194981c708bf&vids=1&msclkid=N>m_.
1 third-party cookie
1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.
5 JavaScript errors while loading
5 errors were logged to the browser console while the page loaded, for example “Warning: No Tracking ID is defined. Please configure it in the apps admin.”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
2 checks passed
Tap targets are thumb-sized
56 of 62 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 risk reducer
No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.
About 758 words of copy
The homepage carries about 758 words of visible text.
3 checks passed
1 short form
A short form (4 fields at most) is right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Tag Manager, Meta Pixel, Mixpanel and TikTok Pixel.
Direct contact links
Visitors can reach you directly: 2 phone links and 1 email link.
Privacy and tracking
7 trackers load before any consent
7Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Ads and 2 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.
26 cookies set on arrival
26Opening the homepage sets 26 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.
38 other companies contacted
Loading the homepage contacts 38 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 vitafor.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
- React
- Analytics
- Google Tag Manager | Mixpanel
- Hosting
- AWS
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 52 issues on vitafor.com.br, including 24 speed issues, 3 SEO issues and 3 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.