Website review, no card needed
alinutri.ind.br website review
Visit site (opens in a new tab)Reviewed 28 October 202638 issues · 81 checks
This review found 38 issues worth fixing on alinutri.ind.br, 17 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.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
62DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 2.1 s |
| May 16, 2026 | 2.1 s |
| May 23, 2026 | 2.1 s |
| May 30, 2026 | 2.0 s |
| Jun 6, 2026 | 2.0 s |
| Jun 13, 2026 | 1.9 s |
| Jun 20, 2026 | 1.8 s |
| Jun 27, 2026 | 1.7 s |
| Jul 4, 2026 | 1.5 s |
| Jul 11, 2026 | 1.4 s |
| Jul 18, 2026 | 1.4 s |
| Jul 25, 2026 | 1.4 s |
| Aug 1, 2026 | 1.4 s |
| Aug 8, 2026 | 1.4 s |
| Aug 15, 2026 | 1.4 s |
| Aug 22, 2026 | 1.4 s |
| Aug 29, 2026 | 1.5 s |
| Sep 5, 2026 | 1.5 s |
| Sep 12, 2026 | 1.6 s |
| Sep 19, 2026 | 1.6 s |
| Sep 26, 2026 | 1.5 s |
| Oct 3, 2026 | 1.6 s |
| Oct 10, 2026 | 1.6 s |
| Oct 17, 2026 | 1.6 s |
| Oct 24, 2026 | 1.5 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 152 ms |
| May 16, 2026 | 151 ms |
| May 23, 2026 | 149 ms |
| May 30, 2026 | 147 ms |
| Jun 6, 2026 | 146 ms |
| Jun 13, 2026 | 152 ms |
| Jun 20, 2026 | 158 ms |
| Jun 27, 2026 | 165 ms |
| Jul 4, 2026 | 172 ms |
| Jul 11, 2026 | 166 ms |
| Jul 18, 2026 | 159 ms |
| Jul 25, 2026 | 154 ms |
| Aug 1, 2026 | 154 ms |
| Aug 8, 2026 | 161 ms |
| Aug 15, 2026 | 169 ms |
| Aug 22, 2026 | 176 ms |
| Aug 29, 2026 | 178 ms |
| Sep 5, 2026 | 178 ms |
| Sep 12, 2026 | 177 ms |
| Sep 19, 2026 | 190 ms |
| Sep 26, 2026 | 194 ms |
| Oct 3, 2026 | 196 ms |
| Oct 10, 2026 | 199 ms |
| Oct 17, 2026 | 188 ms |
| Oct 24, 2026 | 185 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.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Use efficient cache lifetimes
5.5 s · 6.2 MB118 files are served with short cache lifetimes, so returning visitors download them again (6.2 MB).
Improve image delivery
1.9 s · 4.1 MB44 images could be 4.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.9 s faster on a phone.
Reduce unused JavaScript
1.8 s · 1.3 MBAbout 1.3 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.8 s faster on a phone.
Render-blocking requests
1.4 s15 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.4 s.
Mobile performance score: 39
39/100Your mobile performance score is 39 (desktop: 40). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Facebook and leadster.com.br and others), adding 1.7 MB and 1.2 s of main-thread time.
Google Tag Manager adds 702 ms
702 msGoogle Tag Manager costs a phone 702 ms of main-thread work and 1.1 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.
Reduce unused CSS
410 ms · 67 KiBAbout 67 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 410 ms faster on a phone.
Main-thread work: 2.4 s
A phone's processor spends 2.4 s on main-thread work while loading, 1.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
14 long tasks on the main thread
14 long tasks block the main thread while loading, the longest for 209 ms. During a long task the page ignores taps.
Minify JavaScript
150 ms · 19 KiB19 KiB could be saved by minifying JavaScript.
Legacy JavaScript
32 KiBPolyfills for old browsers add 32 KiB JavaScript that modern phones do not need.
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.
1 checks passed
Server response: 4 ms
4 msYour server sent the HTML in 4 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.
Real-user CLS: 0.47
0.47For real visitors the layout shifts by 0.47 (75th percentile). Good is under 0.1.
Largest Contentful Paint: 17.5 s
17.5 sYour largest element takes 17.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Long Life”.
Time to Interactive: 26.1 s
26.1 sThe page becomes fully interactive after 26.1 s. Good is under 3.8 s.
Cumulative Layout Shift: 0.448
0.448The layout shifts by 0.448 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Speed Index: 6.6 s
6.6 sVisually, the page fills in at 6.6 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 3.0 s
3.0 sThe first text or image appears after 3.0 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.
Tap response (INP) got 23% slower for real visitors
+23%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 152 ms to 185 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user TTFB: 943 ms
943 msReal visitors wait 943 ms for your server to start answering (75th percentile). Good is under 800 ms.
59 images without width and height
59 images have no width and height attributes, so the layout jumps as each one loads.
Total Blocking Time: 230 ms
230 msScripts block taps and scrolling for 230 ms in total while the page loads. Good is under 200 ms.
3 checks passed
Real-user INP: 181 ms
181 msReal visitors wait 181 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 1.7 s
1.7 sReal visitors see the first content after 1.7 s (75th percentile). Good is under 1.8 s.
Largest content (LCP) got 27% faster for real visitors
-27%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 2.1 s to 1.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Images and page weight
Page weight: 10.4 MB in 174 requests
10.4 MBYour homepage downloads 10.4 MB in 174 requests on a phone: images 8.3 MB (80), scripts 1.9 MB (44) and stylesheets 129 KiB (14). Under 2 MB keeps phones on slow connections fast.
About 2.9 g of CO₂ per visit
2.95 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.95 g of CO₂e: 353.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
19 buttons without a name
19 buttons have no accessible name, so screen readers announce just “button”.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
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.
5 tap targets too small
5 tap targets are too small or too close together to hit reliably with a finger.
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.
Headings skip levels
Headings skip levels (h3 → h5 and h2 → h4), which makes the page harder to scan with a screen reader.
Elements with role="none" or role="presentation" have conflicts
Elements with role="none" or role="presentation" have conflicts (2 elements).
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (3 elements).
2 checks passed
Every image has alt text
All 54 images in the HTML carry an alt attribute.
5 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 7 WCAG 2.2 A/AA and best-practice rules on the phone render: 5 passed and 2 failed. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (24 characters)
Your title is only 24 characters: “Alinutri Nutrição Animal”. Between 30 and 65 characters leaves room to say what you do and for whom.
Meta description is short (25 characters)
Your meta description is only 25 characters: “Indústria de Ração Animal”. 70 to 160 characters is enough to sell the click.
86 internal links, 13 external
The homepage links to 86 pages on alinutri.ind.br and 13 external pages.
6 checks passed
One H1 headline
Your main headline reads: “Alinutri Nutrição Animal”.
Canonical URL set
The canonical URL is https://alinutri.ind.br/.
Structured data in place
Structured data found: Article, BreadcrumbList, Organization, Person and PetStore.
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 and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at https://alinutri.ind.br/sitemap.xml.
AI search readiness
No llms.txt
There is no https://alinutri.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.
Organization data: 5 of 6 facts
Your Organization JSON-LD gives name, url, logo, description and contact details; sameAs (social profiles) would complete it.
Other pages
6 pages without a meta description
https://alinutri.ind.br/blog, https://alinutri.ind.br/contato, https://alinutri.ind.br/sobre-nos, https://alinutri.ind.br/produtos/pet, https://alinutri.ind.br/marcas and https://alinutri.ind.br/negocie have no meta description, so Google writes the search snippet from whatever text it finds.
5 pages without an H1
https://alinutri.ind.br/trabalhe, https://alinutri.ind.br/marcas, https://alinutri.ind.br/marcas/longlife, https://alinutri.ind.br/marcas/ammy and https://alinutri.ind.br/marcas/nature have no <h1> headline, so visitors and search engines get no clear main topic.
1 page with very little text
https://alinutri.ind.br/negocie has 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.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 34 found) and read each the way a search engine does.
5 checks passed
Linked pages load
14 pages of 15 loaded without an error (the rest turned automated requests away).
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Titles are unique
Every page we checked has its own title.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 14 pages that loaded have a <title>.
Best practices
3 third-party cookies
3 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
2 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
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 phone number on the homepage
A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.
A 16-field form
Your longest form asks for 16 fields (0 required). Every extra field lowers completion.
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.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
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 481 words of copy
The homepage carries about 481 words of visible text.
3 checks passed
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics and Cloudflare Web Analytics.
Opening hours shown
Your opening hours are on the homepage.
LocalBusiness structured data
Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.
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.
5 other companies contacted
Loading the homepage contacts 5 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 alinutri.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
- CMS
- WordPress
- Framework
- jQuery
- Analytics
- Google Analytics | Google Tag Manager
- Hosting
- Cloudflare
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 alinutri.ind.br, including 21 speed issues, 2 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.