1.7 sec in total
69 ms
1.5 sec
76 ms
Visit sushijaponaustin.com now to see the best up-to-date Sushi Japon Austin content and also check out these interesting facts you probably never knew about sushijaponaustin.com
Sushi Japon and Hibachi Grill House is Austin’s modern Asian destination for a unique and unrivaled Japanese dining experience.
Visit sushijaponaustin.comWe analyzed Sushijaponaustin.com page load time and found that the first response time was 69 ms and then it took 1.6 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.
sushijaponaustin.com performance score
name
value
score
weighting
Value3.8 s
27/100
10%
Value8.1 s
2/100
25%
Value25.9 s
0/100
10%
Value72,780 ms
0/100
30%
Value0.556
13/100
15%
Value91.1 s
0/100
10%
69 ms
48 ms
105 ms
120 ms
107 ms
Our browser made a total of 67 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Sushijaponaustin.com, 46% (31 requests) were made to Static.wixstatic.com and 43% (29 requests) were made to Static.parastorage.com. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Static.wixstatic.com.
Page size can be reduced by 356.7 kB (29%)
1.2 MB
857.6 kB
In fact, the total size of Sushijaponaustin.com main page is 1.2 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. 50% of websites need less resources to load. Images take 702.4 kB which makes up the majority of the site volume.
Potential reduce by 356.6 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 356.6 kB or 78% of the original size.
Potential reduce by 0 B
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. Sushi Japon Austin images are well optimized though.
Potential reduce by 57 B
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. This website has mostly compressed JavaScripts.
Potential reduce by 6 B
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. Sushijaponaustin.com has all CSS files already compressed.
Number of requests can be reduced by 10 (20%)
50
40
The browser has sent 50 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Sushi Japon Austin. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and as a result speed up the page load time.
www.sushijaponaustin.com
69 ms
minified.js
48 ms
focus-within-polyfill.js
105 ms
polyfill.min.js
120 ms
bootstrap-features.08dd9a91.bundle.min.js
107 ms
main.c5638ec5.bundle.min.js
106 ms
lodash.min.js
108 ms
react.production.min.js
108 ms
siteTags.bundle.min.js
107 ms
ordering-modal.min.js
144 ms
wix-perf-measure.bundle.min.js
105 ms
react-dom.production.min.js
106 ms
staticCss.min.css
100 ms
thunderbolt
103 ms
f10b04_518f2c68d21541b0bc7b489973d5ca98~mv2.jpg
324 ms
e3bf95a9cdd441ebaf55f139b1b5a7b8.png
25 ms
9fdacc_dfbd0f51a10d4928b740debaa4b790ad.jpg
81 ms
59f6251654c14211a871c16c01de0609.jpg
180 ms
mix%20dring%20.jpg
179 ms
1f59cc_932e0792da704f0c964145477cd7ad5b~mv2.jpg
216 ms
5226e6_4a3c6258d5f3414dbf2b96788958915f~mv2_d_1200_1600_s_2.jpeg
223 ms
5226e6_20e565a621934d94b4c89647d5d23cd6~mv2.jpeg
179 ms
5226e6_b36c663574cd47aca75eba68a8913483~mv2.jpeg
301 ms
5226e6_2bcc2681d7204b559a24a66865a4f5c8~mv2_d_1200_1600_s_2.jpeg
327 ms
5226e6_2fc8be39c5364ca8b2dd1d78e24716c8~mv2.jpeg
381 ms
1f59cc_668b25baca6944299a2aedad62e896d7~mv2.jpg
568 ms
5226e6_2f3730664973494b97a4daf47ad84b82~mv2.jpeg
432 ms
1f59cc_1ffe783b75e04fa389ee04780c08b44e~mv2_d_4256_2832_s_4_2.jpeg
536 ms
5226e6_97a05c184666471683fe63d114acaa3a~mv2.jpeg
498 ms
1f59cc_5217511d4e574763b29e1d10fdd40e30~mv2.jpg
565 ms
5226e6_5a03ff26e1fb4b59845bf9b1fe271bc7~mv2.jpeg
563 ms
1f59cc_2fdabd45e5a2451ebc59fb8feac4051d~mv2.jpg
755 ms
5226e6_620cac07b1504bc2871e992b80518f36~mv2.jpeg
697 ms
5226e6_3f616e0c9daf422c82a49910c975113e~mv2_d_1200_1600_s_2.jpeg
747 ms
5226e6_49dfa079979a47a3bde6e46181b1ab08~mv2_d_1200_1600_s_2.jpeg
736 ms
5226e6_f23c55f4ba0b40d682e27d6c03098a3f~mv2_d_1200_1600_s_2.jpeg
783 ms
1f59cc_d9f73d9f4208492cb8984b565a6d4042~mv2.jpg
829 ms
1f59cc_281ab7f0543242beac88426d7b84359a~mv2.jpg
928 ms
1f59cc_8eb3da25fca94b0182fc3efc558a0e76~mv2.jpg
976 ms
1f59cc_6cd4d3d0d6cd456d894a8272a798b328~mv2.jpg
910 ms
1f59cc_c44ee7b33d8a46fcba372b1fb6bec4a6~mv2.jpg
988 ms
1f59cc_4a01c58f1b734d0aa0276b7e4b024203~mv2.jpg
973 ms
1f59cc_2593cd500fec48ca9f7b8d4eb6fb1310~mv2_d_3744_5616_s_4_2.jpeg
1047 ms
1f59cc_b86ed1484d794118940873555537f9b8~mv2_d_5616_3744_s_4_2.jpeg
1136 ms
11062b_c996aa7f864f4893b59aeb454ec36a0cf000.jpg
1014 ms
ordering-modal.min.css
64 ms
thunderbolt
7 ms
4021a3b9-f782-438b-aeb4-c008109a8b64.woff
6 ms
b56b944e-bbe0-4450-a241-de2125d3e682.woff
7 ms
6f8d1983-4d34-4fa4-9110-988f6c495757.woff
7 ms
908c4810-64db-4b46-bb8e-823eb41f68c0.woff
8 ms
e2b9cbeb-fa8e-41cd-8a6a-46044b29ba52.woff
7 ms
p0A1C4_gK5NzKtuGSwNurQ.woff
21 ms
h3r77AwDsldr1E_2g4qqGBsxEYwM7FgeyaSgU71cLG0.woff
25 ms
bc176270-17fa-4c78-a343-9fe52824e501.woff
24 ms
07d62b21-8d7a-4c36-be86-d32ab1089972.woff
21 ms
a9e95a29-98a7-404a-90ee-1929ad09c696.woff
21 ms
e947b76a-edcf-4519-bc3d-c2da35865717.woff
25 ms
03805817-4611-4dbc-8c65-0f73031c3973.woff
23 ms
cca525a8-ad89-43ae-aced-bcb49fb271dc.woff
24 ms
80de9d5d-ab5f-40ce-911b-104e51e93d7c.woff
26 ms
I1Pn3gihk5vyP0Yw5GqKsQ.woff
26 ms
kU6VHbqMAZhaN_nXCmLQsQ.woff
25 ms
deprecation-en.v5.html
7 ms
bolt-performance
30 ms
deprecation-style.v5.css
9 ms
right-arrow.svg
6 ms
sushijaponaustin.com accessibility score
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
Buttons do not have an accessible name
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
sushijaponaustin.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
sushijaponaustin.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Sushijaponaustin.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Sushijaponaustin.com 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.
sushijaponaustin.com
Open Graph data is detected on the main page of Sushi Japon Austin. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: