Website review, no card needed

farmais.com.br logo

farmais.com.br website review

Visit site (opens in a new tab)Reviewed 18 November 202643 issues · 87 checks

This review found 43 issues worth fixing on farmais.com.br, 18 of them high impact, across 87 checks. The most urgent: page weight: 14.7 MB in 337 requests. 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.0 s3.3 sMay 30Nov 143.7 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20263.4 s
Jun 6, 20263.4 s
Jun 13, 20263.5 s
Jun 20, 20263.6 s
Jun 27, 20263.6 s
Jul 4, 20263.7 s
Jul 11, 20263.7 s
Jul 18, 20263.7 s
Jul 25, 20263.7 s
Aug 1, 20263.7 s
Aug 8, 20263.8 s
Aug 15, 20263.8 s
Aug 22, 20263.9 s
Aug 29, 20263.9 s
Sep 5, 20263.9 s
Sep 12, 20263.9 s
Sep 19, 20263.8 s
Sep 26, 20263.8 s
Oct 3, 20263.8 s
Oct 10, 20263.9 s
Oct 17, 20263.9 s
Oct 24, 20263.9 s
Oct 31, 20263.8 s
Nov 7, 20263.7 s
Nov 14, 20263.7 s
Real-visitor tap response (INP)75th percentile, phones
250 ms195 msMay 30Nov 14223 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026220 ms
Jun 6, 2026223 ms
Jun 13, 2026216 ms
Jun 20, 2026213 ms
Jun 27, 2026209 ms
Jul 4, 2026201 ms
Jul 11, 2026205 ms
Jul 18, 2026204 ms
Jul 25, 2026209 ms
Aug 1, 2026212 ms
Aug 8, 2026211 ms
Aug 15, 2026217 ms
Aug 22, 2026226 ms
Aug 29, 2026238 ms
Sep 5, 2026244 ms
Sep 12, 2026235 ms
Sep 19, 2026221 ms
Sep 26, 2026210 ms
Oct 3, 2026204 ms
Oct 10, 2026206 ms
Oct 17, 2026212 ms
Oct 24, 2026217 ms
Oct 31, 2026224 ms
Nov 7, 2026224 ms
Nov 14, 2026223 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 farmais.com.br (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. farmais.com.br at 0.4 s0.4 s
  2. farmais.com.br at 0.8 s0.8 s
  3. farmais.com.br at 1.1 s1.1 s
  4. farmais.com.br at 1.5 s1.5 s
  5. farmais.com.br at 1.9 s1.9 s
  6. farmais.com.br at 2.3 s2.3 s
  7. farmais.com.br at 2.6 s2.6 s
  8. farmais.com.br at 3.0 s3.0 s

Speed

12 to fix40
  • Mobile performance score: 40

    40/100

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

  • Main-thread work: 8.0 s

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

  • 4,625 HTML elements

    The page has 4,625 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 Tag Manager and Google CDN and others), adding 10.7 MB and 2.3 s of main-thread time.

  • Improve image delivery

    3.0 MB

    65 images could be 3.0 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • vtexassets.com adds 946 ms

    946 ms

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

  • Use efficient cache lifetimes

    1.5 MB

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

  • Reduce unused JavaScript

    150 ms · 757 KiB

    About 757 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.

  • Reduce unused CSS

    450 ms · 130 KiB

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

  • Google CDN adds 445 ms

    445 ms

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

  • Google Tag Manager adds 477 ms

    477 ms

    Google Tag Manager costs a phone 477 ms of main-thread work and 361 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 414 ms. During a long task the page ignores taps.

  • Legacy JavaScript

    47 KiB

    Polyfills for old browsers add 47 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 JavaScript

    4 KiB

    4 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 48 ms

    48 ms

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

  • Real-user CLS: 0.30

    0.30

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

  • Time to Interactive: 26.2 s

    26.2 s

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

  • Largest Contentful Paint: 8.5 s

    8.5 s

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

  • Total Blocking Time: 1.9 s

    1.9 s

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

  • Speed Index: 7.3 s

    7.3 s

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

  • Real-user INP: 246 ms

    246 ms

    Real visitors wait 246 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: 909 ms

    909 ms

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

  • 4 images without width and height

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

  • Tap response (INP) held steady for real visitors

    +1%

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

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

  • First Contentful Paint: 1.5 s

    1.5 s

    The first text or image appears after 1.5 s, inside the 1.8 s “good” threshold.

  • Cumulative Layout Shift: 0.059

    0.059

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

Images and page weight

1 to fix70
  • Page weight: 14.7 MB in 337 requests

    14.7 MB

    Your homepage downloads 14.7 MB in 337 requests on a phone: images 7.6 MB (226), other files 4.0 MB (47) and scripts 2.0 MB (52). Under 2 MB keeps phones on slow connections fast.

  • 1 image below the first screen load straight away

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

  • About 4.2 g of CO₂ per visit

    4.17 g

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

2 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • 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 8489
  • 18 tap targets too small

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

  • 5 text elements with low contrast

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

  • Orphan list items

    Some list items are not inside a list.

  • Malformed lists

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

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

    All page content should be contained by landmarks: 29 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 (3 elements)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 3 elements on the page fail this check, rated moderate by axe-core.

  • 5 links without text

    5 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 (h3 → h6), which makes the page harder to scan with a screen reader.

2 checks passed
  • Every image has alt text

    All 32 images in the HTML carry an alt attribute.

  • 44 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 52 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 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

2 to fixGoogle 10093
  • Structured data has 1 problem

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

  • 27 internal links, 7 external

    The homepage links to 27 pages on farmais.com.br and 7 external pages.

6 checks passed
  • Meta description: 137 characters

    Your meta description is 137 characters: “A Farmais é a sua rede de drogarias com farmácia online: medicamentos, genéricos, dermocosméticos, beleza e cuidados pa…”.

  • One H1 headline

    Your main headline reads: “Farmais: sua farmácia online para toda a família”.

  • Title: 43 characters

    Your title is a healthy 43 characters: “Farmais Drogarias | Cuidando da sua Família”.

  • Canonical URL set

    The canonical URL is https://www.farmais.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.farmais.com.br/sitemap.xml.

AI search readiness

100
  • No llms.txt

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

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

  • Organization data: 5 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and contact details; description would complete it.

  • Text is in the HTML

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

Other pages

4 to fix64
  • 8 linked pages are broken

    Your homepage links to https://www.farmais.com.br/478, https://www.farmais.com.br/353, https://www.farmais.com.br/464, https://www.farmais.com.br/334, https://www.farmais.com.br/386 and https://www.farmais.com.br/427 and 2 others, which answer with an error. Visitors hit a dead end and search engines drop them.

  • 7 pages share a meta description

    https://www.farmais.com.br/politica-de-privacidade-e-seguranca, https://www.farmais.com.br/fale-conosco, https://www.farmais.com.br/quem-somos, https://www.farmais.com.br/nossas-lojas, https://www.farmais.com.br/politica-de-envio and https://www.farmais.com.br/politica-de-privacidade and 1 other use the same meta description. A description written for each page earns more clicks.

  • 1 link to non-canonical URLs

    Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.farmais.com.br/Termos-Comerciais-e-de-Responsabilidade, whose canonical is https://www.farmais.com.br/termos-comerciais-e-de-responsabilidade. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 2 pages without an H1

    https://www.farmais.com.br/fale-conosco and https://www.farmais.com.br/quem-somos have no <h1> headline, so visitors and search engines get no clear main topic.

  • 2 pages slow to respond

    https://www.farmais.com.br/politica-de-envio and https://www.farmais.com.br/politica-de-privacidade 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.

4 checks passed
  • Every page has a meta description

    All 7 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 7 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9687
  • 23 small tap targets

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

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'register')”.

1 checks passed
  • 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 365 words of copy

    The homepage carries about 365 words of visible text.

3 checks passed
  • 1 short form

    A short form (3 fields at most) is right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Direct contact links

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

Privacy and tracking

1 to fix
  • 1 tracker load before any consent

    1

    Before a visitor clicks anything, the page loads Google Tag Manager (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.

  • 9 cookies set on arrival

    9

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

  • 11 other companies contacted

    Loading the homepage contacts 11 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 farmais.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 43 issues on farmais.com.br, including 22 speed issues, 2 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