2.8 sec in total
178 ms
1.9 sec
677 ms
Visit blog.origami.com now to see the best up-to-date Blog Origami content for Japan and also check out these interesting facts you probably never knew about blog.origami.com
株式会社Origamiの会社概要をご紹介します。Origamiの代表者名、所在地、設立年月日、事業内容などの企業情報をご紹介しております。
Visit blog.origami.comWe analyzed Blog.origami.com page load time and found that the first response time was 178 ms and then it took 2.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
blog.origami.com performance score
178 ms
12 ms
8 ms
9 ms
35 ms
Our browser made a total of 99 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Blog.origami.com, 14% (14 requests) were made to Maps.googleapis.com and 14% (14 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (1 sec) relates to the external source 36.media.tumblr.com.
Page size can be reduced by 1.2 MB (20%)
5.9 MB
4.7 MB
In fact, the total size of Blog.origami.com main page is 5.9 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. 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. Images take 4.4 MB which makes up the majority of the site volume.
Potential reduce by 69.9 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 69.9 kB or 79% of the original size.
Potential reduce by 135.6 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 Origami images are well optimized though.
Potential reduce by 947.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 947.0 kB or 68% of the original size.
Potential reduce by 19.7 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.origami.com needs all CSS files to be minified and compressed as it can save up to 19.7 kB or 81% of the original size.
Number of requests can be reduced by 39 (42%)
93
54
The browser has sent 93 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Blog Origami. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 30 to 1 for JavaScripts and as a result speed up the page load time.
blog.origami.com
178 ms
pre_tumblelog.js
12 ms
font-awesome.css
8 ms
jquery-1.9.1.min.js
9 ms
tumblelog_post_message_queue.js
35 ms
stylesheet.css
35 ms
index.js
48 ms
ga.js
126 ms
sdk.js
395 ms
origami-logo-blog.png
134 ms
tumblr_o2zme91akq1tzmpq7o1_1280.jpg
329 ms
tumblr_o2oq3290wz1tzmpq7o1_1280.jpg
132 ms
tumblr_o2oq3290wz1tzmpq7o2_1280.jpg
1045 ms
aa92fbbb631ff9408848f4611e288c3b99210fe4.png
267 ms
embed
264 ms
email_jan_points3x_img4.jpg
263 ms
widgets.js
230 ms
impixu
263 ms
tumblr_o2oq3290wz1tzmpq7o4_1280.jpg
583 ms
tumblr_o2oq0ieXje1tzmpq7o2_1280.jpg
692 ms
tumblr_o2oq0ieXje1tzmpq7o9_1280.jpg
993 ms
impixu
263 ms
email_jan_points3x_img5.jpg
200 ms
email_jan_points3x_img6.jpg
227 ms
email_jan_points3x_img7.jpg
122 ms
email_jan_points3x_img8.jpg
199 ms
email_jan_points3x_img9.jpg
122 ms
email_jan_points3x_img10.jpg
226 ms
email_jan_points3x_img11.jpg
257 ms
tumblr_o2oq3290wz1tzmpq7o3_1280.jpg
226 ms
tumblr_o2oq0ieXje1tzmpq7o10_1280.jpg
226 ms
tumblr_o2oq0ieXje1tzmpq7o1_1280.jpg
216 ms
json
520 ms
analytics.html
153 ms
fontawesome-webfont.woff
17 ms
login_check.html
16 ms
inpage_linkid.js
82 ms
avatar_30fe05302e6f_40.png
72 ms
iframe_logo.png
62 ms
__utm.gif
48 ms
button.831500944bc3eb7ea5276ccdc3f71d2e.js
231 ms
js
84 ms
init_embed.js
43 ms
rapid-3.33.js
46 ms
rapidworker-1.2.js
42 ms
ga.js
142 ms
analytics.js
120 ms
cs.js
158 ms
yql
418 ms
182 ms
xd_arbiter.php
278 ms
xd_arbiter.php
482 ms
__utm.gif
59 ms
tweet_button.6a78875565a912489e9aef879c881358.ja.html
57 ms
common.js
39 ms
map.js
62 ms
google4.png
69 ms
overlay.js
68 ms
util.js
65 ms
onion.js
75 ms
search_impl.js
76 ms
StaticMapService.GetMapImage
298 ms
stats.js
35 ms
openhand_8_8.cur
36 ms
ViewportInfoService.GetViewportInfo
99 ms
controls.js
26 ms
__utm.gif
40 ms
transparent.png
86 ms
css
136 ms
entity11.png
74 ms
jot
151 ms
mapcnt6.png
56 ms
sv5.png
56 ms
ViewportInfoService.GetViewportInfo
45 ms
kh
89 ms
vt
87 ms
vt
171 ms
vt
96 ms
vt
118 ms
vt
132 ms
vt
116 ms
vt
155 ms
vt
154 ms
vt
188 ms
vt
162 ms
vt
206 ms
vt
208 ms
vt
224 ms
tmapctrl.png
53 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
36 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
40 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
44 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
48 ms
ViewportInfoService.GetViewportInfo
26 ms
AuthenticationService.Authenticate
41 ms
cedexis.radar.js
16 ms
like.php
61 ms
-1cfYrhulAt.js
493 ms
LVx-xkvaJ0b.png
554 ms
blog.origami.com SEO score
JA
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Blog.origami.com 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 Blog.origami.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.origami.com
Open Graph data is detected on the main page of Blog Origami. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: