3.2 sec in total
291 ms
2.6 sec
245 ms
Visit todo-en-salud.com now to see the best up-to-date Todo En Salud content for Colombia and also check out these interesting facts you probably never knew about todo-en-salud.com
Información médica, glosario, vademecum, consejos y tips para conocer más sobre el cuerpo humano, sus enfermedades y tratamientos efectivos
Visit todo-en-salud.comWe analyzed Todo-en-salud.com page load time and found that the first response time was 291 ms and then it took 2.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster. This domain responded with an error, which can significantly jeopardize Todo-en-salud.com rating and web reputation
todo-en-salud.com performance score
name
value
score
weighting
Value1.8 s
89/100
10%
Value1.8 s
98/100
25%
Value7.3 s
28/100
10%
Value4,980 ms
0/100
30%
Value0.095
91/100
15%
Value14.7 s
8/100
10%
291 ms
95 ms
160 ms
367 ms
7 ms
Our browser made a total of 127 requests to load all elements on the main page. We found that 8% of them (10 requests) were addressed to the original Todo-en-salud.com, 20% (26 requests) were made to Tpc.googlesyndication.com and 9% (12 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (1.4 sec) relates to the external source Ads62898.hotwords.com.
Page size can be reduced by 293.8 kB (30%)
970.7 kB
676.9 kB
In fact, the total size of Todo-en-salud.com main page is 970.7 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. Images take 439.4 kB which makes up the majority of the site volume.
Potential reduce by 53.3 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 53.3 kB or 75% of the original size.
Potential reduce by 6.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. Todo En Salud images are well optimized though.
Potential reduce by 168.2 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 168.2 kB or 44% of the original size.
Potential reduce by 65.5 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. Todo-en-salud.com needs all CSS files to be minified and compressed as it can save up to 65.5 kB or 82% of the original size.
Number of requests can be reduced by 60 (50%)
121
61
The browser has sent 121 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Todo En Salud. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 50 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
todo-en-salud.com
291 ms
style.css
95 ms
pagenavi-css.css
160 ms
jetpack.css
367 ms
adsbygoogle.js
7 ms
widgets.js
83 ms
all.js
29 ms
devicepx-jetpack.js
54 ms
wp-embed.min.js
184 ms
jquery.js
478 ms
jquery-migrate.min.js
184 ms
ec-stars-rating.js
185 ms
e-201609.js
5 ms
16066.js
108 ms
show.jsp
1390 ms
wp-emoji-release.min.js
207 ms
analytics.js
46 ms
header.png
261 ms
cse.js
63 ms
ca-pub-1328036290525557.js
71 ms
zrt_lookup.html
82 ms
show_ads_impl.js
141 ms
collect
51 ms
jsapi
32 ms
buttons.js
245 ms
310 ms
xd_arbiter.php
37 ms
xd_arbiter.php
157 ms
default+es.css
109 ms
default.css
31 ms
default+es.I.js
87 ms
default.css
174 ms
ads
519 ms
osd.js
35 ms
ads
407 ms
ads
154 ms
ads
126 ms
ads
339 ms
sdk.js
29 ms
ads
435 ms
min-inimage.js
24 ms
abg.js
33 ms
g.gif
12 ms
16066.js
7 ms
kwServe
166 ms
m_js_controller.js
5 ms
s
21 ms
googlelogo_color_112x36dp.png
146 ms
imgad
88 ms
nessie_icon_tiamat_white.png
99 ms
x_button_blue2.png
101 ms
4904022824420069044
25 ms
3135685056959092912
26 ms
17064279322510032531
39 ms
1945211429114966941
38 ms
8305614128825173667
31 ms
13447280090808563051
31 ms
10900954829776566795
27 ms
10038440764447793715
31 ms
867805944983136804
39 ms
7749379126422367397
43 ms
10812114230591914397
40 ms
13987805963897167793
40 ms
5364446850969686980
41 ms
10837720542841117339
51 ms
10069615232436528021
40 ms
4645815976957016789
42 ms
7473651000064142249
43 ms
12329779158817203744
43 ms
2943370436935697562
44 ms
1882080966195763331
45 ms
powered-by-google.png
45 ms
7-1I540iwtLQZRDhQUP9L-vt70m6ZeYTcveWqB03r34.js
2 ms
script.js
78 ms
main.js
78 ms
beacon.js
56 ms
sync
5 ms
plusone.js
204 ms
button.831500944bc3eb7ea5276ccdc3f71d2e.js
195 ms
base.js
94 ms
cb=gapi.loaded_0
24 ms
cb=gapi.loaded_1
50 ms
fastbutton
106 ms
b
21 ms
b
6 ms
postmessageRelay
70 ms
follow_button.6a78875565a912489e9aef879c881358.es.html
61 ms
tweet_button.6a78875565a912489e9aef879c881358.es.html
84 ms
cb=gapi.loaded_0
50 ms
cb=gapi.loaded_1
42 ms
like.php
213 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
92 ms
api.js
52 ms
core:rpc:shindig.random:shindig.sha1.js
92 ms
2536007149-postmessagerelay.js
69 ms
info.json
116 ms
__tt.gif
24 ms
page.php
236 ms
async-ads.js
91 ms
google_custom_search_watermark.gif
53 ms
qbEHJxuVK5u.js
93 ms
small-logo.png
28 ms
search_box_icon.png
28 ms
clear.png
59 ms
nav_logo114.png
29 ms
LVx-xkvaJ0b.png
66 ms
ui
69 ms
q8sTdrz2ueE.css
9 ms
_rx8naC75Dy.js
21 ms
t-KLv3gqZy0.js
17 ms
O6mvGXq05ee.js
44 ms
426082_324697120910779_230998943_n.jpg
75 ms
262940_209692619077897_210421_n.jpg
29 ms
11899899_966643363382207_5538394382069788068_n.jpg
38 ms
11221888_1503104506681925_873121103489096650_n.jpg
35 ms
12342690_483148891892509_5008717181539382700_n.jpg
36 ms
1917924_956808951060083_201222910937695593_n.jpg
35 ms
1935428_10207571870962059_7207141943475281832_n.jpg
35 ms
10308197_782741828403739_883393038674672404_n.jpg
37 ms
12745956_1502819766692508_9163872826719027658_n.jpg
41 ms
wL6VQj7Ab77.png
13 ms
CSXXCvknpgK.png
15 ms
jot.html
35 ms
R9a_DtVRZgv.js
9 ms
cUDgRFxaoIk.js
8 ms
0JBr1QHp8Gi.js
9 ms
kDOzhTr2W91.js
12 ms
todo-en-salud.com accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
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
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
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.
todo-en-salud.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
todo-en-salud.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
robots.txt is not valid
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
ES
ES
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Todo-en-salud.com 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 Todo-en-salud.com 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.
todo-en-salud.com
Open Graph description is not detected on the main page of Todo En Salud. 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: