Tools & Wizards About Us
citealert.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

citealert.com

Measuring an articles impact

Page Load Speed

4.9 sec in total

First Response

156 ms

Resources Loaded

4.6 sec

Page Rendered

191 ms

citealert.com screenshot

About Website

Click here to check amazing Citealert content for United States. Otherwise, check out these important facts you probably never knew about citealert.com

Measure an article or journal’s impact using My Research Dashboard and article level metrics, SNIP, SJR and Impact Factor.

Visit citealert.com

Key Findings

We analyzed Citealert.com page load time and found that the first response time was 156 ms and then it took 4.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

citealert.com performance score

0

Network Requests Diagram

citealert.com

156 ms

measuring-an-articles-impact

1805 ms

269842467.js

74 ms

mercutio.css

264 ms

www.elsevier.com

72 ms

Our browser made a total of 62 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Citealert.com, 39% (24 requests) were made to Cdn.elsevier.io and 21% (13 requests) were made to Elsevier.com. The less responsive or slowest element that took the longest time to load (1.8 sec) relates to the external source Elsevier.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 570.0 kB (67%)

Content Size

846.7 kB

After Optimization

276.7 kB

  • HTML
  • JavaScript
  • CSS

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

HTML Optimization

-75%

Potential reduce by 28.9 kB

  • Original 38.4 kB
  • After minification 30.9 kB
  • After compression 9.5 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.5 kB, which is 19% 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 28.9 kB or 75% of the original size.

JavaScript Optimization

-66%

Potential reduce by 508.8 kB

  • Original 766.5 kB
  • After minification 733.1 kB
  • After compression 257.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 508.8 kB or 66% of the original size.

CSS Optimization

-78%

Potential reduce by 32.4 kB

  • Original 41.8 kB
  • After minification 38.7 kB
  • After compression 9.4 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. Citealert.com needs all CSS files to be minified and compressed as it can save up to 32.4 kB or 78% of the original size.

Requests Breakdown

Number of requests can be reduced by 43 (81%)

Requests Now

53

After Optimization

10

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 53 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Citealert. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 31 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

citealert.com

citealert.com

156 ms

measuring-an-articles-impact

measuring-an-articles-impact

1805 ms

269842467.js

269842467.js

74 ms

mercutio.css

mercutio.css

264 ms

www.elsevier.com

www.elsevier.com

72 ms

main_css.css

main_css.css

193 ms

mercutio.js

mercutio.js

298 ms

twittertypeaheadjquerymin.js

twittertypeaheadjquerymin.js

181 ms

global.js

global.js

182 ms

rURL-set-cookie.js

rURL-set-cookie.js

190 ms

cookie_get.js

cookie_get.js

191 ms

satelliteLib-203157332f7df01b28142e8c867d6813bc4995aa.js

satelliteLib-203157332f7df01b28142e8c867d6813bc4995aa.js

251 ms

cart_widget.css

cart_widget.css

717 ms

cart_widget.js

cart_widget.js

844 ms

elsevier-matrix-global_1.0.1.js

elsevier-matrix-global_1.0.1.js

189 ms

history.js

history.js

191 ms

gcse-tagmanager.js

gcse-tagmanager.js

188 ms

gcse-new.js

gcse-new.js

246 ms

survey.js

survey.js

245 ms

geo2.js

geo2.js

135 ms

event

event

126 ms

gtm.js

gtm.js

186 ms

event

event

114 ms

satellite-54b996243535640015120000.js

satellite-54b996243535640015120000.js

61 ms

analytics.js

analytics.js

42 ms

rd

rd

63 ms

wordmark-elsevier.svg

wordmark-elsevier.svg

50 ms

icon-menu-hamburger.svg

icon-menu-hamburger.svg

51 ms

icon-shopping-cart.svg

icon-shopping-cart.svg

62 ms

icon-magnify-glass.svg

icon-magnify-glass.svg

337 ms

icon-social-facebook.svg

icon-social-facebook.svg

67 ms

icon-social-linkedin.svg

icon-social-linkedin.svg

73 ms

icon-social-twitter.svg

icon-social-twitter.svg

64 ms

icon-social-googleplus-2.svg

icon-social-googleplus-2.svg

67 ms

logo-relxgroup.svg

logo-relxgroup.svg

69 ms

nexussanswebpro.woff

nexussanswebpro.woff

67 ms

nexussanswebpro-bold.woff

nexussanswebpro-bold.woff

66 ms

collect

collect

32 ms

ss-gizmo.woff

ss-gizmo.woff

24 ms

WDSy9G5kYXAAH0yK4AAAA

WDSy9G5kYXAAH0yK4AAAA

5 ms

id

id

153 ms

linkid.js

linkid.js

3 ms

collect

collect

4 ms

collect

collect

53 ms

nexusserifwebpro.woff

nexusserifwebpro.woff

49 ms

nexusserifwebpro-bold.woff

nexusserifwebpro-bold.woff

48 ms

jquery-ui.js

jquery-ui.js

26 ms

__geo

__geo

63 ms

cart

cart

404 ms

modernizr.js

modernizr.js

12 ms

s-code-contents-c4bb5fab90528289cad9f273eeea71005167b85b.js

s-code-contents-c4bb5fab90528289cad9f273eeea71005167b85b.js

139 ms

foundation.js

foundation.js

70 ms

s16496269092895

s16496269092895

16 ms

foundation.offcanvas.js

foundation.offcanvas.js

8 ms

NProgress.js

NProgress.js

11 ms

spine.js

spine.js

4 ms

kubrickology.js

kubrickology.js

17 ms

lightbox.js

lightbox.js

4 ms

conversion_async.js

conversion_async.js

38 ms

50 ms

64 ms

handshake.js

handshake.js

67 ms

SEO Factors

citealert.com SEO score

0

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Citealert.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 Citealert.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

citealert.com

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