4.7 sec in total
857 ms
3.5 sec
345 ms
Welcome to splatoon.biz homepage info - get ready to check Splatoon best content for Japan right away, or after learning these important things about splatoon.biz
引用元: http://toro.2ch.sc/test/read.cgi/famicom/1464227499/ 798: なまえをいれてください (ワッチョイ 6f3d-dCMW)2016/05/26(木) 23:09:38 ID: A4NqYAgJ0.net
Visit splatoon.bizWe analyzed Splatoon.biz page load time and found that the first response time was 857 ms and then it took 3.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
splatoon.biz performance score
857 ms
201 ms
137 ms
138 ms
140 ms
Our browser made a total of 155 requests to load all elements on the main page. We found that 46% of them (72 requests) were addressed to the original Splatoon.biz, 5% (8 requests) were made to Adm.shinobi.jp and 4% (6 requests) were made to C.betrad.com. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Image.moshimo.com.
Page size can be reduced by 1.1 MB (58%)
1.8 MB
769.5 kB
In fact, the total size of Splatoon.biz main page is 1.8 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. 60% of websites need less resources to load. Javascripts take 869.0 kB which makes up the majority of the site volume.
Potential reduce by 107.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. 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 107.1 kB or 82% of the original size.
Potential reduce by 48.7 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. Obviously, Splatoon needs image optimization as it can save up to 48.7 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 592.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 592.7 kB or 68% of the original size.
Potential reduce by 301.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. Splatoon.biz needs all CSS files to be minified and compressed as it can save up to 301.7 kB or 80% of the original size.
Number of requests can be reduced by 107 (74%)
145
38
The browser has sent 145 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Splatoon. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 48 to 1 for JavaScripts and from 21 to 1 for CSS and as a result speed up the page load time.
splatoon.biz
857 ms
style.css
201 ms
feedly.css
137 ms
blog-card.css
138 ms
extension.css
140 ms
other.css
142 ms
sns.css
142 ms
font-awesome.min.css
270 ms
style.css
204 ms
fluidity.min.css
206 ms
buttons.min.css
207 ms
dashicons.min.css
293 ms
mediaelementplayer.min.css
267 ms
wp-mediaelement.css
292 ms
media-views.min.css
341 ms
imgareaselect.css
293 ms
wpp.css
335 ms
jetpack.css
403 ms
utils.min.js
339 ms
jquery.js
476 ms
jquery-migrate.min.js
345 ms
plupload.full.min.js
471 ms
javascript.js
414 ms
jquery.scrollspy.js
414 ms
blog2ch.js
415 ms
jquery.vticker.js
469 ms
c6f7892854fb56106c4abc94b77b3cdd
603 ms
widget.js
1088 ms
pu.js
371 ms
underscore.min.js
418 ms
shortcode.min.js
478 ms
backbone.min.js
488 ms
wp-util.min.js
481 ms
wp-backbone.min.js
481 ms
media-models.min.js
485 ms
wp-plupload.min.js
485 ms
core.min.js
486 ms
widget.min.js
554 ms
mouse.min.js
555 ms
devicepx-jetpack.js
4 ms
gprofiles.js
57 ms
e-201611.js
4 ms
sortable.min.js
554 ms
mediaelement-and-player.min.js
552 ms
wp-mediaelement.js
484 ms
media-views.min.js
621 ms
media-editor.min.js
537 ms
media-audiovideo.min.js
539 ms
wpgroho.js
484 ms
wp-emoji-release.min.js
397 ms
bg.jpg
226 ms
logo.png
229 ms
20150620073645-3403-300x30060-150x150.jpeg
234 ms
20150620073654-6089-300x30052-150x150.jpeg
233 ms
20150620073656-9764-300x30075-150x150.jpeg
235 ms
20150620073651-9512-300x30063-150x150.jpeg
294 ms
20150620073649-5490-300x30062-150x150.jpeg
298 ms
20150620073645-3403-300x30059-150x150.jpeg
302 ms
20150620073645-3403-300x30058-150x150.jpeg
304 ms
20150620073656-9764-300x30074-150x150.jpeg
305 ms
20150620073651-9512-300x30062-150x150.jpeg
305 ms
20150620073647-6868-300x30060-150x150.jpeg
360 ms
1941-featured-75x75.jpeg
365 ms
1954-featured-75x75.jpeg
367 ms
10866-featured-75x75.jpeg
369 ms
10152-featured-75x75.jpeg
371 ms
10974-featured-75x75.jpeg
373 ms
20150620073645-3403-300x30060-100x100.jpeg
427 ms
20150620073654-6089-300x30052-100x100.jpeg
420 ms
20150620073656-9764-300x30075-100x100.jpeg
421 ms
fontawesome-webfont.woff
554 ms
icomoon.woff
419 ms
20150620073651-9512-300x30063-100x100.jpeg
416 ms
20150620073649-5490-300x30062-100x100.jpeg
474 ms
20150620073654-6089-300x3003.jpeg
478 ms
1.0.1.js
482 ms
rakuten_widget.js
1080 ms
impression
897 ms
print.css
69 ms
1.0.0.js
156 ms
sync
175 ms
c6f7892854fb56106c4abc94b77b3cdd
289 ms
c6f7892854fb56106c4abc94b77b3cdd
484 ms
sync
383 ms
sync
704 ms
push_sync
302 ms
0_vUstflFE.jpg
85 ms
creative_add_on.js
58 ms
sync
389 ms
ib
229 ms
surly.js
7 ms
ba.html
4 ms
cms-2c.html
32 ms
4.gif
12 ms
2532.js
3 ms
ping_match.gif
6 ms
2964
49 ms
Pug
46 ms
rum
46 ms
sync
17 ms
mw_view.html
66 ms
pixel
104 ms
demconf.jpg
27 ms
sizzle.min.js
45 ms
tap.php
43 ms
385636.gif
41 ms
rum
72 ms
cookiesync
238 ms
check
43 ms
0_vUstflFE.jpg
44 ms
creative_add_on.js
41 ms
399 ms
ib
231 ms
m.gif
34 ms
parts.php
175 ms
parts.php
110 ms
hovercard.css
36 ms
services.css
100 ms
1.1.0.js
196 ms
pixel.gif
13 ms
pixel
26 ms
dvtp_src.js
25 ms
rs
9 ms
g.gif
8 ms
pc_pcview_all.css
8 ms
front_merged.js
89 ms
m_yahoo.gif
15 ms
getMWConf.php
315 ms
loading.gif
11 ms
buttons.gif
12 ms
match-result
169 ms
dvtp_src_internal26.js
14 ms
sd
154 ms
t2tv7.html
153 ms
visit.js
121 ms
322 ms
sync
51 ms
match
49 ms
rtset
55 ms
event
46 ms
sync
179 ms
receive_sync
155 ms
sync
21 ms
cc
16 ms
xrefid.xgi
15 ms
avs583.js
10 ms
adsct
108 ms
20 ms
event.jpg
37 ms
pixel
42 ms
pixel.gif
24 ms
merge
41 ms
ping_match.gif
19 ms
box_19_top-right.png
4 ms
ci.png
3 ms
splatoon.biz SEO score
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Splatoon.biz 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 Splatoon.biz 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.
splatoon.biz
Open Graph data is detected on the main page of Splatoon. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: