keydesign.com.br website review

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

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

8 third-party services load with your homepage (vtexassets.com, Google Tag Manager and tailwindcss.com and others), adding 2.1 MB and 1.8 s of main-thread time.

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

vtexassets.com costs a phone 613 ms of main-thread work and 985 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.

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

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

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

tailwindcss.com costs a phone 265 ms of main-thread work and 124 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.

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

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

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

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 wait 4.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.

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

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

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

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

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

Real visitors see the first content after 2.5 s (75th percentile). Good is under 1.8 s.

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

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

Your homepage downloads 2.3 MB in 111 requests on a phone: scripts 1.8 MB (54), fonts 202 KiB (1) and HTML 113 KiB (1). Under 2 MB keeps phones on slow connections fast.

d03210cd-7557-43e1-a531-70e6820ea48e___5055d78fb8af49033fcb9 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).

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

2 buttons have no accessible name, so screen readers announce just “button”.

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

Images must have alternative text: 1 element on the page fails this check, rated critical by axe-core.

Interactive controls must not be nested: 6 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.

Links must have discernible text: 1 element on the page fails this check, rated serious by axe-core.

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

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

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

Alternative text of images should not be repeated as text: 2 elements on the page fail this check, rated minor by axe-core.

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

Your meta description is 235 characters; Google truncates after about 160, so the end of your pitch is cut.

Structured data found (WebSite) but with 1 problem, for example “WebSite: missing name”.

No Open Graph image, 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 20 pages on keydesign.com.br and 6 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.keydesign.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.keydesign.com.br/key-design-institucional-sobre-nos, https://www.keydesign.com.br/institucional/fornecedores, https://www.keydesign.com.br/institucional/troca-facil, https://www.keydesign.com.br/institucional/regulamento-personalizacao and https://www.keydesign.com.br/institucional/guia-de-medidas and 1 other all use the title “Key Design - Joias e Semijoias Masculinas e Femininas”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.keydesign.com.br/joias-masculinas-aco-e-prata-key-design, https://www.keydesign.com.br/semijoias-feminino-key-design, https://www.keydesign.com.br/mais-vendidos-masculino-feminino-key-design, https://www.keydesign.com.br/acessorios-com-desconto-outlet-key-design, https://www.keydesign.com.br/novidades-linha-feminina-key-design and https://www.keydesign.com.br/key-design-institucional-sobre-nos and 5 others use the same meta description. A description written for each page earns more clicks.

https://www.keydesign.com.br/joias-masculinas-aco-e-prata-key-design, https://www.keydesign.com.br/semijoias-feminino-key-design, https://www.keydesign.com.br/mais-vendidos-masculino-feminino-key-design, https://www.keydesign.com.br/acessorios-com-desconto-outlet-key-design, https://www.keydesign.com.br/novidades-linha-feminina-key-design and https://www.keydesign.com.br/key-design-institucional-sobre-nos and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.keydesign.com.br/mais-vendidos-masculino-feminino-key-design, https://www.keydesign.com.br/acessorios-com-desconto-outlet-key-design, https://www.keydesign.com.br/novidades-linha-feminina-key-design, https://www.keydesign.com.br/key-design-institucional-sobre-nos, https://www.keydesign.com.br/institucional/fornecedores and https://www.keydesign.com.br/rastreamento and 7 others have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

https://www.keydesign.com.br/joias-masculinas-aco-e-prata-key-design, https://www.keydesign.com.br/semijoias-feminino-key-design and https://www.keydesign.com.br/novidades-linha-feminina-key-design took over 3 s to send their HTML from our server.

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

3 errors were logged to the browser console while the page loaded, for example “Warning: No Pinterest tag ID is defined. ”.

1 image is served at too low a resolution for sharp phone screens.

Requests the notification permission on page load.

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.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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 62 words of visible text; thin pages give Google and first-time buyers little to go on.

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, Google Tag Manager, Meta Pixel and TikTok 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 25 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 23 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.