20.9 sec in total
1.7 sec
18 sec
1.1 sec
Welcome to bess.jp homepage info - get ready to check Bess best content for Japan right away, or after learning these important things about bess.jp
ログハウス、木の家のBESS。ログハウスや都市型木の家から、梺ぐらしが似合う家まで、5シリーズをラインナップ。全国で展開しています。ログハウス、木の家はBESSへ。
Visit bess.jpWe analyzed Bess.jp page load time and found that the first response time was 1.7 sec and then it took 19.2 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.
bess.jp performance score
name
value
score
weighting
Value7.5 s
1/100
10%
Value9.5 s
0/100
25%
Value20.3 s
0/100
10%
Value2,850 ms
3/100
30%
Value1.001
2/100
15%
Value34.3 s
0/100
10%
1717 ms
1306 ms
593 ms
5739 ms
34 ms
Our browser made a total of 80 requests to load all elements on the main page. We found that 63% of them (50 requests) were addressed to the original Bess.jp, 5% (4 requests) were made to Google-analytics.com and 5% (4 requests) were made to F.vimeocdn.com. The less responsive or slowest element that took the longest time to load (7.4 sec) belongs to the original domain Bess.jp.
Page size can be reduced by 347.8 kB (12%)
2.9 MB
2.5 MB
In fact, the total size of Bess.jp main page is 2.9 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. 30% of websites need less resources to load. Images take 2.4 MB which makes up the majority of the site volume.
Potential reduce by 19.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. This page needs HTML code to be minified as it can gain 3.2 kB, which is 13% 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 19.0 kB or 77% of the original size.
Potential reduce by 24.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. Bess images are well optimized though.
Potential reduce by 82.1 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 82.1 kB or 38% of the original size.
Potential reduce by 221.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. Bess.jp needs all CSS files to be minified and compressed as it can save up to 221.8 kB or 90% of the original size.
Number of requests can be reduced by 26 (36%)
73
47
The browser has sent 73 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Bess. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 17 to 1 for JavaScripts and as a result speed up the page load time.
bess.jp
1717 ms
www.bess.jp
1306 ms
index.html
593 ms
base.css
5739 ms
jquery.min.js
34 ms
jquery.easing.1.3.js
1934 ms
froogaloop.min.js
388 ms
lm.js
397 ms
header.js
401 ms
top.js
790 ms
main.js
1576 ms
s_retargeting.js
587 ms
conversion.js
21 ms
logo_01.png
487 ms
icn_house_01.png
487 ms
icn_request.png
487 ms
icn_serch_02.png
488 ms
btn_search.gif
488 ms
icn_house.gif
489 ms
icn_form.gif
887 ms
icn_fb_01.png
887 ms
icn_insta_01.png
893 ms
news_20150406.jpg
894 ms
icn_fb_01.png
898 ms
icn_insta_01.png
907 ms
txt_01.png
1318 ms
txt_02.png
1288 ms
txt_03.png
1287 ms
txt_04.png
1274 ms
txt_05.png
1323 ms
txt_06.png
1335 ms
txt_07.png
1666 ms
txt_08.png
1705 ms
txt_09.png
1707 ms
txt_10.png
1698 ms
icn_arrow_01.gif
1720 ms
text_catch.png
1716 ms
icn_fb.png
2060 ms
icn_tw.png
2889 ms
logo_02.png
2931 ms
icon_paper_02.png
2669 ms
icn_house_03.png
2107 ms
bnr_07.jpg
2555 ms
bnr_08.jpg
3275 ms
bnr_03.jpg
2698 ms
gtm.js
296 ms
118095714
364 ms
icn_arrow_01.png
2933 ms
bg_house_01.jpg
5692 ms
bg_house_02.jpg
6684 ms
bg_house_03.jpg
5800 ms
125 ms
tag.js
51 ms
tag
54 ms
118095713
101 ms
analytics.js
15 ms
76 ms
collect
37 ms
collect
25 ms
collect
27 ms
player.js
184 ms
player.css
163 ms
ga.js
112 ms
vuid.min.js
177 ms
collect
231 ms
collect
228 ms
bg_house_04.jpg
5432 ms
bg_house_05.jpg
5109 ms
bg_house_07.jpg
5731 ms
bg_house_08.jpg
7439 ms
__utm.gif
41 ms
__utm.gif
27 ms
proxy.html
59 ms
505035974.jpg
155 ms
505035140.jpg
118 ms
conversion_async.js
32 ms
25 ms
49 ms
53 ms
30 ms
bess.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.
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
Links do not have a discernible name
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.
bess.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
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
bess.jp SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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 doesn't use 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 Bess.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 Bess.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.
bess.jp
Open Graph data is detected on the main page of Bess. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: