Website review, no card needed
nivalmix.com.br website review
Visit site (opens in a new tab)Reviewed 22 October 202659 issues · 96 checks
This review found 59 issues worth fixing on nivalmix.com.br, 23 of them high impact, across 96 checks. The most urgent: render-blocking requests. 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
63DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 3.7 s |
| May 9, 2026 | 3.7 s |
| May 16, 2026 | 3.7 s |
| May 23, 2026 | 3.7 s |
| May 30, 2026 | 3.7 s |
| Jun 6, 2026 | 3.6 s |
| Jun 13, 2026 | 3.6 s |
| Jun 20, 2026 | 3.6 s |
| Jun 27, 2026 | 3.6 s |
| Jul 4, 2026 | 3.6 s |
| Jul 11, 2026 | 3.6 s |
| Jul 18, 2026 | 3.6 s |
| Jul 25, 2026 | 3.8 s |
| Aug 1, 2026 | 3.8 s |
| Aug 8, 2026 | 3.8 s |
| Aug 15, 2026 | 3.9 s |
| Aug 22, 2026 | 3.8 s |
| Aug 29, 2026 | 3.8 s |
| Sep 5, 2026 | 3.8 s |
| Sep 12, 2026 | 3.8 s |
| Sep 19, 2026 | 3.9 s |
| Sep 26, 2026 | 4.0 s |
| Oct 3, 2026 | 4.1 s |
| Oct 10, 2026 | 4.1 s |
| Oct 17, 2026 | 4.1 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 187 ms |
| May 9, 2026 | 180 ms |
| May 16, 2026 | 172 ms |
| May 23, 2026 | 174 ms |
| May 30, 2026 | 178 ms |
| Jun 6, 2026 | 186 ms |
| Jun 13, 2026 | 187 ms |
| Jun 20, 2026 | 194 ms |
| Jun 27, 2026 | 196 ms |
| Jul 4, 2026 | 195 ms |
| Jul 11, 2026 | 198 ms |
| Jul 18, 2026 | 180 ms |
| Jul 25, 2026 | 183 ms |
| Aug 1, 2026 | 181 ms |
| Aug 8, 2026 | 179 ms |
| Aug 15, 2026 | 187 ms |
| Aug 22, 2026 | 184 ms |
| Aug 29, 2026 | 192 ms |
| Sep 5, 2026 | 196 ms |
| Sep 12, 2026 | 192 ms |
| Sep 19, 2026 | 196 ms |
| Sep 26, 2026 | 191 ms |
| Oct 3, 2026 | 196 ms |
| Oct 10, 2026 | 204 ms |
| Oct 17, 2026 | 206 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.8 s
3.5 s
5.3 s
7.0 s
8.8 s
10.5 s
12.3 s
14.0 s
Speed
Render-blocking requests
5.2 s43 files block the first paint until they finish downloading. Deferring or inlining them could save about 5.2 s.
Use efficient cache lifetimes
1.6 s · 1.8 MB152 files are served with short cache lifetimes, so returning visitors download them again (1.8 MB).
Reduce unused JavaScript
1.7 s · 604 KiBAbout 604 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.7 s faster on a phone.
Mobile performance score: 38
38/100Your mobile performance score is 38 (desktop: 44). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
4,678 HTML elements
The page has 4,678 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
8 third-party services on the page
8 third-party services load with your homepage (vtex.com.br, Google Tag Manager and Facebook and others), adding 3.9 MB and 1.7 s of main-thread time.
Improve image delivery
983 KiB13 images could be 983 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
vtex.com.br adds 669 ms
669 msvtex.com.br costs a phone 669 ms of main-thread work and 86 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.
Google Tag Manager adds 505 ms
505 msGoogle Tag Manager costs a phone 505 ms of main-thread work and 495 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.
Main-thread work: 3.9 s
A phone's processor spends 3.9 s on main-thread work while loading, 2.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Reduce unused CSS
330 ms · 44 KiBAbout 44 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 330 ms faster on a phone.
vteximg.com.br adds 46 ms
46 msvteximg.com.br costs a phone 46 ms of main-thread work and 2.8 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.
Facebook adds 197 ms
197 msFacebook costs a phone 197 ms of main-thread work and 312 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.
15 long tasks on the main thread
15 long tasks block the main thread while loading, the longest for 213 ms. During a long task the page ignores taps.
Legacy JavaScript
150 ms · 46 KiBPolyfills for old browsers add 46 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Minify JavaScript
90 KiB90 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: 39 ms
39 msYour server sent the HTML in 39 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.
First Contentful Paint: 8.5 s
8.5 sThe first text or image appears after 8.5 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 21.2 s
21.2 sYour largest element takes 21.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Principal”.
Speed Index: 14.0 s
14.0 sVisually, the page fills in at 14.0 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 22.8 s
22.8 sThe page becomes fully interactive after 22.8 s. Good is under 3.8 s.
Real-user LCP: 3.4 s
3.4 sReal visitors wait 3.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 2.3 s
2.3 sReal visitors see the first content after 2.3 s (75th percentile). Good is under 1.8 s.
Total Blocking Time: 575 ms
575 msScripts block taps and scrolling for 575 ms in total while the page loads. Good is under 200 ms.
2 images without width and height
2 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) got 12% slower for real visitors
+12%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 187 ms to 206 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 12% slower for real visitors
+12%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 3.7 s to 4.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
2 checks passed
Real-user CLS: 0.03
0.03For real visitors the layout shifts by 0.03 (75th percentile). Good is under 0.1.
Cumulative Layout Shift: 0.091
0.091The layout barely moves while loading (CLS 0.091, good is under 0.1).
Images and page weight
Page weight: 4.9 MB in 260 requests
4.9 MBYour homepage downloads 4.9 MB in 260 requests on a phone: images 2.5 MB (122), scripts 1.5 MB (80) and HTML 665 KiB (1). Under 2 MB keeps phones on slow connections fast.
10 images in older formats
10 images (621 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.
2 images far larger than shown
41 KiB2 images are downloaded at several times the size a phone draws them, for example Lista de Casamento 2026 Desktop.png at 1,280 px wide, shown at 390 px. Resized copies would save about 41 KiB.
6 images below the first screen load straight away
6 images further down the page (242 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 1.4 g of CO₂ per visit
1.40 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.40 g of CO₂e: 167.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
4 buttons without a name
4 buttons have no accessible name, so screen readers announce just “button”.
Hidden but focusable
7 elements hidden from screen readers can still receive keyboard focus.
ARIA input fields must have an accessible name (7 elements)
ARIA input fields must have an accessible name: 7 elements on the page fail this check, rated serious by axe-core.
Interactive controls must not be nested (6 elements)
Interactive controls must not be nested: 6 elements on the page fail this check, rated serious by axe-core.
4 text elements with low contrast
4 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Orphan list items
Some list items are not inside a list.
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 (5 elements)
All page content should be contained by landmarks: 5 elements on the page fail this check, rated moderate by axe-core.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
11 links without text
11 visible links have no text or label, so screen readers cannot say where they go.
7 form fields without a label
7 form fields have no label, so screen readers announce an empty box and autofill guesses.
ARIA role should be appropriate for the element (3 elements)
ARIA role should be appropriate for the element: 3 elements on the page fail this check, rated minor by axe-core.
1 checks passed
46 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 58 WCAG 2.2 A/AA and best-practice rules on the phone render: 46 passed and 12 failed. 5 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.
Title is short (28 characters)
Your title is only 28 characters: “Nivalmix - Completa pra você”. 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.
28 links crawlers can't follow
28 links have no real href, so search engines can't follow them.
Meta description is long (188 characters)
Your meta description is 188 characters; Google truncates after about 160, so the end of your pitch is cut.
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 http://www.lojavazia.com.br/sitemap.xml, so Google discovers your pages only by following links.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
1,027 internal links, 10 external
The homepage links to 1,027 pages on nivalmix.com.br and 10 external pages.
2 checks passed
Canonical URL set
The canonical URL is https://www.nivalmix.com.br/.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
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.nivalmix.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 (1,878 words), so crawlers that don't run JavaScript still read it.
Other pages
1 page points its canonical at the homepage
https://www.nivalmix.com.br/busca declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.
2 pages share a title
/ and https://www.nivalmix.com.br/busca all use the title “Nivalmix - Completa pra você”. Search engines can't tell which page to show for a search, so each competes with the others.
12 pages without a meta description
https://www.nivalmix.com.br/utilidades-domesticas, https://www.nivalmix.com.br/utilidades-domesticas/acess%C3%B3rios-banheiro, https://www.nivalmix.com.br/utilidades-domesticas/aparelho-de-jantar, https://www.nivalmix.com.br/utilidades-domesticas/bandeja, https://www.nivalmix.com.br/utilidades-domesticas/bomboniere and https://www.nivalmix.com.br/utilidades-domesticas/bule and 6 others have no meta description, so Google writes the search snippet from whatever text it finds.
3 pages share a meta description
https://www.nivalmix.com.br/giftlist, https://www.nivalmix.com.br/busca and https://www.nivalmix.com.br/utilidades-domesticas/baixela use the same meta description. A description written for each page earns more clicks.
13 pages without an H1
https://www.nivalmix.com.br/busca, https://www.nivalmix.com.br/utilidades-domesticas, https://www.nivalmix.com.br/utilidades-domesticas/acess%C3%B3rios-banheiro, https://www.nivalmix.com.br/utilidades-domesticas/aparelho-de-jantar, https://www.nivalmix.com.br/utilidades-domesticas/bandeja and https://www.nivalmix.com.br/utilidades-domesticas/bomboniere and 7 others have no <h1> headline, so visitors and search engines get no clear main topic.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 196 found) and read each the way a search engine does.
3 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
10 broken images
10 images failed to load on a phone, for example https://storage.googleapis.com/b8one-200201.appspot.com/nival-mix/assets/img/tramontina.png.
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Event name is not defined”.
21 distorted images
21 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
3 low-resolution images
3 images are served at too low a resolution for sharp phone screens.
2 checks passed
Tap targets are thumb-sized
200 of 202 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.
Local business without LocalBusiness data
Your homepage shows a map but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.
Thin social proof
Social proof on the homepage: 1 testimonial or review block. Pairing it with named testimonials or customer logos makes it far more convincing.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
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 997 words of copy
The homepage carries about 997 words of visible text.
4 checks passed
1 short form
A short form (1 field at most) is right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Tag Manager and Hotjar.
Direct contact links
Visitors can reach you directly: 1 phone link and 1 email link.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar 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.
24 cookies set on arrival
24Opening the homepage sets 24 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.
34 other companies contacted
Loading the homepage contacts 34 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 nivalmix.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 © 2022.
Stack
- Framework
- jQuery
- Analytics
- Google Tag Manager | Hotjar
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 59 issues on nivalmix.com.br, including 22 speed issues, 7 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.