Website review, no card needed

skelt.com.br logo

skelt.com.br website review

Visit site (opens in a new tab)Reviewed 21 October 202659 issues · 97 checks

This review found 59 issues worth fixing on skelt.com.br, 24 of them high impact, across 97 checks. The most urgent: improve image delivery. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
3.9 s3.2 sMay 2Oct 173.5 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20263.7 s
May 9, 20263.5 s
May 16, 20263.5 s
May 23, 20263.5 s
May 30, 20263.5 s
Jun 6, 20263.6 s
Jun 13, 20263.6 s
Jun 20, 20263.6 s
Jun 27, 20263.7 s
Jul 4, 20263.7 s
Jul 11, 20263.7 s
Jul 18, 20263.6 s
Jul 25, 20263.6 s
Aug 1, 20263.6 s
Aug 8, 20263.7 s
Aug 15, 20263.8 s
Aug 22, 20263.8 s
Aug 29, 20263.8 s
Sep 5, 20263.7 s
Sep 12, 20263.6 s
Sep 19, 20263.4 s
Sep 26, 20263.3 s
Oct 3, 20263.3 s
Oct 10, 20263.4 s
Oct 17, 20263.5 s
Real-visitor tap response (INP)75th percentile, phones
400 ms247 msMay 2Oct 17298 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026320 ms
May 9, 2026316 ms
May 16, 2026324 ms
May 23, 2026339 ms
May 30, 2026344 ms
Jun 6, 2026352 ms
Jun 13, 2026356 ms
Jun 20, 2026363 ms
Jun 27, 2026374 ms
Jul 4, 2026382 ms
Jul 11, 2026381 ms
Jul 18, 2026360 ms
Jul 25, 2026330 ms
Aug 1, 2026302 ms
Aug 8, 2026284 ms
Aug 15, 2026270 ms
Aug 22, 2026265 ms
Aug 29, 2026268 ms
Sep 5, 2026270 ms
Sep 12, 2026274 ms
Sep 19, 2026273 ms
Sep 26, 2026279 ms
Oct 3, 2026284 ms
Oct 10, 2026288 ms
Oct 17, 2026298 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of skelt.com.br (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. skelt.com.br at 1.2 s1.2 s
  2. skelt.com.br at 2.5 s2.5 s
  3. skelt.com.br at 3.7 s3.7 s
  4. skelt.com.br at 5.0 s5.0 s
  5. skelt.com.br at 6.2 s6.2 s
  6. skelt.com.br at 7.5 s7.5 s
  7. skelt.com.br at 8.7 s8.7 s
  8. skelt.com.br at 10.0 s10.0 s

Speed

14 to fix43
  • Improve image delivery

    11.2 s · 3.1 MB

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

  • Reduce unused JavaScript

    2.4 s · 1.7 MB

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

  • Render-blocking requests

    2.9 s

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

  • Use efficient cache lifetimes

    1.2 s · 1.2 MB

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

  • Mobile performance score: 43

    43/100

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

  • Main-thread work: 5.3 s

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

  • 8 third-party services on the page

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

  • vtexassets.com adds 539 ms

    539 ms

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

  • Reduce unused CSS

    300 ms · 239 KiB

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

  • Legacy JavaScript

    450 ms · 72 KiB

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

  • Google Tag Manager adds 427 ms

    427 ms

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

  • ZenDesk adds 234 ms

    234 ms

    ZenDesk costs a phone 234 ms of main-thread work and 761 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.

  • 2,321 HTML elements

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

  • usebeon.io adds 189 ms

    189 ms

    usebeon.io costs a phone 189 ms of main-thread work and 418 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.

  • 20 long tasks on the main thread

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

  • Chained critical requests

    Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

  • Minify CSS

    4 KiB

    4 KiB could be saved by minifying CSS.

  • Minify JavaScript

    4 KiB

    4 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 51 ms

    51 ms

    Your server sent the HTML in 51 ms, well inside Google's 600 ms guideline.

Core Web Vitals

12 to fix0
  • Fails Core Web Vitals for real visitors

    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.

  • Largest Contentful Paint: 40.3 s

    40.3 s

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

  • Speed Index: 23.4 s

    23.4 s

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

  • Time to Interactive: 49.6 s

    49.6 s

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

  • First Contentful Paint: 7.3 s

    7.3 s

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

  • Real-user LCP: 2.8 s

    2.8 s

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

  • Real-user INP: 244 ms

    244 ms

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

  • Real-user CLS: 0.11

    0.11

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

  • Real-user FCP: 2.7 s

    2.7 s

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

  • Real-user TTFB: 825 ms

    825 ms

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

  • Total Blocking Time: 474 ms

    474 ms

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

  • 3 images without width and height

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

  • Tap response (INP) held steady for real visitors

    -8%

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

  • Largest content (LCP) held steady for real visitors

    -5%

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

1 checks passed
  • Cumulative Layout Shift: 0.04

    0.04

    The layout barely moves while loading (CLS 0.04, good is under 0.1).

Images and page weight

4 to fix35
  • Page weight: 10.3 MB in 229 requests

    10.3 MB

    Your homepage downloads 10.3 MB in 229 requests on a phone: images 5.7 MB (29), scripts 3.7 MB (97) and other files 423 KiB (83). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    9a97ee60-eb04-4954-939d-f83beb66edd0___9dc7108d104983c0cad5a weighs 1.9 MB. On a phone connection a single image that size takes seconds.

  • 4 images in older formats

    4 images (2.6 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.

  • 3 images far larger than shown

    12 KiB

    3 images are downloaded at several times the size a phone draws them, for example 157944-720-720 at 720 px wide, shown at 238 px. Resized copies would save about 12 KiB.

  • 4 images below the first screen load straight away

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

  • About 2.9 g of CO₂ per visit

    2.92 g

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

Accessibility

13 to fixGoogle 7381
  • 2 buttons without a name

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

  • Images must have alternative text (2 elements)

    Images must have alternative text: 2 elements on the page fail this check, rated critical by axe-core.

  • 21 tap targets too small

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

  • 17 text elements with low contrast

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

  • Hidden but focusable

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

  • ARIA commands must have an accessible name (1 element)

    ARIA commands must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

  • All page content should be contained by landmarks (11 elements)

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

    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.

  • No main landmark

    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)

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

  • 4 links without text

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

  • Elements use prohibited ARIA attributes

    Elements use prohibited ARIA attributes (1 element).

  • 1 form field without a label

    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.

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

1 checks passed
  • 38 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 49 WCAG 2.2 A/AA and best-practice rules on the phone render: 38 passed and 11 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

3 to fixGoogle 9283
  • No H1 headline

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

  • Structured data has 1 problem

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

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No X (Twitter) card tag

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

  • 37 internal links, 6 external

    The homepage links to 37 pages on skelt.com.br and 6 external pages.

5 checks passed
  • Meta description: 151 characters

    Your meta description is 151 characters: “Ter o bronze dos sonhos nunca foi tão fácil. Em apenas alguns minutos, com nossos autobronzeadores, você está com a pel…”.

  • Title: 48 characters

    Your title is a healthy 48 characters: “Skelt | Fragrâncias, Bodycare e Autobronzeadores”.

  • Canonical URL set

    The canonical URL is https://www.skelt.com.br/.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.skelt.com.br/sitemap.xml.

AI search readiness

1 to fix88
  • No Organization structured data

    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.

  • No llms.txt

    There is no https://www.skelt.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.

2 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Text is in the HTML

    Your server sends the page's text in the HTML (666 words), so crawlers that don't run JavaScript still read it.

Other pages

5 to fix67
  • 1 page without a title

    https://www.skelt.com.br/produtos/autobronzeadores has no <title>, so Google invents the link text in results.

  • 2 pages share a title

    https://www.skelt.com.br/produtos and https://www.skelt.com.br/produtos/maquiagens-corporais all use the title “Produtos Skelt para um Glow Inconfundível - Skelt”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 1 page without a meta description

    https://www.skelt.com.br/produtos/autobronzeadores has no meta description, so Google writes the search snippet from whatever text it finds.

  • 7 pages share a meta description

    https://www.skelt.com.br/15-off-na-dupla, https://www.skelt.com.br/linhacompleta-amalfi-sunset/p, https://www.skelt.com.br/perfume-para-cabelos-body-splash-body-cream-amalfi-sunset/p, https://www.skelt.com.br/perfume-para-cabelo-body-splash-amalfi-body-splash-solar-muse/p and https://www.skelt.com.br/produtos/body-splash use the same meta description. A description written for each page earns more clicks.

  • 2 pages without an H1

    https://www.skelt.com.br/15-off-na-dupla and https://www.skelt.com.br/produtos/autobronzeadores have no <h1> headline, so visitors and search engines get no clear main topic.

  • 3 pages slow to respond

    https://www.skelt.com.br/15-off-na-dupla, https://www.skelt.com.br/perfume-para-cabelo-body-splash-amalfi-body-splash-solar-muse/p and https://www.skelt.com.br/produtos/hidratacao-corporal took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

3 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

Best practices

2 to fixGoogle 9287
  • 10 small tap targets

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

  • 4 JavaScript errors while loading

    4 errors were logged to the browser console while the page loaded, for example “No element with attribute "data-trustvox-certificate-fixed" to receive Trustvox fixed certificate.”.

  • 1 low-resolution image

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

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix30
  • No call to action on the first screen

    On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

  • No calls to action

    We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

  • No social proof

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

  • No direct contact details

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

  • No form on the homepage

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

  • No risk reducer

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

  • About 570 words of copy

    The homepage carries about 570 words of visible text.

  • Urgency cues

    The page uses urgency cues (a countdown or limited-time wording).

1 checks passed
  • Analytics in place

    Analytics detected: Google Tag Manager, Meta Pixel and TikTok Pixel.

Privacy and tracking

1 to fix
  • 7 trackers load before any consent

    7

    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.

  • 34 cookies set on arrival

    34

    Opening the homepage sets 34 cookies (measured from a US location before any click).

  • No consent tool detected

    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.

  • 59 other companies contacted

    Loading the homepage contacts 59 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at skelt.com.br, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
React
Analytics
Google Tag Manager

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 59 issues on skelt.com.br, including 26 speed issues, 3 SEO issues and 4 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25