10.7 sec in total
1.3 sec
9.1 sec
329 ms
Welcome to search2.tv-tokyo.co.jp homepage info - get ready to check Search 2 Tv Tokyo best content for Japan right away, or after learning these important things about search2.tv-tokyo.co.jp
テレビ東京 - 日経グループ・在京キー局 JOTX-DTV - の検索結果です。テレビ東京ホームページのサイトが検索できます。
Visit search2.tv-tokyo.co.jpWe analyzed Search2.tv-tokyo.co.jp page load time and found that the first response time was 1.3 sec and then it took 9.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
search2.tv-tokyo.co.jp performance score
1340 ms
1194 ms
1380 ms
1391 ms
1055 ms
Our browser made a total of 204 requests to load all elements on the main page. We found that 3% of them (7 requests) were addressed to the original Search2.tv-tokyo.co.jp, 36% (74 requests) were made to Tv-tokyo.co.jp and 7% (15 requests) were made to Cm.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (2.5 sec) relates to the external source Tv-tokyo.co.jp.
Page size can be reduced by 1.1 MB (46%)
2.4 MB
1.3 MB
In fact, the total size of Search2.tv-tokyo.co.jp main page is 2.4 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 989.2 kB which makes up the majority of the site volume.
Potential reduce by 130.7 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 130.7 kB or 75% of the original size.
Potential reduce by 5.2 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. Search 2 Tv Tokyo images are well optimized though.
Potential reduce by 693.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 693.4 kB or 70% of the original size.
Potential reduce by 293.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. Search2.tv-tokyo.co.jp needs all CSS files to be minified and compressed as it can save up to 293.2 kB or 87% of the original size.
Number of requests can be reduced by 104 (54%)
191
87
The browser has sent 191 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Search 2 Tv Tokyo. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 54 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
search2.tv-tokyo.co.jp
1340 ms
style2.css
1194 ms
header_pr.css
1380 ms
newheader05_pr.css
1391 ms
prtxt.js
1055 ms
probo.css
441 ms
probo.js
295 ms
jquery.js
934 ms
tooltip.js
344 ms
PB.js
860 ms
cm8adam_1_call.js
560 ms
jquery.min.js
31 ms
main.js
2453 ms
search2_header.js
1247 ms
popterm2.js
727 ms
sb_parts01.js
1057 ms
sb_parts02.js
1251 ms
sb_parts03.js
1240 ms
search2_footer.js
1390 ms
s_code_txsearch.js
1555 ms
txsearch.js
1239 ms
spinner40.gif
586 ms
logo.png
200 ms
ico_nanana02.png
190 ms
head_shopping.jpg
346 ms
thum_toranomon.jpg
362 ms
thum_honpoweb.jpg
375 ms
thum_teretomart.jpg
389 ms
foot_shopping.jpg
520 ms
detect
330 ms
browserDataDetect.js
329 ms
detected
458 ms
styles2.css
883 ms
modernizr.min.js
175 ms
tx_time.js
190 ms
css
25 ms
bg_fortunetelling01.png
179 ms
ajs.php
364 ms
CM8Function.js
110 ms
DvlFBScY1r-FMtZSYIYoYw.ttf
30 ms
4cKlrioa77J2iqTqBgkRWg.ttf
48 ms
v0SdcGFAl2aezM9Vq_aFTQ.ttf
68 ms
ads.js
584 ms
lg.php
172 ms
ads
200 ms
2023342.jpg
856 ms
pixel
19 ms
impbcn
391 ms
ban_type09_01.png
181 ms
ban_type09_02.png
175 ms
ban_type09_06.png
182 ms
ban_type09_05.png
165 ms
ban_type09_03.png
347 ms
ban_type09_04.png
170 ms
ban_type09_07.png
329 ms
ban_type09_08.png
339 ms
ban_type09_09.png
346 ms
ban_type09_10.png
348 ms
ban_type09_19.png
359 ms
ban_type09_11.png
494 ms
ban_type09_12.png
507 ms
ban_type09_13.png
522 ms
ban_type09_14.png
520 ms
ban_type09_16.png
521 ms
ban_type09_17.png
539 ms
ban_type09_18.png
655 ms
ban_type09_22.png
678 ms
ban_type09_20.png
700 ms
ban_type09_21.png
701 ms
search_main_s.jpg
712 ms
pixel
43 ms
popterm2.css
691 ms
cookiemapping
529 ms
cookiemapping
743 ms
tv-tokyo-icons-1.woff
671 ms
ajs.php
372 ms
1x1.gif
325 ms
1x1.gif
312 ms
ads
198 ms
lg.php
179 ms
2023440.jpg
167 ms
pixel
25 ms
impbcn
392 ms
bg_ranking.jpg
190 ms
rank01.jpg
188 ms
rank02.jpg
193 ms
rank03.jpg
168 ms
rank04.jpg
186 ms
rank05.jpg
184 ms
rank06.jpg
346 ms
rank07.jpg
361 ms
rank08.jpg
364 ms
rank09.jpg
364 ms
rank10.jpg
367 ms
bg_shopping.jpg
378 ms
gpt.js
4 ms
cookiemapping
335 ms
pubads_impl_81.js
7 ms
container.html
23 ms
ads
363 ms
expansion_embed.js
24 ms
13250232331523409936
153 ms
abg.js
228 ms
m_js_controller.js
225 ms
googlelogo_color_112x36dp.png
149 ms
osd.js
32 ms
weather.json
298 ms
l.json
233 ms
index.json
291 ms
sdk.js
352 ms
widgets.js
127 ms
plusone.js
351 ms
show_ads.js
17 ms
zrt_lookup.html
359 ms
show_ads_impl.js
178 ms
VOD300250.jpg
291 ms
cm
364 ms
audience
547 ms
s
284 ms
x_button_blue2.png
164 ms
push
278 ms
ads
230 ms
white.png
186 ms
09.jpg
179 ms
01.jpg
185 ms
4134ee706e193ada960364fa5b69.jpg
330 ms
5ad1d7b254a8aaa9b4f61c6b461f.png
376 ms
08.jpg
173 ms
a2b94583a51d4bd23c99807fb73f.jpg
306 ms
62939f9b903c76a204ef70052539.jpg
517 ms
10.gif
403 ms
9ea9b987ec0d39f876414ab5edfa.png
404 ms
07.jpg
514 ms
8e7fd239dc949aee4e317e74a07c.jpg
515 ms
cb=gapi.loaded_0
43 ms
ads
158 ms
tv-tokyo-icons-weather.woff
518 ms
136 ms
cover-selection-assoc-a-JP-468x60.jpg
43 ms
149 ms
ads
202 ms
xd_arbiter.php
173 ms
xd_arbiter.php
290 ms
pixel
19 ms
js
174 ms
adj
151 ms
skeleton.js
174 ms
beacon
85 ms
js
185 ms
firstevent
11 ms
img
135 ms
pixel
59 ms
push
91 ms
ck-confirm
147 ms
modernizr_2.8.3_ec185bb44fe5e6bf7455d6e8ef37ed0e_no-classes.js
208 ms
lidar.js
134 ms
surly.js
135 ms
s55321789388544
73 ms
15-Q115_WU__1_Fee_V1_D_Update_Mobile_300x250_EN_US.png
262 ms
sbhK2lTE.js
51 ms
img
107 ms
pixel
106 ms
push
102 ms
ck-confirm
200 ms
ba.html
173 ms
pixel
171 ms
4.gif
193 ms
cTrvNaRi.html
135 ms
3-Q115_Wu_Com__1_Walgreens_Fee_Agent_V4_D_468x60_EN_US.PNG
166 ms
PH_StuffedGarlicKnots_300x250_Animated.html
41 ms
pixel
48 ms
pixel
47 ms
dt
192 ms
4311.js
42 ms
skeleton.js
192 ms
MdyApZkAHG2-UELdOwjNjjFZXSz-CGj4o1JtDR7aGgs.js
41 ms
TweenLite.min.js
153 ms
TimelineLite.min.js
158 ms
CSSPlugin.min.js
165 ms
EasePack.min.js
171 ms
sd
167 ms
activeview
52 ms
pixel
29 ms
activeview
40 ms
dtc
22 ms
pixel
25 ms
background.jpg
14 ms
PHlogot.svg
26 ms
PHlogoHat.svg
29 ms
cheese1.jpg
32 ms
cheese2.jpg
28 ms
cheese3.jpg
31 ms
pizza.png
37 ms
txt16.png
33 ms
txt_surrounding.png
31 ms
txt_largepizza.png
33 ms
txt_cta.png
35 ms
cta.png
34 ms
push
34 ms
gp_match
26 ms
pixel
13 ms
box_19_top-right.png
45 ms
ci.png
10 ms
ui
36 ms
search2.tv-tokyo.co.jp SEO score
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Search2.tv-tokyo.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 Search2.tv-tokyo.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.
search2.tv-tokyo.co.jp
Open Graph description is not detected on the main page of Search 2 Tv Tokyo. 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: