12.5 sec in total
2.2 sec
9.9 sec
401 ms
Visit hab.co.jp now to see the best up-to-date Hab content for Japan and also check out these interesting facts you probably never knew about hab.co.jp
テレビ朝日系列【HAB北陸朝日放送】公式サイト。テレビ番組、アナウンサー紹介、ニュース、天気、イベント、プレゼント情報など、最新の情報をお届け!!北陸・石川県・金沢の情報ならHABへ!
Visit hab.co.jpWe analyzed Hab.co.jp page load time and found that the first response time was 2.2 sec and then it took 10.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
hab.co.jp performance score
name
value
score
weighting
Value8.5 s
0/100
10%
Value28.8 s
0/100
25%
Value16.3 s
0/100
10%
Value2,230 ms
6/100
30%
Value0.417
23/100
15%
Value25.8 s
0/100
10%
2203 ms
392 ms
587 ms
397 ms
7 ms
Our browser made a total of 127 requests to load all elements on the main page. We found that 75% of them (95 requests) were addressed to the original Hab.co.jp, 7% (9 requests) were made to Google.com and 3% (4 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (3.7 sec) belongs to the original domain Hab.co.jp.
Page size can be reduced by 195.4 kB (18%)
1.1 MB
913.7 kB
In fact, the total size of Hab.co.jp main page is 1.1 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. 50% of websites need less resources to load. Images take 828.8 kB which makes up the majority of the site volume.
Potential reduce by 32.9 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 5.1 kB, which is 12% 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 32.9 kB or 75% of the original size.
Potential reduce by 33.7 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. Hab images are well optimized though.
Potential reduce by 89.6 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 89.6 kB or 47% of the original size.
Potential reduce by 39.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. Hab.co.jp needs all CSS files to be minified and compressed as it can save up to 39.1 kB or 82% of the original size.
Number of requests can be reduced by 46 (38%)
122
76
The browser has sent 122 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Hab. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
hab.co.jp
2203 ms
default.css
392 ms
base.css
587 ms
jquery.bxslider.css
397 ms
jquery-1.10.0.min.js
7 ms
smoothscroll.js
422 ms
rollover.js
428 ms
heightLine.js
647 ms
jquery.bxslider.js
1174 ms
getPlayLists_jch.js
835 ms
client.js
72 ms
smp.js
808 ms
cb=gapi.loaded_0
94 ms
ga.js
89 ms
convert.js
399 ms
sticker.jpg
1502 ms
20140212144821.jpg
879 ms
thumb.jpg
823 ms
logo.gif
207 ms
global_08.gif
237 ms
btn_login.png
393 ms
charactor.png
398 ms
btn_present.gif
401 ms
station_live.gif
453 ms
mainslideBigimg000451.jpeg
1166 ms
mainslideBigimg000475.jpeg
1186 ms
mainslideBigimg000471.jpeg
1570 ms
mainslideBigimg000477.jpeg
1212 ms
mainslideSmallimg000452.jpeg
808 ms
mainslideSmallimg000476.jpeg
862 ms
mainslideSmallimg000472.jpeg
1216 ms
mainslideSmallimg000478.jpeg
1221 ms
title_program.gif
1566 ms
btn_program.png
1589 ms
movie.jpg
1769 ms
btn_newsDetail.png
1630 ms
icon_new.png
1662 ms
btn_news.png
1978 ms
title_new.gif
1980 ms
icon_new02.gif
2009 ms
btn_detail.png
2041 ms
icon_new04.gif
2096 ms
icon_new05.gif
2123 ms
icon_new01.gif
2366 ms
title_osusume.gif
2367 ms
subtitle_osusume02.gif
2396 ms
subtitle_osusume03.gif
2433 ms
btn_toTop.png
2522 ms
btn_twitter_hab_big.png
2532 ms
btn_facebook_big.png
2729 ms
btn_twitter_big.png
2775 ms
icon_facebook.png
2836 ms
icon_twitter.png
2853 ms
cse.js
67 ms
2979 ms
cse.js
95 ms
__utm.gif
45 ms
postmessageRelay
59 ms
proxy.html
85 ms
jsapi
60 ms
api.js
37 ms
core:rpc:shindig.random:shindig.sha1.js
97 ms
2536007149-postmessagerelay.js
94 ms
realtime.php
2945 ms
cb=gapi.loaded_0
12 ms
icon_google.png
2909 ms
default+ja.css
12 ms
default.css
16 ms
default+ja.I.js
25 ms
default.css
35 ms
rest
134 ms
async-ads.js
57 ms
google_custom_search_watermark.gif
31 ms
small-logo.png
15 ms
search_box_icon.png
16 ms
clear.png
14 ms
pv_beacon.gif
387 ms
icon_mixi.png
2779 ms
bg_member.gif
2804 ms
bigner.png
2858 ms
playlistItems
28 ms
bg_gnav.gif
2921 ms
gnav_01.gif
2732 ms
gnav_02.gif
2682 ms
gnav_03.gif
2422 ms
gnav_04.gif
2451 ms
gnav_05.gif
2464 ms
bg_contents.gif
2520 ms
bg_contents_top.jpg
3680 ms
bg_mv.gif
2381 ms
bg_weather.gif
2405 ms
line_tab.png
2418 ms
tab_01_o.gif
2438 ms
tab_02.gif
2513 ms
tab_03.gif
2589 ms
tab_04.gif
2407 ms
bg_tabArea.gif
2435 ms
footer_arrow_small.png
2495 ms
bg_footer.gif
2543 ms
footer_arrow_big.png
2649 ms
bigbanner07.png
3094 ms
bx_loader.gif
2496 ms
prev_mv.png
2584 ms
next_mv.png
2568 ms
global_19.gif
2697 ms
jquery.carouFredSel-6.1.0-packed.js
2491 ms
u_t_realtime_01.gif
2161 ms
u_t_realtime_02.gif
2230 ms
bg_bnn.gif
225 ms
bannerImg000417.jpeg
367 ms
bannerImg000441.jpeg
385 ms
bannerImg000430.jpeg
393 ms
bannerImg000412.jpeg
412 ms
bannerImg000339.jpeg
423 ms
bannerImg000414.jpeg
609 ms
bannerImg000423.jpeg
728 ms
bannerImg000023.jpeg
825 ms
bannerImg000481.jpeg
834 ms
bannerImg000474.jpeg
822 ms
bannerImg000479.jpeg
817 ms
bannerImg000480.jpeg
1017 ms
bannerImg000462.jpeg
1117 ms
bannerImg000473.jpeg
1207 ms
prev_bnn.png
1213 ms
next_bnn.png
1214 ms
__utm.gif
11 ms
pv_beacon.gif
369 ms
hab.co.jp 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.
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
hab.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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
Issues were logged in the Issues panel in Chrome Devtools
hab.co.jp 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
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 Hab.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 Hab.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.
hab.co.jp
Open Graph description is not detected on the main page of Hab. 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: