18 sec in total
424 ms
16.1 sec
1.4 sec
Welcome to efarma.it homepage info - get ready to check EFarma best content for Italy right away, or after learning these important things about efarma.it
Su eFarma.com trovi Farmaci, Integratori, Cosmetici, Veterinari, Omeopatici e altro ✔ Spedizione in 24/72h in tutta Italia ✔ Prezzi scontati e offerte!
Visit efarma.itWe analyzed Efarma.it page load time and found that the first response time was 424 ms and then it took 17.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster.
efarma.it performance score
name
value
score
weighting
Value3.3 s
41/100
10%
Value19.5 s
0/100
25%
Value15.4 s
0/100
10%
Value9,370 ms
0/100
30%
Value0.149
76/100
15%
Value41.6 s
0/100
10%
424 ms
771 ms
439 ms
439 ms
437 ms
Our browser made a total of 77 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Efarma.it, 79% (61 requests) were made to Efarma.com and 6% (5 requests) were made to App2.salesmanago.pl. The less responsive or slowest element that took the longest time to load (1.7 sec) relates to the external source Efarma.com.
Page size can be reduced by 1.2 MB (33%)
3.5 MB
2.4 MB
In fact, the total size of Efarma.it main page is 3.5 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. 70% of websites need less resources to load. Javascripts take 2.7 MB which makes up the majority of the site volume.
Potential reduce by 492.7 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. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 492.7 kB or 87% of the original size.
Potential reduce by 0 B
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. EFarma images are well optimized though.
Potential reduce by 658.8 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 658.8 kB or 25% of the original size.
Potential reduce by 577 B
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. Efarma.it has all CSS files already compressed.
Number of requests can be reduced by 54 (78%)
69
15
The browser has sent 69 CSS, Javascripts, AJAX and image requests in order to completely render the main page of EFarma. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 32 to 1 for JavaScripts and from 24 to 1 for CSS and as a result speed up the page load time.
efarma.it
424 ms
www.efarma.com
771 ms
pre-header-desk_29.jpg
439 ms
pre-header-mob_28.jpg
439 ms
logo.svg
437 ms
920891734_1.jpg
355 ms
41545031.p01.png
275 ms
971635925-4178jpg.jpg
511 ms
require.min.js
277 ms
requirejs-min-resolver.min.js
438 ms
bundle0.min.js
344 ms
bundle1.min.js
585 ms
bundle10.min.js
635 ms
bundle11.min.js
580 ms
bundle12.min.js
705 ms
bundle13.min.js
809 ms
bundle2.min.js
830 ms
bundle3.min.js
940 ms
bundle4.min.js
935 ms
bundle5.min.js
997 ms
bundle6.min.js
1064 ms
bundle7.min.js
1168 ms
bundle8.min.js
1179 ms
bundle9.min.js
1311 ms
static.min.js
1211 ms
mixins.min.js
1355 ms
requirejs-config.min.js
1427 ms
common.min.js
1542 ms
instantsearch.min.js
1543 ms
autocomplete.min.js
1586 ms
insights.min.js
1667 ms
v2
93 ms
polyfill.min.js
560 ms
X7C0B1418611C8FF4E490F82C5920AA5F.js
107 ms
js-translation.json
339 ms
widget.js
147 ms
popups.js
806 ms
sm.js
1008 ms
widget.css
113 ms
bootstrap.min.css
479 ms
i
142 ms
open_sans.css
196 ms
1674 ms
api.js
123 ms
recaptcha__en.js
32 ms
sm_war.58ea52024bdbbea4e8e1.js
124 ms
vc.json
180 ms
vs
124 ms
err.gif
234 ms
styles-m.min.css
266 ms
instagram.svg
370 ms
SFUIText-Regular.woff
679 ms
SFUIText-Light.woff
678 ms
SFUIText-Semibold.woff
948 ms
SFUIText-Bold.woff
822 ms
sf-ui-display-semibold-58646eddcae92.woff
678 ms
corona-radiata-icons.woff
572 ms
clearpay-express-checkout.min.css
367 ms
jquery.fancybox.min.css
274 ms
form-builder.min.css
367 ms
form-render.min.css
267 ms
swiper-bundle.min.css
365 ms
autocomplete.min.css
360 ms
grid.min.css
274 ms
algolia-reset.min.css
381 ms
instantsearch.v3.min.css
373 ms
amreview.min.css
354 ms
amcforms.min.css
368 ms
ambrands.min.css
276 ms
amsociallogin.min.css
360 ms
amgdprcookie.min.css
366 ms
amblog.min.css
359 ms
amrelated.min.css
266 ms
amseokit.min.css
370 ms
amxnotif.min.css
273 ms
styles-l.min.css
390 ms
print.min.css
363 ms
efarma.it accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
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
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
efarma.it best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
efarma.it SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
Document uses legible font sizes
IT
IT
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Efarma.it can be misinterpreted by Google and other search engines. Our service has detected that Italian is used on the page, and it matches the claimed language. Our system also found out that Efarma.it 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.
efarma.it
Open Graph description is not detected on the main page of EFarma. 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: