1.1 sec in total
12 ms
686 ms
371 ms
Click here to check amazing Source content. Otherwise, check out these important facts you probably never knew about source.ly
Visit source.lyWe analyzed Source.ly page load time and found that the first response time was 12 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.
source.ly performance score
12 ms
221 ms
30 ms
10 ms
29 ms
Our browser made a total of 63 requests to load all elements on the main page. We found that 75% of them (47 requests) were addressed to the original Source.ly, 3% (2 requests) were made to S7.addthis.com and 3% (2 requests) were made to Ws-na.amazon-adsystem.com. The less responsive or slowest element that took the longest time to load (221 ms) belongs to the original domain Source.ly.
Page size can be reduced by 631.4 kB (63%)
1.0 MB
375.2 kB
In fact, the total size of Source.ly main page is 1.0 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. 40% of websites need less resources to load. Javascripts take 671.6 kB which makes up the majority of the site volume.
Potential reduce by 115.1 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 115.1 kB or 80% of the original size.
Potential reduce by 27.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, Source needs image optimization as it can save up to 27.1 kB or 18% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 458.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 458.0 kB or 68% of the original size.
Potential reduce by 31.3 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.ly needs all CSS files to be minified and compressed as it can save up to 31.3 kB or 80% of the original size.
Number of requests can be reduced by 33 (54%)
61
28
The browser has sent 61 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 14 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
source.ly
12 ms
www.source.ly
221 ms
prototype.js
30 ms
effects.js
10 ms
application.js
29 ms
daily_extra.css
11 ms
icymi.css
16 ms
common.css
9 ms
layout.css
14 ms
layout.js
13 ms
jquery-1.10.2.min.js
44 ms
jquery-ui-1.10.3.custom.min.js
22 ms
jquery-ui-1.10.3.custom.min.css
14 ms
news.js
20 ms
addthis_widget.js
9 ms
q
185 ms
end.js
15 ms
urchin.js
10 ms
button1-share.gif
120 ms
Comet_Coming_-_MAIN.jpg
139 ms
lemur_MAIN.jpg
118 ms
pleasedonate.png
86 ms
go.png
87 ms
dailysource.png
86 ms
email_icon.png
87 ms
sm-plus.gif
85 ms
symbol_video.gif
88 ms
symbol_story.gif
88 ms
left_menu_minus_icon.png
87 ms
left_menu_plus_icon.png
87 ms
email2.png
88 ms
twitter.png
89 ms
blogkeen.png
89 ms
googleplus.png
98 ms
pinterest.png
98 ms
facebook.png
99 ms
nonprofitdonate.png
98 ms
tour.png
99 ms
help.png
98 ms
submit.png
99 ms
makehomepage.png
99 ms
volunteer.png
100 ms
spreadtheword.png
101 ms
donate.png
100 ms
shop.png
101 ms
search.png
100 ms
feedback.png
101 ms
twitter2.png
101 ms
facebook2.png
102 ms
pintrest.png
102 ms
rss2.png
103 ms
go2.png
102 ms
tothetop.png
102 ms
json
98 ms
searchbox_27.html
104 ms
__utm.gif
86 ms
300lo.json
58 ms
sh.8e5f85691f9aaa082472a194.html
43 ms
q
25 ms
ap-search-go-btn.gif
94 ms
ir
6 ms
searchbox-logo-126x32.gif
92 ms
nr-100.js
41 ms
source.ly SEO score
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Source.ly 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 Source.ly 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.
source.ly
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: