Website review, no card needed

fdc.com.br logo

fdc.com.br website review

Visit site (opens in a new tab)Reviewed 23 October 202625 issues · 81 checks

This review found 25 issues worth fixing on fdc.com.br, 9 of them high impact, across 81 checks. The most urgent: reduce unused JavaScript. 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.2 s1.6 sMay 2Oct 171.9 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20262.1 s
May 9, 20262.1 s
May 16, 20261.9 s
May 23, 20261.7 s
May 30, 20261.7 s
Jun 6, 20261.6 s
Jun 13, 20261.6 s
Jun 20, 20261.6 s
Jun 27, 20261.6 s
Jul 4, 20261.7 s
Jul 11, 20261.8 s
Jul 18, 20261.8 s
Jul 25, 20261.9 s
Aug 1, 20261.9 s
Aug 8, 20261.8 s
Aug 15, 20261.9 s
Aug 22, 20262.0 s
Aug 29, 20262.0 s
Sep 5, 20262.0 s
Sep 12, 20262.0 s
Sep 19, 20262.0 s
Sep 26, 20262.0 s
Oct 3, 20262.0 s
Oct 10, 20261.9 s
Oct 17, 20261.9 s
Real-visitor tap response (INP)75th percentile, phones
184 ms134 msMay 2Oct 17178 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026141 ms
May 9, 2026142 ms
May 16, 2026140 ms
May 23, 2026141 ms
May 30, 2026145 ms
Jun 6, 2026143 ms
Jun 13, 2026147 ms
Jun 20, 2026151 ms
Jun 27, 2026150 ms
Jul 4, 2026152 ms
Jul 11, 2026152 ms
Jul 18, 2026149 ms
Jul 25, 2026145 ms
Aug 1, 2026146 ms
Aug 8, 2026145 ms
Aug 15, 2026145 ms
Aug 22, 2026153 ms
Aug 29, 2026154 ms
Sep 5, 2026168 ms
Sep 12, 2026173 ms
Sep 19, 2026164 ms
Sep 26, 2026163 ms
Oct 3, 2026155 ms
Oct 10, 2026156 ms
Oct 17, 2026178 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 fdc.com.br (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. fdc.com.br at 2.3 s2.3 s
  2. fdc.com.br at 4.7 s4.7 s
  3. fdc.com.br at 7.0 s7.0 s
  4. fdc.com.br at 9.4 s9.4 s
  5. fdc.com.br at 11.7 s11.7 s
  6. fdc.com.br at 14.0 s14.0 s
  7. fdc.com.br at 16.4 s16.4 s
  8. fdc.com.br at 18.7 s18.7 s

Speed

7 to fix56
  • Reduce unused JavaScript

    2.9 s · 652 KiB

    About 652 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.9 s faster on a phone.

  • Mobile performance score: 56

    56/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Shopify, Clarity and nice-team.net and others), adding 1.3 MB and 431 ms of main-thread time.

  • Main-thread work: 2.6 s

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

  • Shopify adds 165 ms

    165 ms

    Shopify costs a phone 165 ms of main-thread work and 693 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.

  • 1,504 HTML elements

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

  • azurefd.net adds 21 ms

    21 ms

    azurefd.net costs a phone 21 ms of main-thread work and 316 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.

  • Use efficient cache lifetimes

    200 ms · 25 KiB

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

  • Minify JavaScript

    150 ms · 61 KiB

    61 KiB could be saved by minifying JavaScript.

  • 2 long tasks on the main thread

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

  • Reduce unused CSS

    50 KiB

    About 50 KiB of CSS is downloaded but never applied on this page.

  • Improve image delivery

    40 KiB

    2 images could be 40 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Phones get a much slower page than desktops

    Desktop scores 89 but mobile only 56. A gap that wide usually means heavy scripts and images that hit phones hardest.

  • Duplicated JavaScript

    7 KiB

    7 KiB JavaScript is shipped twice across bundles.

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

    6 ms

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

Core Web Vitals

