Website review, no card needed
casadopicapau.com.br website review
Visit site (opens in a new tab)Reviewed 28 October 202655 issues · 92 checks
This review found 55 issues worth fixing on casadopicapau.com.br, 22 of them high impact, across 92 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
58FClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 3.9 s |
| May 16, 2026 | 4.0 s |
| May 23, 2026 | 4.0 s |
| May 30, 2026 | 4.0 s |
| Jun 6, 2026 | 4.1 s |
| Jun 13, 2026 | 4.3 s |
| Jun 20, 2026 | 4.4 s |
| Jun 27, 2026 | 4.5 s |
| Jul 4, 2026 | 4.5 s |
| Jul 11, 2026 | 4.5 s |
| Jul 18, 2026 | 4.6 s |
| Jul 25, 2026 | 4.6 s |
| Aug 1, 2026 | 4.6 s |
| Aug 8, 2026 | 4.6 s |
| Aug 15, 2026 | 4.6 s |
| Aug 22, 2026 | 4.6 s |
| Aug 29, 2026 | 4.6 s |
| Sep 5, 2026 | 4.7 s |
| Sep 12, 2026 | 4.6 s |
| Sep 19, 2026 | 4.6 s |
| Sep 26, 2026 | 4.6 s |
| Oct 3, 2026 | 4.6 s |
| Oct 10, 2026 | 4.7 s |
| Oct 17, 2026 | 4.9 s |
| Oct 24, 2026 | 4.9 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 363 ms |
| May 16, 2026 | 363 ms |
| May 23, 2026 | 366 ms |
| May 30, 2026 | 370 ms |
| Jun 6, 2026 | 374 ms |
| Jun 13, 2026 | 371 ms |
| Jun 20, 2026 | 369 ms |
| Jun 27, 2026 | 372 ms |
| Jul 4, 2026 | 374 ms |
| Jul 11, 2026 | 379 ms |
| Jul 18, 2026 | 379 ms |
| Jul 25, 2026 | 382 ms |
| Aug 1, 2026 | 383 ms |
| Aug 8, 2026 | 390 ms |
| Aug 15, 2026 | 395 ms |
| Aug 22, 2026 | 399 ms |
| Aug 29, 2026 | 403 ms |
| Sep 5, 2026 | 395 ms |
| Sep 12, 2026 | 393 ms |
| Sep 19, 2026 | 386 ms |
| Sep 26, 2026 | 386 ms |
| Oct 3, 2026 | 393 ms |
| Oct 10, 2026 | 394 ms |
| Oct 17, 2026 | 400 ms |
| Oct 24, 2026 | 411 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.3 s
2.7 s
4.0 s
5.3 s
6.7 s
8.0 s
9.4 s
10.7 s
Speed
Reduce unused JavaScript
1.6 s · 1.8 MBAbout 1.8 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.6 s faster on a phone.
Improve image delivery
1.6 s · 619 KiB12 images could be 619 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.6 s faster on a phone.
Mobile performance score: 32
32/100Your mobile performance score is 32 (desktop: 48). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 5.2 s
A phone's processor spends 5.2 s on main-thread work while loading, 3.2 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 (Google CDN, Google Tag Manager and vtexassets.com and others), adding 6.2 MB and 2.2 s of main-thread time.
Use efficient cache lifetimes
950 ms · 783 KiB19 files are served with short cache lifetimes, so returning visitors download them again (783 KiB).
Google CDN adds 624 ms
624 msGoogle CDN costs a phone 624 ms of main-thread work and 2.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.
Document request latency
700 msThe HTML itself could arrive about 700 ms sooner: redirects, a slow server response or missing compression delay everything after it.
Google Tag Manager adds 605 ms
605 msGoogle Tag Manager costs a phone 605 ms of main-thread work and 874 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 initial server response time
682 msReduce initial server response time. Google estimates savings of 682 ms on a phone.
vtexassets.com adds 462 ms
462 msvtexassets.com costs a phone 462 ms of main-thread work and 1.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.
Render-blocking requests
450 ms1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 450 ms.
Reduce unused CSS
300 ms · 109 KiBAbout 109 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.
Legacy JavaScript
350 ms · 57 KiBPolyfills for old browsers add 57 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 350 ms faster on a phone.
1,646 HTML elements
The page has 1,646 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Server response: 782 ms
782 msYour server takes 782 ms to send the HTML. Google recommends under 600 ms; everything else waits for it.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 195 ms. During a long task the page ignores taps.
Minify JavaScript
150 ms · 22 KiB22 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.
Minify CSS
4 KiB4 KiB could be saved by minifying CSS.
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.28
0.28For real visitors the layout shifts by 0.28 (75th percentile). Good is under 0.1.
Real-user FCP: 3.3 s
3.3 sReal visitors see the first content after 3.3 s (75th percentile). Good is under 1.8 s.
Largest Contentful Paint: 11.6 s
11.6 sYour largest element takes 11.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Maratona STIHL: Potência com Preço Baixo”.
Time to Interactive: 34.0 s
34.0 sThe page becomes fully interactive after 34.0 s. Good is under 3.8 s.
Speed Index: 14.7 s
14.7 sVisually, the page fills in at 14.7 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 822 ms
822 msScripts block taps and scrolling for 822 ms in total while the page loads. Good is under 200 ms.
First Contentful Paint: 3.2 s
3.2 sThe first text or image appears after 3.2 s on a phone. Good is under 1.8 s.
Real-user LCP: 3.8 s
3.8 sReal visitors wait 3.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 316 ms
316 msReal visitors wait 316 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Largest content (LCP) got 24% slower for real visitors
+24%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 3.9 s to 4.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user TTFB: 1.5 s
1.5 sReal visitors wait 1.5 s for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0.183
0.183The layout shifts by 0.183 while loading, so content jumps under the reader's thumb. Good is under 0.1.
23 images without width and height
23 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-24, real Chrome visitors' tap response (inp) went from 363 ms to 411 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Images and page weight
Page weight: 5.9 MB in 177 requests
5.9 MBYour homepage downloads 5.9 MB in 177 requests on a phone: scripts 3.8 MB (72), images 733 KiB (43) and other files 732 KiB (51). Under 2 MB keeps phones on slow connections fast.
9 images far larger than shown
542 KiB9 images are downloaded at several times the size a phone draws them, for example whatsappsticky___e34cde4badf241507adb57825cc8cde9.png at 1,527 px wide, shown at 98 px. Resized copies would save about 542 KiB.
About 1.7 g of CO₂ per visit
1.66 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.66 g of CO₂e: 199.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Accessibility
2 buttons without a name
2 buttons have no accessible name, so screen readers announce just “button”.
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.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
Orphan list items
Some list items are not inside a list.
1 tap target too small
1 tap target is too small or too close together to hit reliably with a finger.
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 (8 elements)
All page content should be contained by landmarks: 8 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 (2 elements)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 elements on the page fail this check, rated moderate by axe-core.
10 links without text
10 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.
1 checks passed
44 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 53 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 9 failed. 5 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
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.
One H1 headline
Your <h1> is empty.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
33 internal links, 12 external
The homepage links to 33 pages on casadopicapau.com.br and 12 external pages.
5 checks passed
Meta description: 145 characters
Your meta description is 145 characters: “Soluções em climatização e refrigeração para casa e negócio. Equipamentos confiáveis, ótimo custo-benefício e entrega r…”.
Title: 60 characters
Your title is a healthy 60 characters: “Casa do Pica-Pau: Sua Loja de Ferramentas e Eletrodomésticos”.
Canonical URL set
The canonical URL is https://www.casadopicapau.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.casadopicapau.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.casadopicapau.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 (233 words), so crawlers that don't run JavaScript still read it.
Other pages
3 linked pages hidden from search
https://www.casadopicapau.com.br/426, https://www.casadopicapau.com.br/425 and https://www.casadopicapau.com.br/430 are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.
3 pages share a meta description
https://www.casadopicapau.com.br/426, https://www.casadopicapau.com.br/425 and https://www.casadopicapau.com.br/430 use the same meta description. A description written for each page earns more clicks.
7 pages slow to respond
https://www.casadopicapau.com.br/425, https://www.casadopicapau.com.br/maquinas-e-ferramentas/ferramentas-eletricas, https://www.casadopicapau.com.br/maquinas-e-ferramentas/geradores, https://www.casadopicapau.com.br/churrasco-e-acessorios, https://www.casadopicapau.com.br/fazenda-e-jardim and https://www.casadopicapau.com.br/institucional/sobre-a-empresa and 1 other took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 24 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.
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 an H1
Each page we checked has a main headline.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
32 small tap targets
32 of 61 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
4 JavaScript errors while loading
4 errors were logged to the browser console while the page loaded, for example “Unexpected identifier 'Affiliate'”.
4 distorted images
4 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.
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 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 263 words of copy
The homepage carries about 263 words of visible text.
3 checks passed
1 short form
A short form (3 fields at most) is right on the homepage, asking for an email.
Social proof on the page
Social proof on the homepage: 2 customer or partner logos and 5 trust badges.
Analytics in place
Analytics detected: Google Tag Manager, Meta Pixel, Hotjar and TikTok Pixel.
Privacy and tracking
7 trackers load before any consent
7Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and Meta Pixel 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.
27 cookies set on arrival
27Opening the homepage sets 27 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.
44 other companies contacted
Loading the homepage contacts 44 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 casadopicapau.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
- Analytics
- Google Tag Manager | Hotjar
- Hosting
- AWS
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 55 issues on casadopicapau.com.br, including 30 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.