Website review, no card needed
brudden.com.br website review
Visit site (opens in a new tab)Reviewed 1 November 202642 issues · 82 checks
This review found 42 issues worth fixing on brudden.com.br, 19 of them high impact, across 82 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
64DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 2.5 s |
| May 16, 2026 | 2.5 s |
| May 23, 2026 | 2.5 s |
| May 30, 2026 | 2.6 s |
| Jun 6, 2026 | 2.6 s |
| Jun 13, 2026 | 2.6 s |
| Jun 20, 2026 | 2.6 s |
| Jun 27, 2026 | 2.5 s |
| Jul 4, 2026 | 2.6 s |
| Jul 11, 2026 | 2.6 s |
| Jul 18, 2026 | 2.6 s |
| Jul 25, 2026 | 2.7 s |
| Aug 1, 2026 | 2.6 s |
| Aug 8, 2026 | 2.6 s |
| Aug 15, 2026 | 2.5 s |
| Aug 22, 2026 | 2.5 s |
| Aug 29, 2026 | 2.6 s |
| Sep 5, 2026 | 2.5 s |
| Sep 12, 2026 | 2.6 s |
| Sep 19, 2026 | 2.5 s |
| Sep 26, 2026 | 2.5 s |
| Oct 3, 2026 | 2.5 s |
| Oct 10, 2026 | 2.5 s |
| Oct 17, 2026 | 2.6 s |
| Oct 24, 2026 | 2.5 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 165 ms |
| May 16, 2026 | 166 ms |
| May 23, 2026 | 166 ms |
| May 30, 2026 | 171 ms |
| Jun 6, 2026 | 172 ms |
| Jun 13, 2026 | 173 ms |
| Jun 20, 2026 | 171 ms |
| Jun 27, 2026 | 164 ms |
| Jul 4, 2026 | 165 ms |
| Jul 11, 2026 | 162 ms |
| Jul 18, 2026 | 164 ms |
| Jul 25, 2026 | 167 ms |
| Aug 1, 2026 | 169 ms |
| Aug 8, 2026 | 168 ms |
| Aug 15, 2026 | 164 ms |
| Aug 22, 2026 | 163 ms |
| Aug 29, 2026 | 167 ms |
| Sep 5, 2026 | 171 ms |
| Sep 12, 2026 | 173 ms |
| Sep 19, 2026 | 173 ms |
| Sep 26, 2026 | 170 ms |
| Oct 3, 2026 | 167 ms |
| Oct 10, 2026 | 172 ms |
| Oct 17, 2026 | 178 ms |
| Oct 24, 2026 | 190 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
Speed
Use efficient cache lifetimes
5.3 s · 8.6 MB54 files are served with short cache lifetimes, so returning visitors download them again (8.6 MB).
Improve image delivery
4.0 s · 8.2 MB22 images could be 8.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 4.0 s faster on a phone.
Reduce unused JavaScript
3.0 s · 835 KiBAbout 835 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.0 s faster on a phone.
Render-blocking requests
1.7 s10 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.7 s.
Mobile performance score: 39
39/100Your mobile performance score is 39. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Reduce unused CSS
900 ms · 185 KiBAbout 185 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 900 ms faster on a phone.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Facebook and Google CDN and others), adding 1.5 MB and 688 ms of main-thread time.
Font display
650 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 650 ms).
Google Tag Manager adds 441 ms
441 msGoogle Tag Manager costs a phone 441 ms of main-thread work and 950 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 CDN adds 72 ms
72 msGoogle CDN costs a phone 72 ms of main-thread work and 348 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.
8 long tasks on the main thread
8 long tasks block the main thread while loading, the longest for 126 ms. During a long task the page ignores taps.
Legacy JavaScript
23 KiBPolyfills for old browsers add 23 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.
Minify JavaScript
3 KiB3 KiB could be saved by minifying JavaScript.
2 checks passed
Main-thread work: 1.4 s
A phone's processor spends 1.4 s on main-thread work while loading, 681 ms of it running JavaScript. That is comfortably low.
Server response: 2 ms
2 msYour server sent the HTML in 2 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.52
0.52For real visitors the layout shifts by 0.52 (75th percentile). Good is under 0.1.
Largest Contentful Paint: 31.2 s
31.2 sYour largest element takes 31.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: 32.8 s
32.8 sThe page becomes fully interactive after 32.8 s. Good is under 3.8 s.
Speed Index: 15.3 s
15.3 sVisually, the page fills in at 15.3 s (Speed Index). Good is under 3.4 s.
Cumulative Layout Shift: 0.7
0.7The layout shifts by 0.7 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Real-user LCP: 2.8 s
2.8 sReal visitors wait 2.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.
23 images without width and height
23 images have no width and height attributes, so the layout jumps as each one loads.
First Contentful Paint: 1.8 s
1.8 sThe first text or image appears after 1.8 s on a phone. Good is under 1.8 s.
Tap response (INP) got 11% slower for real visitors
+11%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 165 ms to 190 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+2%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 2.5 s to 2.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
4 checks passed
Real-user INP: 164 ms
164 msReal visitors wait 164 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 1.5 s
1.5 sReal visitors see the first content after 1.5 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 644 ms
644 msReal visitors wait 644 ms for your server to start answering (75th percentile). Good is under 800 ms.
Total Blocking Time: 158 ms
158 msScripts block the page for only 158 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 13.8 MB in 80 requests
13.8 MBYour homepage downloads 13.8 MB in 80 requests on a phone: images 11.9 MB (32), scripts 1.6 MB (22) and stylesheets 201 KiB (10). Under 2 MB keeps phones on slow connections fast.
7 images over 500 KB
7 images weigh 5.4 MB together. On a phone connection a single image that size takes seconds.
13 images far larger than shown
2.0 MB13 images are downloaded at several times the size a phone draws them, for example motobomba.png at 1,080 px wide, shown at 200 px. Resized copies would save about 2.0 MB.
6 images in older formats
6 images (4.8 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.
12 images below the first screen load straight away
12 images further down the page (2.6 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 3.9 g of CO₂ per visit
3.92 gBy the Sustainable Web Design model, a visit to your homepage emits about 3.92 g of CO₂e: 470.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
2 buttons without a name
2 buttons have no accessible name, so screen readers announce just “button”.
29 images without alt text
29 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (6 elements)
All page content should be contained by landmarks: 6 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.
8 links without text
8 visible links have no text or label, so screen readers cannot say where they go.
6 form fields without a label
6 form fields have no label, so screen readers announce an empty box and autofill guesses.
1 checks passed
41 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 46 WCAG 2.2 A/AA and best-practice rules on the phone render: 41 passed and 5 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (7 characters)
Your title is only 7 characters: “Brudden”. Between 30 and 65 characters leaves room to say what you do and for whom.
14 H1 headlines
There are 14 <h1> headlines (“Trator Cortador de Grama TCG546A”, “Dosador D200 Li” and “Dosador D50T Li”). One clear main headline is easier for people and search engines.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
86 internal links, 17 external
The homepage links to 86 pages on brudden.com.br and 17 external pages.
5 checks passed
Meta description: 144 characters
Your meta description is 144 characters: “Fabricante de equipamentos agrícolas e jardinagem com alto padrão de qualidade, tornando-se referência de comprometimen…”.
Canonical URL set
The canonical URL is https://brudden.com.br/.
Structured data in place
Structured data found: BreadcrumbList, CollectionPage and WebSite.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at http://brudden.com.br/sitemap_index.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://brudden.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.
Opted out of AI training for 5 crawlers
robots.txt blocks GPTBot, ClaudeBot, Google-Extended, Applebot-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.
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 (615 words), so crawlers that don't run JavaScript still read it.
Other pages
15 pages without a meta description
https://brudden.com.br/sobre-nos, https://brudden.com.br/aparadores-de-cerca-viva, https://brudden.com.br/atomizadores, https://brudden.com.br/cortadores-de-grama, https://brudden.com.br/derricadores-de-cafe and https://brudden.com.br/dosadores and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.
2 pages slow to respond
https://brudden.com.br/podadores-de-altura and https://brudden.com.br/pulverizadores-a-bateria took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 42 found) and read each the way a search engine does.
6 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.
Titles are unique
Every page we checked has its own title.
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 15 pages that loaded have a <title>.
Best practices
14 small tap targets
14 of 39 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
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 404 ()”.
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 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 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 416 words of copy
The homepage carries about 416 words of visible text.
2 checks passed
6 short forms
6 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics and Cloudflare Web Analytics.
Privacy and tracking
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager 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.
4 cookies set on arrival
4Opening the homepage sets 4 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.
13 other companies contacted
Loading the homepage contacts 13 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 brudden.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
- 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 42 issues on brudden.com.br, including 19 speed issues, 3 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.