6.2 sec in total
854 ms
5.1 sec
278 ms
Welcome to blue-return.info homepage info - get ready to check Blue Return best content for Japan right away, or after learning these important things about blue-return.info
フリーランス(個人事業主)のデザイナー兼ブロガーの私が、「やよいの青色申告」を使ってMacで初めての青色申告に挑戦。詳しいやり方を画像つきで説明しています。
Visit blue-return.infoWe analyzed Blue-return.info page load time and found that the first response time was 854 ms and then it took 5.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
blue-return.info performance score
name
value
score
weighting
Value4.4 s
17/100
10%
Value13.0 s
0/100
25%
Value9.7 s
11/100
10%
Value870 ms
33/100
30%
Value0
100/100
15%
Value13.3 s
11/100
10%
854 ms
180 ms
358 ms
347 ms
352 ms
Our browser made a total of 77 requests to load all elements on the main page. We found that 31% of them (24 requests) were addressed to the original Blue-return.info, 13% (10 requests) were made to Static.xx.fbcdn.net and 8% (6 requests) were made to Googleads.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Blue-return.info.
Page size can be reduced by 641.8 kB (42%)
1.5 MB
892.3 kB
In fact, the total size of Blue-return.info main page is 1.5 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. 50% of websites need less resources to load. Javascripts take 963.0 kB which makes up the majority of the site volume.
Potential reduce by 44.8 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 44.8 kB or 77% of the original size.
Potential reduce by 17.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. Blue Return images are well optimized though.
Potential reduce by 468.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 468.7 kB or 49% of the original size.
Potential reduce by 111.2 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. Blue-return.info needs all CSS files to be minified and compressed as it can save up to 111.2 kB or 84% of the original size.
Number of requests can be reduced by 44 (63%)
70
26
The browser has sent 70 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Blue Return. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 28 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
www.blue-return.info
854 ms
style.php.pagespeed.ce.0iBDUWujA4.css
180 ms
style.min.css,qver=5.2.20.pagespeed.ce.gKvgQQxmQO.css
358 ms
styles.css,qver=3.5.4.pagespeed.ce.N0CCk-mXI1.css
347 ms
default.min.css,qver=1.2.pagespeed.ce.Yn5bZ3fLc3.css
352 ms
lightbox.min.css,qver=1.4.pagespeed.ce.R0vYCNc3IU.css
354 ms
jquery.js
543 ms
jquery-migrate.min.js
366 ms
show_ads.js
69 ms
rakuten_widget.js
911 ms
jquery.form.min.js
520 ms
scripts.js
528 ms
jquery.touchwipe.min.js
529 ms
jquery.lightbox.min.js
528 ms
wp-embed.min.js
547 ms
import.css
518 ms
core.css
179 ms
layouts.css
178 ms
tuika.css
176 ms
ga.js
37 ms
wp-emoji-release.min.js
183 ms
bgt
797 ms
0.gif
698 ms
51d83Srwb3L._SL160_.jpg
70 ms
gifbanner
484 ms
51F2krUKdSL._SL160_.jpg
57 ms
feed.png.pagespeed.ce.7kvY8Jiy7c.png
177 ms
twitter.png.pagespeed.ce.VfujBjEbd-.png
175 ms
facebook.png.pagespeed.ce.SQXAq6t9zY.png
178 ms
41PoB2l-A5L._SL160_.jpg
67 ms
51XATZDldXL._SL160_.jpg
68 ms
gifbanner
538 ms
gifbanner
538 ms
logo2.gif
173 ms
adsbygoogle.js
167 ms
__utm.gif
46 ms
__utm.gif
12 ms
image1.png
1097 ms
right-icon.gif
284 ms
kl.gif
31 ms
mw_dynamic_view.html
251 ms
yl.gif
15 ms
likebox.php
130 ms
yl.gif
20 ms
kl.gif
24 ms
show_ads_impl.js
280 ms
ZFluMDo2EQh.css
19 ms
AkV4cevgxL7.js
26 ms
Y4zFOWmUObv.js
23 ms
9RGXrkPnS_6.js
49 ms
HbT8HXdZYIC.js
24 ms
IfxMrflzyZZ.js
24 ms
UPBFaju8R95.js
25 ms
W0tkRKZdqEQ.js
65 ms
p55HfXW__mM.js
64 ms
300908250_216168557407502_7682567734882751198_n.jpg
59 ms
UXtr_j2Fwe-.png
7 ms
pc_pcview_all.css
21 ms
front_merged.js
10 ms
getMWConf.php
678 ms
loading.gif
14 ms
buttons.gif
8 ms
1x1.gif
57 ms
1x1.gif
21 ms
1x1.gif
21 ms
zrt_lookup.html
27 ms
ads
43 ms
ads
449 ms
ads
396 ms
9011103348843135357
118 ms
abg_lite.js
21 ms
s
5 ms
window_focus.js
25 ms
qs_click_protection.js
25 ms
ufs_web_display.js
17 ms
one_click_handler_one_afma.js
117 ms
icon.png
12 ms
blue-return.info accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.
Definition list items are not wrapped in <dl> elements
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
Names and labels
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Form elements do not have associated labels
Links do not have a discernible name
blue-return.info best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
blue-return.info SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
![]()
JA
![]()
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Blue-return.info 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 Blue-return.info 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.
blue-return.info
Open Graph description is not detected on the main page of Blue Return. 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: