2.2 sec in total
28 ms
1.9 sec
235 ms
Visit shogo82148.github.io now to see the best up-to-date Shogo 82148 Github content for China and also check out these interesting facts you probably never knew about shogo82148.github.io
Shogo's Page Mar 28th, 2012 2:19 pm blog works tools Mar 28th, 2012 2:19 pm Tweet Comments Please enable JavaScript to view the comments powered by …
Visit shogo82148.github.ioWe analyzed Shogo82148.github.io page load time and found that the first response time was 28 ms and then it took 2.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
shogo82148.github.io performance score
28 ms
45 ms
32 ms
32 ms
31 ms
Our browser made a total of 64 requests to load all elements on the main page. We found that 16% of them (10 requests) were addressed to the original Shogo82148.github.io, 14% (9 requests) were made to C.disquscdn.com and 11% (7 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (990 ms) relates to the external source S.hatena.ne.jp.
Page size can be reduced by 452.4 kB (64%)
701.5 kB
249.0 kB
In fact, the total size of Shogo82148.github.io main page is 701.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. 50% of websites need less resources to load. Javascripts take 638.2 kB which makes up the majority of the site volume.
Potential reduce by 27.7 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 27.7 kB or 73% of the original size.
Potential reduce by 0 B
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. Shogo 82148 Github images are well optimized though.
Potential reduce by 419.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 419.7 kB or 66% of the original size.
Potential reduce by 5.1 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. Shogo82148.github.io needs all CSS files to be minified and compressed as it can save up to 5.1 kB or 76% of the original size.
Number of requests can be reduced by 45 (79%)
57
12
The browser has sent 57 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Shogo 82148 Github. 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 7 to 1 for CSS and as a result speed up the page load time.
shogo82148.github.io
28 ms
shogo82148.github.io
45 ms
screen.css
32 ms
modernizr-2.0.js
32 ms
jquery.min.js
31 ms
octopress.js
56 ms
MathJax.js
59 ms
css
73 ms
css
117 ms
HatenaStar.js
990 ms
bookmark_button.js
917 ms
github.js
56 ms
line-tile.png
66 ms
TeX-AMS-MML_HTMLorMML.js
14 ms
ga.js
20 ms
accessibility-menu.js
48 ms
__utm.gif
13 ms
bookmark_button.js
163 ms
noise.png
71 ms
button-only.gif
195 ms
FUDHvzEKSJww3kCxuiAo2A.ttf
55 ms
0XxGQsSc1g4rdRdjJKZrNC3USBnSvpkopQaUR-2r7iU.ttf
81 ms
EgBlzoNBIHxNPCMwXaAhYPesZW2xOQ-xsNqO47m55DA.ttf
97 ms
QABk9IxT-LFTJ_dQzv7xpJ0EAVxt0G0biEntp43Qt6E.ttf
97 ms
606 ms
embed.js
228 ms
all.js
100 ms
plusone.js
119 ms
widgets.js
79 ms
jXHR.js
67 ms
repos
249 ms
rss.png
43 ms
button.3ccb64e61d4c01fae12cd2b0ed9b2bab.js
20 ms
49 ms
cb=gapi.loaded_0
9 ms
cb=gapi.loaded_1
37 ms
fastbutton
60 ms
0sTQzbapM8j.js
54 ms
tweet_button.f8c8d971a6ac545cf416e3c1ad4bbc65.en.html
25 ms
postmessageRelay
70 ms
rs=AGLTcCOnDxwX8-LbpDmaxOBIoHm7W_kGNA
2 ms
lounge.83b5b8f9aa16033ab1cb9cb54bf59140.css
84 ms
config.js
27 ms
971028622-postmessagerelay.js
28 ms
rpc:shindig_random.js
31 ms
cb=gapi.loaded_0
2 ms
jot
83 ms
common.bundle.8acee1de90e869efdb244e45c7f66630.js
32 ms
195 ms
stat.gif
61 ms
loader-bg.173909e4737a7481df14d5492b5eeb48.png
23 ms
lounge.bundle.9becee0326ce4d1840f8985f1dc0ce21.js
11 ms
lounge.load.6f5768194208e9ee5ea7d3e7ec8ac168.js
8 ms
common.bundle.8acee1de90e869efdb244e45c7f66630.js
6 ms
ping
8 ms
lounge.83b5b8f9aa16033ab1cb9cb54bf59140.css
9 ms
like.php
95 ms
lounge.bundle.9becee0326ce4d1840f8985f1dc0ce21.js
42 ms
config.js
11 ms
reset.css
11 ms
entry-button.css
12 ms
standard.svg
6 ms
ja.js
16 ms
lH1ibRl5GKq.png
21 ms
shogo82148.github.io SEO score
JA
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Shogo82148.github.io can be misinterpreted by Google and other search engines. Our service has detected that Japanese 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 Shogo82148.github.io 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.
shogo82148.github.io
Open Graph description is not detected on the main page of Shogo 82148 Github. 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: