Tools & Wizards About Us
editorial.elsevier.com screenshot

Report Summary

  • 54

    Performance

    Renders faster than
    72% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 72

    SEO

    Google-friendlier than
    31% of websites

editorial.elsevier.com

EMSS Login

Page Load Speed

454 ms in total

First Response

19 ms

Resources Loaded

309 ms

Page Rendered

126 ms

editorial.elsevier.com screenshot

About Website

Welcome to editorial.elsevier.com homepage info - get ready to check Editorial Elsevier best content for China right away, or after learning these important things about editorial.elsevier.com

Visit editorial.elsevier.com

Key Findings

We analyzed Editorial.elsevier.com page load time and found that the first response time was 19 ms and then it took 435 ms to load all DOM resources and completely render a web page. This is an excellent result, as only 5% of websites can load faster.

Performance Metrics

editorial.elsevier.com performance score

54

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.2 s

8/100

10%

LCP (Largest Contentful Paint)

Value7.4 s

4/100

25%

SI (Speed Index)

Value5.8 s

49/100

10%

TBT (Total Blocking Time)

Value100 ms

98/100

30%

CLS (Cumulative Layout Shift)

Value0.111

87/100

15%

TTI (Time to Interactive)

Value7.2 s

51/100

10%

Network Requests Diagram

login;jsessionid=FA9A62F5D195DB5C249B6D6CB7DE4556

19 ms

tundra.css

26 ms

standard-2-3.css

15 ms

Spring.js

24 ms

dojo.js

67 ms

Our browser made a total of 21 requests to load all elements on the main page. We found that all of those requests were addressed to Editorial.elsevier.com and no external sources were called. The less responsive or slowest element that took the longest time to load (67 ms) belongs to the original domain Editorial.elsevier.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 195.6 kB (77%)

Content Size

252.9 kB

After Optimization

57.2 kB

  • HTML
  • JavaScript

In fact, the total size of Editorial.elsevier.com main page is 252.9 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. 45% of websites need less resources to load. Javascripts take 246.1 kB which makes up the majority of the site volume.

HTML Optimization

-68%

Potential reduce by 4.6 kB

  • Original 6.7 kB
  • After minification 5.9 kB
  • After compression 2.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 816 B, which is 12% 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 4.6 kB or 68% of the original size.

JavaScript Optimization

-78%

Potential reduce by 191.1 kB

  • Original 246.1 kB
  • After minification 189.4 kB
  • After compression 55.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 191.1 kB or 78% of the original size.

Requests Breakdown

Number of requests can be reduced by 11 (55%)

Requests Now

20

After Optimization

9

  • Images
  • JavaScript
  • CSS

The browser has sent 20 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Editorial 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 12 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

login;jsessionid=FA9A62F5D195DB5C249B6D6CB7DE4556

login;jsessionid=FA9A62F5D195DB5C249B6D6CB7DE4556

19 ms

tundra.css

tundra.css

26 ms

standard-2-3.css

standard-2-3.css

15 ms

Spring.js

Spring.js

24 ms

dojo.js

dojo.js

67 ms

Spring-Dojo.js

Spring-Dojo.js

38 ms

jquery-1.4.3.min.js

jquery-1.4.3.min.js

23 ms

jquery.noconflict.js

jquery.noconflict.js

24 ms

jquery.marquee.js

jquery.marquee.js

29 ms

scripts.js

scripts.js

29 ms

jquery.validate.js

jquery.validate.js

62 ms

validation.items.js

validation.items.js

32 ms

jFav_v1.0.js

jFav_v1.0.js

31 ms

jquery.form.js

jquery.form.js

33 ms

popup-js-for-select-book.js

popup-js-for-select-book.js

35 ms

dijit.css

dijit.css

26 ms

wrapper-bg.gif

wrapper-bg.gif

4 ms

header-bg.gif

header-bg.gif

5 ms

logo.gif

logo.gif

6 ms

subnav-bg.gif

subnav-bg.gif

6 ms

footer-bg.gif

footer-bg.gif

7 ms

Accessibility Review

editorial.elsevier.com accessibility score

100

Accessibility Issues

Best Practices

editorial.elsevier.com best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

editorial.elsevier.com SEO score

72

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

High

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Editorial.elsevier.com can be misinterpreted by Google and other search engines. Our service has detected that English 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 Editorial.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.

Social Sharing Optimization

editorial.elsevier.com

Open Graph description is not detected on the main page of Editorial 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: