11.7 sec in total
538 ms
10.8 sec
336 ms
Visit fish-bank-tokyo.jp now to see the best up-to-date Fish Bank TOKYO content for Japan and also check out these interesting facts you probably never knew about fish-bank-tokyo.jp
美味しいシーフードにお肉とワインを楽しむモダンフレンチ!Fish Bank TOKYO(汐留、新橋)は地上215mからの東京のパノラマの夜景とゆったりとした空間でご接待や商談などのビジネスでのご会食やウエディングや二次会パーティ・記念日・お顔合わせの会食など、様々なシーンでご利用頂けます。
Visit fish-bank-tokyo.jpWe analyzed Fish-bank-tokyo.jp page load time and found that the first response time was 538 ms and then it took 11.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
fish-bank-tokyo.jp performance score
name
value
score
weighting
Value5.1 s
9/100
10%
Value28.7 s
0/100
25%
Value15.2 s
1/100
10%
Value2,140 ms
6/100
30%
Value1.133
1/100
15%
Value25.2 s
0/100
10%
538 ms
308 ms
309 ms
311 ms
335 ms
Our browser made a total of 159 requests to load all elements on the main page. We found that 98% of them (156 requests) were addressed to the original Fish-bank-tokyo.jp, 1% (2 requests) were made to Google-analytics.com and 1% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (3 sec) belongs to the original domain Fish-bank-tokyo.jp.
Page size can be reduced by 228.5 kB (10%)
2.3 MB
2.1 MB
In fact, the total size of Fish-bank-tokyo.jp main page is 2.3 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. 40% of websites need less resources to load. Images take 2.2 MB which makes up the majority of the site volume.
Potential reduce by 5.5 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 5.5 kB or 70% of the original size.
Potential reduce by 121.9 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. Fish Bank TOKYO images are well optimized though.
Potential reduce by 71.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 71.1 kB or 70% of the original size.
Potential reduce by 30.0 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. Fish-bank-tokyo.jp needs all CSS files to be minified and compressed as it can save up to 30.0 kB or 82% of the original size.
Number of requests can be reduced by 17 (11%)
158
141
The browser has sent 158 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fish Bank 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 6 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
fish-bank-tokyo.jp
538 ms
defalut_index.css
308 ms
common.css
309 ms
jquery.maximage.css
311 ms
landing.css
335 ms
jquery.js
35 ms
fbt.js
343 ms
position.js
357 ms
jquery.cycle.all.js
926 ms
jquery.maximage2.js
797 ms
style.css
344 ms
ga.js
8 ms
__utm.gif
13 ms
op_bg01.jpg
1244 ms
op_bg02.jpg
1323 ms
op_bg03.jpg
1000 ms
op_bg04.jpg
919 ms
fbt_logo.png
354 ms
title_bg.png
358 ms
title.png
824 ms
party.jpg
1741 ms
title_001.png
1131 ms
restaurant.jpg
1743 ms
title_002.png
1350 ms
bridal.jpg
2121 ms
title_003.png
1593 ms
access_off.png
1681 ms
access_on.png
1700 ms
brava_off.png
1923 ms
brava_on.png
2039 ms
bridal_after_party_off.png
2053 ms
bridal_after_party_on.png
2054 ms
bridal_off.png
2074 ms
bridal_on.png
2227 ms
chefs_premium_lunch_off.jpg
2344 ms
chefs_premium_lunch_on.jpg
2382 ms
concept_off.png
2382 ms
concept_on.png
2380 ms
cource10000_off.png
2453 ms
cource10000_on.png
2573 ms
cource13000_off.png
2649 ms
cource13000_on.png
2687 ms
cource16000_off.png
2723 ms
cource16000_on.png
2732 ms
course_party_off.png
2785 ms
course_party_on.png
2925 ms
dinner_off.png
2958 ms
dinner_on.png
3020 ms
drink_off.png
3038 ms
drink_on.png
2703 ms
floor_guide_off.png
2740 ms
floor_guide_on.png
2433 ms
floor_guide_top_off.png
2351 ms
floor_guide_top_on.png
2359 ms
gaiyou_off.png
2225 ms
gaiyou_on.png
2131 ms
gournavi_off.png
2104 ms
gournavi_on.png
2238 ms
information_off.png
2010 ms
information_on.png
1980 ms
kintan_off.png
2008 ms
kintan_on.png
1969 ms
lunch_off.jpg
2017 ms
lunch_on.jpg
1972 ms
lunch_off.png
1894 ms
lunch_on.png
1940 ms
majestic_off.png
1961 ms
majestic_on.png
1985 ms
party_guide_off.png
1987 ms
party_guide_on.png
2017 ms
party_off.png
1919 ms
party_on.png
1921 ms
plan_off.png
1985 ms
plan_on.png
2004 ms
reservetion_off.png
1959 ms
reservetion_on.png
1979 ms
saiyou_off.png
1923 ms
saiyou_on.png
1950 ms
season_party_plan_off.png
1972 ms
season_party_plan_on.png
1969 ms
seasons_lunch_off.jpg
1985 ms
seasons_lunch_on.jpg
1956 ms
seiyuzan_off.png
1918 ms
seiyuzan_on.png
1962 ms
shiodome_value_lunch_off.jpg
1986 ms
shiodome_value_lunch_on.jpg
1976 ms
special_lunch_off.jpg
2008 ms
special_lunch_on.jpg
1935 ms
special_plan_off.png
1950 ms
special_plan_on.png
1981 ms
top_off.png
1979 ms
top_on.png
2003 ms
topics_off.png
1994 ms
topics_on.png
1934 ms
weekly_lunch_off.jpg
1948 ms
weekly_lunch_on.jpg
1985 ms
yoyaku_off.png
1939 ms
yoyaku_on.png
2011 ms
navi_upper_001_on.png
1991 ms
navi_upper_001_off.png
1955 ms
navi_upper_002_on.png
1927 ms
navi_upper_002_off.png
1959 ms
navi_upper_003_on.png
1959 ms
navi_upper_003_off.png
1984 ms
navi_upper_004_on.png
1948 ms
navi_upper_004_off.png
1938 ms
navi_upper_005_on.png
1928 ms
navi_upper_005_off.png
1989 ms
navi_lower_001_on.png
1939 ms
navi_lower_001_off.png
1987 ms
navi_lower_002_on.png
1951 ms
navi_lower_002_off.png
1965 ms
navi_lower_003_on.png
1947 ms
navi_lower_003_off.png
1974 ms
navi_lower_004_on.png
1945 ms
navi_lower_004_off.png
1969 ms
navi_lower_005_on.png
1912 ms
navi_lower_005_off.png
1972 ms
menu_01_off.png
1985 ms
menu_01_on.png
2169 ms
menu_02_off.png
1966 ms
menu_02_on.png
1956 ms
menu_03_off.png
1903 ms
menu_03_on.png
2125 ms
menu_01_off.png
1961 ms
menu_01_on.png
1962 ms
menu_02_off.png
1966 ms
menu_02_on.png
1933 ms
chefs_premium_lunch_off.jpg
2070 ms
chefs_premium_lunch_on.jpg
2117 ms
seasons_lunch_off.jpg
2059 ms
seasons_lunch_on.jpg
1985 ms
shiodome_value_lunch_off.jpg
1986 ms
shiodome_value_lunch_on.jpg
1925 ms
special_lunch_off.jpg
2099 ms
special_lunch_on.jpg
2091 ms
weekly_lunch_off.jpg
2082 ms
weekly_lunch_on.jpg
1993 ms
menu_01_off.png
1988 ms
menu_01_on.png
2104 ms
menu_02_off.png
2122 ms
menu_02_on.png
2221 ms
menu_03_off.png
2059 ms
menu_03_on.png
2113 ms
sub_drink_01_off.jpg
1964 ms
sub_drink_01_on.jpg
2144 ms
sub_drink_02_off.jpg
2108 ms
sub_drink_02_on.jpg
2075 ms
sub_drink_03_off.jpg
2108 ms
sub_drink_03_on.jpg
2122 ms
sub_info_01_off.jpg
2115 ms
sub_info_01_on.jpg
2138 ms
sub_info_02_off.jpg
2156 ms
sub_info_02_on.jpg
2100 ms
sub_info_03_off.jpg
2094 ms
sub_info_03_on.jpg
2082 ms
sub_info_04_off.jpg
2096 ms
sub_info_04_on.jpg
2115 ms
l_style.css
159 ms
fish-bank-tokyo.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
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
fish-bank-tokyo.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
Displays images with incorrect aspect ratio
Serves images with low resolution
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
fish-bank-tokyo.jp SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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 doesn't use 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 Fish-bank-tokyo.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 Fish-bank-tokyo.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.
fish-bank-tokyo.jp
Open Graph description is not detected on the main page of Fish Bank 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: