TV-TOKYO.CO.JP テレ東・BSテレ東 7ch(公式)

tv-tokyo.co.jp Website Information

Daily Unique Visits: 376,449

Daily Page Views: 3,011,592

Income Per Day: $3,012

Estimated Value: $3,252,960

This website is located in Japan and is using following IP address 210.140.185.70. See the complete list of popular websites hosted in Japan.

tv-tokyo.co.jp is registered under .JP top-level domain. Please check other sites in .JP zone.

Website tv-tokyo.co.jp is using the following name servers:

  • dns-b.iij.ad.jp
  • dns-c.iij.ad.jp

and is probably hosted by AMAZON-02 - Amazon.com, Inc., US. See the full list of other websites hosted by AMAZON-02 - Amazon.com, Inc., US.

The highest website tv-tokyo.co.jp position in Alexa rank database was 3435 and the lowest rank position was 4203. Current position of tv-tokyo.co.jp in Alexa rank database is 4048.

Desktop speed score of tv-tokyo.co.jp (38/100) is better than the results of 13.38% of other sites and shows that the page desktop performance can be improved.

Mobile usability score of tv-tokyo.co.jp (91/100) is better than the results of 32.41% of other sites and means that the page is mobile-friendly.

Mobile speed score of tv-tokyo.co.jp (22/100) is better than the results of 5.33% of other sites and shows that the landing page performance on mobile devices is poor and can be improved.

Advertisement

tv-tokyo.co.jp Alexa Rank

The traffic rank is based on three months of aggregated historical traffic data from millions of Alexa Toolbar users and is a combined measure of page views and users.


tv-tokyo.co.jp whois

WHOIS gives you the ability to lookup any generic domains to find out the registered domain holder. WHOIS database are provided for information purposes only. It allows the public to check whether a specific domain name is still available or not and to obtain information related to the registration records of existing domain names.


[ JPRS database provides information on network administration. Its use is ]
[ restricted to network administration purposes. For further information, ]
[ use 'whois -h whois.jprs.jp help'. To suppress Japanese output, add'/e' ]
[ at the end of command, e.g. 'whois -h whois.jprs.jp xxx/e'. ]
Domain Information: [ドメイン情報]
a. [ドメイン名] TV-TOKYO.CO.JP
e. [そしきめい] かぶしきがいしゃ てれびとうきょう
f. [組織名] 株式会社 テレビ東京
g. [Organization] TV TOKYO Corporation
k. [組織種別] 株式会社
l. [Organization Type] Company
m. [登録担当者] SO26273JP
n. [技術連絡担当者] KS59321JP
p. [ネームサーバ] ns013-r63h5hbmpo40m4ik.r.d-53.info
p. [ネームサーバ] ns013-r63h5hbmpo40m4ik.r.d-53.jp
p. [ネームサーバ] ns013-r63h5hbmpo40m4ik.r.d-53.net
s. [署名鍵] 51083 13 2 (
63D0901C8D089FF7520C16FD8FB8D25C
84FA3927641C2D9215D798CE9CE3F922 )
[状態] Connected (2025/05/31)
[登録年月日] 1995/05/09
[接続年月日] 1995/07/07
[最終更新] 2024/06/01 01:02:25 (JST)

tv-tokyo.co.jp server information

Servers Location

tv-tokyo.co.jp desktop page speed rank

Last tested: 2018-10-07


Desktop Speed Bad
38/100

tv-tokyo.co.jp Desktop Speed Test Quick Summary


priority - 83Enable compression

Compressing resources with gzip or deflate can reduce the number of bytes sent over the network.

Enable compression for the following resources to reduce their transfer size by 810.9KiB (79% reduction).

Compressing http://www.tv-tokyo.co.jp/ could save 339.4KiB (86% reduction).
Compressing http://www.tv-tokyo.co.jp/js/main.js could save 227KiB (71% reduction).
Compressing http://www.tv-tokyo.co.jp/css/top.css could save 178.8KiB (86% reduction).
Compressing http://www.tv-tokyo.co.jp/index/scatalyst/s_code.js could save 39.6KiB (63% reduction).
Compressing http://www.tv-tokyo.co.jp/txcms/js/txcmsdata.pickup.js could save 6.7KiB (72% reduction).
Compressing http://d.socdm.com/adsv/v1?posall=SSPLOC&id=64339&….7.0&sdktype=3&t=json3 could save 4.8KiB (78% reduction).
Compressing https://j.zucks.net.zimg.jp/j?f=320748 could save 3.7KiB (58% reduction).
Compressing https://j.zucks.net.zimg.jp/j?f=320749 could save 3.7KiB (58% reduction).
Compressing http://www.tv-tokyo.co.jp/txcms/json/footerbanner/l.json could save 2.1KiB (60% reduction).
Compressing http://www.tv-tokyo.co.jp/txcms/json/jack/top.json could save 1.6KiB (70% reduction).
Compressing http://www.tv-tokyo.co.jp/txcms/json/footerbanner/s.json could save 1KiB (58% reduction).
Compressing http://www.tv-tokyo.co.jp/txcms/js/top.panel.js could save 739B (53% reduction).
Compressing http://www.tv-tokyo.co.jp/index/scatalyst/site/index_utf8.js could save 582B (54% reduction).
Compressing http://www.tv-tokyo.co.jp/txcms/json/footerbanner/r.json could save 515B (42% reduction).
Compressing http://www.tv-tokyo.co.jp/txcms/js/side.banner.js could save 416B (64% reduction).
Compressing http://www.tv-tokyo.co.jp/txcms/js/top.pickup.js could save 391B (44% reduction).

priority - 54Optimize images

Properly formatting and compressing images can save many bytes of data.

Optimize the following images to reduce their size by 528.3KiB (56% reduction).

Compressing http://www.tv-tokyo.co.jp/txcms/media/jack/pc/5e/3…e70734a29a7bb7f000.jpg could save 226.5KiB (65% reduction).
Compressing http://www.tv-tokyo.co.jp/txcms/media/pg/L/52/68/8…f134283a45b5c73d70.jpg could save 189.9KiB (63% reduction).
Compressing http://img.gsspat.jp/e/c3470165d9153aaf27c042e4d91…32b7da9af5da2db232.jpg could save 69.5KiB (77% reduction).
Compressing http://www.tv-tokyo.co.jp/txcms/media/pg/L/02/ec/b…7c68178af274dca145.jpg could save 14KiB (14% reduction).
Compressing https://tpc.googlesyndication.com/simgad/10870163713543111053 could save 12.9KiB (36% reduction).
Compressing and resizing http://www.tv-tokyo.co.jp/images/logo.png could save 9.1KiB (61% reduction).
Compressing http://www.tv-tokyo.co.jp/txcms/media/pg/L/7a/31/7…66903795911f9fc005.jpg could save 6.5KiB (14% reduction).

priority - 26Leverage browser caching

Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.

Leverage browser caching for the following cacheable resources:

http://img.gsspat.jp/e/c3470165d9153aaf27c042e4d91…32b7da9af5da2db232.jpg (expiration not specified)
http://js.gsspcln.jp/t/288/413/a1288413.js (expiration not specified)
http://js.gsspcln.jp/t/288/414/a1288414.js (expiration not specified)
http://js.gsspcln.jp/t/288/416/a1288416.js (expiration not specified)
http://js.gsspcln.jp/t/288/418/a1288418.js (expiration not specified)
http://js.gsspcln.jp/t/299/665/a1299665.js (expiration not specified)
http://js.gsspcln.jp/t/299/775/a1299775.js (expiration not specified)
https://cdn.ad.maist.jp/ad/js/pjs.js (expiration not specified)
https://js.gsspcln.jp/t/236/581/a1236581.js (expiration not specified)
https://media.gssp.asia/ls/opt_icon.png (expiration not specified)
https://media.gssp.asia/ls/opt_icon_text.png (expiration not specified)
http://www.tv-tokyo.co.jp/fonts/tv-tokyo-icons-1.woff (60 seconds)
http://www.tv-tokyo.co.jp/fonts/tv-tokyo-icons-2.woff (60 seconds)
http://www.tv-tokyo.co.jp/fonts/tv-tokyo-icons-sns.woff (60 seconds)
http://www.tv-tokyo.co.jp/index/js/adrich.js (60 seconds)
http://www.tv-tokyo.co.jp/index/scatalyst/s_code.js (60 seconds)
http://www.tv-tokyo.co.jp/index/scatalyst/site/index_utf8.js (60 seconds)
http://www.tv-tokyo.co.jp/js/main.js (60 seconds)
http://www.tv-tokyo.co.jp/txcms/js/side.banner.js (60 seconds)
http://www.tv-tokyo.co.jp/txcms/js/top.panel.js (60 seconds)
http://www.tv-tokyo.co.jp/txcms/js/top.pickup.js (60 seconds)
http://www.tv-tokyo.co.jp/txcms/js/txcmsdata.pickup.js (60 seconds)
http://www.tv-tokyo.co.jp/txcms/json/footerbanner/l.json (60 seconds)
http://www.tv-tokyo.co.jp/txcms/json/footerbanner/r.json (60 seconds)
http://www.tv-tokyo.co.jp/txcms/json/footerbanner/s.json (60 seconds)
http://www.tv-tokyo.co.jp/txcms/json/jack/top.json (60 seconds)
http://www.tv-tokyo.co.jp/txcms/json/ticker/index.json (60 seconds)
https://j.zucks.net.zimg.jp/j?f=320748 (5 minutes)
https://j.zucks.net.zimg.jp/j?f=320749 (5 minutes)
http://www.tv-tokyo.co.jp/css/top.css (10 minutes)
http://www.tv-tokyo.co.jp/images/ico_nanana02.png (10 minutes)
http://www.tv-tokyo.co.jp/images/logo.png (10 minutes)
http://www.tv-tokyo.co.jp/images/white.png (10 minutes)
http://www.tv-tokyo.co.jp/images/white21x10.png (10 minutes)
http://www.tv-tokyo.co.jp/images/white37x10.png (10 minutes)
http://www.tv-tokyo.co.jp/images/white3x1.png (10 minutes)
http://www.tv-tokyo.co.jp/images/white3x2.png (10 minutes)
http://www.tv-tokyo.co.jp/txcms/media/jack/pc/5e/3…e70734a29a7bb7f000.jpg (10 minutes)
http://www.tv-tokyo.co.jp/txcms/media/pg/L/02/ec/b…7c68178af274dca145.jpg (10 minutes)
http://www.tv-tokyo.co.jp/txcms/media/pg/L/4cd96f7…a205486d6af21d1302.jpg (10 minutes)
http://www.tv-tokyo.co.jp/txcms/media/pg/L/4dbb1d8…04c5aae9154bcfb691.jpg (10 minutes)
http://www.tv-tokyo.co.jp/txcms/media/pg/L/52/68/8…f134283a45b5c73d70.jpg (10 minutes)
http://www.tv-tokyo.co.jp/txcms/media/pg/L/7a/31/7…66903795911f9fc005.jpg (10 minutes)
http://www.googletagservices.com/tag/js/gpt.js (15 minutes)
https://www.googletagmanager.com/gtm.js?id=GTM-ND9WBXK (15 minutes)
http://cdn.cxense.com/cx.js (60 minutes)
http://genieejapan-d.openx.net/w/1.0/jstag (60 minutes)
http://jpmarket-d.openx.net/w/1.0/jstag (60 minutes)
http://pagead2.googlesyndication.com/pagead/js/adsbygoogle.js (60 minutes)
http://pagead2.googlesyndication.com/pagead/osd.js (60 minutes)
http://pagead2.googlesyndication.com/pagead/show_ads.js (60 minutes)
http://tvtokyo-d.openx.net/w/1.0/jstag (60 minutes)
https://www.google-analytics.com/analytics.js (2 hours)
http://c.nakanohito.jp/b3/bi.js (3 hours)

priority - 12Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 5 blocking script resources and 2 blocking CSS resources. This causes a delay in rendering your page.

Remove render-blocking JavaScript:

http://www.tv-tokyo.co.jp/txcms/js/txcmsdata.pickup.js
http://www.tv-tokyo.co.jp/js/main.js
http://www.tv-tokyo.co.jp/txcms/js/side.banner.js
http://www.tv-tokyo.co.jp/index/js/adrich.js
http://www.tv-tokyo.co.jp/txcms/js/top.panel.js

Optimize CSS Delivery of the following:

http://fonts.googleapis.com/css?family=Lato:400,700,900
http://www.tv-tokyo.co.jp/css/top.css

priority - 0Minify JavaScript

Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and execution time.

Minify JavaScript for the following resources to reduce their size by 238B (23% reduction).

Minifying http://www.tv-tokyo.co.jp/index/scatalyst/site/index_utf8.js could save 238B (23% reduction).

tv-tokyo.co.jp Desktop Resource Breakdown

Total Resources233
Number of Hosts71
Static Resources75
JavaScript Resources90
CSS Resources2

tv-tokyo.co.jp mobile page speed rank

Last tested: 2018-10-07


Mobile Speed Bad
22/100

tv-tokyo.co.jp Mobile Speed Test Quick Summary


priority - 136Enable compression

Compressing resources with gzip or deflate can reduce the number of bytes sent over the network.

Enable compression for the following resources to reduce their transfer size by 1.3MiB (79% reduction).

Compressing http://www.tv-tokyo.co.jp/ could save 339.4KiB (86% reduction).
Compressing http://www.tv-tokyo.co.jp/smp/ could save 275.9KiB (86% reduction).
Compressing http://www.tv-tokyo.co.jp/js/main.js could save 227KiB (71% reduction).
Compressing http://www.tv-tokyo.co.jp/css/top.css could save 178.8KiB (86% reduction).
Compressing http://www.tv-tokyo.co.jp/js/main_sp.js could save 160.1KiB (69% reduction).
Compressing http://www.tv-tokyo.co.jp/css/top_sp.css could save 91.5KiB (84% reduction).
Compressing http://www.tv-tokyo.co.jp/index/scatalyst/s_code.js could save 39.6KiB (63% reduction).
Compressing http://www.tv-tokyo.co.jp/txcms/js/txcmsdata.pickup.js could save 6.7KiB (72% reduction).
Compressing http://www.tv-tokyo.co.jp/txcms/json/footerbanner/l.json could save 2.1KiB (60% reduction).
Compressing http://www.tv-tokyo.co.jp/txcms/json/footerbanner/smp.json could save 2.1KiB (60% reduction).
Compressing http://www.tv-tokyo.co.jp/txcms/json/jack/top.json could save 1.6KiB (70% reduction).
Compressing http://www.tv-tokyo.co.jp/txcms/js/smp-pc.js could save 1.1KiB (49% reduction).
Compressing http://www.tv-tokyo.co.jp/txcms/json/footerbanner/s.json could save 1KiB (58% reduction).
Compressing http://www.tv-tokyo.co.jp/txcms/js/top.panel.js could save 739B (53% reduction).
Compressing http://www.tv-tokyo.co.jp/index/scatalyst/site/index_utf8.js could save 582B (54% reduction).
Compressing http://www.tv-tokyo.co.jp/txcms/json/footerbanner/r.json could save 515B (42% reduction).
Compressing http://www.tv-tokyo.co.jp/txcms/js/side.banner.js could save 416B (64% reduction).
Compressing http://www.tv-tokyo.co.jp/txcms/js/top.pickup.js could save 391B (44% reduction).

priority - 70Optimize images

Properly formatting and compressing images can save many bytes of data.

Optimize the following images to reduce their size by 682.9KiB (58% reduction).

Compressing http://www.tv-tokyo.co.jp/txcms/media/jack/sp/0a/0…a23303b8317720cb96.jpg could save 267.8KiB (68% reduction).
Compressing http://www.tv-tokyo.co.jp/txcms/media/pg/L/52/68/8…f134283a45b5c73d70.jpg could save 189.9KiB (63% reduction).
Compressing http://www.tv-tokyo.co.jp/txcms/media/pg/L/27/84/7…9d8bb26d5fa4ef2184.jpg could save 162.8KiB (65% reduction).
Compressing http://www.tv-tokyo.co.jp/txcms/media/pg/S/d9/0f/9…1adfd24502d1181d93.jpg could save 37.2KiB (68% reduction).
Compressing http://www.tv-tokyo.co.jp/txcms/media/pg/L/02/ec/b…7c68178af274dca145.jpg could save 14KiB (14% reduction).
Compressing http://www.tv-tokyo.co.jp/txcms/media/pg/L/7a/31/7…66903795911f9fc005.jpg could save 6.5KiB (14% reduction).
Compressing http://www.tv-tokyo.co.jp/images/logo.png could save 2.8KiB (19% reduction).
Compressing http://www.tv-tokyo.co.jp/txcms/media/pg/S/fa/e6/2…65b0a313cfee1824c1.jpg could save 2KiB (17% reduction).

priority - 48Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 15 blocking script resources and 4 blocking CSS resources. This causes a delay in rendering your page.

Remove render-blocking JavaScript:

http://www.tv-tokyo.co.jp/txcms/js/txcmsdata.pickup.js
http://www.tv-tokyo.co.jp/js/main.js
http://www.tv-tokyo.co.jp/txcms/js/side.banner.js
http://www.tv-tokyo.co.jp/index/js/adrich.js
http://www.tv-tokyo.co.jp/txcms/js/top.panel.js
http://www.tv-tokyo.co.jp/txcms/js/top.pickup.js
http://www.tv-tokyo.co.jp/index/scatalyst/s_code.js
http://www.tv-tokyo.co.jp/index/scatalyst/site/index_utf8.js
http://www.tv-tokyo.co.jp/txcms/js/txcmsdata.pickup.js
http://www.tv-tokyo.co.jp/txcms/js/smp-pc.js
http://www.tv-tokyo.co.jp/txcms/js/top.panel.js
http://www.tv-tokyo.co.jp/txcms/js/top.pickup.js
http://www.tv-tokyo.co.jp/js/main_sp.js
http://www.tv-tokyo.co.jp/index/scatalyst/s_code.js
http://www.tv-tokyo.co.jp/index/scatalyst/site/index_utf8.js

Optimize CSS Delivery of the following:

http://fonts.googleapis.com/css?family=Lato:400,700,900
http://www.tv-tokyo.co.jp/css/top.css
http://fonts.googleapis.com/css?family=Lato:400,700,900
http://www.tv-tokyo.co.jp/css/top_sp.css

priority - 41Leverage browser caching

Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.

Leverage browser caching for the following cacheable resources:

http://js.gsspcln.jp/t/288/418/a1288418.js (expiration not specified)
https://js.gsspcln.jp/t/288/439/a1288439.js (expiration not specified)
http://www.tv-tokyo.co.jp/fonts/tv-tokyo-icons-1.woff (60 seconds)
http://www.tv-tokyo.co.jp/fonts/tv-tokyo-icons-2.woff (60 seconds)
http://www.tv-tokyo.co.jp/fonts/tv-tokyo-icons-sns.woff (60 seconds)
http://www.tv-tokyo.co.jp/index/js/adrich.js (60 seconds)
http://www.tv-tokyo.co.jp/index/scatalyst/s_code.js (60 seconds)
http://www.tv-tokyo.co.jp/index/scatalyst/site/index_utf8.js (60 seconds)
http://www.tv-tokyo.co.jp/js/main.js (60 seconds)
http://www.tv-tokyo.co.jp/js/main_sp.js (60 seconds)
http://www.tv-tokyo.co.jp/txcms/js/side.banner.js (60 seconds)
http://www.tv-tokyo.co.jp/txcms/js/smp-pc.js (60 seconds)
http://www.tv-tokyo.co.jp/txcms/js/top.panel.js (60 seconds)
http://www.tv-tokyo.co.jp/txcms/js/top.pickup.js (60 seconds)
http://www.tv-tokyo.co.jp/txcms/js/txcmsdata.pickup.js (60 seconds)
http://www.tv-tokyo.co.jp/txcms/json/footerbanner/l.json (60 seconds)
http://www.tv-tokyo.co.jp/txcms/json/footerbanner/r.json (60 seconds)
http://www.tv-tokyo.co.jp/txcms/json/footerbanner/s.json (60 seconds)
http://www.tv-tokyo.co.jp/txcms/json/footerbanner/smp.json (60 seconds)
http://www.tv-tokyo.co.jp/txcms/json/jack/top.json (60 seconds)
http://www.tv-tokyo.co.jp/txcms/json/ticker/index.json (60 seconds)
http://s.yimg.jp/images/advertising/common/js/iicon.min.js?2018100701 (9.7 minutes)
http://s.yimg.jp/images/listing/tool/yads/uadf/yads_vimps.js?2018100701 (9.9 minutes)
http://yads.c.yimg.jp/js/yads.js (10 minutes)
http://www.tv-tokyo.co.jp/css/top.css (10 minutes)
http://www.tv-tokyo.co.jp/css/top_sp.css (10 minutes)
http://www.tv-tokyo.co.jp/images/btn_download01_02.png (10 minutes)
http://www.tv-tokyo.co.jp/images/ico_circle01_01.png (10 minutes)
http://www.tv-tokyo.co.jp/images/ico_circle01_01_o.png (10 minutes)
http://www.tv-tokyo.co.jp/images/ico_nanana02.png (10 minutes)
http://www.tv-tokyo.co.jp/images/logo.png (10 minutes)
http://www.tv-tokyo.co.jp/images/white.png (10 minutes)
http://www.tv-tokyo.co.jp/images/white1x1.png (10 minutes)
http://www.tv-tokyo.co.jp/images/white21x10.png (10 minutes)
http://www.tv-tokyo.co.jp/images/white37x10.png (10 minutes)
http://www.tv-tokyo.co.jp/images/white3x1.png (10 minutes)
http://www.tv-tokyo.co.jp/images/white3x2.png (10 minutes)
http://www.tv-tokyo.co.jp/txcms/media/jack/sp/0a/0…a23303b8317720cb96.jpg (10 minutes)
http://www.tv-tokyo.co.jp/txcms/media/pg/L/02/ec/b…7c68178af274dca145.jpg (10 minutes)
http://www.tv-tokyo.co.jp/txcms/media/pg/L/27/84/7…9d8bb26d5fa4ef2184.jpg (10 minutes)
http://www.tv-tokyo.co.jp/txcms/media/pg/L/4cd96f7…a205486d6af21d1302.jpg (10 minutes)
http://www.tv-tokyo.co.jp/txcms/media/pg/L/4dbb1d8…04c5aae9154bcfb691.jpg (10 minutes)
http://www.tv-tokyo.co.jp/txcms/media/pg/L/52/68/8…f134283a45b5c73d70.jpg (10 minutes)
http://www.tv-tokyo.co.jp/txcms/media/pg/L/7a/31/7…66903795911f9fc005.jpg (10 minutes)
http://www.tv-tokyo.co.jp/txcms/media/pg/S/d9/0f/9…1adfd24502d1181d93.jpg (10 minutes)
http://www.tv-tokyo.co.jp/txcms/media/pg/S/fa/e6/2…65b0a313cfee1824c1.jpg (10 minutes)
http://www.googletagservices.com/tag/js/gpt.js (15 minutes)
https://www.googletagmanager.com/gtm.js?id=GTM-ND9WBXK (15 minutes)
http://cdn.cxense.com/cx.js (60 minutes)
http://pagead2.googlesyndication.com/pagead/js/adsbygoogle.js (60 minutes)
http://pagead2.googlesyndication.com/pagead/osd.js (60 minutes)
http://tvtokyo-d.openx.net/mw/1.0/jstag (60 minutes)
http://tvtokyo-d.openx.net/w/1.0/jstag (60 minutes)
https://www.google-analytics.com/analytics.js (2 hours)
http://c.nakanohito.jp/b3/bi.js (3 hours)

priority - 32Prioritize visible content

Your page requires additional network round trips to render the above-the-fold content. For best performance, reduce the amount of HTML needed to render above-the-fold content.

The entire HTML response was not sufficient to render the above-the-fold content. This usually indicates that additional resources, loaded after HTML parsing, were required to render above-the-fold content. Prioritize visible content that is needed for rendering above-the-fold by including it directly in the HTML response.

Only about 28% of the final above-the-fold content could be rendered with the full HTML response.
Click to see the screenshot with only the HTML response:

priority - 0Minify JavaScript

Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and execution time.

Minify JavaScript for the following resources to reduce their size by 1,005B (17% reduction).

Minifying http://js.gsspcln.jp/j/rtct_adp_lib.20180606.min.j…ryZoneName=gpb_1288439 could save 767B (16% reduction) after compression.
Minifying http://www.tv-tokyo.co.jp/index/scatalyst/site/index_utf8.js could save 238B (23% reduction).

priority - 0Minify HTML

Compacting HTML code, including any inline JavaScript and CSS contained in it, can save many bytes of data and speed up download and parse times.

Minify HTML for the following resources to reduce their size by 116B (11% reduction).

Minifying http://i.yimg.jp/images/listing/tool/yads/yads-ifr…%2f&tagpos=0x0&async=0 could save 116B (11% reduction) after compression.

tv-tokyo.co.jp Mobile Resource Breakdown

Total Resources225
Number of Hosts58
Static Resources86
JavaScript Resources86
CSS Resources3

tv-tokyo.co.jp mobile page usability

Last tested: 2018-10-07


Mobile Usability Good
91/100

tv-tokyo.co.jp Mobile Usability Test Quick Summary


priority - 8Size tap targets appropriately

Some of the links/buttons on your webpage may be too small for a user to easily tap on a touchscreen. Consider making these tap targets larger to provide a better user experience.

The following tap targets are close to other nearby tap targets and may need additional spacing around them.

The tap target <a href="//www.tv-tokyo…dex/timetable/">番組表</a> is close to 1 other tap targets.

The tap target <a href="#txcms_search">番組検索</a> and 1 others are close to other tap targets.

The tap target <button type="button" class="slick-prev">Previous</button> and 2 others are close to other tap targets.
The tap target <button type="button" class="slick-prev">Previous</button> and 3 others are close to other tap targets.
The tap target <a href="http://twitter…AE%AE%E6%AE%BF" class="txcms_btn txcms_isTwitter">つぶやく</a> and 7 others are close to other tap targets.
The tap target <a href="http://twitter…AE%AE%E6%AE%BF" class="txcms_btn txcms_isTwitter">つぶやく</a> and 3 others are close to other tap targets.
The tap target <a href="http://www.fac…F00065693.html" class="txcms_btn txcms_isFacebook">シェア</a> and 3 others are close to other tap targets.
The tap target <button type="button" class="slick-prev slick-disabled">Previous</button> is close to 1 other tap targets.
The tap target <li class="slick-active">1</li> and 9 others are close to other tap targets.
The tap target <li class="slick-active">1</li> and 19 others are close to other tap targets.
The tap target <a href="http://www.tv-…genre/biz.html">報道</a> and 5 others are close to other tap targets.
The tap target <a href="http://www.tv-….co.jp/kaisha/">テレビ東京</a> and 16 others are close to other tap targets.
The tap target <a href="http://www.tv-…nation_180709/">平成30年7月豪雨災害義援金の募集</a> and 4 others are close to other tap targets.
The tap target <a href="http://www.tv-…nation_180709/">平成30年7月豪雨災害義援金の募集</a> and 4 others are close to other tap targets.

tv-tokyo.co.jp HTML validation

Errors

A document must not include more than one “meta” element with a “charset” attribute.

Line: 5 Column: 1 - 22
"...="UTF-8"> <meta charset="UTF-8"> <meta..."

Element “style” not allowed as child of element “body” in this context. (Suppressing further errors from this subtree.)

Line: 39 Column: 52 - 58
"...;</script><style>.tbcms..."

Element “div” not allowed as child of element “button” in this context. (Suppressing further errors from this subtree.)

Line: 66 Column: 627 - 671
"...bal-menu"><div class="tbcms_header__global-menu-inner"><span>..." Line: 66 Column: 861 - 916
"...e-button"><div class="tbcms_global-navigation__close-button-icon"></div>..."

No space between attributes.

Line: 66 Column: - 2307
"...rts/index.html""><div class="t..."

Saw “"” when expecting an attribute name. Probable cause: “=” missing immediately before.

Line: 66 Column: - 2307
"...rts/index.html""><div class="t..."

Attribute “"” not allowed on element “a” at this point.

Line: 66 Column: 2215 - 2308
"...ory-item"><a class="tbcms_global-navigation__link" href="//www.tv-tokyo.co.jp/genre_sports/index.html""><div c..."

Element “div” not allowed as child of element “h2” in this context. (Suppressing further errors from this subtree.)

Line: 563 Column: 1 - 61
"...">おすすめアニメ <div class="tbcms_recommend-list__read-more tbcms_read-more"><a cla..."

Bad value “” for attribute “target” on element “a”: Browsing context name must be at least one character long.

Line: 574 Column: 37 - 118
"...st__item"><a class="tbcms_notice-list__link" href="http://www.tv-tokyo.co.jp/kb/" target="">カラオケバト..." Line: 575 Column: 37 - 124
"...st__item"><a class="tbcms_notice-list__link" href="https://www.tv-tokyo.co.jp/monitor/" target="">2019年度..." Line: 576 Column: 37 - 136
"...st__item"><a class="tbcms_notice-list__link" href="http://www.tv-tokyo.co.jp/info/donation_160415/" target="">熊本地震義援..." Line: 577 Column: 37 - 137
"...st__item"><a class="tbcms_notice-list__link" href="http://www.tv-tokyo.co.jp/info/caution_20140319/" target="">番組関係者を..."

Attribute “targe” not allowed on element “a” at this point.

Line: 712 Column: 30 - 116
"...ead-more"><a class="tbcms_read-more__link" href="//www.tv-tokyo.co.jp/announcer/" targe="_blank">アナウンサー..." Line: 882 Column: 71 - 119
"...ory-item"><a href="https://www.txhd.co.jp/" targe="_blank">テレビ東京ホ..."

Warnings

Attribute “"” is not serializable as XML 1.0.

Line: 66 Column: 2215 - 2308
"...ory-item"><a class="tbcms_global-navigation__link" href="//www.tv-tokyo.co.jp/genre_sports/index.html""><div c..."

The “main” role is unnecessary for element “main”.

Line: 68 Column: 12045 - 58
"...></nav> <main id="tbcms_main-top" role="main" data-cxtxn="06636fc581769dbf494375642a20bf1e59286727" data-cxtxv="9af86e070c5b570e89d49e91bcacc1e784435f90"> <div>..."

The document is not mappable to XML 1.0 due to two consecutive hyphens in a comment.

Line: 942 Column: - 151
"...vigation-link--state_current" ..."

tv-tokyo.co.jp similar domains

Similar domains:
www.tv-tokyo.com
www.tv-tokyo.net
www.tv-tokyo.org
www.tv-tokyo.info
www.tv-tokyo.biz
www.tv-tokyo.us
www.tv-tokyo.mobi
www.v-tokyo.co.jp
www.tv-tokyo.co.jp
www.rv-tokyo.co.jp
www.trv-tokyo.co.jp
www.rtv-tokyo.co.jp
www.fv-tokyo.co.jp
www.tfv-tokyo.co.jp
www.ftv-tokyo.co.jp
www.gv-tokyo.co.jp
www.tgv-tokyo.co.jp
www.gtv-tokyo.co.jp
www.yv-tokyo.co.jp
www.tyv-tokyo.co.jp
www.ytv-tokyo.co.jp
www.t-tokyo.co.jp
www.tc-tokyo.co.jp
www.tvc-tokyo.co.jp
www.tcv-tokyo.co.jp
www.tf-tokyo.co.jp
www.tvf-tokyo.co.jp
www.tg-tokyo.co.jp
www.tvg-tokyo.co.jp
www.tb-tokyo.co.jp
www.tvb-tokyo.co.jp
www.tbv-tokyo.co.jp
www.tvtokyo.co.jp
www.tv-okyo.co.jp
www.tv-rokyo.co.jp
www.tv-trokyo.co.jp
www.tv-rtokyo.co.jp
www.tv-fokyo.co.jp
www.tv-tfokyo.co.jp
www.tv-ftokyo.co.jp
www.tv-gokyo.co.jp
www.tv-tgokyo.co.jp
www.tv-gtokyo.co.jp
www.tv-yokyo.co.jp
www.tv-tyokyo.co.jp
www.tv-ytokyo.co.jp
www.tv-tkyo.co.jp
www.tv-tikyo.co.jp
www.tv-toikyo.co.jp
www.tv-tiokyo.co.jp
www.tv-tkkyo.co.jp
www.tv-tokkyo.co.jp
www.tv-tkokyo.co.jp
www.tv-tlkyo.co.jp
www.tv-tolkyo.co.jp
www.tv-tlokyo.co.jp
www.tv-tpkyo.co.jp
www.tv-topkyo.co.jp
www.tv-tpokyo.co.jp
www.tv-toyo.co.jp
www.tv-tojyo.co.jp
www.tv-tokjyo.co.jp
www.tv-tojkyo.co.jp
www.tv-toiyo.co.jp
www.tv-tokiyo.co.jp
www.tv-tomyo.co.jp
www.tv-tokmyo.co.jp
www.tv-tomkyo.co.jp
www.tv-tolyo.co.jp
www.tv-toklyo.co.jp
www.tv-tooyo.co.jp
www.tv-tokoyo.co.jp
www.tv-tookyo.co.jp
www.tv-toko.co.jp
www.tv-tokto.co.jp
www.tv-tokyto.co.jp
www.tv-toktyo.co.jp
www.tv-tokgo.co.jp
www.tv-tokygo.co.jp
www.tv-tokgyo.co.jp
www.tv-tokho.co.jp
www.tv-tokyho.co.jp
www.tv-tokhyo.co.jp
www.tv-tokuo.co.jp
www.tv-tokyuo.co.jp
www.tv-tokuyo.co.jp
www.tv-toky.co.jp
www.tv-tokyi.co.jp
www.tv-tokyoi.co.jp
www.tv-tokyio.co.jp
www.tv-tokyk.co.jp
www.tv-tokyok.co.jp
www.tv-tokyko.co.jp
www.tv-tokyl.co.jp
www.tv-tokyol.co.jp
www.tv-tokylo.co.jp
www.tv-tokyp.co.jp
www.tv-tokyop.co.jp
www.tv-tokypo.co.jp

tv-tokyo.co.jp Ping

Ping is a computer network administration software utility used to test the reachability of a host on an Internet Protocol (IP) network. It measures the round-trip time for messages sent from the originating host to a destination computer that are echoed back to the source.


tv-tokyo.co.jp TRACEROUTE

Traceroute is a computer network diagnostic tool for displaying the route (path) and measuring transit delays of packets across an Internet Protocol (IP) network. The history of the route is recorded as the round-trip times of the packets received from each successive host (remote node) in the route (path); the sum of the mean times in each hop is a measure of the total time spent to establish the connection. Traceroute proceeds unless all (three) sent packets are lost more than twice, then the connection is lost and the route cannot be evaluated.