5 to fix100
  • Largest Contentful Paint: 14.3 s

    14.3 s

    Your largest element takes 14.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “FDC Vitaminas - suplementos para rotina diária”.

  • Speed Index: 20.0 s

    20.0 s

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

  • First Contentful Paint: 5.6 s

    5.6 s

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

  • Time to Interactive: 14.4 s

    14.4 s

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

  • 14 images without width and height

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

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

    +18%

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

9 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 1.6 s

    1.6 s

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

  • Real-user INP: 195 ms

    195 ms

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

  • Real-user CLS: 0.01

    0.01

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

  • Real-user FCP: 1.4 s

    1.4 s

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

  • Real-user TTFB: 558 ms

    558 ms

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

  • Largest content (LCP) got 11% faster for real visitors

    -11%

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

  • Cumulative Layout Shift: 0

    0

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

  • Total Blocking Time: 45 ms

    45 ms

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

Images and page weight

2 to fix75
  • Page weight: 3.5 MB in 356 requests

    3.5 MB

    Your homepage downloads 3.5 MB in 356 requests on a phone: other files 1.4 MB (242), scripts 1.1 MB (73) and images 614 KiB (15). Under 2 MB keeps phones on slow connections fast.

  • 1 image far larger than shown

    34 KiB

    1 image is downloaded at several times the size a phone draws it, for example fdc-logo-header-pro.webp at 801 px wide, shown at 161 px. Resized copies would save about 34 KiB.

  • 1 image in older formats

    1 image (54 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.0 g of CO₂ per visit

    1.00 g

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

1 checks passed
  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

Accessibility

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

  • 5 tap targets too small

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

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

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

  • 33 links without text

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

  • 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 41 images in the HTML carry an alt attribute.

  • 51 automated accessibility rules passed

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

SEO

1 to fixGoogle 10096
  • Structured data has 1 problem

    Structured data found (Organization and WebSite) but with 1 problem, for example “Organization: logo is not an absolute URL ("//fdc.com.br/cdn/shop/t/162/assets/fdc-favicon.png?v=95…”.

  • 154 internal links, 2 external

    The homepage links to 154 pages on fdc.com.br and 2 external pages.

7 checks passed
  • Meta description: 160 characters

    Your meta description is 160 characters: “Encontre na FDC Vitaminas uma ampla variedade de suplementos vitamínicos e nutricionais para promover sua saúde e bem-e…”.

  • One H1 headline

    Your main headline reads: “FDC Vitaminas — Vitaminas e Suplementos para a sua rotina diária”.

  • Title: 50 characters

    Your title is a healthy 50 characters: “FDC Vitaminas | Vitaminas e Suplementos há 66 anos”.

  • Canonical URL set

    The canonical URL is https://fdc.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 and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://fdc.com.br/sitemap.xml.

AI search readiness

100
4 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 sameAs (social profiles); description and contact details would complete it.

  • Text is in the HTML

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

  • llms.txt published

    The site publishes https://fdc.com.br/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

1 to fix95
  • 1 link to non-canonical URLs

    Your homepage links to 1 page by a URL that isn't its canonical one, for example https://fdc.com.br/products/complexo-b-100-cps, whose canonical is https://fdc.com.br/products/complexo-b-completo-100-comprimidos. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 37 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.

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

Best practices

2 to fixGoogle 9687
  • 9 small tap targets

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

  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Unexpected token ','”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix83
  • 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 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 771 words of copy

    The homepage carries about 771 words of visible text.

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Contact us”.

  • 7 short forms

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

  • Social proof on the page

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

  • Analytics in place

    Analytics detected: Microsoft Clarity.

  • Direct contact links

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

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

  • 17 cookies set on arrival

    17

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

  • 30 other companies contacted

    Loading the homepage contacts 30 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 fdc.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

E-commerce
Shopify
Analytics
Microsoft Clarity

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 25 issues on fdc.com.br, including 12 speed issues, 1 SEO issue and 1 conversion gap. 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