luxcar.com.br website review

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

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

17 images could be 1.0 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.1 s faster on a phone.

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

About 220 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.5 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 34 (desktop: 58). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

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

8 third-party services load with your homepage (YouTube, Other Google APIs/SDKs and Google Tag Manager and others), adding 2.7 MB and 981 ms of main-thread time.

YouTube costs a phone 642 ms of main-thread work and 2.0 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.

15 KiB could be saved by minifying CSS.

The page has 1,742 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

33 KiB could be saved by minifying JavaScript.

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

Polyfills for old browsers add 12 KiB JavaScript that modern phones do not need.

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.

For real visitors the layout shifts by 0.61 (75th percentile). Good is under 0.1.

Your largest element takes 24.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

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

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

The layout shifts by 0.626 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

Real visitors wait 3.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.

13 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' tap response (inp) went from 119 ms to 122 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 9.9 MB in 297 requests on a phone: images 6.0 MB (194), scripts 3.1 MB (46) and stylesheets 334 KiB (27). Under 2 MB keeps phones on slow connections fast.

Nova-Home-2020-Final.png weighs 600 KiB. On a phone connection a single image that size takes seconds.

9 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.

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

1 image is downloaded at several times the size a phone draws it, for example banner_farol.jpg at 1,404 px wide, shown at 324 px. Resized copies would save about 78 KiB.

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

Active <area> elements must have alternative text: 10 elements on the page fail this check, rated critical by axe-core.

Some list items are not inside a list.

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

Some lists contain elements other than list items, which screen readers announce wrongly.

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

2 elements hidden from screen readers can still receive keyboard focus.

ARIA input fields must have an accessible name: 2 elements on the page fail this check, rated serious by axe-core.

Interactive controls must not be nested: 2 elements on the page fail this check, rated serious by axe-core.

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

35 images have no alt text, which hurts accessibility and image search.

1 element use ARIA attributes their role does not allow, which confuses screen readers.

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children. (1 element).

All page content should be contained by landmarks: 23 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 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.

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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

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

ARIA toggle fields do not have accessible names (1 element).

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

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

Elements with role="none" or role="presentation" have conflicts (1 element).

Elements with visible text labels do not have matching accessible names. (1 element).

No meta description, so Google writes its own snippet from whatever text it finds.

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

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

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

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

The homepage links to 56 pages on luxcar.com.br and 60 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://www.luxcar.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://www.luxcar.com.br/about, https://www.luxcar.com.br/produtos, https://www.luxcar.com.br/limpeza, https://www.luxcar.com.br/acessorios, https://www.luxcar.com.br/seguranca-e-manutencao and https://www.luxcar.com.br/eletricidade-do-auto and 6 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.luxcar.com.br/produtos, https://www.luxcar.com.br/limpeza, https://www.luxcar.com.br/acessorios-para-limpeza, https://www.luxcar.com.br/newfresh, https://www.luxcar.com.br/acessorios and https://www.luxcar.com.br/seguranca-e-manutencao and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

6 images are served at too low a resolution for sharp phone screens.

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

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: 112 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.

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 729 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Meta Pixel (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 4 cookies, 1 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 16 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.