6.6 sec in total
866 ms
5.5 sec
246 ms
Visit wdi.co.jp now to see the best up-to-date WDI content for Japan and also check out these interesting facts you probably never knew about wdi.co.jp
カプリチョーザ、ウルフギャング・ステーキハウス、ハードロックカフェ、サラベスなど、20以上のレストランブランドを国内外で展開している外食事業会社WDI GROUPのコーポレートサイトです。
Visit wdi.co.jpWe analyzed Wdi.co.jp page load time and found that the first response time was 866 ms and then it took 5.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
wdi.co.jp performance score
866 ms
323 ms
831 ms
494 ms
1833 ms
Our browser made a total of 84 requests to load all elements on the main page. We found that 95% of them (80 requests) were addressed to the original Wdi.co.jp, 2% (2 requests) were made to Fonts.googleapis.com and 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.4 sec) belongs to the original domain Wdi.co.jp.
Page size can be reduced by 422.6 kB (19%)
2.2 MB
1.8 MB
In fact, the total size of Wdi.co.jp main page is 2.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. 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 14.8 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.3 kB, which is 17% 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 14.8 kB or 75% of the original size.
Potential reduce by 26.1 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. WDI images are well optimized though.
Potential reduce by 336.7 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 336.7 kB or 82% of the original size.
Potential reduce by 44.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. Wdi.co.jp needs all CSS files to be minified and compressed as it can save up to 44.9 kB or 82% of the original size.
Number of requests can be reduced by 25 (30%)
83
58
The browser has sent 83 CSS, Javascripts, AJAX and image requests in order to completely render the main page of WDI. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
wdi.co.jp
866 ms
reset.css
323 ms
style.css
831 ms
grid.css
494 ms
jquery-1.6.3.js
1833 ms
jquery_auto.js
380 ms
superfish.js
643 ms
jquery.color.js
503 ms
jquery.easing.1.3.js
763 ms
mediaelement.js
1032 ms
orbit-1.2.3.css
675 ms
jquery.orbit-1.2.3.js
973 ms
logo_mouseon.js
851 ms
tms-0.3.js
960 ms
tms_presets.js
1014 ms
superfish.css
206 ms
galleriffic.css
322 ms
jquery.jscrollpane.css
302 ms
tm-slider.css
348 ms
css
24 ms
css
36 ms
analytics.js
72 ms
btn_eng.gif
167 ms
logo.gif
159 ms
btn_gnavi-1.gif
170 ms
btn_gnavi-news.gif
194 ms
btn_gnavi-2.gif
190 ms
btn_gnavi-3.gif
166 ms
btn_gnavi-4.gif
321 ms
btn_gnavi-5.gif
337 ms
btn_gnavi-6.gif
344 ms
btn_gnavi-7.gif
344 ms
btn_gnavi-8.gif
375 ms
slide1.jpg
1781 ms
slide2.jpg
1611 ms
slide3.jpg
1825 ms
menu_re-capri-logo.jpg
617 ms
menu_re-stone-logo.jpg
631 ms
menu_re-tony-logo.jpg
659 ms
menu_re-hard-logo.jpg
894 ms
menu_re-bubba-logo.jpg
906 ms
menu_re-cpk-logo.jpg
934 ms
menu_re-eggsn-logo.jpg
1114 ms
menu_re-century-logo.jpg
1124 ms
menu_re-primi-logo.jpg
1147 ms
menu_re-breeze-logo.jpg
1295 ms
menu_re-oysterbar-logo.jpg
1298 ms
menu_re-aquavit-logo.jpg
1344 ms
menu_re-sarabeths-logo.jpg
1492 ms
menu_re-kyogyu-logo.jpg
1494 ms
menu_re-balboa-logo.jpg
1568 ms
menu_re-utsuke-logo.jpg
1693 ms
menu_re-taor-logo.jpg
1698 ms
menu_re-wolfgangs-logo.jpg
1753 ms
menu_re-inakaya-logo.jpg
1771 ms
menu_re-sa-logo.jpg
1859 ms
banner_partyplan2015-3.png
2396 ms
btn_search.gif
1877 ms
collect
37 ms
banner_pepper.png
1797 ms
banner_recruit201507.jpg
1866 ms
banner4.jpg
1873 ms
banner_concierge-wide.jpg
1892 ms
loading.gif
1944 ms
bg-content.png
1919 ms
marker.gif
1896 ms
btn_eng_over.gif
1869 ms
btn_gnavi-1_over.gif
1879 ms
btn_gnavi-news_over.gif
1931 ms
btn_gnavi-2_over.gif
1945 ms
btn_gnavi-3_over.gif
1757 ms
btn_gnavi-4_over.gif
1774 ms
btn_gnavi-5_over.gif
1729 ms
btn_gnavi-6_over.gif
1542 ms
btn_gnavi-7_over.gif
1599 ms
btn_gnavi-8_over.gif
1611 ms
banner_partyplan2015-3_over.png
1787 ms
btn_search_over.gif
1476 ms
banner_pepper_over.png
1502 ms
banner_recruit201507_over.jpg
1373 ms
banner4_over.jpg
1427 ms
banner_concierge-wide_over.jpg
1395 ms
rotator-black.png
170 ms
pause-black.png
158 ms
wdi.co.jp SEO score
JA
N/A
SHIFT_JIS
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Wdi.co.jp can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Wdi.co.jp main page’s claimed encoding is shift_jis. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
wdi.co.jp
Open Graph description is not detected on the main page of WDI. 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: