Website review, no card needed

nutrire.ind.br logo

nutrire.ind.br website review

Visit site (opens in a new tab)Reviewed 29 October 202643 issues · 81 checks

This review found 43 issues worth fixing on nutrire.ind.br, 20 of them high impact, across 81 checks. The most urgent: use efficient cache lifetimes. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
5.8 s2.6 sMay 9Oct 175.5 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20265.2 s
May 16, 20264.3 s
May 23, 20263.7 s
May 30, 20263.3 s
Jun 6, 20263.0 s
Jun 13, 20263.6 s
Jun 20, 20263.9 s
Jun 27, 20265.2 s
Jul 4, 20265.2 s
Oct 10, 20265.0 s
Oct 17, 20265.5 s

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

Full-page screenshot of nutrire.ind.br (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. nutrire.ind.br at 2.6 s2.6 s
  2. nutrire.ind.br at 5.2 s5.2 s
  3. nutrire.ind.br at 7.8 s7.8 s
  4. nutrire.ind.br at 10.3 s10.3 s
  5. nutrire.ind.br at 12.9 s12.9 s
  6. nutrire.ind.br at 15.5 s15.5 s
  7. nutrire.ind.br at 18.1 s18.1 s
  8. nutrire.ind.br at 20.7 s20.7 s

Speed

13 to fix26
  • Use efficient cache lifetimes

    24.6 s · 42.7 MB

    33 files are served with short cache lifetimes, so returning visitors download them again (42.7 MB).

  • Reduce unused JavaScript

    12.2 s · 8.2 MB

    About 8.2 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 12.2 s faster on a phone.

  • YouTube adds 7.0 s

    7.0 s

    YouTube costs a phone 7.0 s of main-thread work and 15.1 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Render-blocking requests

    8.3 s

    5 files block the first paint until they finish downloading. Deferring or inlining them could save about 8.3 s.

  • Reduce unused CSS

    5.4 s · 565 KiB

    About 565 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 5.4 s faster on a phone.

  • Main-thread work: 20.7 s

    A phone's processor spends 20.7 s on main-thread work while loading, 13.0 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • Mobile performance score: 26

    26/100

    Your mobile performance score is 26. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • 4 third-party services on the page

    4 third-party services load with your homepage (YouTube, Other Google APIs/SDKs and ibge.gov.br and others), adding 16.1 MB and 7.2 s of main-thread time.

  • Improve image delivery

    7.9 MB

    15 images could be 7.9 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Minify CSS

    450 ms · 52 KiB

    52 KiB could be saved by minifying CSS.

  • 20 long tasks on the main thread

    20 long tasks block the main thread while loading, the longest for 426 ms. During a long task the page ignores taps.

  • Other Google APIs/SDKs adds 176 ms

    176 ms

    Other Google APIs/SDKs costs a phone 176 ms of main-thread work and 379 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 Fonts adds 0 ms

    0 ms

    Google Fonts costs a phone 0 ms of main-thread work and 611 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.

  • Document request latency

    105 KiB

    The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

  • 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

    3 KiB

    3 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 495 ms

    495 ms

    Your server sent the HTML in 495 ms, well inside Google's 600 ms guideline.

Core Web Vitals

6 to fix35
  • First Contentful Paint: 14.8 s

    14.8 s

    The first text or image appears after 14.8 s on a phone. Good is under 1.8 s.

  • Largest Contentful Paint: 68.2 s

    68.2 s

    Your largest element takes 68.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

  • Speed Index: 80.3 s

    80.3 s

    Visually, the page fills in at 80.3 s (Speed Index). Good is under 3.4 s.

  • Time to Interactive: 241.4 s

    241.4 s

    The page becomes fully interactive after 241.4 s. Good is under 3.8 s.

  • Total Blocking Time: 2.6 s

    2.6 s

    Scripts block taps and scrolling for 2.6 s in total while the page loads. Good is under 200 ms.

  • 7 images without width and height

    7 images have no width and height attributes, so the layout jumps as each one loads.

  • Largest content (LCP) got 10% slower for real visitors

    +10%

    Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 5.2 s to 5.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

1 checks passed
  • Cumulative Layout Shift: 0.001

    0.001

    The layout barely moves while loading (CLS 0.001, good is under 0.1).

Images and page weight

4 to fix25
  • Page weight: 59.6 MB in 246 requests

    59.6 MB

    Your homepage downloads 59.6 MB in 246 requests on a phone: images 34.2 MB (43), scripts 21.7 MB (75) and stylesheets 1.4 MB (36). Under 2 MB keeps phones on slow connections fast.

  • 10 images over 500 KB

    10 images weigh 26.4 MB together. On a phone connection a single image that size takes seconds.

  • 1 image far larger than shown

    1.2 MB

    1 image is downloaded at several times the size a phone draws it, for example products.png at 1,711 px wide, shown at 315 px. Resized copies would save about 1.2 MB.

  • 13 images in older formats

    13 images (26.9 MB) 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 16.9 g of CO₂ per visit

    16.88 g

    By the Sustainable Web Design model, a visit to your homepage emits about 16.88 g of CO₂e: 2026.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 checks passed
  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

Accessibility

5 to fixGoogle 7891
  • 6 text elements with low contrast

    6 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • 8 images without alt text

    8 images have no alt text, which hurts accessibility and image search.

  • 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.

  • 5 links without text

    5 visible links have no text or label, so screen readers cannot say where they go.

  • 3 form fields without a label

    3 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • Headings skip levels

    Headings skip levels (h2 → h5 and h2 → h4), which makes the page harder to scan with a screen reader.

1 checks passed
  • 35 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: 35 passed and 5 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

7 to fixGoogle 9268
  • Title is short (24 characters)

    Your title is only 24 characters: “Página Inicial - Nutrire”. 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.

  • Meta description is short (14 characters)

    Your meta description is only 14 characters: “Página Inicial”. 70 to 160 characters is enough to sell the click.

  • 3 H1 headlines

    There are 3 <h1> headlines (“onde encontrar”, “greenlike” and “sobre nós”). 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.

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No XML sitemap

    No XML sitemap at https://nutrire.ind.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.

  • 69 internal links, 7 external

    The homepage links to 69 pages on nutrire.ind.br and 7 external pages.

1 checks passed
  • robots.txt in place

    robots.txt is in place.

AI search readiness

1 to fix88
  • 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://nutrire.ind.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,374 words), so crawlers that don't run JavaScript still read it.

Other pages

3 to fix86
  • 2 pages share a title

    https://nutrire.ind.br/en and https://nutrire.ind.br/es all use the title “Home - Nutrire”. 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://nutrire.ind.br/en and https://nutrire.ind.br/es use the same meta description. A description written for each page earns more clicks.

  • 13 pages without an H1

    https://nutrire.ind.br/contato, https://nutrire.ind.br/faq, https://nutrire.ind.br/politica-de-cookies, https://nutrire.ind.br/central-de-privacidade, https://nutrire.ind.br/politica-de-privacidade and https://nutrire.ind.br/politica-de-seguranca-da-informacao and 7 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 3 pages slow to respond

    https://nutrire.ind.br/en, https://nutrire.ind.br/es and https://nutrire.ind.br/politica-de-cookies took over 3 s to send their HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 30 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.

  • 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

Google 92100
  • Missing source maps

    Large scripts ship without source maps.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

3 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

    15 of 18 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix42
  • 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 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 1,108 words of copy

    The homepage carries about 1,108 words of visible text.

2 checks passed
  • 2 short forms

    2 short forms (3 fields at most) are right on the homepage.

  • Direct contact links

    Visitors can reach you directly: 1 phone link and 0 email links.

Privacy and tracking

  • 2 cookies set on arrival

    2

    Opening the homepage sets 2 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.

  • 8 other companies contacted

    Loading the homepage contacts 8 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 nutrire.ind.br, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Hosting
Servicos de Internet SA

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 43 issues on nutrire.ind.br, including 19 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25