67.8 sec in total
548 ms
45.3 sec
21.9 sec
Welcome to ees.elsevier.com homepage info - get ready to check Ees Elsevier best content for China right away, or after learning these important things about ees.elsevier.com
Elsevier's new web-based system to support the editorial process for journals which replaces the Elsevier Editorial System (EES).
Visit ees.elsevier.comWe analyzed Ees.elsevier.com page load time and found that the first response time was 548 ms and then it took 67.2 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.
ees.elsevier.com performance score
name
value
score
weighting
Value3.9 s
25/100
10%
Value5.0 s
26/100
25%
Value8.7 s
16/100
10%
Value690 ms
43/100
30%
Value0.031
100/100
15%
Value9.1 s
33/100
10%
548 ms
87 ms
5278 ms
1797 ms
3508 ms
Our browser made a total of 68 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Ees.elsevier.com, 38% (26 requests) were made to Cdn.elsevier.io and 10% (7 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (10.4 sec) relates to the external source Fonts.gstatic.com.
Page size can be reduced by 1.2 MB (66%)
1.8 MB
626.0 kB
In fact, the total size of Ees.elsevier.com main page is 1.8 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. 80% 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. Javascripts take 882.5 kB which makes up the majority of the site volume.
Potential reduce by 37.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. This page needs HTML code to be minified as it can gain 7.4 kB, which is 15% 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 37.3 kB or 77% of the original size.
Potential reduce by 331.1 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. Obviously, Ees Elsevier needs image optimization as it can save up to 331.1 kB or 55% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 593.1 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 593.1 kB or 67% of the original size.
Potential reduce by 250.8 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. Ees.elsevier.com needs all CSS files to be minified and compressed as it can save up to 250.8 kB or 82% of the original size.
Number of requests can be reduced by 42 (72%)
58
16
The browser has sent 58 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ees 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 28 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
ees.elsevier.com
548 ms
evise
87 ms
269842467.js
5278 ms
gtm.js
1797 ms
mercutio.min.css
3508 ms
matrix.css
4057 ms
jquery.min.js
3463 ms
foundation.min.js
3462 ms
mercutio.js
5189 ms
scripts-top.js
5227 ms
satelliteLib-203157332f7df01b28142e8c867d6813bc4995aa.js
7364 ms
cart_widget.css
8130 ms
cart_widget.js
7860 ms
promotions.js
8131 ms
vendor.js
7362 ms
scripts-bottom.js
7362 ms
analytics.js
5132 ms
geo2.js
3720 ms
event
5593 ms
satellite-54b996243535640015120000.js
918 ms
satellite-56fc039f64746d1da9000225.js
1385 ms
nexussanswebpro.woff
1072 ms
nexussanswebpro-bold.woff
1072 ms
collect
1456 ms
ELS_NS_Logo_2C_RGB.svg
3304 ms
EVISE_logo_W_RGB.jpg
3551 ms
wordmark-elsevier.svg
2734 ms
icon-menu-hamburger-sized.svg
3002 ms
icon-shopping-cart-sized.svg
2674 ms
icon-magnify-glass-sized.svg
3358 ms
icon-menu-hamburger-white-sized.svg
2867 ms
icon-social-facebook.svg
2620 ms
icon-social-linkedin.svg
3462 ms
icon-social-twitter.svg
3409 ms
icon-social-youtube.svg
3461 ms
logo-relxgroup.svg
3410 ms
linkid.js
2822 ms
JamcnC-4HzM
3344 ms
rd
1497 ms
ss-gizmo.woff
1799 ms
id
2601 ms
www-player-vflMqr8uC.css
1549 ms
www-embed-player.js
1822 ms
base.js
1823 ms
collect
74 ms
collect
3757 ms
nexusserifwebpro.woff
3682 ms
nexusserifwebpro-bold.woff
3682 ms
jquery-ui.js
1461 ms
iframe_api
1443 ms
_nocache
1330 ms
cart
1243 ms
s-code-contents-c4bb5fab90528289cad9f273eeea71005167b85b.js
994 ms
id
1890 ms
YubHWiCUdycrt9r0pwxtCFMvWBBxMHmgtw0lFaZzSbY.js
7310 ms
ad_status.js
7309 ms
ec.js
5569 ms
modernizr.js
2560 ms
www-widgetapi.js
9790 ms
s89837846965529
1357 ms
QHD8zigcbDB8aPfIoaupKOvvDin1pK8aKteLpeZ5c0A.ttf
10197 ms
RxZJdnzeo3R5zSexge8UUSZ2oysoEQEeKwjgmXLRnTc.ttf
10372 ms
collect
1176 ms
collect
1176 ms
collect
8940 ms
logo_ringo-vflOpz8ZI.png
8939 ms
ga-audiences
8906 ms
NProgress.js
1681 ms
ees.elsevier.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
ees.elsevier.com 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
Browser errors were logged to the console
Issues were logged in the Issues panel in Chrome Devtools
ees.elsevier.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Page is blocked from indexing
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ees.elsevier.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Ees.elsevier.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.
ees.elsevier.com
Open Graph description is not detected on the main page of Ees 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: