Tools & Wizards About Us
source.info screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

source.info

Welcome to Source | Source

Page Load Speed

18.8 sec in total

First Response

336 ms

Resources Loaded

18.2 sec

Page Rendered

257 ms

source.info screenshot

About Website

Welcome to source.info homepage info - get ready to check Source best content for Ireland right away, or after learning these important things about source.info

Visit source.info

Key Findings

We analyzed Source.info page load time and found that the first response time was 336 ms and then it took 18.5 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.

Performance Metrics

source.info performance score

0

Network Requests Diagram

source.info

336 ms

www.sourceetf.com

16100 ms

26416.js

80 ms

css_lQaZfjVpwP_oGNqdtWCSpJT1EMqXdMiU84ekLLxQnc4.css

152 ms

css_h9_I_U0fpptebKHqYGYzns-7rtnYJoLKZB9dmgjkfp4.css

231 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 Source.info, 68% (42 requests) were made to Sourceetf.com and 6% (4 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (16.1 sec) relates to the external source Sourceetf.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 234.1 kB (70%)

Content Size

332.8 kB

After Optimization

98.7 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Source.info main page is 332.8 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 180.9 kB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 21.8 kB

  • Original 29.4 kB
  • After minification 27.4 kB
  • After compression 7.6 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. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 21.8 kB or 74% of the original size.

JavaScript Optimization

-61%

Potential reduce by 109.7 kB

  • Original 180.9 kB
  • After minification 180.9 kB
  • After compression 71.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 109.7 kB or 61% of the original size.

CSS Optimization

-84%

Potential reduce by 102.7 kB

  • Original 122.5 kB
  • After minification 122.5 kB
  • After compression 19.9 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. Source.info needs all CSS files to be minified and compressed as it can save up to 102.7 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 42 (75%)

Requests Now

56

After Optimization

14

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

source.info

source.info

336 ms

www.sourceetf.com

www.sourceetf.com

16100 ms

26416.js

26416.js

80 ms

css_lQaZfjVpwP_oGNqdtWCSpJT1EMqXdMiU84ekLLxQnc4.css

css_lQaZfjVpwP_oGNqdtWCSpJT1EMqXdMiU84ekLLxQnc4.css

152 ms

css_h9_I_U0fpptebKHqYGYzns-7rtnYJoLKZB9dmgjkfp4.css

css_h9_I_U0fpptebKHqYGYzns-7rtnYJoLKZB9dmgjkfp4.css

231 ms

css_TkU9oINdB6rRnwD_ZHyFcgEQvOS1SzWpVEv1jhvNkR4.css

css_TkU9oINdB6rRnwD_ZHyFcgEQvOS1SzWpVEv1jhvNkR4.css

233 ms

css_TKy_WszwBKJVZbeT6LoBli8iSAD1sD7UsnQ6VqmlLcY.css

css_TKy_WszwBKJVZbeT6LoBli8iSAD1sD7UsnQ6VqmlLcY.css

233 ms

bootstrap.min.css

bootstrap.min.css

56 ms

css_TPrLf_qUlYRptP4GxJybwx7Pb1bGkqnFJHNIydtvgpQ.css

css_TPrLf_qUlYRptP4GxJybwx7Pb1bGkqnFJHNIydtvgpQ.css

384 ms

jquery.min.js

jquery.min.js

573 ms

jquery.once.js

jquery.once.js

233 ms

drupal.js

drupal.js

380 ms

jquery-1.11.0.min.js

jquery-1.11.0.min.js

531 ms

modernizr.min.js

modernizr.min.js

391 ms

jquery.once.js

jquery.once.js

307 ms

jquery.transform2d.js

jquery.transform2d.js

460 ms

jquery.nanoscroller.js

jquery.nanoscroller.js

529 ms

jquery.color.js

jquery.color.js

457 ms

switch.js

switch.js

457 ms

bootstrap.js

bootstrap.js

51 ms

smp_faq.js

smp_faq.js

531 ms

smp_project.js

smp_project.js

532 ms

jquery.dd.min.js

jquery.dd.min.js

535 ms

underscore.min.js

underscore.min.js

642 ms

backbone.min.js

backbone.min.js

642 ms

backbone.localStorage.js

backbone.localStorage.js

647 ms

collapsible-div.js

collapsible-div.js

647 ms

jquery.ui.widget.min.js

jquery.ui.widget.min.js

647 ms

jquery.selectBoxIt.min.js

jquery.selectBoxIt.min.js

648 ms

app.js

app.js

715 ms

countryView.js

countryView.js

717 ms

investorView.js

investorView.js

717 ms

languageView.js

languageView.js

714 ms

errorField.js

errorField.js

715 ms

googleanalytics.js

googleanalytics.js

724 ms

lang_dropdown.js

lang_dropdown.js

789 ms

bootstrap.js

bootstrap.js

730 ms

main.js

main.js

737 ms

5fe40703ec6cd77aceea43901b90ecd4.js

5fe40703ec6cd77aceea43901b90ecd4.js

181 ms

i.js

i.js

469 ms

css

css

56 ms

analytics.js

analytics.js

30 ms

3b7e4a437a037b3ac8fc8582995e1489

3b7e4a437a037b3ac8fc8582995e1489

369 ms

s.js

s.js

117 ms

collect

collect

15 ms

logo.png

logo.png

746 ms

light-bulb.jpg

light-bulb.jpg

318 ms

lee-kranefuss.jpg

lee-kranefuss.jpg

221 ms

question.jpg

question.jpg

173 ms

pilot.jpg

pilot.jpg

161 ms

webinar.jpg

webinar.jpg

204 ms

cJZKeOuBrn4kERxqtaUH3bO3LdcAZYWl9Si6vvxL-qU.woff

cJZKeOuBrn4kERxqtaUH3bO3LdcAZYWl9Si6vvxL-qU.woff

134 ms

DXI1ORHCpsQm3Vp6mXoaTaRDOzjiPcYnFooOUGCOsRk.woff

DXI1ORHCpsQm3Vp6mXoaTaRDOzjiPcYnFooOUGCOsRk.woff

134 ms

MTP_ySUJH_bn48VBG8sNSqRDOzjiPcYnFooOUGCOsRk.woff

MTP_ySUJH_bn48VBG8sNSqRDOzjiPcYnFooOUGCOsRk.woff

157 ms

k3k702ZOKiLJc3WVjuplzKRDOzjiPcYnFooOUGCOsRk.woff

k3k702ZOKiLJc3WVjuplzKRDOzjiPcYnFooOUGCOsRk.woff

156 ms

aquant.js

aquant.js

147 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

264 ms

514456.js

514456.js

234 ms

logo-dark.png

logo-dark.png

142 ms

s.gif

s.gif

365 ms

pixel;r=1169137185;a=p-gcA8kC4u8yFvp;orderid=;revenue=;labels=_fp.event.Homepage;fpan=1;fpa=P0-1964481225-1459163678974;ns=0;ce=1;cm=;je=0;sr=1024x768x32;enc=n;dst=0;et=1459163678973;tzo=-180;ref=;url=https%3A%2F%2Fwww.sourceetf.com%2F;ogl=

pixel;r=1169137185;a=p-gcA8kC4u8yFvp;orderid=;revenue=;labels=_fp.event.Homepage;fpan=1;fpa=P0-1964481225-1459163678974;ns=0;ce=1;cm=;je=0;sr=1024x768x32;enc=n;dst=0;et=1459163678973;tzo=-180;ref=;url=https%3A%2F%2Fwww.sourceetf.com%2F;ogl=

37 ms

__ptq.gif

__ptq.gif

37 ms

SEO Factors

source.info 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 Source.info 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 Source.info 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

source.info

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