1.8 sec in total
101 ms
1.5 sec
171 ms
Welcome to sushi-go.com homepage info - get ready to check Sushi Go best content right away, or after learning these important things about sushi-go.com
Visit sushi-go.comWe analyzed Sushi-go.com page load time and found that the first response time was 101 ms and then it took 1.7 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.
sushi-go.com performance score
name
value
score
weighting
Value2.5 s
67/100
10%
Value8.2 s
2/100
25%
Value4.3 s
76/100
10%
Value290 ms
80/100
30%
Value1.652
0/100
15%
Value10.4 s
24/100
10%
101 ms
27 ms
40 ms
32 ms
30 ms
Our browser made a total of 35 requests to load all elements on the main page. We found that 6% of them (2 requests) were addressed to the original Sushi-go.com, 29% (10 requests) were made to Img4.wsimg.com and 23% (8 requests) were made to Maps.googleapis.com. The less responsive or slowest element that took the longest time to load (547 ms) relates to the external source Google.com.
Page size can be reduced by 800.2 kB (60%)
1.3 MB
536.2 kB
In fact, the total size of Sushi-go.com main page is 1.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. 55% of websites need less resources to load. Javascripts take 1.1 MB which makes up the majority of the site volume.
Potential reduce by 43.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 43.5 kB or 71% of the original size.
Potential reduce by 1.3 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. Sushi Go images are well optimized though.
Potential reduce by 728.5 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 728.5 kB or 66% of the original size.
Potential reduce by 26.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. Sushi-go.com needs all CSS files to be minified and compressed as it can save up to 26.9 kB or 78% of the original size.
Number of requests can be reduced by 19 (59%)
32
13
The browser has sent 32 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Sushi Go. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and as a result speed up the page load time.
www.sushi-go.com
101 ms
css
27 ms
css
40 ms
site.css
32 ms
duel.js
30 ms
jq.js
58 ms
a5834d361c59a9cf59b3b964488b835f
353 ms
social.share.js
146 ms
analytics.js
26 ms
maps
121 ms
cookiemanager.js
123 ms
iebackground.js
122 ms
ba20ce2418e8c89dd70991811c848229
283 ms
22614920926716c79802a7005b5c568a
245 ms
191b45f9db95553c483d50a190a193d7
198 ms
fe0cf2f93e5fc3a413d01d1190646949
231 ms
c01df071c451633946318d76d2b867ac
134 ms
collect
62 ms
embed
547 ms
util.instances.js
7 ms
util.model.js
6 ms
helper.js
6 ms
util.window.js
12 ms
browser.js
9 ms
js
87 ms
init_embed.js
46 ms
common.js
115 ms
map.js
115 ms
google4.png
42 ms
overlay.js
40 ms
addthis_widget.js
26 ms
util.js
34 ms
onion.js
32 ms
search_impl.js
116 ms
StaticMapService.GetMapImage
103 ms
sushi-go.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
Image elements do not have [alt] attributes
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
sushi-go.com 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
sushi-go.com SEO score
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Sushi-go.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 Sushi-go.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.
sushi-go.com
Open Graph description is not detected on the main page of Sushi Go. 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: