Website review, no card needed

drogariarosario.com.br logo

drogariarosario.com.br website review

Visit site (opens in a new tab)Reviewed 19 November 202651 issues · 91 checks

This review found 51 issues worth fixing on drogariarosario.com.br, 21 of them high impact, across 91 checks. The most urgent: vtexassets.com adds 1.8 s. 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
4.9 s3.2 sMay 30Nov 143.4 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20263.6 s
Jun 6, 20263.9 s
Jun 13, 20264.1 s
Jun 20, 20264.4 s
Jun 27, 20264.5 s
Jul 4, 20264.6 s
Jul 11, 20264.6 s
Jul 18, 20264.6 s
Jul 25, 20264.7 s
Aug 1, 20264.7 s
Aug 8, 20264.5 s
Aug 15, 20264.1 s
Aug 22, 20263.8 s
Aug 29, 20263.5 s
Sep 5, 20263.5 s
Sep 12, 20263.5 s
Sep 19, 20263.5 s
Sep 26, 20263.5 s
Oct 3, 20263.6 s
Oct 10, 20263.6 s
Oct 17, 20263.7 s
Oct 24, 20263.6 s
Oct 31, 20263.6 s
Nov 7, 20263.5 s
Nov 14, 20263.4 s
Real-visitor tap response (INP)75th percentile, phones
306 ms237 msMay 30Nov 14286 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026254 ms
Jun 6, 2026246 ms
Jun 13, 2026245 ms
Jun 20, 2026246 ms
Jun 27, 2026254 ms
Jul 4, 2026263 ms
Jul 11, 2026272 ms
Jul 18, 2026273 ms
Jul 25, 2026274 ms
Aug 1, 2026279 ms
Aug 8, 2026285 ms
Aug 15, 2026293 ms
Aug 22, 2026298 ms
Aug 29, 2026292 ms
Sep 5, 2026284 ms
Sep 12, 2026270 ms
Sep 19, 2026259 ms
Sep 26, 2026262 ms
Oct 3, 2026268 ms
Oct 10, 2026274 ms
Oct 17, 2026279 ms
Oct 24, 2026283 ms
Oct 31, 2026286 ms
Nov 7, 2026286 ms
Nov 14, 2026286 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 drogariarosario.com.br (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. drogariarosario.com.br at 4.2 s4.2 s
  2. drogariarosario.com.br at 8.3 s8.3 s
  3. drogariarosario.com.br at 12.5 s12.5 s
  4. drogariarosario.com.br at 16.7 s16.7 s
  5. drogariarosario.com.br at 20.8 s20.8 s
  6. drogariarosario.com.br at 25.0 s25.0 s
  7. drogariarosario.com.br at 29.2 s29.2 s
  8. drogariarosario.com.br at 33.4 s33.4 s

Speed

14 to fix13
  • vtexassets.com adds 1.8 s

    1.8 s

    vtexassets.com costs a phone 1.8 s of main-thread work and 4.8 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Improve image delivery

    1.5 s · 279 KiB

    3 images could be 279 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.5 s faster on a phone.

  • Render-blocking requests

    1.3 s

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

  • Main-thread work: 10.7 s

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

  • Mobile performance score: 13

    13/100

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

  • 3,512 HTML elements

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

  • 8 third-party services on the page

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

  • Reduce unused JavaScript

    450 ms · 2.2 MB

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

  • Use efficient cache lifetimes

    350 ms · 1.3 MB

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

  • Google CDN adds 814 ms

    814 ms

    Google CDN costs a phone 814 ms of main-thread work and 2.8 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.

  • Google Tag Manager adds 731 ms

    731 ms

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

  • Insider adds 473 ms

    473 ms

    Insider costs a phone 473 ms of main-thread work and 736 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.

  • Reduce unused CSS

    300 ms · 92 KiB

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

  • Hotjar adds 178 ms

    178 ms

    Hotjar costs a phone 178 ms of main-thread work and 737 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.

  • Legacy JavaScript

    200 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 200 ms faster on a phone.

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

  • Minify JavaScript

    8 KiB

    8 KiB could be saved by minifying JavaScript.

  • 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: 13 ms

    13 ms

    Your server sent the HTML in 13 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.44

    0.44

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

  • Cumulative Layout Shift: 1.402

    1.402

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

  • Speed Index: 18.2 s

    18.2 s

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

  • Time to Interactive: 33.5 s

    33.5 s

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

  • Largest Contentful Paint: 7.8 s

    7.8 s

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

  • Total Blocking Time: 1.3 s

    1.3 s

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

  • Real-user INP: 376 ms

    376 ms

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

  • Real-user FCP: 2.3 s

    2.3 s

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

  • Real-user TTFB: 1.1 s

    1.1 s

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

  • First Contentful Paint: 2.6 s

    2.6 s

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

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

    +14%

    Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 254 ms to 286 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-11-14, real Chrome visitors' largest content (lcp) went from 3.6 s to 3.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

1 checks passed
  • Real-user LCP: 2.4 s

    2.4 s

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

Images and page weight

2 to fix64
  • Page weight: 6.0 MB in 412 requests

    6.0 MB

    Your homepage downloads 6.0 MB in 412 requests on a phone: scripts 3.5 MB (121), images 1.0 MB (80) and other files 867 KiB (185). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    c48a5a1a-e0bd-43ae-ad3c-b229dfef2e2e___24a2a9d9feb998fbb1261 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).

  • 1 image in older formats

    1 image (330 KiB) is 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 1.7 g of CO₂ per visit

    1.69 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.69 g of CO₂e: 202.8 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 7889
  • 2 buttons without a name

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

  • Orphan list items

    Some list items are not inside a list.

  • Interactive controls must not be nested (1 element)

    Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.

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

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

  • 2 text elements with low contrast

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

  • 2 form fields without a label

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

  • Alternative text of images should not be repeated as text (7 elements)

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

  • Elements with visible text labels do not have matching accessible names.

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

2 checks passed
  • Every image has alt text

    All 48 images in the HTML carry an alt attribute.

  • 42 automated accessibility rules passed

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

SEO

5 to fixGoogle 8574
  • No H1 headline

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

  • Title is short (16 characters)

    Your title is only 16 characters: “Drogaria Rosário”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • Structured data has 1 problem

    Structured data found (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.

  • 2 links crawlers can't follow

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

  • 50 internal links, 13 external

    The homepage links to 50 pages on drogariarosario.com.br and 13 external pages.

4 checks passed
  • Meta description: 94 characters

    Your meta description is 94 characters: “Drogaria Rosário. Farmácia 24h. Preços e condições imperdíveis. Compre agora e retire na loja.”.

  • Canonical URL set

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

Other pages

3 to fix86
  • 2 linked pages hidden from search

    https://www.drogariarosario.com.br/529 and https://www.drogariarosario.com.br/844 are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

  • 2 pages share a meta description

    https://www.drogariarosario.com.br/529 and https://www.drogariarosario.com.br/844 use the same meta description. A description written for each page earns more clicks.

  • 13 pages without an H1

    https://www.drogariarosario.com.br/novidades-do-momento, https://www.drogariarosario.com.br/destaques, https://www.drogariarosario.com.br/descontos-especiais, https://www.drogariarosario.com.br/ofertas-destaque, https://www.drogariarosario.com.br/cuidado-adulto and https://www.drogariarosario.com.br/529 and 7 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 10 pages slow to respond

    https://www.drogariarosario.com.br/destaques, https://www.drogariarosario.com.br/descontos-especiais, https://www.drogariarosario.com.br/cuidado-adulto, https://www.drogariarosario.com.br/529, https://www.drogariarosario.com.br/destaques-especiais and https://www.drogariarosario.com.br/ofertas-quinzenais 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 43 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.

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

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9678
  • 3 broken images

    3 images failed to load on a phone, for example https://dmvfarma.vteximg.com.br/arquivos/ids/226287_2.

  • 6 JavaScript errors while loading

    6 errors were logged to the browser console while the page loaded, for example “Failed to execute 'appendChild' on 'Node': Identifier 'verifyAttributes' has already been declared https://rosario.vtex…”.

2 checks passed
  • Tap targets are thumb-sized

    30 of 33 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix40
  • 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: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

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

    The homepage carries about 478 words of visible text.

1 checks passed
  • Analytics in place

    Analytics detected: Google Tag Manager and Meta Pixel.

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, Hotjar and Meta Pixel 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.

  • 21 cookies set on arrival

    21

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

  • 64 other companies contacted

    Loading the homepage contacts 64 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 drogariarosario.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
Hosting
CloudFront

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 drogariarosario.com.br, including 25 speed issues, 5 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