3.2 sec in total
272 ms
2.5 sec
427 ms
Click here to check amazing Elsevier content for Germany. Otherwise, check out these important facts you probably never knew about elsevier.de
Elsevier hilft Institutionen und Fachleuten, die Wissenschaft voranzutreiben und die Gesundheitsversorgung und Performance zu verbessern.
Visit elsevier.deWe analyzed Elsevier.de page load time and found that the first response time was 272 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.
elsevier.de performance score
name
value
score
weighting
Value4.3 s
18/100
10%
Value6.8 s
7/100
25%
Value5.2 s
59/100
10%
Value320 ms
76/100
30%
Value0.925
3/100
15%
Value7.1 s
52/100
10%
272 ms
716 ms
181 ms
106 ms
277 ms
Our browser made a total of 59 requests to load all elements on the main page. We found that 58% of them (34 requests) were addressed to the original Elsevier.de, 8% (5 requests) were made to Cdn.elsevier.io and 8% (5 requests) were made to . The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Elsevier.de.
Page size can be reduced by 803.8 kB (41%)
2.0 MB
1.2 MB
In fact, the total size of Elsevier.de main page is 2.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. 45% of websites need less resources to load. Javascripts take 922.3 kB which makes up the majority of the site volume.
Potential reduce by 43.2 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 8.9 kB, which is 17% 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 43.2 kB or 83% of the original size.
Potential reduce by 52.4 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. Elsevier images are well optimized though.
Potential reduce by 626.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 626.2 kB or 68% of the original size.
Potential reduce by 82.0 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. Elsevier.de needs all CSS files to be minified and compressed as it can save up to 82.0 kB or 81% of the original size.
Number of requests can be reduced by 21 (43%)
49
28
The browser has sent 49 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Elsevier. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 15 to 1 for JavaScripts and as a result speed up the page load time.
elsevier.de
272 ms
www.elsevier.de
716 ms
wp-emoji-release.min.js
181 ms
mercutio.css
106 ms
prod.css
277 ms
font-awesome.css
282 ms
841370011.js
183 ms
jquery.min.js
79 ms
jquery-ui.min.js
129 ms
3520741559.js
279 ms
gravitate_event_tracking.js
322 ms
mercutio.min.js
653 ms
masonry.min.js
420 ms
prod.js
670 ms
jscripts-ftr2-min.js
421 ms
wp-embed.min.js
411 ms
event
106 ms
GAAAAMmQwNWJjNWVlZWI2NTNhZGJhMTg1NTlmNjVjMGViMzU=
31 ms
8DBolRdQAAAGQ3YTc0NTgwMGFjMGFkZjlkYjdlZjNkNDIxM2U2YjYw
30 ms
event
159 ms
gtm.js
202 ms
wordmark-elsevier.svg
36 ms
icon-menu-hamburger.svg
50 ms
logo-relxgroup.svg
60 ms
Fotolia_74022769_M_Ausschnitt.png
809 ms
icon1.png
129 ms
arrow_left.jpg
130 ms
201602-Hermanns.jpg
208 ms
201601_Dt.-Pflegetag.png
534 ms
201602_Generation-Elsevier.png
542 ms
arrow_right.jpg
535 ms
clinical-key.jpg
542 ms
science-direct.jpg
542 ms
journals.jpg
542 ms
elsevier-medizin.jpg
541 ms
check-me.jpg
631 ms
klinik.jpg
630 ms
vector_4.jpg
728 ms
e-library.jpg
634 ms
student_consult.jpg
634 ms
sobotta1.jpg
729 ms
vector_3.jpg
900 ms
professional-solutions1.jpg
731 ms
vector_26.jpg
905 ms
health-analytics.jpg
807 ms
vector_21.jpg
1078 ms
0201.js
130 ms
ZVB+53RhwSLClygHwkNrQ+FhL0z1znqduyPSLqezGYx25Bw+GTak7zDeDKjqtNA2R9W+nZj7SN9YUuRYKiwlvxxR2H0o0BYk7FLBrL5FecgRhduPnfwDx7JQKgAAZjYwMzViMDk5MGVjMjIxZTljZjZiNjlhYmE1M2MyZGY=
10 ms
AZXpUdkAADIzYTU3Y2ZlZmI3MmZmMDAzNWNkY2YyYzY5NGU2Njk2
8 ms
ss-gizmo.woff
71 ms
WDSy9G5kYXAAH0yK4AAAA
6 ms
fontawesome-webfont.woff
943 ms
analytics.js
298 ms
s
72 ms
t.js
91 ms
u
70 ms
collect
14 ms
collect
55 ms
s
9 ms
elsevier.de 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.
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
List items (<li>) are not contained within <ul> or <ol> parent elements.
elsevier.de 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
Page has valid source maps
elsevier.de 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
Tap targets are not sized appropriately
DE
DE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Elsevier.de 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 Elsevier.de 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.
elsevier.de
Open Graph description is not detected on the main page of Elsevier. 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: