jockos.com.br website review

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

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

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

Your mobile performance score is 63 (desktop: 87). Pages that score under 90 lose visitors before the first paint.

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

About 291 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.

About 55 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.

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

7 KiB could be saved by minifying CSS.

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

Shopify costs a phone 74 ms of main-thread work and 462 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.

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

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

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

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.9 s. Good is under 3.8 s.

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

Real visitors wait 201 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

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

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

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

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

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

2 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 1.4 s to 1.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 3.9 MB in 223 requests on a phone: images 1.9 MB (36), scripts 1.1 MB (72) and other files 675 KiB (97). Under 2 MB keeps phones on slow connections fast.

3 images are downloaded at several times the size a phone draws them, for example google_verify.webp at 1,689 px wide, shown at 156 px. Resized copies would save about 341 KiB.

1 image (226 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.

1 image further down the page (226 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

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

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

All page content should be contained by landmarks: 2 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 on the page fails this check, rated moderate by axe-core.

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

ARIA role should be appropriate for the element: 4 elements on the page fail this check, rated minor by axe-core.

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

Your title is only 7 characters: “Jocko's”. Between 30 and 65 characters leaves room to say what you do and for whom.

The homepage links to 261 pages on jockos.com.br and 8 external pages.

Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

https://jockos.com.br/collections/colecao-lancamentos-fem, https://jockos.com.br/collections/colecao-lancamentos-masc, https://jockos.com.br/collections/blusas-regata-femininas, https://jockos.com.br/collections/blusa-manga-curta, https://jockos.com.br/collections/camisetas-femininas and https://jockos.com.br/collections/camisas-fem and 4 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://jockos.com.br/collections/colecao-lancamentos-fem, https://jockos.com.br/collections/colecao-lancamentos-masc, https://jockos.com.br/collections/todas-as-blusas-femininas, https://jockos.com.br/collections/blusas-regata-femininas, https://jockos.com.br/collections/blusa-manga-curta and https://jockos.com.br/collections/blusas-manga-longa-femininas and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

4 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://api.reclameaqui.com.br/embed-raverified/hash/NDA1ODE6am9ja29z' from origin 'https:…”.

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.

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Clarity and 2 mores (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 20 cookies, 3 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.