1.4 sec in total
280 ms
993 ms
87 ms
Visit linkinghub.elsevier.com now to see the best up-to-date Linkinghub Elsevier content for China and also check out these interesting facts you probably never knew about linkinghub.elsevier.com
Visit linkinghub.elsevier.comWe analyzed Linkinghub.elsevier.com page load time and found that the first response time was 280 ms and then it took 1.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.
linkinghub.elsevier.com performance score
name
value
score
weighting
Value3.4 s
36/100
10%
Value5.2 s
23/100
25%
Value3.4 s
89/100
10%
Value340 ms
74/100
30%
Value0.009
100/100
15%
Value4.5 s
83/100
10%
280 ms
166 ms
132 ms
369 ms
177 ms
Our browser made a total of 7 requests to load all elements on the main page. We found that 86% of them (6 requests) were addressed to the original Linkinghub.elsevier.com, 14% (1 request) were made to Adobetag.com. The less responsive or slowest element that took the longest time to load (369 ms) belongs to the original domain Linkinghub.elsevier.com.
Page size can be reduced by 12.7 kB (73%)
17.5 kB
4.8 kB
In fact, the total size of Linkinghub.elsevier.com main page is 17.5 kB. This result falls within a vast category (top 1 000 000) of heavyweight, probably not optimized, and thus slow loading web pages. Only a small number of websites need less resources to load. CSS take 7.2 kB which makes up the majority of the site volume.
Potential reduce by 2.9 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 544 B, which is 13% 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 2.9 kB or 68% of the original size.
Potential reduce by 3.7 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 3.7 kB or 63% of the original size.
Potential reduce by 6.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. Linkinghub.elsevier.com needs all CSS files to be minified and compressed as it can save up to 6.0 kB or 84% of the original size.
We found no issues to fix!
4
4
The browser has sent 4 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Linkinghub Elsevier. According to our analytics all requests are already optimized.
linkinghub.elsevier.com
280 ms
index.htm
166 ms
articleLocatorNew.css
132 ms
s_code_IHUB.js
369 ms
IHUB.js
177 ms
els_logo.gif
175 ms
icon_update.gif
137 ms
linkinghub.elsevier.com accessibility score
linkinghub.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
linkinghub.elsevier.com 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
N/A
N/A
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Linkinghub.elsevier.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Linkinghub.elsevier.com 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.
linkinghub.elsevier.com
Open Graph description is not detected on the main page of Linkinghub 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: