clovis.com.br website review

Your mobile performance score is 72. Pages that score under 90 lose visitors before the first paint.

35 files are served with short cache lifetimes, so returning visitors download them again (692 KiB).

8 third-party services load with your homepage (Google Tag Manager, jQuery CDN and Clarity and others), adding 872 KiB and 601 ms of main-thread time.

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

About 539 KiB of JavaScript is downloaded but never used on this page.

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

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

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

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

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

1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 250 ms.

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

21 KiB could be saved by minifying JavaScript.

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.

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

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

Real visitors wait 1.0 s for your server to start answering (75th percentile). Good is under 800 ms.

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

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

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

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 3.8 s to 3.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 2.7 MB in 172 requests on a phone: images 1.3 MB (43), scripts 1.1 MB (78) and fonts 145 KiB (8). Under 2 MB keeps phones on slow connections fast.

01a15f0f-b7ba-73ff-b338-2a4eed6cc430 is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

1 image (138 KiB) is 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 0.76 g of CO₂e: 91.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

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

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

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

Elements with visible text labels do not have matching accessible names. (2 elements).

The homepage links to 112 pages on clovis.com.br and 18 external pages.

Your homepage links to /s, which answers with an error. Visitors hit a dead end and search engines drop it.

/esporte is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

/feminino and /feminino/sandalia,tamanco,rasteira all use the title “Compre Calçados Femininos Online | Clovis Calçados”. Search engines can't tell which page to show for a search, so each competes with the others.

/nossas-lojas, /novidades, /esporte, /marcas, /outlet and /esquenta and 1 other use the same meta description. A description written for each page earns more clicks.

Your homepage links to 2 pages by a URL that isn't their canonical one, for example /Converse, whose canonical is /converse. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

/Converse has no <h1> headline, so visitors and search engines get no clear main topic.

/melissa and /vizzano took over 3 s to send their HTML from our server.

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

4 errors were logged to the browser console while the page loaded, for example “Uncaught (in promise) TypeError: Cannot read properties of undefined (reading 'register')”.

Large scripts ship without source maps.

1 link to other sites is dead, for example https://www.clovisesporte.com.br/termo (404).

No Strict-Transport-Security header, so browsers may still try plain http first on a return visit.

X-Content-Type-Options: nosniff is missing, so browsers may guess file types.

4 links go through two or more redirects, for example http://www.clovisesporte.com.br/.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

clovis.com.br has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

clovis.com.br's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

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 trust badge. 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 673 words of visible text.

DMARC is set to p=none, so mail pretending to be clovis.com.br is still delivered. Add a report address, check the reports, then move to quarantine.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

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

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