Website review, no card needed

drogariatotal.com.br logo

drogariatotal.com.br website review

Visit site (opens in a new tab)Reviewed 26 October 202651 issues · 94 checks

This review found 51 issues worth fixing on drogariatotal.com.br, 22 of them high impact, across 94 checks. The most urgent: use efficient cache lifetimes. 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
6.1 s5.0 sMay 9Oct 245.4 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20265.1 s
May 16, 20265.1 s
May 23, 20265.1 s
May 30, 20265.2 s
Jun 6, 20265.3 s
Jun 13, 20265.4 s
Jun 20, 20265.6 s
Jun 27, 20265.6 s
Jul 4, 20265.8 s
Jul 11, 20266.0 s
Jul 18, 20265.8 s
Jul 25, 20265.7 s
Aug 1, 20265.5 s
Aug 8, 20265.3 s
Aug 15, 20265.2 s
Aug 22, 20265.4 s
Aug 29, 20265.5 s
Sep 5, 20265.6 s
Sep 12, 20265.6 s
Sep 19, 20265.6 s
Sep 26, 20265.6 s
Oct 3, 20265.6 s
Oct 10, 20265.6 s
Oct 17, 20265.5 s
Oct 24, 20265.4 s
Real-visitor tap response (INP)75th percentile, phones
214 ms180 msMay 9Oct 24191 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026210 ms
May 16, 2026205 ms
May 23, 2026204 ms
May 30, 2026200 ms
Jun 6, 2026197 ms
Jun 13, 2026195 ms
Jun 20, 2026191 ms
Jun 27, 2026190 ms
Jul 4, 2026188 ms
Jul 11, 2026191 ms
Jul 18, 2026193 ms
Jul 25, 2026197 ms
Aug 1, 2026197 ms
Aug 8, 2026196 ms
Aug 15, 2026194 ms
Aug 22, 2026196 ms
Aug 29, 2026195 ms
Sep 5, 2026194 ms
Sep 12, 2026198 ms
Sep 19, 2026192 ms
Sep 26, 2026193 ms
Oct 3, 2026188 ms
Oct 10, 2026184 ms
Oct 17, 2026186 ms
Oct 24, 2026191 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 drogariatotal.com.br (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. drogariatotal.com.br at 1.4 s1.4 s
  2. drogariatotal.com.br at 2.9 s2.9 s
  3. drogariatotal.com.br at 4.3 s4.3 s
  4. drogariatotal.com.br at 5.7 s5.7 s
  5. drogariatotal.com.br at 7.1 s7.1 s
  6. drogariatotal.com.br at 8.5 s8.5 s
  7. drogariatotal.com.br at 10.0 s10.0 s
  8. drogariatotal.com.br at 11.4 s11.4 s

Speed

16 to fix55
  • Use efficient cache lifetimes

    47.6 s · 18.4 MB

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

  • Reduce unused CSS

    28.6 s · 4.8 MB

    About 4.8 MB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 28.6 s faster on a phone.

  • Render-blocking requests

    33.0 s

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

  • Reduce unused JavaScript

    25.5 s · 3.4 MB

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

  • Improve image delivery

    1.3 s · 4.5 MB

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

  • Main-thread work: 4.1 s

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

  • Mobile performance score: 55

    55/100

    Your mobile performance score is 55. Pages that score under 90 lose visitors before the first paint.

  • 4 third-party services on the page

    4 third-party services load with your homepage (Google Maps, Other Google APIs/SDKs and Google Fonts and others), adding 2.4 MB and 738 ms of main-thread time.

  • Google Maps adds 729 ms

    729 ms

    Google Maps costs a phone 729 ms of main-thread work and 2.3 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.

  • Minify CSS

    730 ms · 172 KiB

    172 KiB could be saved by minifying CSS.

  • Font display

    900 ms

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

  • Document request latency

    550 ms · 341 KiB

    The HTML itself could arrive about 550 ms sooner: redirects, a slow server response or missing compression delay everything after it.

  • Minify JavaScript

    710 ms · 118 KiB

    118 KiB could be saved by minifying JavaScript.

  • Reduce initial server response time

    541 ms

    Reduce initial server response time. Google estimates savings of 541 ms on a phone.

  • 2,152 HTML elements

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

  • Server response: 641 ms

    641 ms

    Your server takes 641 ms to send the HTML. Google recommends under 600 ms; everything else waits for it.

  • 5 long tasks on the main thread

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

  • Legacy JavaScript

    100 ms · 32 KiB

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

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

Core Web Vitals

9 to fix67
  • 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 LCP: 5.9 s

    5.9 s

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

  • Real-user FCP: 4.7 s

    4.7 s

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

  • Real-user TTFB: 2.6 s

    2.6 s

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

  • First Contentful Paint: 34.2 s

    34.2 s

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

  • Largest Contentful Paint: 82.0 s

    82.0 s

    Your largest element takes 82.0 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: 34.2 s

    34.2 s

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

  • Time to Interactive: 82.8 s

    82.8 s

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

  • 6 images without width and height

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

  • Tap response (INP) held steady for real visitors

    -9%

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

  • Largest content (LCP) held steady for real visitors

    +7%

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

4 checks passed
  • Real-user INP: 190 ms

    190 ms

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

  • Real-user CLS: 0.00

    0.00

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

  • Cumulative Layout Shift: 0

    0

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

  • Total Blocking Time: 59 ms

    59 ms

    Scripts block the page for only 59 ms while loading. Good is under 200 ms.

Images and page weight

1 to fix70
  • Page weight: 21.3 MB in 295 requests

    21.3 MB

    Your homepage downloads 21.3 MB in 295 requests on a phone: images 10.0 MB (49), scripts 5.3 MB (121) and stylesheets 5.1 MB (88). Under 2 MB keeps phones on slow connections fast.

  • 2 images in older formats

    2 images (372 KiB) 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.

  • 1 image below the first screen load straight away

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

  • About 6.0 g of CO₂ per visit

    6.03 g

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

1 checks passed
  • Images are sized for phones

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

Accessibility

8 to fixGoogle 8390
  • Unlabelled dropdowns

    1 dropdown has no label.

  • Positive tabindex

    2 elements have a tabindex above 0, which scrambles the keyboard order.

  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

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

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

  • 6 links without text

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

  • 1 form field without a label

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

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 64 images in the HTML carry an alt attribute.

  • 45 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 53 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 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 7772
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • Title is long (107 characters)

    Your title is 107 characters, so Google will cut it off around 60: “Drogaria Total – Na Drogaria Total você encontra a maior variedade de Medicamentos e Gené…”.

  • No structured data

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

  • 3 H1 headlines

    There are 3 <h1> headlines (“Advanced healthcare treatment solutions”, “Ofertas e Promoções” and “Estamos prontos para ouvir você”). One clear main headline is easier for people and search engines.

  • 2 links crawlers can't follow

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

  • Open Graph partly set

    Open Graph is missing og:title, so shared links fall back to guesses.

  • No X (Twitter) card tag

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

  • 57 internal links, 44 external

    The homepage links to 57 pages on drogariatotal.com.br and 44 external pages.

3 checks passed
  • Canonical URL set

    The canonical URL is https://www.drogariatotal.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.drogariatotal.com.br/wp-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.drogariatotal.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,816 words), so crawlers that don't run JavaScript still read it.

Other pages

4 to fix58
  • 5 linked pages are broken

    Your homepage links to https://www.drogariatotal.com.br/our-services, https://www.drogariatotal.com.br/services/pharmacy-services, https://www.drogariatotal.com.br/services/maternity-ward, https://www.drogariatotal.com.br/services/outpatient-clinic and https://www.drogariatotal.com.br/services/laboratory-service, which answer with an error. Visitors hit a dead end and search engines drop them.

  • 8 pages share 4 titles

    https://www.drogariatotal.com.br/nossas-lojas and https://www.drogariatotal.com.br/services/nossas-lojas all use the title “Nossas lojas – Drogaria Total”, and 3 other titles repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

  • 10 pages without a meta description

    https://www.drogariatotal.com.br/nossas-lojas, https://www.drogariatotal.com.br/quem-somos, https://www.drogariatotal.com.br/ofertas, https://www.drogariatotal.com.br/convenio-farmacia, https://www.drogariatotal.com.br/services/nossas-lojas and https://www.drogariatotal.com.br/services_group/drogaria-total and 4 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 8 pages without an H1

    https://www.drogariatotal.com.br/nossas-lojas, https://www.drogariatotal.com.br/convenio-farmacia, https://www.drogariatotal.com.br/services/nossas-lojas, https://www.drogariatotal.com.br/services_group/drogaria-total, https://www.drogariatotal.com.br/services/ofertas and https://www.drogariatotal.com.br/services/radio-popular and 2 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 10 pages slow to respond

    https://www.drogariatotal.com.br/nossas-lojas, https://www.drogariatotal.com.br/quem-somos, https://www.drogariatotal.com.br/ofertas, https://www.drogariatotal.com.br/convenio-farmacia, https://www.drogariatotal.com.br/services/nossas-lojas and https://www.drogariatotal.com.br/services_group/drogaria-total and 4 others took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

3 checks passed
  • 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.

  • Every page has a title

    All 10 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9678
  • 1 broken image

    1 image failed to load on a phone, for example https://www.drogariatotal.com.br/pub/media/wysiwyg/drogariatotal/fav.png.

  • 5 JavaScript errors while loading

    5 errors were logged to the browser console while the page loaded, for example “Access to font at 'https://novosite.drogariatotal.com.br/wp-content/uploads/elementor/google-fonts/fonts/roboto-fb5169d…”.

2 checks passed
  • Tap targets are thumb-sized

    7 of 8 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix63
  • 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.

  • Local business without LocalBusiness data

    Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • No phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

  • No analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

  • 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 opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

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

    The homepage carries about 630 words of visible text.

3 checks passed
  • 1 call to action

    The homepage has 1 call to action, for example “Start search”.

  • 3 short forms

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

  • Social proof on the page

    Social proof on the homepage: 30 testimonial or review blocks and 1 trust badge.

Privacy and tracking

  • 8 cookies set on arrival

    8

    Opening the homepage sets 8 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.

  • 8 other companies contacted

    Loading the homepage contacts 8 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 drogariatotal.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

CMS
WordPress
Framework
jQuery
E-commerce
WooCommerce

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 51 issues on drogariatotal.com.br, including 25 speed issues, 5 SEO issues and 5 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