Website review, no card needed

fmiligrama.com.br logo

fmiligrama.com.br website review

Visit site (opens in a new tab)Reviewed 19 October 202644 issues · 89 checks

This review found 44 issues worth fixing on fmiligrama.com.br, 23 of them high impact, across 89 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.3 s1.6 sMay 2Oct 172.0 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20261.8 s
May 9, 20261.8 s
May 16, 20261.9 s
May 23, 20261.9 s
May 30, 20261.9 s
Jun 6, 20262.0 s
Jun 13, 20261.9 s
Jun 20, 20261.8 s
Jun 27, 20261.8 s
Jul 4, 20261.7 s
Jul 11, 20261.7 s
Jul 18, 20261.7 s
Jul 25, 20261.7 s
Aug 1, 20261.7 s
Aug 8, 20261.7 s
Aug 15, 20261.7 s
Aug 22, 20261.7 s
Aug 29, 20261.8 s
Sep 5, 20261.8 s
Sep 12, 20261.9 s
Sep 19, 20262.0 s
Sep 26, 20262.2 s
Oct 3, 20262.2 s
Oct 10, 20262.1 s
Oct 17, 20262.0 s
Real-visitor tap response (INP)75th percentile, phones
265 ms185 msMay 2Oct 17194 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026245 ms
May 9, 2026237 ms
May 16, 2026240 ms
May 23, 2026248 ms
May 30, 2026256 ms
Jun 6, 2026245 ms
Jun 13, 2026229 ms
Jun 20, 2026214 ms
Jun 27, 2026203 ms
Jul 4, 2026204 ms
Jul 11, 2026206 ms
Jul 18, 2026207 ms
Jul 25, 2026211 ms
Aug 1, 2026212 ms
Aug 8, 2026213 ms
Aug 15, 2026218 ms
Aug 22, 2026217 ms
Aug 29, 2026219 ms
Sep 5, 2026219 ms
Sep 12, 2026213 ms
Sep 19, 2026207 ms
Sep 26, 2026203 ms
Oct 3, 2026196 ms
Oct 10, 2026194 ms
Oct 17, 2026194 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 fmiligrama.com.br (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. fmiligrama.com.br at 1.6 s1.6 s
  2. fmiligrama.com.br at 3.2 s3.2 s
  3. fmiligrama.com.br at 4.8 s4.8 s
  4. fmiligrama.com.br at 6.4 s6.4 s
  5. fmiligrama.com.br at 8.1 s8.1 s
  6. fmiligrama.com.br at 9.7 s9.7 s
  7. fmiligrama.com.br at 11.3 s11.3 s
  8. fmiligrama.com.br at 12.9 s12.9 s

Speed

11 to fix22
  • Improve image delivery

    4.3 s · 7.2 MB

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

  • Use efficient cache lifetimes

    3.3 s · 4.4 MB

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

  • Mobile performance score: 22

    22/100

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

  • Main-thread work: 5.4 s

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

  • 3,876 HTML elements

    The page has 3,876 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 (Google Tag Manager, smarthint.co and Facebook and others), adding 1.6 MB and 1.1 s of main-thread time.

  • Reduce unused JavaScript

    150 ms · 564 KiB

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

  • Google Tag Manager adds 429 ms

    429 ms

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

    300 ms · 87 KiB

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

  • 11 long tasks on the main thread

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

  • smarthint.co adds 260 ms

    260 ms

    smarthint.co costs a phone 260 ms of main-thread work and 300 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

    91 KiB

    About 91 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 JavaScript

    44 KiB

    44 KiB could be saved by minifying JavaScript.

  • Minify CSS

    9 KiB

    9 KiB could be saved by minifying CSS.

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

    414 ms

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

Core Web Vitals

13 to fix0
  • 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.36

    0.36

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

  • Real-user TTFB: 1.9 s

    1.9 s

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

  • Largest Contentful Paint: 25.8 s

    25.8 s

    Your largest element takes 25.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Banner Principal | Outubro Rosa - Geral Campanha”.

  • Time to Interactive: 32.1 s

    32.1 s

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

  • Speed Index: 15.0 s

    15.0 s

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

  • Cumulative Layout Shift: 0.429

    0.429

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

  • Total Blocking Time: 764 ms

    764 ms

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

  • First Contentful Paint: 3.0 s

    3.0 s

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

  • Real-user LCP: 2.9 s

    2.9 s

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

  • Real-user INP: 213 ms

    213 ms

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

  • Real-user FCP: 2.4 s

    2.4 s

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

  • 22 images without width and height

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

  • Largest content (LCP) got 14% slower for real visitors

    +14%

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

1 checks passed
  • Tap response (INP) got 20% faster for real visitors

    -20%

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

Images and page weight

5 to fix29
  • Page weight: 11.5 MB in 249 requests

    11.5 MB

    Your homepage downloads 11.5 MB in 249 requests on a phone: images 8.6 MB (92), scripts 1.8 MB (68) and other files 469 KiB (69). Under 2 MB keeps phones on slow connections fast.

  • 4 images over 500 KB

    4 images weigh 2.7 MB together. On a phone connection a single image that size takes seconds.

  • 18 images far larger than shown

    2.8 MB

    18 images are downloaded at several times the size a phone draws them, for example bff637bfd9eb2588df33768c58fac001.webp at 1,860 px wide, shown at 370 px. Resized copies would save about 2.8 MB.

  • 26 images below the first screen load straight away

    26 images further down the page (4.5 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • An image on the first screen is lazy-loaded

    89ca9bea2823dcf2d5ced001c4f9f4ae.webp 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 3.3 g of CO₂ per visit

    3.26 g

    By the Sustainable Web Design model, a visit to your homepage emits about 3.26 g of CO₂e: 391.2 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

5 to fixGoogle 9492
  • 32 text elements with low contrast

    32 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 (1 element)

    ARIA input fields must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

  • 48 images without alt text

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

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

  • 1 form field without a label

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

1 checks passed
  • 48 automated accessibility rules passed

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

SEO

3 to fixGoogle 8590
  • Structured data has 1 problem

    Structured data found (Pharmacy, Store and WebSite) but with 1 problem, for example “WebSite: missing name”.

  • No XML sitemap

    No XML sitemap at https://www.fmiligrama.com.br/sitemap.xml, so Google discovers your pages only by following links.

  • 10 links crawlers can't follow

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

  • 169 internal links, 9 external

    The homepage links to 169 pages on fmiligrama.com.br and 9 external pages.

6 checks passed
  • Meta description: 155 characters

    Your meta description is 155 characters: “Há mais de 21 anos, a Miligrama é referência em manipulação de medicamentos com qualidade farmacêutica. Fórmulas person…”.

  • One H1 headline

    Your main headline reads: “Farmácia de Manipulação Miligrama”.

  • Title: 57 characters

    Your title is a healthy 57 characters: “Farmácia Miligrama | 21 Anos de excelência em Manipulação”.

  • Canonical URL set

    The canonical URL is https://www.fmiligrama.com.br/.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • robots.txt in place

    robots.txt is in place.

AI search readiness

100
  • No llms.txt

    There is no https://www.fmiligrama.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: 4 of 6 facts

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

  • Text is in the HTML

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

Other pages

2 to fix70
  • 1 linked page is broken

    Your homepage links to https://www.fmiligrama.com.br/busca, which answers with an error. Visitors hit a dead end and search engines drop it.

  • 2 pages without a meta description

    https://www.fmiligrama.com.br/estetica and https://www.fmiligrama.com.br/emagrecimento have no meta description, so Google writes the search snippet from whatever text it finds.

  • 11 pages slow to respond

    https://www.fmiligrama.com.br/vitrine/mais-vendidos, https://www.fmiligrama.com.br/uc-ii-40mg-60-capsulas-colageno-tipo-ii.html, https://www.fmiligrama.com.br/digere-bem-30-doses.html, https://www.fmiligrama.com.br/silimarina-cardo-mariano-200mg-120-capsulas.html, https://www.fmiligrama.com.br/silimarina-cardo-mariano-200mg-60-capsulas.html and https://www.fmiligrama.com.br/pill-food-turbinado-60-capsulas.html and 5 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 31 found) and read each the way a search engine does.

5 checks passed
  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Titles are unique

    Every page we checked has its own title.

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

Best practices

1 to fixGoogle 9293
  • 4 JavaScript errors while loading

    4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

  • Missing source maps

    Large scripts ship without source maps.

  • 1 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

2 checks passed
  • Tap targets are thumb-sized

    85 of 105 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix67
  • 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 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 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 map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

  • 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 3,134 words of copy

    The homepage carries about 3,134 words of visible text.

5 checks passed
  • 2 short forms

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

  • Social proof on the page

    Social proof on the homepage: 48 testimonial or review blocks, a star rating and 49 trust badges.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Opening hours shown

    Your opening hours are on the homepage.

  • LocalBusiness structured data

    Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.

Privacy and tracking

  • 1 cookie set on arrival

    1

    Opening the homepage sets 1 cookie (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.

  • 6 other companies contacted

    Loading the homepage contacts 6 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 fmiligrama.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
Nuxt
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 44 issues on fmiligrama.com.br, including 24 speed issues, 3 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