Website review, no card needed

dracherie.com.br logo

dracherie.com.br website review

Visit site (opens in a new tab)Reviewed 23 October 202647 issues · 91 checks

This review found 47 issues worth fixing on dracherie.com.br, 16 of them high impact, across 91 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.7 s1.8 sMay 2Oct 172.5 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20262.5 s
May 9, 20262.6 s
May 16, 20262.5 s
May 23, 20262.2 s
May 30, 20262.0 s
Jun 6, 20261.9 s
Jun 13, 20261.9 s
Jun 20, 20261.9 s
Jun 27, 20261.9 s
Jul 4, 20262.0 s
Jul 11, 20262.0 s
Jul 18, 20262.0 s
Jul 25, 20262.0 s
Aug 1, 20262.2 s
Aug 8, 20262.3 s
Aug 15, 20262.4 s
Aug 22, 20262.4 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.4 s
Oct 10, 20262.4 s
Oct 17, 20262.5 s
Real-visitor tap response (INP)75th percentile, phones
224 ms170 msMay 2Oct 17218 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026182 ms
May 9, 2026181 ms
May 16, 2026179 ms
May 23, 2026177 ms
May 30, 2026177 ms
Jun 6, 2026176 ms
Jun 13, 2026179 ms
Jun 20, 2026181 ms
Jun 27, 2026182 ms
Jul 4, 2026185 ms
Jul 11, 2026185 ms
Jul 18, 2026184 ms
Jul 25, 2026185 ms
Aug 1, 2026191 ms
Aug 8, 2026199 ms
Aug 15, 2026206 ms
Aug 22, 2026210 ms
Aug 29, 2026209 ms
Sep 5, 2026210 ms
Sep 12, 2026210 ms
Sep 19, 2026211 ms
Sep 26, 2026212 ms
Oct 3, 2026213 ms
Oct 10, 2026213 ms
Oct 17, 2026218 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 dracherie.com.br (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. dracherie.com.br at 1.2 s1.2 s
  2. dracherie.com.br at 2.3 s2.3 s
  3. dracherie.com.br at 3.5 s3.5 s
  4. dracherie.com.br at 4.6 s4.6 s
  5. dracherie.com.br at 5.8 s5.8 s
  6. dracherie.com.br at 7.0 s7.0 s
  7. dracherie.com.br at 8.1 s8.1 s
  8. dracherie.com.br at 9.3 s9.3 s

Speed

11 to fix51
  • Improve image delivery

    15.7 s · 3.4 MB

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

  • Main-thread work: 6.6 s

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

  • Reduce unused JavaScript

    310 ms · 1.4 MB

    About 1.4 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 310 ms faster on a phone.

  • Minify JavaScript

    910 ms · 209 KiB

    209 KiB could be saved by minifying JavaScript.

  • Mobile performance score: 51

    51/100

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

  • Reduce unused CSS

    750 ms · 221 KiB

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

  • Render-blocking requests

    800 ms

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

  • Use efficient cache lifetimes

    300 ms · 462 KiB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (New Relic, Vimeo and goadopt.io and others), adding 2.9 MB and 415 ms of main-thread time.

  • Vimeo adds 130 ms

    130 ms

    Vimeo costs a phone 130 ms of main-thread work and 2.6 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.

  • 2,209 HTML elements

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

  • 13 long tasks on the main thread

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

  • Legacy JavaScript

    10 KiB

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

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

1 checks passed
  • Server response: 16 ms

    16 ms

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

Core Web Vitals

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

  • Largest Contentful Paint: 34.8 s

    34.8 s

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

  • Speed Index: 18.8 s

    18.8 s

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

  • Time to Interactive: 45.4 s

    45.4 s

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

  • Real-user LCP: 2.6 s

    2.6 s

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

  • Real-user INP: 261 ms

    261 ms

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

  • Total Blocking Time: 330 ms

    330 ms

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

  • Cumulative Layout Shift: 0.14

    0.14

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

  • First Contentful Paint: 2.0 s

    2.0 s

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

  • 15 images without width and height

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

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

    +19%

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

  • Largest content (LCP) held steady for real visitors

    -2%

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

3 checks passed
  • Real-user CLS: 0.05

    0.05

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

  • Real-user FCP: 1.2 s

    1.2 s

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

  • Real-user TTFB: 517 ms

    517 ms

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

Images and page weight

3 to fix42
  • Page weight: 9.0 MB in 478 requests

    9.0 MB

    Your homepage downloads 9.0 MB in 478 requests on a phone: images 4.8 MB (75), scripts 3.2 MB (274) and fonts 382 KiB (4). Under 2 MB keeps phones on slow connections fast.

  • 3 images far larger than shown

    579 KiB

    3 images are downloaded at several times the size a phone draws them, for example FOTO-CATEGORIA-JAQUETA--MOBILE.png at 588 px wide, shown at 103 px. Resized copies would save about 579 KiB.

  • An image on the first screen is lazy-loaded

    BANNER-REGUA-CAREINPINK-MOBILE.jpg.jpeg 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).

  • About 2.6 g of CO₂ per visit

    2.55 g

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

1 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

Accessibility

9 to fixGoogle 7888
  • Certain ARIA roles must be contained by particular parents (3 elements)

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

  • Certain ARIA roles must contain particular children (1 element)

    Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

  • Malformed lists

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

  • Scrollable region must have keyboard access (3 elements)

    Scrollable region must have keyboard access: 3 elements on the page fail this check, rated serious by axe-core.

  • Orphan list items

    Some list items are not inside a list.

  • Zoom is disabled

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

  • Heading levels should only increase by one (1 element)

    Heading levels should only increase by one: 1 element on the page fails this check, rated moderate by axe-core.

  • 13 links without text

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

  • 2 form fields without a label

    2 form fields have 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. (1 element).

2 checks passed
  • Every image has alt text

    All 98 images in the HTML carry an alt attribute.

  • 50 automated accessibility rules passed

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

SEO

5 to fixGoogle 10079
  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • 2 H1 headlines

    There are 2 <h1> headlines (“Best sellers” and “Lançamentos”). One clear main headline is easier for people and search engines.

  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

  • Meta description is long (202 characters)

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

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

  • No X (Twitter) card tag

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

  • 169 internal links, 16 external

    The homepage links to 169 pages on dracherie.com.br and 16 external pages.

3 checks passed
  • Title: 45 characters

    Your title is a healthy 45 characters: “Dra Cherie - Jalecos e Vestuário Profissional”.

  • 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.dracherie.com.br/media/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.dracherie.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 (1,315 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix93
  • 8 pages share a meta description

    https://www.dracherie.com.br/default/campaigns/best-sellers-cherie, https://www.dracherie.com.br/default/new-in, https://www.dracherie.com.br/default/feminino/jalecos-femininos/jalecos-brancos, https://www.dracherie.com.br/default/feminino/macacoes-femininos, https://www.dracherie.com.br/feminino/scrubs-e-macacoes and https://www.dracherie.com.br/default/feminino/scrubs-e-macacoes/linhas/basica and 2 others use the same meta description. A description written for each page earns more clicks.

  • 1 page without an H1

    https://www.dracherie.com.br/default/stores/store/redirect/___store/dcen/___from_store/default/uenc/aHR0cHM6Ly93d3cuZHJhY2hlcmllLmNvbS5ici9kY2VuLw~~ has no <h1> headline, so visitors and search engines get no clear main topic.

  • 2 pages slow to respond

    https://www.dracherie.com.br/default/new-in and https://www.dracherie.com.br/default/feminino/jalecos/linhas/basica took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

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

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • 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

3 to fixGoogle 5888
  • 13 small tap targets

    13 of 43 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.

  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

  • Browser-reported issues

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

2 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix50
  • 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 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 324 words of copy

    The homepage carries about 324 words of visible text.

3 checks passed
  • 18 short forms

    18 short forms (1 field at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Direct contact links

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

Privacy and tracking

  • 15 cookies set on arrival

    15

    Opening the homepage sets 15 cookies, 2 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.

  • 14 other companies contacted

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

1 checks passed
  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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 dracherie.com.br, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

  • The footer still says © 2016.

Stack

E-commerce
Magento
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 47 issues on dracherie.com.br, including 21 speed issues, 5 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