Website review, no card needed
bhs.com.br website review
Visit site (opens in a new tab)Reviewed 4 November 202642 issues · 89 checks
This review found 42 issues worth fixing on bhs.com.br, 21 of them high impact, across 89 checks. The most urgent: render-blocking requests. 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
74CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Jul 4, 2026 | 2.0 s |
| Jul 11, 2026 | 1.9 s |
| Jul 18, 2026 | 2.9 s |
| Jul 25, 2026 | 3.3 s |
| Aug 1, 2026 | 3.3 s |
| Aug 8, 2026 | 3.3 s |
| Aug 15, 2026 | 3.3 s |
| Aug 22, 2026 | 3.2 s |
| Aug 29, 2026 | 3.2 s |
| Sep 5, 2026 | 3.3 s |
| Sep 12, 2026 | 2.6 s |
| Sep 19, 2026 | 2.3 s |
| Sep 26, 2026 | 2.6 s |
| Oct 3, 2026 | 2.5 s |
| Oct 10, 2026 | 2.5 s |
| Oct 17, 2026 | 2.4 s |
| Oct 24, 2026 | 2.3 s |
| Oct 31, 2026 | 2.3 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Jul 11, 2026 | 124 ms |
| Jul 18, 2026 | 197 ms |
| Jul 25, 2026 | 243 ms |
| Aug 1, 2026 | 269 ms |
| Aug 8, 2026 | 283 ms |
| Aug 15, 2026 | 303 ms |
| Aug 22, 2026 | 298 ms |
| Aug 29, 2026 | 291 ms |
| Sep 5, 2026 | 291 ms |
| Sep 12, 2026 | 239 ms |
| Sep 19, 2026 | 170 ms |
| Sep 26, 2026 | 198 ms |
| Oct 3, 2026 | 220 ms |
| Oct 10, 2026 | 226 ms |
| Oct 17, 2026 | 233 ms |
| Oct 24, 2026 | 239 ms |
| Oct 31, 2026 | 221 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
Render-blocking requests
5.3 s58 files block the first paint until they finish downloading. Deferring or inlining them could save about 5.3 s.
Reduce unused CSS
1.8 s · 401 KiBAbout 401 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.8 s faster on a phone.
Mobile performance score: 37
37/100Your mobile performance score is 37. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 5.0 s
A phone's processor spends 5.0 s on main-thread work while loading, 2.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Improve image delivery
2.1 MB9 images could be 2.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, goadopt.io and leadster.com.br and others), adding 1.4 MB and 1.6 s of main-thread time.
Reduce unused JavaScript
450 ms · 688 KiBAbout 688 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 450 ms faster on a phone.
Google Tag Manager adds 930 ms
930 msGoogle Tag Manager costs a phone 930 ms of main-thread work and 818 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
354 KiB8 files are served with short cache lifetimes, so returning visitors download them again (354 KiB).
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 326 ms. During a long task the page ignores taps.
goadopt.io adds 253 ms
253 msgoadopt.io costs a phone 253 ms of main-thread work and 263 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.
Minify CSS
130 ms · 30 KiB30 KiB could be saved by minifying CSS.
Legacy JavaScript
50 ms · 8 KiBPolyfills for old browsers add 8 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 50 ms faster on a phone.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Minify JavaScript
17 KiB17 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.
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: 5 ms
5 msYour server sent the HTML in 5 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: 20.7 s
20.7 sThe page becomes fully interactive after 20.7 s. Good is under 3.8 s.
First Contentful Paint: 5.9 s
5.9 sThe first text or image appears after 5.9 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 5.9 s
5.9 sYour largest element takes 5.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Tecnologia segura para empresas que precisam crescer.”. Most of its time is element render delay (2.4 s).
Speed Index: 8.3 s
8.3 sVisually, the page fills in at 8.3 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 1.2 s
1.2 sScripts block taps and scrolling for 1.2 s in total while the page loads. Good is under 200 ms.
Real-user INP: 219 ms
219 msReal visitors wait 219 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 43% slower for real visitors
+43%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 124 ms to 221 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 18% slower for real visitors
+18%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.0 s to 2.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 checks passed
Real-user LCP: 2.2 s
2.2 sReal visitors wait 2.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.04
0.04For real visitors the layout shifts by 0.04 (75th percentile). Good is under 0.1.
Real-user FCP: 1.8 s
1.8 sReal visitors see the first content after 1.8 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 568 ms
568 msReal visitors wait 568 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0.002
0.002The layout barely moves while loading (CLS 0.002, good is under 0.1).
Images and page weight
Page weight: 5.6 MB in 141 requests
5.6 MBYour homepage downloads 5.6 MB in 141 requests on a phone: images 3.2 MB (26), scripts 1.7 MB (46) and stylesheets 495 KiB (40). Under 2 MB keeps phones on slow connections fast.
1 image over 500 KB
svc-service-desk-suporte-ti-hero-1024x546.png weighs 522 KiB. On a phone connection a single image that size takes seconds.
1 image far larger than shown
49 KiB1 image is downloaded at several times the size a phone draws it, for example hero-tablet.png at 1,280 px wide, shown at 390 px. Resized copies would save about 49 KiB.
3 images in older formats
3 images (109 KiB) 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.
2 images below the first screen load straight away
2 images further down the page (99 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 1.6 g of CO₂ per visit
1.60 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.60 g of CO₂e: 191.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
Certain ARIA roles must contain particular children (2 elements)
Certain ARIA roles must contain particular children: 2 elements on the page fail this check, rated critical by axe-core.
Unlabelled dropdowns
2 dropdowns have no label.
7 text elements with low contrast
7 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
4 tap targets too small
4 tap targets are too small or too close together to hit reliably with a finger.
Links look like plain text
3 links inside paragraphs rely on colour alone to stand out.
Scrollable region must have keyboard access (1 element)
Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.
All page content should be contained by landmarks (24 elements)
All page content should be contained by landmarks: 24 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 (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.
9 form fields without a label
9 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 (1 element)
Alternative text of images should not be repeated as text: 1 element on the page fails this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 60 images in the HTML carry an alt attribute.
46 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 56 WCAG 2.2 A/AA and best-practice rules on the phone render: 46 passed and 10 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
100 internal links, 11 external
The homepage links to 100 pages on bhs.com.br and 11 external pages.
7 checks passed
Meta description: 126 characters
Your meta description is 126 characters: “Transforme sua operação de TI com soluções BHS em nuvem, cibersegurança, service desk, field services e tecnologias Mic…”.
One H1 headline
Your main headline reads: “Tecnologia segura para empresas que precisam crescer.”.
Title: 51 characters
Your title is a healthy 51 characters: “BHS | Soluções em Nuvem, Segurança e Serviços de TI”.
Canonical URL set
The canonical URL is https://www.bhs.com.br/.
Structured data in place
Structured data found: BreadcrumbList, CollectionPage, Organization 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 https://bhs.com.br/sitemap_index.xml.
AI search readiness
4 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: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (780 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://bhs.com.br/llms.txt (4 KiB, 44 links), a plain-text guide to the site for AI tools.
Other pages
1 linked page is broken
Your homepage links to https://bhs.com.br/services/compliance-e-assessment, which answers with an error. Visitors hit a dead end and search engines drop it.
14 pages point its canonical at the homepage
https://bhs.com.br/services/gestao-de-nuvem, https://bhs.com.br/services/service-desk, https://bhs.com.br/services/field-services, https://bhs.com.br/services/licenciamento-azure, https://bhs.com.br/services/licenciamento-aws and https://bhs.com.br/services/licenciamento-microsoft-365 and 8 others declare the homepage as their canonical URL, which tells Google they are copies of the homepage and keeps them out of search results. A site-wide template setting usually causes this.
15 pages share a title
/, https://bhs.com.br/services/gestao-de-nuvem, https://bhs.com.br/services/service-desk, https://bhs.com.br/services/field-services, https://bhs.com.br/services/licenciamento-azure and https://bhs.com.br/services/licenciamento-aws and 9 others all use the title “BHS | Soluções em Nuvem, Segurança e Serviços de TI”. Search engines can't tell which page to show for a search, so each competes with the others.
14 pages share a meta description
https://bhs.com.br/services/gestao-de-nuvem, https://bhs.com.br/services/service-desk, https://bhs.com.br/services/field-services, https://bhs.com.br/services/licenciamento-azure, https://bhs.com.br/services/licenciamento-aws and https://bhs.com.br/services/licenciamento-microsoft-365 and 8 others use the same meta description. A description written for each page earns more clicks.
4 pages slow to respond
https://bhs.com.br/services/soc-24x7, https://bhs.com.br/services/agentes-de-ia, https://bhs.com.br/services/inteligencia-artificial and https://bhs.com.br/services/alocacao-de-especialistas took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 54 found) and read each the way a search engine does.
4 checks passed
Every page has a meta description
All 14 pages that loaded have a meta description.
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 14 pages that loaded have a <title>.
Best practices
7 small tap targets
7 of 12 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 “Identifier 'registerAllyAction' has already been declared”.
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.
A 10-field form
Your longest form asks for 10 fields (8 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 544 words of copy
The homepage carries about 544 words of visible text.
4 checks passed
1 call to action
The homepage has 1 call to action, for example “Start search”.
Social proof on the page
Social proof on the homepage: 24 customer or partner logos and 1 trust badge.
Analytics in place
Analytics detected: Google Tag Manager and Microsoft Clarity.
Direct contact links
Visitors can reach you directly: 1 phone link and 0 email links.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, LinkedIn Insight 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.
24 other companies contacted
Loading the homepage contacts 24 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 bhs.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 Tag Manager | Microsoft Clarity
- Hosting
- WP Engine
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 bhs.com.br, including 19 speed issues, 1 SEO issue and 2 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.