kainos.com.br website review

173 files are served with short cache lifetimes, so returning visitors download them again (11.0 MB).

60 files block the first paint until they finish downloading. Deferring or inlining them could save about 16.4 s.

About 1.5 MB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 8.8 s faster on a phone.

About 1.3 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.4 s faster on a phone.

Your mobile performance score is 39. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

A phone's processor spends 7.0 s on main-thread work while loading, 2.9 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

8 third-party services load with your homepage (Google CDN, Google Tag Manager and Other Google APIs/SDKs and others), adding 1.6 MB and 1.2 s of main-thread time.

Google CDN costs a phone 723 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.

17 images could be 691 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

63 KiB could be saved by minifying CSS.

Google Tag Manager costs a phone 280 ms of main-thread work and 304 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.

45 KiB could be saved by minifying JavaScript.

18 long tasks block the main thread while loading, the longest for 228 ms. During a long task the page ignores taps.

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 200 ms).

The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

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 visitors see the first content after 6.1 s (75th percentile). Good is under 1.8 s.

The first text or image appears after 18.0 s on a phone. Good is under 1.8 s.

Your largest element takes 34.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “CONHEÇA NOSSOS SERVIÇOS RELACIONAMENTO COM O CLIENTE INFRAE…”.

Visually, the page fills in at 23.2 s (Speed Index). Good is under 3.4 s.

The page becomes fully interactive after 44.2 s. Good is under 3.8 s.

Scripts block taps and scrolling for 620 ms in total while the page loads. Good is under 200 ms.

11 images have no width and height attributes, so the layout jumps as each one loads.

Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 195 ms to 189 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 13.1 MB in 211 requests on a phone: media 3.7 MB (3), scripts 3.1 MB (66) and images 2.9 MB (56). Under 2 MB keeps phones on slow connections fast.

09.-DIGITAL-05-Por-que-a-YOU-Tecnologia-ARTIGO-scaled.png weighs 1.2 MB. On a phone connection a single image that size takes seconds.

7 images are downloaded at several times the size a phone draws them, for example image31.png at 390 px wide, shown at 100 px. Resized copies would save about 576 KiB.

12 images (2.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.

7 images further down the page (672 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

By the Sustainable Web Design model, a visit to your homepage emits about 3.71 g of CO₂e: 445.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

3 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

All page content should be contained by landmarks: 7 elements on the page fail this check, rated moderate by axe-core.

The skip-link target should exist and be focusable: 1 element on the page fails this check, rated moderate by axe-core.

5 visible links have no text or label, so screen readers cannot say where they go.

1 form field has no label, so screen readers announce an empty box and autofill guesses.

Your title is only 18 characters: “Home - YOU.BPOTECH”. Between 30 and 65 characters leaves room to say what you do and for whom.

There are 6 <h1> headlines (“CONECTANDO”, “EXPERIÊNCIAS” and “COM VOCÊ”). One clear main headline is easier for people and search engines.

The homepage links to 95 pages on kainos.com.br and 13 external pages.

There is no https://youbpotech.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.

https://youbpotech.com.br/quem-somos, https://youbpotech.com.br/servicos, https://youbpotech.com.br/conteudo, https://youbpotech.com.br/release, https://youbpotech.com.br/contato and https://youbpotech.com.br/por-que-a-you-e-a-melhor-escolha and 5 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://youbpotech.com.br/quem-somos, https://youbpotech.com.br/release, https://youbpotech.com.br/contato and https://youbpotech.com.br/politica-de-privacidade have no <h1> headline, so visitors and search engines get no clear main topic.

We fetched 11 pages linked from your homepage and read each the way a search engine does.

5 of 22 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

3 errors were logged to the browser console while the page loaded, for example “Unrecognized Content-Security-Policy directive 'prefetch-src'.”.

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

Chrome logged issues while loading the page (“Content security policy”).

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

Your homepage shows a map but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

The homepage has only about 117 words of visible text; thin pages give Google and first-time buyers little to go on.

The homepage shows no opening hours. If customers visit or call, show when.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Google Tag Manager (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.

Opening the homepage sets 5 cookies (measured from a US location before any click).

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.

Loading the homepage contacts 17 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.