5.3 sec in total
1.3 sec
3.4 sec
557 ms
Visit blog.yohanliyanage.com now to see the best up-to-date Blog Yohanliyanage content for United States and also check out these interesting facts you probably never knew about blog.yohanliyanage.com
Visit blog.yohanliyanage.comWe analyzed Blog.yohanliyanage.com page load time and found that the first response time was 1.3 sec and then it took 4 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
blog.yohanliyanage.com performance score
1339 ms
23 ms
34 ms
270 ms
490 ms
Our browser made a total of 64 requests to load all elements on the main page. We found that 19% of them (12 requests) were addressed to the original Blog.yohanliyanage.com, 20% (13 requests) were made to Apis.google.com and 14% (9 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Blog.yohanliyanage.com.
Page size can be reduced by 228.2 kB (55%)
412.5 kB
184.3 kB
In fact, the total size of Blog.yohanliyanage.com main page is 412.5 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 133.9 kB which makes up the majority of the site volume.
Potential reduce by 96.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. 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 96.2 kB or 86% of the original size.
Potential reduce by 1.4 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. Blog Yohanliyanage images are well optimized though.
Potential reduce by 72.6 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 72.6 kB or 54% of the original size.
Potential reduce by 58.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. Blog.yohanliyanage.com needs all CSS files to be minified and compressed as it can save up to 58.0 kB or 83% of the original size.
Number of requests can be reduced by 34 (60%)
57
23
The browser has sent 57 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Blog Yohanliyanage. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 27 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
blog.yohanliyanage.com
1339 ms
css
23 ms
css
34 ms
style.css
270 ms
async-share.css
490 ms
font-awesome.css
5 ms
font-awesome-corp.css
493 ms
font-awesome-ext.css
500 ms
font-awesome-social.css
497 ms
jquery.js
774 ms
jquery-migrate.min.js
517 ms
devicepx-jetpack.js
5 ms
functions.js
733 ms
async-share.js
731 ms
ga.js
47 ms
blog_header_bg.jpg
516 ms
search-icon.png
302 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
41 ms
BTu4SsVveqk58cdYjlaM9g.ttf
40 ms
4GwpJM7qx9X5Obd9KsnKxQ.ttf
41 ms
fontawesome-webfont.woff
39 ms
__utm.gif
20 ms
all.js
24 ms
widgets.js
24 ms
plusone.js
129 ms
in.js
123 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
139 ms
277 ms
xd_arbiter.php
32 ms
xd_arbiter.php
128 ms
secureAnonymousFramework
255 ms
cb=gapi.loaded_0
85 ms
cb=gapi.loaded_1
166 ms
sharebutton
207 ms
sharebutton
205 ms
sharebutton
201 ms
sharebutton
199 ms
sharebutton
196 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.en.html
91 ms
postmessageRelay
268 ms
rs=AGLTcCMZQMkD3nQb9neyXrDGlfp1IpCqrw
32 ms
rs=AGLTcCPeW_yxohM6d2vzOu9_v18SNdO9Aw
57 ms
rs=AGLTcCNEeBXwi31Sa43CyaFD4uWCwotgXw
29 ms
sprite_connect_v14.png
79 ms
3193398744-postmessagerelay.js
63 ms
rpc:shindig_random.js
57 ms
bdHGHleUa-ndQCOrdpfxfw.ttf
60 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
77 ms
cb=gapi.loaded_0
14 ms
jot.html
2 ms
like.php
106 ms
like.php
124 ms
like.php
123 ms
like.php
198 ms
qeKvIRsJabD.js
35 ms
LVx-xkvaJ0b.png
29 ms
like.php
176 ms
qeKvIRsJabD.js
15 ms
qeKvIRsJabD.js
82 ms
qeKvIRsJabD.js
79 ms
qeKvIRsJabD.js
44 ms
qeKvIRsJabD.js
41 ms
qeKvIRsJabD.js
32 ms
qeKvIRsJabD.js
29 ms
blog.yohanliyanage.com SEO score
N/A
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Blog.yohanliyanage.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), while the claimed language is English. Our system also found out that Blog.yohanliyanage.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.
blog.yohanliyanage.com
Open Graph description is not detected on the main page of Blog Yohanliyanage. 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: