6.3 sec in total
1.3 sec
4.7 sec
295 ms
Click here to check amazing Sorae content for Japan. Otherwise, check out these important facts you probably never knew about sorae.jp
sorae.jpは、宇宙に関する最新ニュースや天文情報などを、よりスピーディーに、より分かり易く紹介していくサイトです。
Visit sorae.jpWe analyzed Sorae.jp page load time and found that the first response time was 1.3 sec and then it took 4.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
sorae.jp performance score
1332 ms
543 ms
922 ms
1312 ms
1521 ms
Our browser made a total of 154 requests to load all elements on the main page. We found that 26% of them (40 requests) were addressed to the original Sorae.jp, 14% (21 requests) were made to Pbs.twimg.com and 7% (11 requests) were made to Googleads.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (2.3 sec) belongs to the original domain Sorae.jp.
Page size can be reduced by 366.9 kB (13%)
2.7 MB
2.4 MB
In fact, the total size of Sorae.jp main page is 2.7 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. 75% 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 2.2 MB which makes up the majority of the site volume.
Potential reduce by 37.0 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 37.0 kB or 76% of the original size.
Potential reduce by 61.2 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. Sorae images are well optimized though.
Potential reduce by 189.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 189.0 kB or 49% of the original size.
Potential reduce by 79.8 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. Sorae.jp needs all CSS files to be minified and compressed as it can save up to 79.8 kB or 83% of the original size.
Number of requests can be reduced by 66 (44%)
150
84
The browser has sent 150 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Sorae. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 42 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
sorae.jp
1332 ms
reset.css
543 ms
style.css
922 ms
jetpack.css
1312 ms
jquery.js
1521 ms
jquery-migrate.min.js
905 ms
loader.php
888 ms
loader.js
122 ms
jquery.min.js
41 ms
adsbygoogle.js
5 ms
menu.js
192 ms
jquery.smoothScroll.js
758 ms
pageback.js
503 ms
jquery.adrotate.clicktracker.js
536 ms
devicepx-jetpack.js
57 ms
gprofiles.js
53 ms
wpgroho.js
536 ms
e-201609.js
4 ms
wp-emoji-release.min.js
660 ms
logo.png
235 ms
0229hitomi.jpg
1171 ms
160229nei.jpeg
811 ms
0229falcon-9-e1456715582358.jpg
381 ms
160228npluto.jpg
542 ms
160226ng1.jpg
618 ms
0228falcon-9-e1456661256102.jpg
1036 ms
0228dlr-e1456658983375.jpg
1128 ms
0227erg-e1456566653880.gif
975 ms
0227minatomirai.jpg
1449 ms
20160229jaxa-300x199.jpg
1193 ms
0218hitomi-e1455759995976-300x212.jpg
1125 ms
matenro_hk.jpg
1261 ms
20160203nkrocket-200x300.jpg
1301 ms
20160119IST1-300x225.png
1688 ms
2015_12_30_ISS-300x191.jpg
1550 ms
151231nsun1.jpg
2328 ms
23282658734_571a193371_o-200x300.jpg
1593 ms
151213ndro1.jpg
1656 ms
ca-pub-3904840174429365.js
48 ms
zrt_lookup.html
47 ms
show_ads_impl.js
56 ms
snsicon.png
1606 ms
icon_category.png
1724 ms
icon-search.png
1766 ms
tt-top.png
1779 ms
bg-top-categorytip.png
1816 ms
tt-sponsor.png
1856 ms
icon-list.png
1889 ms
bg-top-pickup.png
1911 ms
sdk.js
35 ms
ads
234 ms
osd.js
29 ms
ads
211 ms
ads
196 ms
201 ms
ads
362 ms
xd_arbiter.php
79 ms
xd_arbiter.php
117 ms
widgets.js
112 ms
ads
424 ms
analytics.js
69 ms
hovercard.css
58 ms
services.css
101 ms
g.gif
20 ms
ads
373 ms
ads
351 ms
ads
339 ms
collect
99 ms
collect
86 ms
timeline.1b43d11859b7663a2225b885f87704a5.js
211 ms
1807497384751568404
68 ms
abg.js
78 ms
m_js_controller.js
73 ms
googlelogo_color_112x36dp.png
118 ms
12921553144625405806
54 ms
5513704021182547325
91 ms
page.php
170 ms
s
33 ms
x_button_blue2.png
25 ms
E4WYPs_lNJIuXrWpTsOcc3FIG36RfI0ERc0srw5QW9Y.js
8 ms
d5xjefPVHuZ.css
82 ms
_rx8naC75Dy.js
106 ms
t-KLv3gqZy0.js
160 ms
uLtKx7ldlvR.js
176 ms
syndication
218 ms
659079305108942848
309 ms
215 ms
adj
180 ms
beacon
157 ms
15056539925222142763
102 ms
css
149 ms
12549833196257329546
101 ms
12063441_418793201646592_44323580679698467_n.jpg
156 ms
12118791_419461214913124_8574862696968077771_n.jpg
128 ms
12743816_905155639599740_2514145705571519243_n.jpg
158 ms
1524604_483346615120174_2102267569_n.jpg
160 ms
12295283_1668799566711138_5703529801251227164_n.jpg
200 ms
wL6VQj7Ab77.png
61 ms
CSXXCvknpgK.png
60 ms
91 ms
0
281 ms
pixel
58 ms
lidar.js
56 ms
sbhK2lTE.js
56 ms
favicon
263 ms
favicon
272 ms
nessie_icon_tiamat_white.png
75 ms
pixel
229 ms
cTrvNaRi.html
63 ms
LPRF00532997.jpg
335 ms
adServer.bs
272 ms
verify_selector.js
334 ms
blank.gif
332 ms
bapi
277 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
47 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
175 ms
R9a_DtVRZgv.js
149 ms
cUDgRFxaoIk.js
150 ms
0JBr1QHp8Gi.js
149 ms
kDOzhTr2W91.js
181 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
225 ms
lRvdU5NZ_normal.jpg
267 ms
CcYZ5-IVIAEam4O.jpg:small
394 ms
CcX74hgVAAAnLBY.jpg:small
389 ms
CcXGmilUsAEjeEb.jpg:small
419 ms
CcWd9mIW8AA_hyv.jpg:small
397 ms
CcV8grSUYAAeX9l.jpg:small
432 ms
CcVhGLCUkAAxp3v.jpg:small
449 ms
CcTO9sKUMAAeuN-.jpg:small
416 ms
CcTGACUUEAAKV8L.jpg:small
421 ms
CcNnuY1WAAAgjjM.jpg:small
424 ms
CcNiGzGUUAIcEZP.jpg:small
560 ms
CcIZjgPUkAELsk9.jpg:small
443 ms
CcHtU3hUsAI8OQw.jpg:small
470 ms
CcGHKp7UEAAral9.jpg:small
513 ms
CcDgDicUsAAWxpx.jpg:small
460 ms
CcDUlrMUMAAyumW.jpg:small
645 ms
CcDIedKVIAASGGI.jpg:small
504 ms
CcDC9xwUEAQ4TN-.jpg:small
489 ms
Cb-8_2sUUAAaXF0.jpg:small
499 ms
Cb-fLojUMAERtt0.jpg:small
550 ms
Cb-Y4QXWoAEQdDW.jpg:small
547 ms
sd
8 ms
verifyr.js
31 ms
client-verify.adtricity.com
339 ms
beacon.js
46 ms
dbapi
24 ms
0
22 ms
bg.png
46 ms
adchoices.en.png
70 ms
jot
41 ms
dt
72 ms
dt
71 ms
activeview
12 ms
sorae.jp SEO score
JA
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Sorae.jp 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 Sorae.jp 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.
sorae.jp
Open Graph description is not detected on the main page of Sorae. 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: