3.8 sec in total
670 ms
2.4 sec
661 ms
Visit rarerecord.jugem.jp now to see the best up-to-date RARE Record Jugem content for Japan and also check out these interesting facts you probably never knew about rarerecord.jugem.jp
Visit rarerecord.jugem.jpWe analyzed Rarerecord.jugem.jp page load time and found that the first response time was 670 ms and then it took 3.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
rarerecord.jugem.jp performance score
670 ms
459 ms
5 ms
6 ms
5 ms
Our browser made a total of 96 requests to load all elements on the main page. We found that 4% of them (4 requests) were addressed to the original Rarerecord.jugem.jp, 19% (18 requests) were made to Imaging.jugem.jp and 15% (14 requests) were made to Maps.googleapis.com. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Img-cdn.jg.jugem.jp.
Page size can be reduced by 642.4 kB (40%)
1.6 MB
954.8 kB
In fact, the total size of Rarerecord.jugem.jp main page is 1.6 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. 65% of websites need less resources to load. Images take 760.4 kB which makes up the majority of the site volume.
Potential reduce by 62.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. This page needs HTML code to be minified as it can gain 10.6 kB, which is 15% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 62.1 kB or 86% of the original size.
Potential reduce by 51.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. RARE Record Jugem images are well optimized though.
Potential reduce by 514.4 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 514.4 kB or 69% of the original size.
Potential reduce by 14.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. Rarerecord.jugem.jp needs all CSS files to be minified and compressed as it can save up to 14.7 kB or 79% of the original size.
Number of requests can be reduced by 40 (43%)
93
53
The browser has sent 93 CSS, Javascripts, AJAX and image requests in order to completely render the main page of RARE Record Jugem. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 25 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
rarerecord.jugem.jp
670 ms
jm_style.css
459 ms
style.css
5 ms
cookie.js
6 ms
script.js
5 ms
jquery.min.js
28 ms
metallica.css
7 ms
metallica.js
6 ms
fav.js
7 ms
fav.css
7 ms
login_popup.css
7 ms
jsapi.cgi
695 ms
share.js
296 ms
analytics.js
34 ms
bg_body_dot.gif
11 ms
20160219_1531218.jpg
1077 ms
rarerecord.jugem.jp
308 ms
powered_07b.gif
155 ms
20160131_1520506.jpg
995 ms
20160126_1517819.jpg
472 ms
20151202_1483863.jpg
824 ms
20150106_1270423.jpg
479 ms
bg_header.gif
23 ms
logo_jugem.gif
21 ms
bg_dot.gif
21 ms
logo_pepabo.gif
22 ms
bg_title_blue.jpg
35 ms
add_heart.gif
14 ms
add_bubble.gif
15 ms
lovewindow_b.gif
15 ms
collect
27 ms
collect
62 ms
powered_07b.gif
3 ms
embed
242 ms
share_button.html
386 ms
share_button.html
385 ms
share_button.html
384 ms
share_button.html
381 ms
share_button.html
383 ms
share_button.html
382 ms
share_button.html
653 ms
share_button.html
654 ms
share_button.html
655 ms
share_button.html
656 ms
sdk.js
22 ms
share_button.php
146 ms
share_button.php
122 ms
117 ms
xd_arbiter.php
35 ms
xd_arbiter.php
47 ms
share_button.php
201 ms
share_button.php
206 ms
share_button.php
197 ms
share_button.php
204 ms
share_button.php
206 ms
share_button.php
282 ms
share_button.php
276 ms
share_button.php
170 ms
qeKvIRsJabD.js
42 ms
LVx-xkvaJ0b.png
28 ms
js
192 ms
init_embed.js
190 ms
bt_check_6.png
42 ms
common.js
47 ms
map.js
46 ms
google4.png
67 ms
overlay.js
13 ms
util.js
105 ms
onion.js
63 ms
search_impl.js
81 ms
StaticMapService.GetMapImage
244 ms
stats.js
71 ms
openhand_8_8.cur
42 ms
kh
102 ms
transparent.png
27 ms
ViewportInfoService.GetViewportInfo
82 ms
ViewportInfoService.GetViewportInfo
61 ms
controls.js
29 ms
ViewportInfoService.GetViewportInfo
49 ms
vt
125 ms
vt
151 ms
css
81 ms
entity11.png
51 ms
vt
90 ms
vt
93 ms
vt
100 ms
vt
98 ms
vt
160 ms
vt
163 ms
vt
156 ms
vt
154 ms
mapcnt6.png
22 ms
sv5.png
27 ms
tmapctrl.png
22 ms
jsapi.cgi
313 ms
AuthenticationService.Authenticate
12 ms
rarerecord.jugem.jp SEO score
JA
JA
EUC-JP
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Rarerecord.jugem.jp can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and it matches the claimed language. Our system also found out that Rarerecord.jugem.jp main page’s claimed encoding is euc-jp. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
rarerecord.jugem.jp
Open Graph description is not detected on the main page of RARE Record Jugem. 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: