9.6 sec in total
841 ms
8.6 sec
187 ms
Click here to check amazing Behome content. Otherwise, check out these important facts you probably never knew about behome.jp
美容院・美容室・ヘアサロンのベホマは、阿佐ヶ谷駅北口より徒歩5分にあります。店内見学でも、髪型の相談だけでも、お気軽に扉を開けてくださいね!9周年です♪
Visit behome.jpWe analyzed Behome.jp page load time and found that the first response time was 841 ms and then it took 8.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
behome.jp performance score
name
value
score
weighting
Value2.6 s
63/100
10%
Value3.5 s
65/100
25%
Value5.1 s
61/100
10%
Value120 ms
97/100
30%
Value0
100/100
15%
Value2.8 s
97/100
10%
841 ms
870 ms
18 ms
703 ms
718 ms
Our browser made a total of 50 requests to load all elements on the main page. We found that 92% of them (46 requests) were addressed to the original Behome.jp, 4% (2 requests) were made to Google-analytics.com and 2% (1 request) were made to Google.com. The less responsive or slowest element that took the longest time to load (6.3 sec) belongs to the original domain Behome.jp.
Page size can be reduced by 295.3 kB (16%)
1.8 MB
1.5 MB
In fact, the total size of Behome.jp 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. 15% of websites need less resources to load. Images take 1.7 MB which makes up the majority of the site volume.
Potential reduce by 7.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 7.0 kB or 68% of the original size.
Potential reduce by 228.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. Obviously, Behome needs image optimization as it can save up to 228.2 kB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 34.2 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 34.2 kB or 56% of the original size.
Potential reduce by 26.0 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. Behome.jp needs all CSS files to be minified and compressed as it can save up to 26.0 kB or 83% of the original size.
Number of requests can be reduced by 33 (67%)
49
16
The browser has sent 49 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Behome. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 8 to 1 for JavaScripts and as a result speed up the page load time.
behome.jp
841 ms
style.css
870 ms
jsapi
18 ms
yuga.js
703 ms
sisso.js
718 ms
jQselectable.js
537 ms
ImgSrcChanges2.js
363 ms
jquery.slider.min.js
699 ms
jquery.min.js
29 ms
ga.js
43 ms
bg_top.png
355 ms
bg_body.jpg
1597 ms
spacer.gif
348 ms
icon_email.gif
348 ms
icon_tel.gif
348 ms
logo_pc4.png
550 ms
navi_01.gif
671 ms
navi_02.gif
696 ms
navi_03.gif
701 ms
navi_04.gif
698 ms
navi_05.gif
896 ms
navi_06.gif
1022 ms
navi_07.gif
1063 ms
navi_08.gif
1063 ms
btn_company_recruit.jpg
1251 ms
tumiki%20naka.JPG
4527 ms
2016.03.jpg
3127 ms
top4.JPG
6266 ms
top3.JPG
3049 ms
top5.JPG
5513 ms
title_news.png
1940 ms
icon_li.gif
2282 ms
title_blog.png
2633 ms
bg_blog_s.gif
2990 ms
bg_blog_top.gif
3332 ms
bg_blog_bottom.gif
3400 ms
title_recommends.png
3476 ms
btn_facebook.png
4408 ms
btn_twitter.png
4495 ms
slider_prev.png
3823 ms
slider_next.png
4175 ms
__utm.gif
13 ms
navi_01_o.gif
344 ms
navi_02_o.gif
344 ms
navi_03_o.gif
349 ms
navi_04_o.gif
347 ms
navi_05_o.gif
348 ms
navi_06_o.gif
352 ms
navi_07_o.gif
685 ms
navi_08_o.gif
689 ms
behome.jp 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.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
Image elements do not have [alt] attributes
Links do not have a discernible name
behome.jp 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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
behome.jp 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
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Behome.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 Behome.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.
behome.jp
Open Graph description is not detected on the main page of Behome. 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: