4.5 sec in total
415 ms
3.9 sec
177 ms
Click here to check amazing Medline content for Cote d'Ivoire. Otherwise, check out these important facts you probably never knew about medline.ch
Die vereinfachte, zeitsparende Suche in der Medline-Datenbank durch vordefinierte Suchstrategien mit klinischem Fokus
Visit medline.chWe analyzed Medline.ch page load time and found that the first response time was 415 ms and then it took 4.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
medline.ch performance score
name
value
score
weighting
Value5.9 s
4/100
10%
Value7.7 s
3/100
25%
Value10.0 s
9/100
10%
Value3,550 ms
1/100
30%
Value0.031
100/100
15%
Value14.1 s
10/100
10%
415 ms
1634 ms
101 ms
194 ms
197 ms
Our browser made a total of 156 requests to load all elements on the main page. We found that 29% of them (46 requests) were addressed to the original Medline.ch, 12% (18 requests) were made to Ib.adnxs.com and 5% (8 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Medline.ch.
Page size can be reduced by 397.5 kB (67%)
593.7 kB
196.2 kB
In fact, the total size of Medline.ch main page is 593.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. 60% of websites need less resources to load. Javascripts take 454.6 kB which makes up the majority of the site volume.
Potential reduce by 64.1 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 64.1 kB or 79% of the original size.
Potential reduce by 752 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. Medline images are well optimized though.
Potential reduce by 291.0 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 291.0 kB or 64% of the original size.
Potential reduce by 41.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. Medline.ch needs all CSS files to be minified and compressed as it can save up to 41.7 kB or 86% of the original size.
Number of requests can be reduced by 131 (89%)
148
17
The browser has sent 148 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Medline. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 51 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
medline.ch
415 ms
www.medline.ch
1634 ms
fachportal_ns0.css
101 ms
rc.css
194 ms
rc0.css
197 ms
template_au.css
208 ms
template_0.css
210 ms
template.css
210 ms
template_0.css
212 ms
jquery-1.4.2.min.js
576 ms
jquery.cookie.js
293 ms
jquery.cycle.all.js
523 ms
middle.js
309 ms
search.js
310 ms
subnavigation.js
314 ms
rightSpecifik.js
386 ms
func.GoTo.js
410 ms
class.Session.js
416 ms
spcjs.php
136 ms
spc.php
80 ms
fl.js
19 ms
analytics.js
6 ms
HONConduct723834.jpg
236 ms
show_image.php
102 ms
spacer.gif
109 ms
spacer.gif
107 ms
zoom-in.png
107 ms
zoom-out.png
108 ms
show_image.php
98 ms
show_image.php
194 ms
show_image.php
233 ms
show_image.php
238 ms
show_image.php
239 ms
previews_page.gif
236 ms
next_page.gif
240 ms
lg.php
14 ms
bounce
10 ms
ttj
108 ms
trk.js
38 ms
click
83 ms
post_edgeinitiative
273 ms
ca
37 ms
jload
79 ms
modernizr_2.8.3_ec185bb44fe5e6bf7455d6e8ef37ed0e_no-classes.js
44 ms
dfa7banner_flash_html_inpage_rendering_lib_200_98.js
35 ms
lidar.js
24 ms
async_usersync.html
12 ms
ca
10 ms
async_usersync
9 ms
cap
41 ms
mon
20 ms
tab1.gif
109 ms
tab1_end.gif
129 ms
tab1.gif
109 ms
tab1_end.gif
108 ms
top_nav.gif
109 ms
left_back_white.gif
106 ms
left_back.gif
224 ms
left_back_trans.gif
222 ms
u.php
247 ms
pixel
25 ms
match-user.html
69 ms
gif
24 ms
sync
219 ms
tap.php
12 ms
dt
25 ms
left.gif
207 ms
mapuid
20 ms
setuid
26 ms
pixel
17 ms
plusone.js
59 ms
post1.gif
195 ms
line_point1.gif
195 ms
ttj
29 ms
lg.php
26 ms
mapuid
24 ms
ttj
89 ms
sfp-user-match.js
34 ms
cb=gapi.loaded_0
9 ms
cb=gapi.loaded_1
27 ms
fastbutton
85 ms
match.sharethrough.com
33 ms
postmessageRelay
63 ms
click
42 ms
post_edgeinitiative
89 ms
ca
12 ms
jload
70 ms
cb=gapi.loaded_0
36 ms
cb=gapi.loaded_1
35 ms
grlryt2bdKIyfMSOhzd1eA.woff
56 ms
3193398744-postmessagerelay.js
49 ms
rpc:shindig_random.js
47 ms
dfa7banner_flash_html_inpage_rendering_lib_200_119.js
28 ms
mapuid
24 ms
async_usersync
21 ms
ca
26 ms
cb=gapi.loaded_0
33 ms
sync
31 ms
Pug
34 ms
bd
46 ms
dpixel
33 ms
usersync.aspx
33 ms
tap.php
30 ms
cap
28 ms
mon
25 ms
post.gif
104 ms
setuid
17 ms
pxj
14 ms
dt
20 ms
sd
24 ms
ttj
12 ms
lg.php
17 ms
ttj
100 ms
setuid
10 ms
click
22 ms
post_edgeinitiative
92 ms
jload
53 ms
async_usersync
24 ms
cap
23 ms
mon
21 ms
right_back_trans.gif
99 ms
line_point2.gif
108 ms
sync
19 ms
sync
179 ms
sync
18 ms
1x1.gif
29 ms
match
18 ms
right_back.gif
106 ms
grey_tree.gif
105 ms
dt
22 ms
ttj
13 ms
lg.php
20 ms
ttj
130 ms
lr.gif
5 ms
click
26 ms
post_edgeinitiative
145 ms
ca
19 ms
jload
67 ms
trpx.gif
106 ms
ca
12 ms
ca
61 ms
async_usersync
15 ms
ca
25 ms
UserMatchAppnexus.ashx
61 ms
rtcsync.php
167 ms
serve
78 ms
78 ms
um
81 ms
apnxs
76 ms
5007498867967563260
91 ms
cap
54 ms
mon
53 ms
xuid
18 ms
dt
91 ms
ecc
19 ms
setuid
71 ms
medline.ch 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
Image elements do not have [alt] attributes
Form elements do not have associated labels
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
medline.ch 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
Browser errors were logged to the console
Page has valid source maps
Issues were logged in the Issues panel in Chrome Devtools
medline.ch SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
DE
DE
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Medline.ch can be misinterpreted by Google and other search engines. Our service has detected that German is used on the page, and it matches the claimed language. Our system also found out that Medline.ch main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
medline.ch
Open Graph description is not detected on the main page of Medline. 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: