5.2 sec in total
325 ms
4.5 sec
446 ms
Welcome to endocrinologo.org homepage info - get ready to check Endocrinologo best content right away, or after learning these important things about endocrinologo.org
Visit endocrinologo.orgWe analyzed Endocrinologo.org page load time and found that the first response time was 325 ms and then it took 4.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
endocrinologo.org performance score
name
value
score
weighting
Value3.7 s
29/100
10%
Value4.7 s
33/100
25%
Value5.5 s
54/100
10%
Value710 ms
41/100
30%
Value0.345
32/100
15%
Value5.7 s
68/100
10%
325 ms
1862 ms
218 ms
291 ms
268 ms
Our browser made a total of 105 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Endocrinologo.org, 59% (62 requests) were made to Fabrizioangelini.it and 24% (25 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (1.9 sec) relates to the external source Fabrizioangelini.it.
Page size can be reduced by 392.2 kB (39%)
1.0 MB
609.1 kB
In fact, the total size of Endocrinologo.org main page is 1.0 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 527.4 kB which makes up the majority of the site volume.
Potential reduce by 89.9 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 14.8 kB, which is 14% 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 89.9 kB or 84% of the original size.
Potential reduce by 29.0 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. Endocrinologo images are well optimized though.
Potential reduce by 158.6 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 158.6 kB or 68% of the original size.
Potential reduce by 114.7 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. Endocrinologo.org needs all CSS files to be minified and compressed as it can save up to 114.7 kB or 86% of the original size.
Number of requests can be reduced by 54 (52%)
103
49
The browser has sent 103 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Endocrinologo. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 26 to 1 for JavaScripts and from 14 to 1 for CSS and as a result speed up the page load time.
endocrinologo.org
325 ms
www.fabrizioangelini.it
1862 ms
style.css
218 ms
prettyPhoto.css
291 ms
style.php
268 ms
custom.css
214 ms
opera-ie-only.css
212 ms
style-buddypress.css
289 ms
styles.css
316 ms
jquery.min.js
33 ms
jquery-ui.min.js
80 ms
dynamix.min.js
436 ms
Lucida_Sans_Unicode_400.font.js
337 ms
jquery.form.min.js
276 ms
scripts.js
296 ms
wp-embed.min.js
296 ms
wp-emoji-release.min.js
118 ms
ga.js
24 ms
blank.gif
542 ms
fabrizioangelini.png
541 ms
timthumb.php
565 ms
timthumb.php
550 ms
timthumb.php
548 ms
timthumb.php
561 ms
timthumb.php
563 ms
timthumb.php
549 ms
timthumb.php
572 ms
timthumb.php
572 ms
timthumb.php
581 ms
timthumb.php
574 ms
timthumb.php
576 ms
timthumb.php
574 ms
timthumb.php
578 ms
timthumb.php
578 ms
timthumb.php
596 ms
timthumb.php
597 ms
timthumb.php
597 ms
timthumb.php
599 ms
timthumb.php
600 ms
timthumb.php
642 ms
timthumb.php
669 ms
timthumb.php
683 ms
youtube.jpg
684 ms
smallIcon-yt.png
689 ms
smallIcon-twitter.png
702 ms
smallIcon-facebook.png
745 ms
gradient-a.png
764 ms
panel-tab-a.png
782 ms
panel-tab-l.png
780 ms
panel-tab-m.png
785 ms
gradient-d.png
798 ms
search.png
839 ms
break-c.png
867 ms
button-a.png
884 ms
__utm.gif
50 ms
widgets.js
13 ms
panel-tab-r.png
361 ms
likebox.php
393 ms
header-c-custom.png
356 ms
header-d-custom.png
382 ms
break-c-custom.png
634 ms
gradient-f-light.png
623 ms
break-a.png
623 ms
button-overlay.png
618 ms
shadow-d.png
616 ms
li-arrow-drk.png
615 ms
footer-a-custom.png
615 ms
footer-m-custom.png
618 ms
E3TzvQNU166.css
47 ms
Q-OWgaJvbhn.css
30 ms
mJ3scex-8ho.css
37 ms
wYbR6_M9nOB.css
38 ms
EQVvsAj4CHs.css
51 ms
v71QAkXMWiC.css
50 ms
eaaxszj_coS.css
60 ms
q68gy-v_YMF.js
67 ms
FJmpeSpHpjS.js
94 ms
0wM5s1Khldu.js
88 ms
1bNoFZUdlYZ.js
89 ms
njO1TPvGzoR.js
93 ms
1QuX41zDRrx.js
90 ms
Oagsvfb4VWi.js
89 ms
LTv6ZK-5zxz.js
119 ms
1FCa-btixu2.js
135 ms
DVtj8v6ogQI.js
140 ms
IjqSyiwKeaX.js
141 ms
n6VgtouijQL.js
118 ms
10454294_781718205223616_5376366018715775461_n.jpg
237 ms
safe_image.php
155 ms
102 ms
safe_image.php
57 ms
safe_image.php
276 ms
safe_image.php
68 ms
safe_image.php
54 ms
394026_290178147710960_1647728066_n.jpg
51 ms
10275978_1010294092366025_1762249984147716109_n.jpg
73 ms
10363380_1009816772413757_5615923493809188256_n.jpg
94 ms
wL6VQj7Ab77.png
25 ms
s7jcwEQH7Sx.png
34 ms
K00K-UgnsKu.png
34 ms
QDwYpIaRyfG.png
23 ms
I6-MnjEovm5.js
114 ms
pQrUxxo5oQp.js
114 ms
gallery-navigation.png
109 ms
iubenda_cs.js
17 ms
endocrinologo.org 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
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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.
endocrinologo.org best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Issues were logged in the Issues panel in Chrome Devtools
endocrinologo.org 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
ES
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Endocrinologo.org can be misinterpreted by Google and other search engines. Our service has detected that Spanish is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Endocrinologo.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.
endocrinologo.org
Open Graph description is not detected on the main page of Endocrinologo. 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: