Website review, no card needed
condor.ind.br website review
Visit site (opens in a new tab)Reviewed 28 October 202647 issues · 86 checks
This review found 47 issues worth fixing on condor.ind.br, 15 of them high impact, across 86 checks. The most urgent: font display. 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
80BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Jun 6, 2026 | 1.8 s |
| Jun 13, 2026 | 1.7 s |
| Jun 20, 2026 | 1.7 s |
| Jun 27, 2026 | 1.7 s |
| Jul 4, 2026 | 1.6 s |
| Jul 11, 2026 | 1.6 s |
| Jul 18, 2026 | 1.6 s |
| Jul 25, 2026 | 1.6 s |
| Aug 1, 2026 | 1.7 s |
| Aug 8, 2026 | 1.7 s |
| Aug 15, 2026 | 1.7 s |
| Aug 22, 2026 | 1.7 s |
| Aug 29, 2026 | 2.0 s |
| Sep 5, 2026 | 2.0 s |
| Sep 12, 2026 | 2.0 s |
| Sep 19, 2026 | 2.0 s |
| Sep 26, 2026 | 1.7 s |
| Oct 3, 2026 | 1.7 s |
| Oct 10, 2026 | 1.7 s |
| Oct 17, 2026 | 1.8 s |
| Oct 24, 2026 | 1.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Jun 6, 2026 | 85 ms |
| Jun 13, 2026 | 85 ms |
| Jun 20, 2026 | 85 ms |
| Jun 27, 2026 | 88 ms |
| Jul 4, 2026 | 87 ms |
| Jul 11, 2026 | 87 ms |
| Jul 18, 2026 | 86 ms |
| Jul 25, 2026 | 84 ms |
| Aug 1, 2026 | 85 ms |
| Aug 8, 2026 | 87 ms |
| Aug 15, 2026 | 87 ms |
| Aug 22, 2026 | 88 ms |
| Aug 29, 2026 | 108 ms |
| Sep 5, 2026 | 112 ms |
| Sep 12, 2026 | 115 ms |
| Sep 19, 2026 | 114 ms |
| Sep 26, 2026 | 98 ms |
| Oct 3, 2026 | 93 ms |
| Oct 10, 2026 | 93 ms |
| Oct 17, 2026 | 93 ms |
| Oct 24, 2026 | 95 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.6 s
1.2 s
1.8 s
2.4 s
3.0 s
3.6 s
4.2 s
4.8 s
Speed
Font display
1.3 sWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 1.3 s).
Render-blocking requests
1.1 s9 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.1 s.
Mobile performance score: 69
69/100Your mobile performance score is 69 (desktop: 79). Pages that score under 90 lose visitors before the first paint.
8 third-party services on the page
8 third-party services load with your homepage (gtranslate.net, Google Tag Manager and Clarity and others), adding 723 KiB and 761 ms of main-thread time.
Reduce unused CSS
510 ms · 158 KiBAbout 158 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 510 ms faster on a phone.
gtranslate.net adds 394 ms
394 msgtranslate.net costs a phone 394 ms of main-thread work and 58 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.
Use efficient cache lifetimes
300 ms · 76 KiB5 files are served with short cache lifetimes, so returning visitors download them again (76 KiB).
Improve image delivery
333 KiB8 images could be 333 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Main-thread work: 2.3 s
A phone's processor spends 2.3 s on main-thread work while loading, 1.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Google Tag Manager adds 185 ms
185 msGoogle Tag Manager costs a phone 185 ms of main-thread work and 307 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.
1,579 HTML elements
The page has 1,579 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Reduce unused JavaScript
150 ms · 192 KiBAbout 192 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.
5 long tasks on the main thread
5 long tasks block the main thread while loading, the longest for 131 ms. During a long task the page ignores taps.
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: 142 ms
142 msYour server sent the HTML in 142 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.
Time to Interactive: 14.4 s
14.4 sThe page becomes fully interactive after 14.4 s. Good is under 3.8 s.
Speed Index: 8.2 s
8.2 sVisually, the page fills in at 8.2 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 3.9 s
3.9 sThe first text or image appears after 3.9 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 4.4 s
4.4 sYour largest element takes 4.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “FROG”.
Real-user TTFB: 1.0 s
1.0 sReal visitors wait 1.0 s for your server to start answering (75th percentile). Good is under 800 ms.
12 images without width and height
12 images have no width and height attributes, so the layout jumps as each one loads.
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 85 ms to 95 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
0%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 1.8 s to 1.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
6 checks passed
Real-user LCP: 1.7 s
1.7 sReal visitors wait 1.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 89 ms
89 msReal visitors wait 89 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.09
0.09For real visitors the layout shifts by 0.09 (75th percentile). Good is under 0.1.
Real-user FCP: 1.6 s
1.6 sReal visitors see the first content after 1.6 s (75th percentile). Good is under 1.8 s.
Total Blocking Time: 105 ms
105 msScripts block the page for only 105 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0.029
0.029The layout barely moves while loading (CLS 0.029, good is under 0.1).
Images and page weight
Page weight: 3.7 MB in 153 requests
3.7 MBYour homepage downloads 3.7 MB in 153 requests on a phone: images 2.5 MB (84), scripts 561 KiB (24) and fonts 482 KiB (13). Under 2 MB keeps phones on slow connections fast.
31 images in older formats
31 images (1.5 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 1.1 g of CO₂ per visit
1.06 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.06 g of CO₂e: 127.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
27 text elements with low contrast
27 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
27 tap targets too small
27 tap targets are too small or too close together to hit reliably with a finger.
14 images without alt text
14 images have no alt text, which hurts accessibility and image search.
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.
25 links without text
25 visible links have no text or label, so screen readers cannot say where they go.
2 form fields without a label
2 form fields have no label, so screen readers announce an empty box and autofill guesses.
Alternative text of images should not be repeated as text (6 elements)
Alternative text of images should not be repeated as text: 6 elements on the page fail this check, rated minor by axe-core.
1 checks passed
40 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 48 WCAG 2.2 A/AA and best-practice rules on the phone render: 40 passed and 8 failed. 3 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 long (85 characters)
Your title is 85 characters, so Google will cut it off around 60: “Condor: Faça a vida brilhar | Produtos para pintura, limpeza, beleza e higiene bucal.”.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
22 links with vague text
22 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
194 internal links, 53 external
The homepage links to 194 pages on condor.ind.br and 53 external pages.
4 checks passed
Meta description: 134 characters
Your meta description is 134 characters: “Condor. Produtos de qualidade que transformam seu dia a dia com soluções práticas para casa, pintura, limpeza, beleza e…”.
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.
XML sitemap found
Your XML sitemap is reachable at https://www.condor.ind.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.
3 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 (754 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.condor.ind.br/llms.txt (20 KiB, 0 links), a plain-text guide to the site for AI tools.
Other pages
2 pages without a title
https://www.condor.ind.br/institucional/download/relatorio_sustentabilidade_pdf_br and https://www.condor.ind.br/institucional/download/relatorio_sustentabilidade_pdf_es have no <title>, so Google invents the link text in results.
3 pages share a title
/, https://www.condor.ind.br/contato and https://www.condor.ind.br/politica-de-privacidade all use the title “Condor: Faça a vida brilhar | Produtos para pintura, limpeza, beleza …”. Search engines can't tell which page to show for a search, so each competes with the others.
2 pages without a meta description
https://www.condor.ind.br/institucional/download/relatorio_sustentabilidade_pdf_br and https://www.condor.ind.br/institucional/download/relatorio_sustentabilidade_pdf_es have no meta description, so Google writes the search snippet from whatever text it finds.
13 pages share a meta description
https://www.condor.ind.br/area-restrita, https://www.condor.ind.br/produto/beleza, https://www.condor.ind.br/produto/limpeza, https://www.condor.ind.br/produto/higiene-bucal, https://www.condor.ind.br/produto/pintura-imobiliaria and https://www.condor.ind.br/produto/pintura-artistica and 7 others use the same meta description. A description written for each page earns more clicks.
2 pages without an H1
https://www.condor.ind.br/institucional/download/relatorio_sustentabilidade_pdf_br and https://www.condor.ind.br/institucional/download/relatorio_sustentabilidade_pdf_es have no <h1> headline, so visitors and search engines get no clear main topic.
2 pages slow to respond
https://www.condor.ind.br/produto/beleza and https://www.condor.ind.br/institucional/download/relatorio_sustentabilidade_pdf_br took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 52 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.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Best practices
38 small tap targets
38 of 102 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
33 distorted images
33 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
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.
Thin social proof
Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.
A 9-field form
Your longest form asks for 9 fields (0 required). Every extra field lowers completion.
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 325 words of copy
The homepage carries about 325 words of visible text.
2 checks passed
Analytics in place
Analytics detected: Google Analytics and Microsoft Clarity.
Direct contact links
Visitors can reach you directly: 0 phone links and 1 email link.
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 Microsoft Clarity (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.
8 cookies set on arrival
8Opening the homepage sets 8 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.
19 other companies contacted
Loading the homepage contacts 19 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 condor.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
- Framework
- Tailwind CSS
- Analytics
- Google Analytics | Microsoft Clarity
- Hosting
- Servicos de Internet SA
Company
- Founded
- 1929
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 47 issues on condor.ind.br, including 18 speed issues, 5 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.