8.6 sec in total
604 ms
7.7 sec
300 ms
Welcome to whitehouse.co.jp homepage info - get ready to check Whitehouse best content for Japan right away, or after learning these important things about whitehouse.co.jp
輸入車、輸入二輪車正規ディーラーのホワイトハウスグループ。輸入車、輸入二輪車、中古車販売買取、キャンピングカー、オフロードビークルなど、お客さまの豊かなカーライフをサポートいたします
Visit whitehouse.co.jpWe analyzed Whitehouse.co.jp page load time and found that the first response time was 604 ms and then it took 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.
whitehouse.co.jp performance score
name
value
score
weighting
Value7.8 s
0/100
10%
Value16.0 s
0/100
25%
Value16.8 s
0/100
10%
Value960 ms
29/100
30%
Value1.581
0/100
15%
Value15.4 s
7/100
10%
604 ms
816 ms
396 ms
405 ms
401 ms
Our browser made a total of 117 requests to load all elements on the main page. We found that 84% of them (98 requests) were addressed to the original Whitehouse.co.jp, 4% (5 requests) were made to Scontent-nrt1-1.xx.fbcdn.net and 3% (3 requests) were made to V6.advg.jp. The less responsive or slowest element that took the longest time to load (2.8 sec) belongs to the original domain Whitehouse.co.jp.
Page size can be reduced by 110.9 kB (3%)
3.6 MB
3.5 MB
In fact, the total size of Whitehouse.co.jp main page is 3.6 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. 35% of websites need less resources to load. Images take 3.4 MB which makes up the majority of the site volume.
Potential reduce by 22.7 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 22.7 kB or 79% of the original size.
Potential reduce by 4.6 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. Whitehouse images are well optimized though.
Potential reduce by 72.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 72.1 kB or 49% of the original size.
Potential reduce by 11.6 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. Whitehouse.co.jp needs all CSS files to be minified and compressed as it can save up to 11.6 kB or 78% of the original size.
Number of requests can be reduced by 36 (34%)
107
71
The browser has sent 107 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Whitehouse. 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.
whitehouse.co.jp
604 ms
www.whitehouse.co.jp
816 ms
normalize.css
396 ms
default.css
405 ms
index.css
401 ms
c_header_logo01.gif
408 ms
c_header_t01.gif
432 ms
c_header_t02.gif
433 ms
c_header_t03.gif
592 ms
c_header_btn01.gif
600 ms
c_header_btn02.gif
601 ms
c_nav01.gif
604 ms
c_nav02.gif
624 ms
c_nav03.gif
631 ms
c_nav04.gif
788 ms
c_nav05.gif
799 ms
c_nav06.gif
802 ms
c_nav07.gif
801 ms
c_nav08.gif
833 ms
i_car_p01.jpg
1681 ms
i_car_p02.jpg
1578 ms
i_car_p03.jpg
1797 ms
i_car_p04.jpg
1799 ms
i_car_p05.jpg
1599 ms
i_car_p06.jpg
1464 ms
i_car_p07.jpg
1886 ms
i_car_p08.jpg
1973 ms
i_car_p09.jpg
2201 ms
i_car_p10.jpg
2103 ms
i_car_p11.jpg
2394 ms
i_car_p12.jpg
2196 ms
i_car_p13.jpg
2307 ms
i_car_p14.jpg
2370 ms
i_cycle_p01.jpg
2523 ms
i_cycle_p02.jpg
2599 ms
i_cycle_p03.jpg
2602 ms
i_cycle_p04.jpg
2726 ms
ojs
547 ms
jquery-1.11.2.min.js
2571 ms
common.js
2207 ms
index.js
2341 ms
newsevent.js
2394 ms
topics.js
2377 ms
i_cycle_p05.jpg
2581 ms
i_cycle_p06.jpg
2725 ms
i_cycle_p07.jpg
2576 ms
i_cycle_p08.jpg
2573 ms
i_cycle_p09.jpg
2598 ms
i_cycle_p10.jpg
2604 ms
i_cycle_p11.jpg
2791 ms
i_honda_p01.jpg
2738 ms
i_camp_p01.jpg
2591 ms
i_used_p01.jpg
2570 ms
i_offroad_p01.jpg
2602 ms
i_product_p01.jpg
2606 ms
i_car_btn01.png
2747 ms
i_car_btn02.png
2104 ms
i_car_btn03.png
2013 ms
i_car_btn04.png
2006 ms
i_car_btn05.png
1929 ms
i_car_btn06.png
1818 ms
i_car_btn07.png
1969 ms
i_car_btn08.png
1903 ms
i_car_btn09.png
1827 ms
i_car_btn10.png
1700 ms
i_car_btn11.png
1611 ms
i_car_btn12.png
1612 ms
i_car_btn13.png
1657 ms
i_car_btn14.png
1626 ms
c_close_btn01.gif
1620 ms
i_cycle_btn01.png
1480 ms
i_cycle_btn02.png
1415 ms
i_cycle_btn03.png
1415 ms
i_cycle_btn04.png
1560 ms
i_cycle_btn05.png
1481 ms
i_cycle_btn06.png
1470 ms
i_cycle_btn07.png
1422 ms
i_cycle_btn08.png
1431 ms
ga.js
29 ms
ojs2
362 ms
i_cycle_btn09.png
1414 ms
__utm.gif
12 ms
collect
56 ms
ga-audiences
47 ms
i_cycle_btn10.png
1356 ms
i_cycle_btn11.png
1256 ms
i_news_tit01.gif
1258 ms
7tn
534 ms
7tn
858 ms
7tn
869 ms
conversion.js
17 ms
us0
510 ms
i_topics_tit01.gif
1244 ms
i_topics_btn01.gif
1223 ms
i_bn01.gif
1235 ms
i_bn02.gif
1200 ms
i_bn03.gif
1242 ms
c_footer_logo01.gif
1238 ms
c_footer_pagetop01.gif
1219 ms
c_header_bg01.gif
1226 ms
c_content_bg01.gif
1238 ms
c_nav_bg01.gif
1195 ms
i_car_bg01.png
1234 ms
i_dot01.gif
1225 ms
42 ms
xml_portal
858 ms
fb_rss.json
1095 ms
us
2366 ms
16 ms
2016_02_23_recruit.jpg
613 ms
2016_02_23_tmcs.jpg
862 ms
2016_02_23_nagoya.jpg
427 ms
11248873_944698512261654_6015839873069854601_n.jpg
719 ms
11407223_940887569309415_6393777896206470680_n.jpg
881 ms
11401254_940395679358604_7858284465180984989_n.jpg
1055 ms
11423613_936161213115384_4678120890280005479_n.jpg
1226 ms
1654374_935493573182148_2593079162649534339_n.jpg
1230 ms
whitehouse.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.
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.
List items (<li>) are not contained within <ul> or <ol> parent elements.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Links do not have a discernible name
whitehouse.co.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
Browser errors were logged to the console
whitehouse.co.jp SEO score
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 Whitehouse.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 Whitehouse.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.
whitehouse.co.jp
Open Graph data is detected on the main page of Whitehouse. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: