2.5 sec in total
162 ms
2 sec
308 ms
Welcome to restaurantetakasu.com.br homepage info - get ready to check Restaurante TAKASU best content for Brazil right away, or after learning these important things about restaurantetakasu.com.br
Primeiro restaurante do Brasil especializado em Yakiniku, o churrasco Japonês! Venha experimentar o melhor da culinária oriental.
Visit restaurantetakasu.com.brWe analyzed Restaurantetakasu.com.br page load time and found that the first response time was 162 ms and then it took 2.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
restaurantetakasu.com.br performance score
162 ms
138 ms
86 ms
65 ms
71 ms
Our browser made a total of 115 requests to load all elements on the main page. We found that 3% of them (3 requests) were addressed to the original Restaurantetakasu.com.br, 34% (39 requests) were made to Static.parastorage.com and 18% (21 requests) were made to Static.wixstatic.com. The less responsive or slowest element that took the longest time to load (788 ms) relates to the external source Static.wixstatic.com.
Page size can be reduced by 3.1 MB (68%)
4.5 MB
1.5 MB
In fact, the total size of Restaurantetakasu.com.br main page is 4.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. 70% of websites need less resources to load. Javascripts take 3.6 MB which makes up the majority of the site volume.
Potential reduce by 87.1 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 87.1 kB or 84% of the original size.
Potential reduce by 25.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. Restaurante TAKASU images are well optimized though.
Potential reduce by 2.7 MB
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 2.7 MB or 74% of the original size.
Potential reduce by 256.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. Restaurantetakasu.com.br needs all CSS files to be minified and compressed as it can save up to 256.2 kB or 83% of the original size.
Number of requests can be reduced by 65 (61%)
106
41
The browser has sent 106 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Restaurante TAKASU. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 49 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
restaurantetakasu.com.br
162 ms
www.restaurantetakasu.com.br
138 ms
bt
86 ms
require.min.js
65 ms
main-r.min.js
71 ms
viewer.css
84 ms
dynamicmodel
11 ms
e65494_4cdcda6de84ea76765d42d8317510832_44.json.z
338 ms
e65494_0f1ea5376a0410fa5128469400411d95_44.json.z
403 ms
ugc-viewer
94 ms
bt
236 ms
skins.min.js
89 ms
components.min.js
49 ms
utils.min.js
230 ms
core.min.js
85 ms
react-with-addons.min.js
84 ms
lodash.min.js
21 ms
TweenMax.min.js
84 ms
layout.min.js
88 ms
tpa.min.js
85 ms
fonts.min.js
83 ms
animations.min.js
91 ms
swfobject.min.js
84 ms
mousetrap.min.js
84 ms
tweenEngine.min.js
85 ms
DrawSVGPlugin.min.js
84 ms
react-dom.min.js
84 ms
ScrollToPlugin.min.js
84 ms
widgets.min.js
84 ms
experiment.js
221 ms
render.min.js
84 ms
wixappsCore.min.js
87 ms
wixappsBuilder.min.js
83 ms
zepto.min.js
84 ms
color.min.js
85 ms
react-dom-server.min.js
147 ms
bt
90 ms
bt
36 ms
dc.js
38 ms
bt
217 ms
latin.css
181 ms
StripShowcase.html
124 ms
googleMap.html
127 ms
__utm.gif
83 ms
e316f544f9094143b9eac01f1f19e697.png
27 ms
c090bd269d424abf8f035befe86158de.png
27 ms
a1b09fe8b7f04378a9fe076748ad4a6a.png
32 ms
e65494_9457c6e5dd624c65bc28ea1e1f5ff7ef.jpg
233 ms
e65494_f93f709acceb455590c398722aa85920.jpg
232 ms
e65494_0403ad3118724fb2af343c3f2a95f52b.png
289 ms
e65494_5a51499985d24ae0b9037a6ac7e196c5.png
250 ms
e65494_609aa73a7a214e29a97195bbe96d63f8.jpg
457 ms
e65494_c842779d72f74217b34d136ca8c489be.jpg
277 ms
e65494_8fc67557cbd441ecb9fee7a54cb86eee.jpg
551 ms
e65494_472ec47ed4654d3091c14afe351a299d.jpg
457 ms
e65494_8122a176e26445b69a97a7ffd43314ea.jpg
622 ms
e65494_99210b7ea7aa4dbab423ee6e95e4f19f.png
738 ms
e65494_2beda92fd1c74117882b13da73a769da.png
615 ms
e65494_257f092470fc4ddfbabc13628dccf7bc.png
622 ms
e65494_dc8be1f35fee44d18ad999a538cbc3ee.png
648 ms
e65494_f93f709acceb455590c398722aa85920.jpg
788 ms
e65494_70a848b986094ca692aaed694451fea4.jpg
728 ms
bt
43 ms
bt
44 ms
jquery.min.js
31 ms
jquery.easing-1.3.min.js
24 ms
lodash.min.js
24 ms
Wix.js
286 ms
style.min.css
24 ms
app.min.js
49 ms
Hmoey0Dhqxc
118 ms
js
192 ms
bc176270-17fa-4c78-a343-9fe52824e501.woff
11 ms
03805817-4611-4dbc-8c65-0f73031c3973.woff
10 ms
4021a3b9-f782-438b-aeb4-c008109a8b64.woff
10 ms
www-embed-player-vflfNyN_r.css
92 ms
www-embed-player.js
109 ms
base.js
183 ms
common.js
59 ms
map.js
183 ms
util.js
225 ms
marker.js
181 ms
StaticMapService.GetMapImage
397 ms
Lrq7Jibxdtv2QOPyDSqncpDfQFNs3PE6SoUrUNh2GTU.js
139 ms
ad_status.js
138 ms
ugc-viewer
91 ms
infowindow.js
76 ms
onion.js
104 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
81 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
81 ms
ViewportInfoService.GetViewportInfo
135 ms
stats.js
64 ms
controls.js
73 ms
e65494_70a848b986094ca692aaed694451fea4.jpg
310 ms
spotlight-poi.png
81 ms
css
85 ms
transparent.png
64 ms
google4.png
46 ms
mapcnt6.png
45 ms
tmapctrl.png
47 ms
cb_scout5.png
56 ms
tmapctrl4.png
57 ms
imgs8.png
57 ms
vt
27 ms
vt
26 ms
vt
27 ms
vt
27 ms
vt
25 ms
vt
79 ms
vt
41 ms
vt
40 ms
vt
48 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
5 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
8 ms
AuthenticationService.Authenticate
17 ms
restaurantetakasu.com.br SEO score
PT
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Restaurantetakasu.com.br can be misinterpreted by Google and other search engines. Our service has detected that Portuguese 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 Restaurantetakasu.com.br 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.
restaurantetakasu.com.br
Open Graph data is detected on the main page of Restaurante TAKASU. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: