6.3 sec in total
1.1 sec
4.9 sec
314 ms
Click here to check amazing Honka content for Japan. Otherwise, check out these important facts you probably never knew about honka.co.jp
ログハウスならホンカ・ジャパン。北欧フィンランド生まれの世界No.1ログハウスメーカー、ホンカ・ジャパン。輸入住宅、本物の木の家をお届けしています。
Visit honka.co.jpWe analyzed Honka.co.jp page load time and found that the first response time was 1.1 sec and then it took 5.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
honka.co.jp performance score
name
value
score
weighting
Value5.6 s
6/100
10%
Value17.2 s
0/100
25%
Value23.5 s
0/100
10%
Value1,210 ms
20/100
30%
Value0.561
12/100
15%
Value63.0 s
0/100
10%
1146 ms
1010 ms
350 ms
360 ms
555 ms
Our browser made a total of 55 requests to load all elements on the main page. We found that 80% of them (44 requests) were addressed to the original Honka.co.jp, 4% (2 requests) were made to Google.com and 4% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.9 sec) belongs to the original domain Honka.co.jp.
Page size can be reduced by 336.9 kB (29%)
1.2 MB
823.5 kB
In fact, the total size of Honka.co.jp main page is 1.2 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. 25% of websites need less resources to load. Images take 871.3 kB which makes up the majority of the site volume.
Potential reduce by 28.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.9 kB, which is 11% 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 28.0 kB or 78% of the original size.
Potential reduce by 134.5 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, Honka needs image optimization as it can save up to 134.5 kB or 15% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 117.4 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 117.4 kB or 64% of the original size.
Potential reduce by 56.9 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. Honka.co.jp needs all CSS files to be minified and compressed as it can save up to 56.9 kB or 82% of the original size.
Number of requests can be reduced by 11 (21%)
52
41
The browser has sent 52 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Honka. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 7 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
honka.co.jp
1146 ms
style.css
1010 ms
default.css
350 ms
nivo-slider.css
360 ms
jquery.fancybox.css
555 ms
jquery.min.js
1336 ms
jsapi
42 ms
jquery.fancybox.pack.js
909 ms
main.js
538 ms
jquery.nivo.slider.pack.js
712 ms
reset.css
182 ms
btn-inquiry.png
361 ms
btn-contact.png
172 ms
img-tel.png
919 ms
sp-icon-menu.png
192 ms
sp-menu-about.png
360 ms
sp-menu-special.png
176 ms
sp-menu-lineup.png
338 ms
sp-menu-gallery.png
350 ms
sp-menu-voice.png
573 ms
sp-menu-network.png
506 ms
tunne_top_cover.png
1566 ms
hj25_top_bnr.png
1474 ms
hj_top_lifewithhonka.jpg
1475 ms
bnr_main_db_1.png
1346 ms
sp-btn-inquiry.png
1373 ms
sp-img-tel.png
1284 ms
bnr_mini_markosroom2.png
1877 ms
bnr_model55.png
1682 ms
bnr_25th_sub.png
1754 ms
bnr_business_use.png
2009 ms
bnr_%20for_children.png
2229 ms
bnr_business_view.png
1911 ms
bnr_%20rd_clubhonka.gif
2017 ms
bnr_%20rd_facebook.gif
1945 ms
bnr_c_dealer.png
2062 ms
bnr_c_2.jpg
2432 ms
bnr_%20rd_worldofhonkabook.gif
2516 ms
bnr_%20rd_honka_com.gif
2366 ms
6532_3.png
2857 ms
no1_bnr.jpg
2614 ms
all.js
274 ms
575 ms
analytics.js
24 ms
logo.png
2304 ms
menubar.png
2629 ms
loading.gif
2478 ms
arrows.png
2509 ms
collect
14 ms
collect
54 ms
ga-audiences
17 ms
129 ms
xd_arbiter.php
227 ms
xd_arbiter.php
432 ms
cssreset-min.css
9 ms
honka.co.jp 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-hidden="true"] elements contain focusable descendents
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
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
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
honka.co.jp best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
honka.co.jp SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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 Honka.co.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 Honka.co.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.
honka.co.jp
Open Graph description is not detected on the main page of Honka. 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: