7.6 sec in total
1.6 sec
5.7 sec
287 ms
Visit tokyo.uz now to see the best up-to-date Tokyo content for Uzbekistan and also check out these interesting facts you probably never knew about tokyo.uz
Главная
Visit tokyo.uzWe analyzed Tokyo.uz page load time and found that the first response time was 1.6 sec and then it took 6 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
tokyo.uz performance score
1592 ms
234 ms
375 ms
400 ms
417 ms
Our browser made a total of 81 requests to load all elements on the main page. We found that 85% of them (69 requests) were addressed to the original Tokyo.uz, 5% (4 requests) were made to Fonts.gstatic.com and 2% (2 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (3 sec) belongs to the original domain Tokyo.uz.
Page size can be reduced by 679.8 kB (27%)
2.5 MB
1.8 MB
In fact, the total size of Tokyo.uz main page is 2.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. 60% of websites need less resources to load. Images take 1.8 MB which makes up the majority of the site volume.
Potential reduce by 65.3 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 23.5 kB, which is 31% 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 65.3 kB or 86% of the original size.
Potential reduce by 127.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. Tokyo images are well optimized though.
Potential reduce by 316.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 316.4 kB or 71% of the original size.
Potential reduce by 170.8 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. Tokyo.uz needs all CSS files to be minified and compressed as it can save up to 170.8 kB or 86% of the original size.
Number of requests can be reduced by 32 (44%)
73
41
The browser has sent 73 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 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 24 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
tokyo.uz
1592 ms
gt-push-menu.css
234 ms
gt-push-menu-icons.css
375 ms
style.css
400 ms
shortcodes.css
417 ms
general.css
626 ms
8.css
447 ms
jquery.js
678 ms
jquery-migrate.min.js
570 ms
gtpm.js
592 ms
modernizr.custom.js
604 ms
jquery.nicescroll.js
845 ms
jquery.tap.min.js
750 ms
modernizr-2.5.3.min.js
796 ms
html5.js
38 ms
jquery.nicescroll.min.js
1000 ms
comment-reply.min.js
818 ms
css
25 ms
style.css
879 ms
jquery.ui.core.min.js
953 ms
jquery.ui.widget.min.js
977 ms
jquery.ui.accordion.min.js
1090 ms
jquery.ui.tabs.min.js
1091 ms
ale-shortcodes-lib.js
1091 ms
jquery.form.min.js
1146 ms
jquery.cookie.js
1224 ms
post-like.js
1226 ms
modules.js
1227 ms
scripts.js
1241 ms
GIF-PNG.png
504 ms
adress.png
371 ms
social.png
373 ms
menu_li8.png
373 ms
hide.png
433 ms
MainSlide-1.jpg
792 ms
MainSlide-2.jpg
1205 ms
MainSlide-5.jpg
1092 ms
MainSlide-11.jpg
1888 ms
MainSlide-9.jpg
962 ms
MainSlide-12.jpg
1103 ms
MainSlide-10.jpg
1386 ms
MainSlide-7.jpg
1339 ms
MainSlide-4.jpg
1509 ms
Default-logo-size-443-182px1.png
1336 ms
mobile-header-logo-size-280-115px-.png
1406 ms
opening8.png
1558 ms
botslide.png
1551 ms
About-us-Logo.png
1583 ms
icon28.png
1588 ms
Delivery-Logo1.png
1693 ms
1326x215_1.jpg
2320 ms
Face1.jpg
1968 ms
Face2.jpg
1790 ms
Face3.jpg
1779 ms
arrow.png
1877 ms
JAPAN_0001_Sloy-10_1-230x150.jpg
1972 ms
dollar.png
2972 ms
JAPAN_0002_Layer-13_1-230x150.jpg
2000 ms
JAPAN_0003_Layer-10_1-230x150.jpg
2004 ms
plusone.js
134 ms
widgets.js
34 ms
ga.js
58 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
50 ms
DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf
57 ms
MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf
58 ms
k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf
57 ms
JAPAN_0004_Sloy-12-kopiya_1-230x150.jpg
2126 ms
JAPAN_0005_harusame-s-moreproduktami-36.500-risovaya-lapsha-s-mornproduktami_1-230x150.jpg
2068 ms
__utm.gif
20 ms
JAPAN_0006_yaki-udon-s-kuritsey-26.500-pshenichnaya-lapsha-s-ovoshhami-i-kuritsey_1-230x150.jpg
2057 ms
footer-logo-size-98-38px.png
2064 ms
cb=gapi.loaded_0
147 ms
logo-RBK1.png
2165 ms
gtpm.woff
2445 ms
AAAAEAAAAAAADtwABAAAAAAAAAAAAAAAAAAAACgAAAAAAAAAAAAAAAAIAAAADJQAAA7cAAAO3AAkDbgAAAW4AAAFuABoAAAAAAAoAFAAeANgBLAHmAkACZAKSAAAAAQAAAAoAhQAGAAAAAAACAAAAAAAAAAAAAAAAAAAAAAAAAA4ArgABAAAAAAABAAoAAAABAAAAAAACAA4AOQABAAAAAAADAAoAIAABAAAAAAAEAAoARwABAAAAAAAFABYACgABAAAAAAAGAAUAKgABAAAAAAAKACgAUQADAAEECQABAAoAAAADAAEECQACAA4AOQADAAEECQADAAoAIAADAAEECQAEAAoARwADAAEECQAFABYACgADAAEECQAGAAoALwADAAEECQAKACgAUQBnAHQAcABtAGIAVgBlAHIAcwBpAG8AbgAgADAALgAwAGcAdABwAG0AYmd0cG1iAGcAdABwAG0AYgBSAGUAZwB1AGwAYQByAGcAdABwAG0AYgBHAGUAbgBlAHIAYQB0AGUAZAAgAGIAeQAgAEkAYwBvAE0AbwBvAG4AAAMAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA=
6 ms
touch.css
2080 ms
leftslide.png
2095 ms
rightslide.png
2146 ms
arrowleft.png
2134 ms
arrowright.png
2136 ms
touch.css
203 ms
tokyo.uz SEO score
N/A
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Tokyo.uz can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Tokyo.uz 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.
tokyo.uz
Open Graph data is detected on the main page of Tokyo. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: