10.5 sec in total
470 ms
9.4 sec
639 ms
Click here to check amazing Wi Ho content for Japan. Otherwise, check out these important facts you probably never knew about wi-ho.net
WiFiBOXストアをご利用になるには、JavaScript が有効になっている必要があります。このブラウザでは、JavaScript が無効になっているか、サポートされていないようです。ブラウザの設定を変更して JavaScript を有効にするか、別のブラウザでもう一度お試しください。 トップページに戻る
Visit wi-ho.netWe analyzed Wi-ho.net page load time and found that the first response time was 470 ms and then it took 10 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
wi-ho.net performance score
name
value
score
weighting
Value8.1 s
0/100
10%
Value14.6 s
0/100
25%
Value15.6 s
0/100
10%
Value1,250 ms
19/100
30%
Value0.189
65/100
15%
Value22.0 s
1/100
10%
470 ms
1742 ms
1081 ms
1437 ms
1514 ms
Our browser made a total of 159 requests to load all elements on the main page. We found that 67% of them (107 requests) were addressed to the original Wi-ho.net, 6% (10 requests) were made to Static.xx.fbcdn.net and 4% (7 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (2.6 sec) belongs to the original domain Wi-ho.net.
Page size can be reduced by 678.5 kB (34%)
2.0 MB
1.3 MB
In fact, the total size of Wi-ho.net main page is 2.0 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. 55% of websites need less resources to load. Images take 1.3 MB which makes up the majority of the site volume.
Potential reduce by 59.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. 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 59.8 kB or 77% of the original size.
Potential reduce by 212.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. Obviously, Wi Ho needs image optimization as it can save up to 212.1 kB or 16% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 316.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 316.4 kB or 66% of the original size.
Potential reduce by 90.1 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. Wi-ho.net needs all CSS files to be minified and compressed as it can save up to 90.1 kB or 83% of the original size.
Number of requests can be reduced by 61 (40%)
152
91
The browser has sent 152 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Wi Ho. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 40 to 1 for JavaScripts and from 14 to 1 for CSS and as a result speed up the page load time.
wi-ho.net
470 ms
www.wi-ho.net
1742 ms
import.css
1081 ms
jquery.qtip.css
1437 ms
top.css
1514 ms
top_banner.css
1647 ms
colorbox.css
1648 ms
popup_style.css
828 ms
common.js
993 ms
jquery-1.8.3.min.js
1977 ms
jquery.scrollTo.min.js
1244 ms
subnavi.js
1410 ms
fixHeight.js
1576 ms
biggerLink.js
1608 ms
jquery.bxslider.min.js
1688 ms
jquery.qtip.min.js
2074 ms
top.js
1956 ms
jqtransform.js
2009 ms
jquery.colorbox.js
2045 ms
popup_config.js
2131 ms
styles.css
1973 ms
jquery.js
2554 ms
jquery-migrate.min.js
2057 ms
jquery.form.min.js
1745 ms
scripts.js
1813 ms
wp-embed.min.js
1810 ms
si.js
58 ms
s_retargeting.js
532 ms
conversion.js
17 ms
reset.css
1327 ms
modules.css
1334 ms
base.css
1718 ms
www.wi-ho.net
939 ms
cse.js
45 ms
wp-emoji-release.min.js
491 ms
btn_menu.png
273 ms
logo.png
275 ms
logo_sp.png
274 ms
logo_ts.png
274 ms
ico_gnav01.png
177 ms
ico_gnav02.png
376 ms
ico_gnav03.png
377 ms
ico_gnav04.png
376 ms
ico_gnav05.png
379 ms
ico_gnav06.png
383 ms
ico_gnav07.png
663 ms
20160229_omoidetrip_banner_new-1.jpg
1469 ms
bg_default.jpg
1428 ms
img_cloud.png
908 ms
icon_speech.png
661 ms
img_intro01.jpg
1554 ms
img_intro02.jpg
1184 ms
icon_wiho.png
840 ms
icon_plane.gif
1019 ms
img_charge01.jpg
1973 ms
img_charge02.jpg
1551 ms
img_iphone.png
1361 ms
img_enhance.gif
1541 ms
icon_heart.gif
1594 ms
img_mobile.gif
1642 ms
icon_yellow.gif
1716 ms
img_usb.gif
1729 ms
btn_more.png
1715 ms
bnr_banner02.jpg
1759 ms
bnr_banner03.jpg
1816 ms
bnr_free_wiho.gif
1885 ms
bnr_LCC.gif
1899 ms
img_apply.png
2440 ms
img_step01.png
1926 ms
gtm.js
101 ms
img_pick.png
1987 ms
cse.js
123 ms
sdk.js
259 ms
smarticon
51 ms
41 ms
7ee53bce-a3e2-44cb-b97e-1b630f183c94.js
50 ms
analytics.js
7 ms
conversion_async.js
27 ms
jsapi
136 ms
collect
10 ms
collect
158 ms
120 ms
16 ms
WRf4.js
4 ms
100 ms
img_step02.png
1879 ms
conversion.js
611 ms
country_code.json
1810 ms
img_box.png
1841 ms
img_step04.png
1879 ms
img_use.png
1900 ms
default+ja.css
27 ms
default.css
34 ms
default+ja.I.js
33 ms
ga-audiences
52 ms
default.css
69 ms
120 ms
xd_arbiter.php
297 ms
xd_arbiter.php
396 ms
img_step03.png
1842 ms
bg_load.png
1884 ms
new.png
1888 ms
img_whatis01.gif
1949 ms
img_whatis.gif
1969 ms
img_privacy.gif
1731 ms
img_qr.gif
1772 ms
flogo.gif
1766 ms
conversion.js
581 ms
beacon.gif
154 ms
bg_search.png
1663 ms
bg_gnav.png
1619 ms
btn_hd_reserve.png
1525 ms
bg_alpha.png
1412 ms
bnr_top.png
1609 ms
888 ms
fbevents.js
41 ms
bg_section_bottom.gif
1193 ms
20 ms
bg_wi.gif
1210 ms
bg_star.gif
1161 ms
bg_heading.png
1156 ms
bg_block.gif
1208 ms
bg_block_bottom.gif
1204 ms
btn_reservation.png
1564 ms
bg_block01.gif
1161 ms
bg_block01_top.gif
1157 ms
bg_block01_bottom.gif
1197 ms
ico_arrow07.gif
1220 ms
bg_release_hd.gif
1223 ms
bg_bullet01.gif
1166 ms
bg_pink.gif
1192 ms
bg_yellow.gif
1216 ms
bg_whatis_top.gif
1188 ms
bg_whatis_mid.gif
1212 ms
bg_whatis_bottom.gif
1174 ms
btn_pagetop.png
1150 ms
bg_fnavareainner.gif
1209 ms
bg_fnavlink.gif
1188 ms
btn_visual.png
1196 ms
print.css
166 ms
collect
15 ms
page.php
89 ms
xPv7gOXb_eI.css
178 ms
_rx8naC75Dy.js
259 ms
t-KLv3gqZy0.js
291 ms
uLtKx7ldlvR.js
379 ms
12524273_1711474752400087_2132826363206898122_n.jpg
174 ms
10262153_1550057525208478_8241096733476990215_n.png
210 ms
564725_430084413697704_421946349_n.jpg
249 ms
12509366_1069386739760752_2789503862541871513_n.jpg
280 ms
403920_137117303093509_1641741979_n.jpg
283 ms
576365_449110331795048_1277099568_n.jpg
292 ms
12239509_897671550340406_1689422711248508172_n.jpg
290 ms
wL6VQj7Ab77.png
132 ms
CSXXCvknpgK.png
47 ms
R9a_DtVRZgv.js
42 ms
cUDgRFxaoIk.js
42 ms
0JBr1QHp8Gi.js
38 ms
kDOzhTr2W91.js
76 ms
wi-ho.net 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
wi-ho.net 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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
wi-ho.net SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Document doesn't have a valid hreflang
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
EN
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Wi-ho.net can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed Japanese language. Our system also found out that Wi-ho.net 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.
wi-ho.net
Open Graph data is detected on the main page of Wi Ho. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: