proteautobrasil.com.br website review

About 995 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.5 s faster on a phone.

6 images could be 395 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.1 s faster on a phone.

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

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

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

About 797 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 470 ms faster on a phone.

8 third-party services load with your homepage (Google Tag Manager, Facebook and Clarity and others), adding 1.4 MB and 897 ms of main-thread time.

16 files block the first paint until they finish downloading. Deferring or inlining them could save about 900 ms.

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

Polyfills for old browsers add 39 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 300 ms faster on a phone.

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

Facebook costs a phone 232 ms of main-thread work and 367 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.

Vimeo costs a phone 34 ms of main-thread work and 526 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.

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

8 KiB could be saved by minifying CSS.

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.

4 KiB could be saved by minifying JavaScript.

Your largest element takes 15.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Faça uma simulação Saiba qual seria o valor para sua proteç…”.

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

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

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

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

26 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-17, real Chrome visitors' largest content (lcp) went from 2.7 s to 2.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 10.3 MB in 237 requests on a phone: other files 4.3 MB (63), scripts 3.0 MB (69) and images 1.5 MB (59). Under 2 MB keeps phones on slow connections fast.

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

7 images (377 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.

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

1 button has no accessible name, so screen readers announce just “button”.

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

17 tap targets are too small or too close together to hit reliably with a finger.

2 frames have no title, so screen-reader users cannot tell what they contain.

1 image has no alt text, which hurts accessibility and image search.

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

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

Headings skip levels (h2 → h5, h2 → h5 and h2 → h5), which makes the page harder to scan with a screen reader.

There is no <h1>, so neither visitors nor Google get a clear main headline.

Your title is only 29 characters: “Proteauto - Proteção Veicular”. Between 30 and 65 characters leaves room to say what you do and for whom.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

Your meta description is only 51 characters: “Associação dos proprietários de veículos do Brasil.”. 70 to 160 characters is enough to sell the click.

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

No XML sitemap at https://proteautobrasil.com.br/sitemap.xml, so Google discovers your pages only by following links.

There is no robots.txt at proteautobrasil.com.br/robots.txt, the first file search crawlers ask for.

2 links have no real href, so search engines can't follow them.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 83 pages on proteautobrasil.com.br and 17 external pages.

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.

There is no https://proteautobrasil.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://proteautobrasil.com.br/simule-agora.php and https://proteautobrasil.com.br/a-empresa.php all use the title “Proteauto - Proteção Veicular”. Search engines can't tell which page to show for a search, so each competes with the others.

https://proteautobrasil.com.br/simule-agora.php, https://proteautobrasil.com.br/a-empresa.php, https://proteautobrasil.com.br/beneficios/avaliacao.php, https://proteautobrasil.com.br/beneficios/cobertura-completa.php, https://proteautobrasil.com.br/beneficios/danos-a-terceiros.php and https://proteautobrasil.com.br/beneficios/rastreador.php and 8 others use the same meta description. A description written for each page earns more clicks.

https://proteautobrasil.com.br/simule-agora.php has no <h1> headline, so visitors and search engines get no clear main topic.

We fetched 15 pages linked from your homepage (of 22 found) and read each the way a search engine does.

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

2 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

3 errors were logged to the browser console while the page loaded, for example “Cannot read properties of null (reading 'style')”.

2 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

Chrome logged issues while loading the page (“Cookie”).

Large scripts ship without source maps.

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.

Social proof on the homepage: 1 testimonial or review block. Pairing it with named testimonials or customer logos makes it far more convincing.

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

There is no form on the homepage, so every lead has to click through to another page first.

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

The homepage carries about 623 words of visible text.

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

Opening the homepage sets 11 cookies, 2 of them by other companies (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 34 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.