6.7 sec in total
1.7 sec
4.7 sec
357 ms
Click here to check amazing Whhl content. Otherwise, check out these important facts you probably never knew about whhl.net
ワールドホテルホットラインでは、一流の国内ホテル、海外ホテルが数多く揃っています。世界中に展開するチェーンや独立系の小さなホテル、デザインの優れたホテルからクラッシックなホテルなど、4ッ星・5ッ星クラスのホテルを取り揃えています。
Visit whhl.netWe analyzed Whhl.net page load time and found that the first response time was 1.7 sec and then it took 5.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
whhl.net performance score
name
value
score
weighting
Value6.0 s
4/100
10%
Value6.5 s
9/100
25%
Value10.1 s
9/100
10%
Value350 ms
73/100
30%
Value0.219
57/100
15%
Value6.4 s
59/100
10%
1667 ms
960 ms
1700 ms
539 ms
490 ms
Our browser made a total of 63 requests to load all elements on the main page. We found that 79% of them (50 requests) were addressed to the original Whhl.net, 6% (4 requests) were made to Platform.twitter.com and 5% (3 requests) were made to J1.ax.xrea.com. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain Whhl.net.
Page size can be reduced by 130.8 kB (22%)
593.6 kB
462.8 kB
In fact, the total size of Whhl.net main page is 593.6 kB. 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 414.3 kB which makes up the majority of the site volume.
Potential reduce by 47.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 16.5 kB, which is 28% 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 47.8 kB or 82% of the original size.
Potential reduce by 656 B
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. Whhl images are well optimized though.
Potential reduce by 64.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 64.1 kB or 64% of the original size.
Potential reduce by 18.2 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. Whhl.net needs all CSS files to be minified and compressed as it can save up to 18.2 kB or 84% of the original size.
Number of requests can be reduced by 50 (82%)
61
11
The browser has sent 61 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Whhl. 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 4 to 1 for CSS and as a result speed up the page load time.
whhl.net
1667 ms
styles-index.css
960 ms
jquery-1.6.1.min.js
1700 ms
jquery.li-scroller.1.0.js
539 ms
li-scroller.css
490 ms
jquery.min.js
194 ms
l.j
442 ms
main_background.gif
191 ms
x.gif
147 ms
l4.f
718 ms
ulogin.jsp
184 ms
image_logo_whhl.gif
318 ms
telbook05.jpg
720 ms
ts.gif
291 ms
widgets.js
107 ms
ct_115.jpg
868 ms
line239px.gif
187 ms
banner.jpg
695 ms
banner.jpg
496 ms
banner.jpg
821 ms
banner.jpg
964 ms
banner.jpg
931 ms
banner.jpg
692 ms
banner.jpg
1166 ms
banner.jpg
1020 ms
title_green_specialfree.gif
875 ms
butten_specialfree.jpg
988 ms
notice.gif
1233 ms
banner_s_left.jpg
1094 ms
banner_s_center.jpg
1337 ms
banner_s_right.jpg
1317 ms
banner_s_left.jpg
1197 ms
banner_s_center.jpg
1411 ms
banner_s_right.jpg
1336 ms
banner_s_left.jpg
1374 ms
banner_s_center.jpg
1591 ms
banner_s_right.jpg
1485 ms
title_green_quickretrieval.gif
1500 ms
line_sep_quick.gif
1521 ms
title_green_domestic.gif
1544 ms
banner.jpg
1775 ms
1823.jpg
2141 ms
84101.jpg
1993 ms
83884.jpg
1906 ms
84331.jpg
2055 ms
pickup.gif
1770 ms
20935.jpg
1956 ms
line169px.gif
1932 ms
timeline.d11f7a3b3287fb94220e8ee6d03cc772.js
133 ms
16348.jpg
1952 ms
84330.jpg
1958 ms
84328.jpg
2139 ms
syndication
97 ms
356982567267885056
225 ms
title_green_login.gif
1875 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
29 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
107 ms
butten_login.gif
1739 ms
whhl-logo_normal.gif
208 ms
CdLDmv6UYAAnIXZ.jpg:small
251 ms
line_sep_white.gif
1601 ms
topmark_arrow.gif
1579 ms
jot
26 ms
whhl.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
<frame> or <iframe> elements do not have a title
whhl.net best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
whhl.net 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 uses legible font sizes
N/A
N/A
SHIFT_JIS
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Whhl.net can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Whhl.net 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.
whhl.net
Open Graph description is not detected on the main page of Whhl. 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: