4.8 sec in total
387 ms
4.2 sec
185 ms
Click here to check amazing Wiki Farmaco content for Italy. Otherwise, check out these important facts you probably never knew about wikifarmaco.org
l'enciclopedia dei farmaci, degli integratori e dei rimedi omeopatici facile da consultare
Visit wikifarmaco.orgWe analyzed Wikifarmaco.org page load time and found that the first response time was 387 ms and then it took 4.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
wikifarmaco.org performance score
name
value
score
weighting
Value1.9 s
87/100
10%
Value2.0 s
97/100
25%
Value4.7 s
68/100
10%
Value70 ms
99/100
30%
Value0
100/100
15%
Value3.2 s
95/100
10%
387 ms
338 ms
373 ms
1389 ms
174 ms
Our browser made a total of 112 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Wikifarmaco.org, 12% (13 requests) were made to Static.xx.fbcdn.net and 7% (8 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (1.4 sec) relates to the external source It.wikifarmaco.org.
Page size can be reduced by 313.7 kB (51%)
618.6 kB
304.9 kB
In fact, the total size of Wikifarmaco.org main page is 618.6 kB. 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 438.4 kB which makes up the majority of the site volume.
Potential reduce by 42.4 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 42.4 kB or 73% of the original size.
Potential reduce by 8.9 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. Wiki Farmaco images are well optimized though.
Potential reduce by 259.4 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 259.4 kB or 59% of the original size.
Potential reduce by 3.1 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. Wikifarmaco.org needs all CSS files to be minified and compressed as it can save up to 3.1 kB or 74% of the original size.
Number of requests can be reduced by 66 (62%)
107
41
The browser has sent 107 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Wiki Farmaco. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 46 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
Pagina_principale
387 ms
load.php
338 ms
load.php
373 ms
load.php
1389 ms
jquery.fancybox.css
174 ms
jquery.fancybox.js
184 ms
adsbygoogle.js
6 ms
widgets.js
5 ms
load.php
369 ms
load.php
458 ms
load.php
232 ms
load.php
143 ms
search-ltr.png
167 ms
poweredby_mediawiki_88x31.png
167 ms
ca-pub-9863531382306914.js
59 ms
zrt_lookup.html
189 ms
show_ads_impl.js
80 ms
wiki.png
150 ms
all.js
36 ms
plusone.js
291 ms
load.php
267 ms
load.php
148 ms
ga.js
97 ms
ads
283 ms
osd.js
61 ms
332 ms
__utm.gif
40 ms
xd_arbiter.php
119 ms
xd_arbiter.php
148 ms
ads
240 ms
counter.js
38 ms
like.php
388 ms
t.php
191 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
135 ms
ping
294 ms
likebox.php
340 ms
cb=gapi.loaded_0
48 ms
cb=gapi.loaded_1
97 ms
fastbutton
162 ms
240 ms
adj
182 ms
beacon
182 ms
share_button.php
180 ms
m_js_controller.js
151 ms
abg.js
197 ms
follow_button.b9740740e0bcf9b0657c5b11bd4388da.it.html
49 ms
postmessageRelay
201 ms
pJeswbKZO4XwVR0035gpgvesZW2xOQ-xsNqO47m55DA.ttf
150 ms
cb=gapi.loaded_0
101 ms
cb=gapi.loaded_1
70 ms
qeKvIRsJabD.js
145 ms
LVx-xkvaJ0b.png
134 ms
favicon
149 ms
googlelogo_color_112x36dp.png
97 ms
nessie_icon_thin_arrow_big_white.png
81 ms
qeKvIRsJabD.js
153 ms
jot
278 ms
s
37 ms
x_button_blue2.png
87 ms
ebiMDO3r-8l.css
49 ms
jGc-59L_9lo.css
53 ms
q68gy-v_YMF.js
53 ms
FJmpeSpHpjS.js
90 ms
0wM5s1Khldu.js
88 ms
1bNoFZUdlYZ.js
88 ms
44 ms
0
244 ms
surly.js
285 ms
index.html
451 ms
verify_selector.js
296 ms
blank.gif
273 ms
bapi
281 ms
3193398744-postmessagerelay.js
202 ms
rpc:shindig_random.js
156 ms
400908_428568383917609_1377721106_n.png
168 ms
931243_428567923917655_534247010_n.png
154 ms
11215192_1023323014384912_4832498097361464321_n.jpg
270 ms
12049620_980001655376033_4229513523990908218_n.jpg
151 ms
1910091_10208499670998247_753897241551266846_n.jpg
149 ms
304781_485774451452462_1638994887_n.jpg
147 ms
12345398_512659485570891_1624478892358599488_n.jpg
335 ms
11205554_10204288315717244_8933162203676822934_n.jpg
228 ms
wL6VQj7Ab77.png
67 ms
s7jcwEQH7Sx.png
67 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
67 ms
cb=gapi.loaded_0
10 ms
ba.html
64 ms
pixel
20 ms
4.gif
126 ms
lidar.js
17 ms
sbhK2lTE.js
16 ms
pixel
185 ms
pixel
186 ms
cTrvNaRi.html
55 ms
verifyr.js
83 ms
4311.js
126 ms
beacon.js
92 ms
dbapi
74 ms
0
58 ms
bg.png
74 ms
adchoices.en.png
95 ms
dt
109 ms
I6-MnjEovm5.js
33 ms
pQrUxxo5oQp.js
32 ms
BreastAugmentation_300x250_logo.png
52 ms
BreastAugmentation_300x250_bg2.jpg
93 ms
BreastAugmentation_300x250_bg1.jpg
120 ms
dt
84 ms
sd
23 ms
box_19_top-right.png
36 ms
ci.png
35 ms
ui
45 ms
wikifarmaco.org accessibility score
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
Links do not have a discernible name
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.
wikifarmaco.org 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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
wikifarmaco.org SEO score
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
Tap targets are not sized appropriately
IT
IT
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Wikifarmaco.org 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 Wikifarmaco.org 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.
wikifarmaco.org
Open Graph description is not detected on the main page of Wiki Farmaco. 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: