8.2 sec in total
1.3 sec
6.4 sec
464 ms
Visit blue.boo-log.com now to see the best up-to-date Blue Boo Log content for Japan and also check out these interesting facts you probably never knew about blue.boo-log.com
コスメとかコスメとかコスメのことを綴ります。
Visit blue.boo-log.comWe analyzed Blue.boo-log.com page load time and found that the first response time was 1.3 sec and then it took 6.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
blue.boo-log.com performance score
name
value
score
weighting
Value3.6 s
32/100
10%
Value3.8 s
55/100
25%
Value8.4 s
19/100
10%
Value1,690 ms
11/100
30%
Value0.779
5/100
15%
Value12.9 s
13/100
10%
1305 ms
1085 ms
447 ms
2132 ms
1147 ms
Our browser made a total of 65 requests to load all elements on the main page. We found that 14% of them (9 requests) were addressed to the original Blue.boo-log.com, 25% (16 requests) were made to Img01.boo-log.com and 18% (12 requests) were made to Boo-log.com. The less responsive or slowest element that took the longest time to load (4 sec) relates to the external source Img01.boo-log.com.
Page size can be reduced by 244.6 kB (28%)
859.3 kB
614.7 kB
In fact, the total size of Blue.boo-log.com main page is 859.3 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 35% of websites need less resources to load. Images take 489.6 kB which makes up the majority of the site volume.
Potential reduce by 25.6 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 25.6 kB or 76% of the original size.
Potential reduce by 2.9 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 Boo Log images are well optimized though.
Potential reduce by 201.3 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 201.3 kB or 63% of the original size.
Potential reduce by 14.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. Blue.boo-log.com needs all CSS files to be minified and compressed as it can save up to 14.8 kB or 84% of the original size.
Number of requests can be reduced by 32 (51%)
63
31
The browser has sent 63 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Blue Boo Log. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 14 to 1 for JavaScripts and as a result speed up the page load time.
blue.boo-log.com
1305 ms
style.css
1085 ms
oz2-740style.css
447 ms
script.php
2132 ms
clog_ad.js
1147 ms
show_ads.js
8 ms
greybox.js
903 ms
gb_styles.css
459 ms
bling_bp_s.js
1898 ms
counter.php
1716 ms
topnavi.js
864 ms
ga.js
9 ms
bg_body.gif
688 ms
121.gif
433 ms
c.php
397 ms
cosmereview88_31.gif
664 ms
awake_com_banner_60.jpg
371 ms
045.gif
447 ms
188.gif
452 ms
097.gif
455 ms
181.gif
459 ms
111.gif
461 ms
102.gif
883 ms
album-icon.png
1143 ms
btn_login.gif
1225 ms
bn_150-339.png
1143 ms
message.gif
229 ms
logo_s2.gif
669 ms
arrow_right.png
684 ms
DSC_2422.JPG
1601 ms
DSC_2514.JPG
1575 ms
DSC_2524.JPG
1232 ms
profile.jpg
455 ms
DSC_2422-s.JPG
684 ms
DSC_2528-s.JPG
702 ms
DSC_2489sk2k-s.JPG
2473 ms
DSC_2427_1-s.JPG
2620 ms
0409792_01-s.jpg
2626 ms
DSC_2410-s.JPG
2609 ms
DSC_2489-s.JPG
2991 ms
DSC_2428-s.JPG
3003 ms
DSC_2457_1-s.JPG
3813 ms
DSC_2466-s.JPG
3957 ms
blog_qr.png
3737 ms
__utm.gif
27 ms
header.gif
910 ms
middle.gif
464 ms
ca-pub-5330715798156668.js
93 ms
zrt_lookup.html
147 ms
show_ads_impl.js
87 ms
date.gif
454 ms
title.gif
467 ms
sidetiltle.gif
459 ms
ads
152 ms
checkplayer.js
389 ms
osd.js
24 ms
ads
161 ms
bg_footer.gif
459 ms
abg.js
21 ms
swfobject.js
362 ms
flensed.js
369 ms
bar_logo.gif
229 ms
0.gif
362 ms
styles.css
459 ms
bar_bg.gif
231 ms
blue.boo-log.com accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
blue.boo-log.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
blue.boo-log.com 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
Mobile Friendly
Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).
Impact
Issue
Document uses legible font sizes
Tap targets are not sized appropriately
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Blue.boo-log.com 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.boo-log.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.
blue.boo-log.com
Open Graph data is detected on the main page of Blue Boo Log. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: