12.9 sec in total
539 ms
11.9 sec
417 ms
Welcome to fctokyo.co.jp homepage info - get ready to check F C TOKYO best content for Japan right away, or after learning these important things about fctokyo.co.jp
最新ニュース、選手や試合日程・結果、味の素スタジアム観戦ガイド(アクセス)、チケット、グッズ、アカデミー、スクールの情報など、FC東京に関する情報をご覧いただけます。
Visit fctokyo.co.jpWe analyzed Fctokyo.co.jp page load time and found that the first response time was 539 ms and then it took 12.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.
fctokyo.co.jp performance score
name
value
score
weighting
Value5.3 s
7/100
10%
Value29.0 s
0/100
25%
Value37.5 s
0/100
10%
Value49,920 ms
0/100
30%
Value0.253
49/100
15%
Value99.2 s
0/100
10%
539 ms
1094 ms
624 ms
314 ms
503 ms
Our browser made a total of 208 requests to load all elements on the main page. We found that 80% of them (167 requests) were addressed to the original Fctokyo.co.jp, 6% (12 requests) were made to Google.com and 3% (6 requests) were made to Jleague.jp. The less responsive or slowest element that took the longest time to load (3.7 sec) belongs to the original domain Fctokyo.co.jp.
Page size can be reduced by 1.6 MB (24%)
6.5 MB
5.0 MB
In fact, the total size of Fctokyo.co.jp main page is 6.5 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 5.8 MB which makes up the majority of the site volume.
Potential reduce by 119.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 119.8 kB or 83% of the original size.
Potential reduce by 1.0 MB
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, F C TOKYO needs image optimization as it can save up to 1.0 MB or 18% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 333.2 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 333.2 kB or 67% of the original size.
Potential reduce by 69.9 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. Fctokyo.co.jp needs all CSS files to be minified and compressed as it can save up to 69.9 kB or 84% of the original size.
Number of requests can be reduced by 55 (28%)
199
144
The browser has sent 199 CSS, Javascripts, AJAX and image requests in order to completely render the main page of F C 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 27 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
fctokyo.co.jp
539 ms
www.fctokyo.co.jp
1094 ms
stylenew.css
624 ms
clocknew.css
314 ms
camera.css
503 ms
ui.tabs.css
340 ms
jquery-1.8.2.min.js
1038 ms
jquery.autoheight.js
470 ms
jquery.carouFredSel.js
1011 ms
jquery.mousewheel.min.js
626 ms
jquery.touchSwipe.min.js
668 ms
jquery.ba-throttle-debounce.min.js
718 ms
smoothscroll.js
773 ms
smartRollover.js
780 ms
ui.core.js
835 ms
ui.tabs.js
898 ms
jquery.easing.1.3.js
942 ms
camera.min.js
1251 ms
jquery.droppy.js
1001 ms
banner.js
1078 ms
592 ms
back_2015.jpg
1824 ms
mobile.jpg
478 ms
logo.png
940 ms
site.png
363 ms
01.gif
280 ms
02.gif
281 ms
04.gif
508 ms
coa.png
692 ms
long30.png
537 ms
short07-h.png
638 ms
nhg.png
1010 ms
fctokyo.png
885 ms
vs.png
790 ms
BecamexBinDuongFC.png
858 ms
toppanel_up.gif
947 ms
navi01_off.gif
1022 ms
navi02_off.gif
1058 ms
navi03_off.gif
1094 ms
navi04_off.gif
1104 ms
navi05_off.gif
1178 ms
navi06_off.gif
1188 ms
navi07_off.gif
1232 ms
navi09_off.gif
1261 ms
navi08_off.gif
1263 ms
10.png
1346 ms
vs.png
1524 ms
home_back.gif
1406 ms
away_back.gif
1420 ms
listback_lt.gif
1423 ms
listback_lb.gif
1513 ms
listback_rt.gif
1580 ms
listback_rb.gif
1575 ms
mobile.jpg
1582 ms
sns_01.jpg
1681 ms
sns_02.jpg
1692 ms
cse.js
33 ms
inc_scheduletop.php
1738 ms
cse.js
243 ms
ga.js
31 ms
header.js
112 ms
126 ms
128 ms
__utm.gif
40 ms
inc_left_seturank.php
1495 ms
sns_03.jpg
1459 ms
ftokyo.html
314 ms
jsapi
46 ms
17 ms
26 ms
collect
59 ms
35 ms
default+ja.css
12 ms
default.css
62 ms
default+ja.I.js
33 ms
sns_04.jpg
1491 ms
default.css
39 ms
async-ads.js
84 ms
google_custom_search_watermark.gif
36 ms
small-logo.png
19 ms
search_box_icon.png
18 ms
clear.gif
24 ms
nav_logo114.png
6 ms
j1_top_u23.jpg
1558 ms
diary.jpg
1393 ms
volleyball.jpg
1841 ms
reset.css
5 ms
jheader.css
18 ms
analytics.js
17 ms
gpt.js
16 ms
jheader_jlogo.png
14 ms
jheader_team_emb_s_bw.png
13 ms
pubads_impl_81.js
14 ms
linkid.js
45 ms
bailetokyo.jpg
1467 ms
ads
68 ms
container.html
14 ms
collect
26 ms
ntv_acl.jpg
1669 ms
collect
11 ms
3283956207473580058
28 ms
554891454251115848
27 ms
osd.js
15 ms
fc_e-uketsuke.jpg
1567 ms
hn.png
1199 ms
01.jpg
1318 ms
activeview
15 ms
activeview
18 ms
02.jpg
1276 ms
03.jpg
1345 ms
08.jpg
1361 ms
04.jpg
1353 ms
05.jpg
1411 ms
07.jpg
1433 ms
06.jpg
1444 ms
tab_bac_top.gif
1362 ms
koutaJPG-3-150x150.jpg
1341 ms
icon_media.gif
1457 ms
%E3%82%A8%E3%83%B3%E3%83%96%E3%83%AC%E3%83%A02.jpg
1380 ms
icon_club.gif
1432 ms
icon_event.gif
1341 ms
icon_ticket.gif
1305 ms
icon_goods.gif
1489 ms
tab_bac_bot.gif
1391 ms
0303Number_eye-150x150.jpg
1329 ms
%E3%82%A8%E3%83%B3%E3%83%96%E3%83%AC%E3%83%A01.jpg
1321 ms
icon_team.gif
1286 ms
1%E3%83%91%E3%83%83%E3%82%B1%E3%83%BC%E3%82%B81-150x150.jpg
1298 ms
%E6%9D%B1%E4%BA%AC%E3%83%89%E3%83%AD%E3%83%B3%E3%83%91%E3%82%A2%E3%82%A4%E3%82%AD%E3%83%A3%E3%83%83%E3%83%811-150x150.jpg
1406 ms
MDP%E3%82%A2%E3%82%A4%E3%82%AD%E3%83%A3%E3%83%83%E3%83%81-150x150.jpg
1317 ms
%EF%BE%95%EF%BE%86%EF%BE%8C%EF%BD%AB%EF%BD%B0%EF%BE%91%EF%BD%B7%EF%BD%B0%EF%BE%8E%EF%BE%99%EF%BE%80%EF%BE%9E%EF%BD%B0ACLver.-150x150.jpg
1308 ms
tokyo-logo.jpg
1292 ms
SOCIO%E3%83%AD%E3%82%B42-150x150.jpg
1295 ms
icon_us.gif
1493 ms
b_01.jpg
1521 ms
b_02.jpg
2075 ms
b_03.jpg
1578 ms
b_04.jpg
1669 ms
b_05.jpg
1328 ms
b_06.jpg
1887 ms
photo_title.gif
1316 ms
pn.gif
1340 ms
340A6375-640x480-150x150.jpg
1345 ms
AK0R5137-640x481-150x150.jpg
1337 ms
%E9%9A%8A%E5%93%A1%E7%95%AA%E5%8F%B7066%EF%BC%9A%E6%9D%89%E4%B8%A6%E5%8C%BA%E8%A5%BF%E8%8D%BB%E7%AA%AA%E3%81%AE%E5%AD%90%E3%81%A9%E3%82%82%E6%9C%8D%E5%BA%97-150x150.jpg
1361 ms
AK0R7248-640x481-150x150.jpg
1425 ms
%E9%9A%8A%E5%93%A1%E7%95%AA%E5%8F%B7005%EF%BC%9A%E4%B8%96%E7%94%B0%E8%B0%B7%E5%8C%BA%E6%9D%BE%E5%8E%9F%E3%81%AE%E8%87%AA%E5%AE%85%E5%A1%80-150x150.jpg
1508 ms
151226_1396-640x481-150x150.jpg
1507 ms
151122_1447-640x481-150x150.jpg
1427 ms
DSC_3467-640x479-150x150.jpg
1428 ms
151111_0705-640x481-150x150.jpg
1527 ms
%E9%9A%8A%E5%93%A1%E7%95%AA%E5%8F%B7003%EF%BC%9A%E5%BA%9C%E4%B8%AD%E5%B8%82%E7%BE%8E%E5%A5%BD%E7%94%BA%E3%81%AE%E8%87%AA%E5%AE%85-150x150.jpg
1513 ms
b_07.jpg
1687 ms
b_09.jpg
1947 ms
b_12.jpg
1892 ms
bn01.jpg
1858 ms
bn02.gif
1693 ms
bn03.jpg
1690 ms
bn04.jpg
1589 ms
fctokyo_bannar_0331.gif
1878 ms
anime_his.gif
1732 ms
fc_bn01.gif
1711 ms
fc_bn02.gif
1849 ms
fc_bn03.gif
1833 ms
fc_bn04.gif
1761 ms
fc_bn05.gif
1737 ms
fc_bn06.gif
1742 ms
fc_bn07.gif
1861 ms
fc_bn08.gif
1863 ms
jcom.gif
1776 ms
xscore.gif
1572 ms
soccer.gif
1516 ms
bnr130122.gif
1448 ms
nitecs.gif
1543 ms
topbackl.png
2320 ms
topback.png
1861 ms
fc.png
1562 ms
toppanel_left.jpg
1397 ms
clock.png
1482 ms
databox.png
1641 ms
panel_under.gif
1392 ms
title01.jpg
1637 ms
title02.jpg
1937 ms
sns.jpg
1518 ms
detail_botton_off.gif
1652 ms
tab_bac_mid.gif
1622 ms
news_tipback.gif
1628 ms
left.gif
1629 ms
right.gif
1541 ms
ad_top.gif
1411 ms
ad_bot.gif
1460 ms
fi.gif
1439 ms
fi_a.gif
1409 ms
fi.gif
1404 ms
camera_skins.png
1598 ms
camera-loader.gif
1424 ms
ACLPO.jpg
2599 ms
2016SOCIO%E3%83%90%E3%83%8A%E3%83%BC_%E3%83%95%E3%82%A1%E3%83%9F%E3%83%AA%E3%83%BC%E3%82%AA%E3%83%88%E3%82%AF_752%C3%97252.jpg
3375 ms
20160201%EF%BD%9E0229%E3%83%90%E3%83%8A%E3%83%BC.jpg
1733 ms
2016%E3%82%AF%E3%83%A9%E3%82%B5%E3%83%9D%E3%83%90%E3%83%8A%E3%83%BC%E4%B8%B8%E5%B1%B1-1280x429.jpg
2677 ms
%E3%82%AA%E3%83%BC%E3%83%AD%E3%83%A9%E3%83%93%E3%82%B8%E3%83%A7%E3%83%B3.jpg
2430 ms
ACLPO.jpg
3661 ms
inc_scheduletop.php
1899 ms
title03.jpg
1935 ms
ts_td_left.gif
2096 ms
ts_td_right.gif
2254 ms
2016SOCIO%E3%83%90%E3%83%8A%E3%83%BC_%E3%83%95%E3%82%A1%E3%83%9F%E3%83%AA%E3%83%BC%E3%82%AA%E3%83%88%E3%82%AF_752%C3%97252.jpg
1102 ms
blank.gif
158 ms
fctokyo.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.
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
Image elements do not have [alt] attributes
Links do not have a discernible name
fctokyo.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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
fctokyo.co.jp SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fctokyo.co.jp can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Fctokyo.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.
fctokyo.co.jp
Open Graph description is not detected on the main page of F C 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: