Report Summary

  • 4

    Performance

    Renders faster than
    20% of other websites

  • 63

    Accessibility

    Visual factors better than
    that of 28% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 84

    SEO

    Google-friendlier than
    53% of websites

farmacity.com.ar

Farmacity

Page Load Speed

18.6 sec in total

First Response

5.3 sec

Resources Loaded

13 sec

Page Rendered

258 ms

farmacity.com.ar screenshot

About Website

Visit farmacity.com.ar now to see the best up-to-date Farmacity content for Argentina and also check out these interesting facts you probably never knew about farmacity.com.ar

Bienvenidos a Farmacity. La salud también se contagia.

Visit farmacity.com.ar

Key Findings

We analyzed Farmacity.com.ar page load time and found that the first response time was 5.3 sec and then it took 13.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

farmacity.com.ar performance score

4

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.6 s

0/100

10%

LCP (Largest Contentful Paint)

Value25.1 s

0/100

25%

SI (Speed Index)

Value16.5 s

0/100

10%

TBT (Total Blocking Time)

Value6,850 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.366

29/100

15%

TTI (Time to Interactive)

Value25.1 s

0/100

10%

Network Requests Diagram

www.farmacity.com.ar

5330 ms

reset.css

337 ms

visual-form-builder.css

1178 ms

jquery-ui-1.9.2.min.css

503 ms

default.min.css

341 ms

Our browser made a total of 81 requests to load all elements on the main page. We found that 74% of them (60 requests) were addressed to the original Farmacity.com.ar, 5% (4 requests) were made to Platform.twitter.com and 4% (3 requests) were made to Facebook.com. The less responsive or slowest element that took the longest time to load (5.3 sec) belongs to the original domain Farmacity.com.ar.

Page Optimization Overview & Recommendations

Page size can be reduced by 376.5 kB (28%)

Content Size

1.4 MB

After Optimization

990.7 kB

In fact, the total size of Farmacity.com.ar main page is 1.4 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 50% of websites need less resources to load. Images take 939.0 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 42.5 kB

  • Original 52.7 kB
  • After minification 44.6 kB
  • After compression 10.2 kB

HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. This page needs HTML code to be minified as it can gain 8.1 kB, which is 15% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 42.5 kB or 81% of the original size.

Image Optimization

-8%

Potential reduce by 74.7 kB

  • Original 939.0 kB
  • After minification 864.3 kB

Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. Farmacity images are well optimized though.

JavaScript Optimization

-62%

Potential reduce by 151.7 kB

  • Original 245.6 kB
  • After minification 234.5 kB
  • After compression 93.9 kB

It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 151.7 kB or 62% of the original size.

CSS Optimization

-83%

Potential reduce by 107.5 kB

  • Original 129.9 kB
  • After minification 83.7 kB
  • After compression 22.4 kB

CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Farmacity.com.ar needs all CSS files to be minified and compressed as it can save up to 107.5 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 56 (71%)

Requests Now

79

After Optimization

23

The browser has sent 79 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Farmacity. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 23 to 1 for JavaScripts and from 24 to 1 for CSS and as a result speed up the page load time.

Accessibility Review

farmacity.com.ar accessibility score

63

Accessibility Issues

Names and labels

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

farmacity.com.ar best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

farmacity.com.ar SEO score

84

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

Mobile Friendly

Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).

Impact

Issue

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    ES

  • Language Claimed

    ES

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Farmacity.com.ar can be misinterpreted by Google and other search engines. Our service has detected that Spanish is used on the page, and it matches the claimed language. Our system also found out that Farmacity.com.ar main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.

Social Sharing Optimization

Open Graph description is not detected on the main page of Farmacity. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: