Website review, no card needed

medimfarm.ro logo

medimfarm.ro website review

Visit site (opens in a new tab)Reviewed 23 October 202644 issues · 85 checks

This review found 44 issues worth fixing on medimfarm.ro, 20 of them high impact, across 85 checks. The most urgent: avoid multiple page redirects. 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.5 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.7 s
May 23, 20261.7 s
May 30, 20261.7 s
Jun 6, 20261.7 s
Jun 13, 20261.8 s
Jun 20, 20261.8 s
Jun 27, 20261.9 s
Jul 4, 20261.9 s
Jul 11, 20261.9 s
Jul 18, 20262.2 s
Jul 25, 20262.3 s
Aug 1, 20262.3 s
Aug 8, 20262.4 s
Aug 15, 20262.2 s
Aug 22, 20262.3 s
Aug 29, 20262.3 s
Sep 5, 20262.2 s
Sep 12, 20262.1 s
Sep 19, 20262.0 s
Sep 26, 20262.0 s
Oct 3, 20262.0 s
Oct 10, 20262.0 s
Oct 17, 20262.0 s
Real-visitor tap response (INP)75th percentile, phones
238 ms117 msMay 2Oct 17195 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026131 ms
May 9, 2026133 ms
May 16, 2026132 ms
May 23, 2026133 ms
May 30, 2026136 ms
Jun 6, 2026138 ms
Jun 13, 2026143 ms
Jun 20, 2026147 ms
Jun 27, 2026158 ms
Jul 4, 2026163 ms
Jul 11, 2026171 ms
Jul 18, 2026185 ms
Jul 25, 2026187 ms
Aug 1, 2026191 ms
Aug 8, 2026195 ms
Aug 15, 2026199 ms
Aug 22, 2026210 ms
Aug 29, 2026222 ms
Sep 5, 2026224 ms
Sep 12, 2026219 ms
Sep 19, 2026206 ms
Sep 26, 2026198 ms
Oct 3, 2026196 ms
Oct 10, 2026195 ms
Oct 17, 2026195 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 medimfarm.ro (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. medimfarm.ro at 3.9 s3.9 s
  2. medimfarm.ro at 7.8 s7.8 s
  3. medimfarm.ro at 11.7 s11.7 s
  4. medimfarm.ro at 15.6 s15.6 s
  5. medimfarm.ro at 19.5 s19.5 s
  6. medimfarm.ro at 23.4 s23.4 s
  7. medimfarm.ro at 27.4 s27.4 s
  8. medimfarm.ro at 31.3 s31.3 s

Speed

12 to fix26
  • Avoid multiple page redirects

    89.2 s

    The page goes through 2 redirects before it starts loading, costing about 89.2 s. Link and advertise the final URL directly.

  • Improve image delivery

    7.7 s · 1.9 MB

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

  • Reduce unused JavaScript

    5.6 s · 1.1 MB

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

  • Render-blocking requests

    2.7 s

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

  • Use efficient cache lifetimes

    1.6 s · 202 KiB

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

  • Main-thread work: 15.4 s

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

  • Mobile performance score: 26

    26/100

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

  • 4,011 HTML elements

    The page has 4,011 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, Facebook and Amazon Web Services and others), adding 873 KiB and 960 ms of main-thread time.

  • Google Tag Manager adds 723 ms

    723 ms

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

    600 ms · 57 KiB

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

  • 20 long tasks on the main thread

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

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

    208 ms

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

Core Web Vitals

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

  • Largest Contentful Paint: 80.7 s

    80.7 s

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

  • Speed Index: 22.1 s

    22.1 s

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

  • Time to Interactive: 84.6 s

    84.6 s

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

  • First Contentful Paint: 7.2 s

    7.2 s

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

  • Total Blocking Time: 3.3 s

    3.3 s

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

  • Real-user INP: 218 ms

    218 ms

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

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

    +48%

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

  • Real-user TTFB: 809 ms

    809 ms

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

  • 34 images without width and height

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

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

    +11%

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

4 checks passed
  • Real-user LCP: 2.1 s

    2.1 s

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

  • Real-user CLS: 0.03

    0.03

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

  • Real-user FCP: 1.5 s

    1.5 s

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

  • Cumulative Layout Shift: 0.027

    0.027

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

Images and page weight

3 to fix53
  • Page weight: 29.5 MB in 365 requests

    29.5 MB

    Your homepage downloads 29.5 MB in 365 requests on a phone: images 26.1 MB (149), scripts 2.4 MB (28) and stylesheets 406 KiB (12). Under 2 MB keeps phones on slow connections fast.

  • 35 images below the first screen load straight away

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

  • 33 images in older formats

    33 images (3.1 MB) 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.

  • About 8.4 g of CO₂ per visit

    8.37 g

    By the Sustainable Web Design model, a visit to your homepage emits about 8.37 g of CO₂e: 1004.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 are sized for phones

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

Accessibility

7 to fixGoogle 7790
  • 430 text elements with low contrast

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

  • 4 buttons without a name

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

  • 1 image without alt text

    1 image has no alt text, which hurts accessibility and image search.

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

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  • 1 form field without a label

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

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

1 checks passed
  • 45 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: 45 passed and 6 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 9285
  • No H1 headline

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

  • Meta description is long (234 characters)

    Your meta description is 234 characters; Google truncates after about 160, so the end of your pitch is cut.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

  • 420 internal links, 14 external

    The homepage links to 420 pages on medimfarm.ro and 14 external pages.

6 checks passed
  • Title: 35 characters

    Your title is a healthy 35 characters: “Acasa - Medimfarm - Farmacie Online”.

  • Canonical URL set

    The canonical URL is https://medimfarm.ro/.

  • Structured data in place

    Structured data found: Pharmacy and WebSite.

  • 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://medimfarm.ro/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.

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.

  • Text is in the HTML

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

  • llms.txt published

    The site publishes https://medimfarm.ro/llms.txt (63 KiB, 337 links), a plain-text guide to the site for AI tools.

Other pages

4 to fix81
  • 2 linked pages hidden from search

    https://medimfarm.ro/page/politica-de-retur and https://medimfarm.ro/page/transort-si-livrare are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

  • 9 pages share a meta description

    https://medimfarm.ro/product-promotions, https://medimfarm.ro/locations, https://medimfarm.ro/articles/0/sfatul-farmacistului, https://medimfarm.ro/page/plata-in-rate, https://medimfarm.ro/page/d1c17f55-6022-4702-8bea-ce8add8306e7/dai-de-veste-castigi-din-poveste and https://medimfarm.ro/page/money-back-10-la-fiecare-comanda and 3 others 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://medimfarm.ro/page/d1c17f55-6022-4702-8bea-ce8add8306e7/dai-de-veste-castigi-din-poveste, whose canonical is https://medimfarm.ro/page/d1c17f55-6022-4702-8bea-ce8add8306e7. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 6 pages without an H1

    https://medimfarm.ro/page/plata-in-rate, https://medimfarm.ro/page/d1c17f55-6022-4702-8bea-ce8add8306e7/dai-de-veste-castigi-din-poveste, https://medimfarm.ro/page/money-back-10-la-fiecare-comanda, https://medimfarm.ro/page/metode-de-plata, https://medimfarm.ro/page/politica-de-retur and https://medimfarm.ro/page/transort-si-livrare have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

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

4 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Every page has a meta description

    All 14 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has a title

    All 14 pages that loaded have a <title>.

Best practices

Google 100100
3 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

    64 of 66 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix72
  • 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 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.

  • Thin social proof

    Social proof on the homepage: 2 testimonial or review blocks. 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 opening hours

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

  • No map or directions link

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

  • About 1,156 words of copy

    The homepage carries about 1,156 words of visible text.

5 checks passed
  • 2 calls to action

    The homepage has 2 calls to action, for example “Contact” and “Ministerul Sănătății - Contact”.

  • 3 short forms

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

  • Analytics in place

    Analytics detected: Google Tag Manager and Meta Pixel.

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

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

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

  • 7 cookies set on arrival

    7

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

  • 15 other companies contacted

    Loading the homepage contacts 15 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 medimfarm.ro, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

CMS
TopManager Platform - topmanager.ro
Analytics
Google Tag Manager

Company

Founded
1991
Headquarters
Ploiești

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 medimfarm.ro, including 22 speed issues, 2 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