Website review, no card needed

farmaoliva.com.py logo

farmaoliva.com.py website review

Visit site (opens in a new tab)Reviewed 22 October 202670 issues · 105 checks

This review found 70 issues worth fixing on farmaoliva.com.py, 33 of them high impact, across 105 checks. The most urgent: render-blocking 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
3.0 s2.6 sMay 2Oct 172.6 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20262.8 s
May 9, 20262.7 s
May 16, 20262.6 s
May 23, 20262.7 s
May 30, 20262.7 s
Jun 6, 20262.7 s
Jun 13, 20262.8 s
Jun 20, 20262.8 s
Jun 27, 20262.8 s
Jul 4, 20262.7 s
Jul 11, 20262.7 s
Jul 18, 20262.7 s
Jul 25, 20262.7 s
Aug 1, 20262.7 s
Aug 8, 20262.7 s
Aug 15, 20262.7 s
Aug 22, 20262.7 s
Aug 29, 20262.6 s
Sep 5, 20262.8 s
Sep 12, 20262.8 s
Sep 19, 20262.8 s
Sep 26, 20262.9 s
Oct 3, 20262.8 s
Oct 10, 20262.7 s
Oct 17, 20262.6 s
Real-visitor tap response (INP)75th percentile, phones
148 ms131 msMay 2Oct 17145 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026146 ms
May 9, 2026146 ms
May 16, 2026144 ms
May 23, 2026142 ms
May 30, 2026142 ms
Jun 6, 2026142 ms
Jun 13, 2026144 ms
Jun 20, 2026142 ms
Jun 27, 2026141 ms
Jul 4, 2026139 ms
Jul 11, 2026138 ms
Jul 18, 2026140 ms
Jul 25, 2026142 ms
Aug 1, 2026143 ms
Aug 8, 2026144 ms
Aug 15, 2026144 ms
Aug 22, 2026143 ms
Aug 29, 2026135 ms
Sep 5, 2026133 ms
Sep 12, 2026136 ms
Sep 19, 2026136 ms
Sep 26, 2026143 ms
Oct 3, 2026146 ms
Oct 10, 2026145 ms
Oct 17, 2026145 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 farmaoliva.com.py (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. farmaoliva.com.py at 1.3 s1.3 s
  2. farmaoliva.com.py at 2.6 s2.6 s
  3. farmaoliva.com.py at 3.8 s3.8 s
  4. farmaoliva.com.py at 5.1 s5.1 s
  5. farmaoliva.com.py at 6.4 s6.4 s
  6. farmaoliva.com.py at 7.7 s7.7 s
  7. farmaoliva.com.py at 9.0 s9.0 s
  8. farmaoliva.com.py at 10.2 s10.2 s

Speed

15 to fix26
  • Render-blocking requests

    3.0 s

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

  • Font display

    2.2 s

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 2.2 s).

  • 11,817 HTML elements

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

  • Mobile performance score: 26

    26/100

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

  • Main-thread work: 5.0 s

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

  • Improve image delivery

    600 ms · 2.4 MB

    17 images could be 2.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 600 ms faster on a phone.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Facebook and Google Analytics and others), adding 4.6 MB and 349 ms of main-thread time.

  • Reduce unused CSS

    600 ms · 134 KiB

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

  • 8 long tasks on the main thread

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

  • Reduce initial server response time

    523 ms

    Reduce initial server response time. Google estimates savings of 523 ms on a phone.

  • Document request latency

    500 ms

    The HTML itself could arrive about 500 ms sooner: redirects, a slow server response or missing compression delay everything after it.

  • dattamax.com adds 0 ms

    0 ms

    dattamax.com costs a phone 0 ms of main-thread work and 4.0 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.

  • Reduce unused JavaScript

    308 KiB

    About 308 KiB of JavaScript is downloaded but never used on this page.

  • Google Tag Manager adds 199 ms

    199 ms

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

  • Server response: 623 ms

    623 ms

    Your server takes 623 ms to send the HTML. Google recommends under 600 ms; everything else waits for it.

  • Use efficient cache lifetimes

    218 KiB

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

  • Legacy JavaScript

    12 KiB

    Polyfills for old browsers add 12 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.

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 INP: 1.7 s

    1.7 s

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

  • Real-user CLS: 0.41

    0.41

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

  • Speed Index: 12.6 s

    12.6 s

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

  • Time to Interactive: 18.0 s

    18.0 s

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

  • Largest Contentful Paint: 6.6 s

    6.6 s

    Your largest element takes 6.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image. Most of its time is element render delay (2.8 s).

  • Cumulative Layout Shift: 0.408

    0.408

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

  • First Contentful Paint: 3.5 s

    3.5 s

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

  • Total Blocking Time: 638 ms

    638 ms

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

  • Real-user LCP: 3.0 s

    3.0 s

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

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

    1.2 s

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

  • 17 images without width and height

    17 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-10-17, real Chrome visitors' tap response (inp) went from 146 ms to 145 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Largest content (LCP) held steady for real visitors

    -2%

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

Images and page weight

5 to fix18
  • Page weight: 5.4 MB in 103 requests

    5.4 MB

    Your homepage downloads 5.4 MB in 103 requests on a phone: images 4.1 MB (48), scripts 787 KiB (11) and fonts 219 KiB (7). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    web-03.png weighs 1.3 MB. On a phone connection a single image that size takes seconds.

  • 4 images far larger than shown

    1.5 MB

    4 images are downloaded at several times the size a phone draws them, for example web-03.png at 3,583 px wide, shown at 360 px. Resized copies would save about 1.5 MB.

  • 4 images in older formats

    4 images (2.0 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.

  • 3 images below the first screen load straight away

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

  • About 1.5 g of CO₂ per visit

    1.52 g

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

Accessibility

20 to fixGoogle 5278
  • Hidden but focusable

    168 elements hidden from screen readers can still receive keyboard focus.

  • Certain ARIA roles must contain particular children (11 elements)

    Certain ARIA roles must contain particular children: 11 elements on the page fail this check, rated critical by axe-core.

  • Invalid ARIA attributes

    9 elements use ARIA attributes their role does not allow, which confuses screen readers.

  • ARIA attributes must conform to valid values (2 elements)

    ARIA attributes must conform to valid values: 2 elements on the page fail this check, rated critical by axe-core.

  • 1 button without a name

    1 button has 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 (13 elements)

    Interactive controls must not be nested: 13 elements on the page fail this check, rated serious by axe-core.

  • ARIA input fields must have an accessible name (10 elements)

    ARIA input fields must have an accessible name: 10 elements on the page fail this check, rated serious by axe-core.

  • 6 text elements with low contrast

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

  • ARIA toggle fields must have an accessible name (4 elements)

    ARIA toggle fields must have an accessible name: 4 elements on the page fail this check, rated serious by axe-core.

  • 2 images without alt text

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

  • 352 form fields without a label

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

  • Heading levels should only increase by one (1 element)

    Heading levels should only increase by one: 1 element on the page fails 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.

  • Zoom is disabled

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

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

  • 37 links without text

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

  • Elements marked as presentational should be consistently ignored (9 elements)

    Elements marked as presentational should be consistently ignored: 9 elements on the page fail this check, rated minor by axe-core.

  • Headings should not be empty (4 elements)

    Headings should not be empty: 4 elements on the page fail this check, rated minor by axe-core.

1 checks passed
  • 52 automated accessibility rules passed

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

SEO

5 to fixGoogle 8373
  • No H1 headline

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

  • 353 links crawlers can't follow

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

  • Title is short (10 characters)

    Your title is only 10 characters: “Farmaoliva”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

  • No X (Twitter) card tag

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

  • 361 internal links, 4 external

    The homepage links to 361 pages on farmaoliva.com.py and 4 external pages.

4 checks passed
  • Meta description: 148 characters

    Your meta description is 148 characters: “Encontrá de TODO en Farmaoliva desde la comodidad de tu casa. ¡Aprovecha mayores descuentos en la WEB todos los días! ¡…”.

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

  • XML sitemap found

    Your XML sitemap is reachable at https://www.farmaoliva.com.py/sitemap.xml.

AI search readiness

2 to fix75
  • 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.

  • Some text only appears after JavaScript runs

    55%

    The HTML your server sends has 1,690 of the 3,071 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.

  • No llms.txt

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

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

Other pages

3 to fix86
  • 10 pages share 2 titles

    / and https://www.farmaoliva.com.py/sucursales all use the title “Farmaoliva”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

  • 13 pages share a meta description

    https://www.farmaoliva.com.py/preguntas-frecuentes, https://www.farmaoliva.com.py/como-comprar, https://www.farmaoliva.com.py/sucursales, https://www.farmaoliva.com.py/blog, https://www.farmaoliva.com.py/carrito and https://www.farmaoliva.com.py/catalogo/cuidado-personal-c1 and 7 others use the same meta description. A description written for each page earns more clicks.

  • 2 pages without an H1

    https://www.farmaoliva.com.py/sucursales and https://www.farmaoliva.com.py/carrito have no <h1> headline, so visitors and search engines get no clear main topic.

  • 2 pages slow to respond

    https://www.farmaoliva.com.py/sucursales and https://www.farmaoliva.com.py/carrito took over 3 s to send their HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 188 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 13 pages that loaded have a meta description.

  • 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

3 to fixGoogle 5488
  • 3 third-party cookies

    3 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 (Not Found)”.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

  • Missing source maps

    Large scripts ship without source maps.

2 checks passed
  • Tap targets are thumb-sized

    244 of 286 tappable elements near the top are at least 24 px.

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

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

3 checks passed
  • 2 short forms

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

  • Analytics in place

    Analytics detected: Google Analytics.

  • Direct contact links

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

Privacy and tracking

1 to fix
  • 5 trackers load before any consent

    5

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

  • 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 farmaoliva.com.py, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Analytics
Google Analytics

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 70 issues on farmaoliva.com.py, including 28 speed issues, 5 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