Website review, no card needed

dermage.com.br logo

dermage.com.br website review

Visit site (opens in a new tab)Reviewed 17 November 202658 issues · 102 checks

This review found 58 issues worth fixing on dermage.com.br, 28 of them high impact, across 102 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
2.6 s2.2 sMay 30Nov 142.3 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20262.5 s
Jun 6, 20262.5 s
Jun 13, 20262.5 s
Jun 20, 20262.5 s
Jun 27, 20262.5 s
Jul 4, 20262.5 s
Jul 11, 20262.5 s
Jul 18, 20262.5 s
Jul 25, 20262.5 s
Aug 1, 20262.5 s
Aug 8, 20262.5 s
Aug 15, 20262.5 s
Aug 22, 20262.5 s
Aug 29, 20262.4 s
Sep 5, 20262.4 s
Sep 12, 20262.4 s
Sep 19, 20262.4 s
Sep 26, 20262.4 s
Oct 3, 20262.5 s
Oct 10, 20262.5 s
Oct 17, 20262.5 s
Oct 24, 20262.5 s
Oct 31, 20262.5 s
Nov 7, 20262.4 s
Nov 14, 20262.3 s
Real-visitor tap response (INP)75th percentile, phones
243 ms191 msMay 30Nov 14237 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026197 ms
Jun 6, 2026203 ms
Jun 13, 2026205 ms
Jun 20, 2026212 ms
Jun 27, 2026211 ms
Jul 4, 2026211 ms
Jul 11, 2026209 ms
Jul 18, 2026202 ms
Jul 25, 2026210 ms
Aug 1, 2026210 ms
Aug 8, 2026211 ms
Aug 15, 2026218 ms
Aug 22, 2026212 ms
Aug 29, 2026212 ms
Sep 5, 2026212 ms
Sep 12, 2026209 ms
Sep 19, 2026210 ms
Sep 26, 2026208 ms
Oct 3, 2026211 ms
Oct 10, 2026211 ms
Oct 17, 2026214 ms
Oct 24, 2026217 ms
Oct 31, 2026222 ms
Nov 7, 2026233 ms
Nov 14, 2026237 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 dermage.com.br (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. dermage.com.br at 4.3 s4.3 s
  2. dermage.com.br at 8.6 s8.6 s
  3. dermage.com.br at 13.0 s13.0 s
  4. dermage.com.br at 17.3 s17.3 s
  5. dermage.com.br at 21.6 s21.6 s
  6. dermage.com.br at 25.9 s25.9 s
  7. dermage.com.br at 30.3 s30.3 s
  8. dermage.com.br at 34.6 s34.6 s

Speed

13 to fix11
  • Improve image delivery

    5.7 s · 1.3 MB

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

  • Use efficient cache lifetimes

    4.3 s · 1.9 MB

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

  • Reduce unused JavaScript

    3.5 s · 934 KiB

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

  • Render-blocking requests

    2.5 s

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

  • Avoid multiple page redirects

    2.4 s

    The page goes through 1 redirect before it starts loading, costing about 2.4 s. Link and advertise the final URL directly.

  • Mobile performance score: 11

    11/100

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

  • Main-thread work: 6.2 s

    A phone's processor spends 6.2 s on main-thread work while loading, 3.8 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 (Google Tag Manager, vtexassets.com and vtex.com.br and others), adding 2.3 MB and 2.6 s of main-thread time.

  • Google Tag Manager adds 845 ms

    845 ms

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

  • vtexassets.com adds 658 ms

    658 ms

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

  • vtex.com.br adds 378 ms

    378 ms

    vtex.com.br costs a phone 378 ms of main-thread work and 92 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 on the main thread

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

  • 2,402 HTML elements

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

  • Legacy JavaScript

    100 ms · 47 KiB

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

  • Minify JavaScript

    110 ms · 9 KiB

    9 KiB could be saved by minifying JavaScript.

  • Reduce unused CSS

    65 KiB

    About 65 KiB of CSS is downloaded but never applied on this page.

  • Font display

    50 ms

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

  • Minify CSS

    6 KiB

    6 KiB could be saved by minifying CSS.

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

1 checks passed
  • Server response: 6 ms

    6 ms

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

Core Web Vitals

11 to fix33
  • 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.

  • Real-user CLS: 0.86

    0.86

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

  • Largest Contentful Paint: 43.8 s

    43.8 s

    Your largest element takes 43.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “SELEÇÃO DERMA FRIDAY”.

  • Speed Index: 17.3 s

    17.3 s

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

  • Time to Interactive: 48.8 s

    48.8 s

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

  • Cumulative Layout Shift: 0.885

    0.885

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

  • First Contentful Paint: 5.9 s

    5.9 s

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

  • Total Blocking Time: 844 ms

    844 ms

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

  • Real-user INP: 205 ms

    205 ms

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

  • Real-user TTFB: 1.2 s

    1.2 s

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

  • 35 images without width and height

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

  • Tap response (INP) got 18% slower for real visitors

    +18%

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

  • Largest content (LCP) held steady for real visitors

    -8%

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

2 checks passed
  • Real-user LCP: 1.8 s

    1.8 s

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

  • Real-user FCP: 1.5 s

    1.5 s

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

Images and page weight

2 to fix60
  • Page weight: 8.0 MB in 367 requests

    8.0 MB

    Your homepage downloads 8.0 MB in 367 requests on a phone: images 4.9 MB (51), scripts 2.7 MB (185) and other files 158 KiB (92). Under 2 MB keeps phones on slow connections fast.

  • 4 images in older formats

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

  • About 2.3 g of CO₂ per visit

    2.28 g

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

2 checks passed
  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

16 to fixGoogle 6079
  • Invalid ARIA attributes

    3 elements use ARIA attributes their role does not allow, which confuses screen readers.

  • Certain ARIA roles must contain particular children (3 elements)

    Certain ARIA roles must contain particular children: 3 elements on the page fail this check, rated critical by axe-core.

  • ARIA attributes must conform to valid values (3 elements)

    ARIA attributes must conform to valid values: 3 elements on the page fail this check, rated critical by axe-core.

  • 41 text elements with low contrast

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

  • ARIA input fields must have an accessible name (5 elements)

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

  • 5 tap targets too small

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

  • Interactive controls must not be nested (3 elements)

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

  • <html> element must have a lang attribute (1 element)

    <html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

  • Malformed lists

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

  • 28 images without alt text

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

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    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.

  • Zoom is disabled

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

  • 11 form fields without a label

    11 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • 5 links without text

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

  • No page language

    The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

  • Elements marked as presentational should be consistently ignored (3 elements)

    Elements marked as presentational should be consistently ignored: 3 elements on the page fail this check, rated minor by axe-core.

  • Headings skip levels

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

1 checks passed
  • 46 automated accessibility rules passed

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

SEO

4 to fixGoogle 8584
  • Title is short (7 characters)

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

  • Structured data has 2 problems

    Structured data found (untyped) but with 2 problems, for example “ld+json block 1 is not valid JSON (Bad control character in string literal in JSON at position )”.

  • No social preview image

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

  • 7 links crawlers can't follow

    7 links have no real href, so search engines can't follow them.

  • No X (Twitter) card tag

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

  • 141 internal links, 31 external

    The homepage links to 141 pages on dermage.com.br and 31 external pages.

5 checks passed
  • Meta description: 143 characters

    Your meta description is 143 characters: “Venha conhecer os dermocosméticos para os cuidados da pele tipicamente brasileira. A Dermage oferece produtos recomenda…”.

  • One H1 headline

    Your main headline reads: “teste”.

  • Canonical URL set

    The canonical URL is https://www.dermage.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.dermage.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.dermage.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 (731 words), so crawlers that don't run JavaScript still read it.

Other pages

3 to fix86
  • 3 pages share a title

    https://www.dermage.com.br/institucional/a-dermage, https://www.dermage.com.br/institucional/a-dermage/english and https://www.dermage.com.br/institucional/a-dermage/spanish all use the title “Institucional – Dermage”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 3 pages share a meta description

    https://www.dermage.com.br/institucional/a-dermage, https://www.dermage.com.br/institucional/a-dermage/english and https://www.dermage.com.br/institucional/a-dermage/spanish use the same meta description. A description written for each page earns more clicks.

  • 3 links to non-canonical URLs

    Your homepage links to 3 pages by a URL that isn't their canonical one, for example https://www.dermage.com.br/institucional/a-dermage, whose canonical is https://www.dermage.com.br/institucional. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 2 pages slow to respond

    https://www.dermage.com.br/rosto/tonico-facial and https://www.dermage.com.br/rosto/esfoliacao took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

5 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • Every page has an H1

    Each page we checked has a main headline.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

4 to fixGoogle 6983
  • 14 small tap targets

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

  • 2 third-party cookies

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

  • 6 JavaScript errors while loading

    6 errors were logged to the browser console while the page loaded, for example “Refused to apply style from 'https://dermage.vteximg.com.br/arquivos/mobile-IphoneIPod.css' because its MIME type ('') …”.

  • 2 distorted images

    2 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

  • Browser-reported issues

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

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix58
  • 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.

  • Thin social proof

    Social proof on the homepage: 4 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.

  • 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 439 words of copy

    The homepage carries about 439 words of visible text.

3 checks passed
  • 4 short forms

    4 short forms (6 fields at most) are right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Direct contact links

    Visitors can reach you directly: 1 phone link and 0 email links.

Privacy and tracking

1 to fix
  • 6 trackers load before any consent

    6

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

  • 32 cookies set on arrival

    32

    Opening the homepage sets 32 cookies, 1 of them by other companies (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.

  • 55 other companies contacted

    Loading the homepage contacts 55 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 dermage.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
jQuery
Analytics
Google Tag Manager
Hosting
AWS

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 58 issues on dermage.com.br, including 24 speed issues, 4 SEO issues and 3 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