7.3 sec in total
1 sec
5.7 sec
595 ms
Click here to check amazing Sushilines content. Otherwise, check out these important facts you probably never knew about sushilines.be
This domain may be for sale!
Visit sushilines.beWe analyzed Sushilines.be page load time and found that the first response time was 1 sec and then it took 6.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
sushilines.be performance score
name
value
score
weighting
Value0
0/100
10%
Value0
0/100
25%
Value0
0/100
10%
Value0
0/100
30%
Value0.084
93/100
15%
Value0
0/100
10%
1037 ms
191 ms
316 ms
313 ms
314 ms
Our browser made a total of 73 requests to load all elements on the main page. We found that 99% of them (72 requests) were addressed to the original Sushilines.be, 1% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (2.2 sec) belongs to the original domain Sushilines.be.
Page size can be reduced by 473.6 kB (21%)
2.2 MB
1.8 MB
In fact, the total size of Sushilines.be main page is 2.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. 45% of websites need less resources to load. Images take 1.7 MB which makes up the majority of the site volume.
Potential reduce by 23.4 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 3.5 kB, which is 12% 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 23.4 kB or 81% of the original size.
Potential reduce by 57.6 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. Sushilines images are well optimized though.
Potential reduce by 270.8 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 270.8 kB or 72% of the original size.
Potential reduce by 121.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. Sushilines.be needs all CSS files to be minified and compressed as it can save up to 121.9 kB or 82% of the original size.
Number of requests can be reduced by 32 (44%)
72
40
The browser has sent 72 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Sushilines. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 10 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.
sushilines.be
1037 ms
k2.css
191 ms
modal.css
316 ms
normalize.css
313 ms
layout.css
314 ms
joomla.css
310 ms
system.css
351 ms
template.css
383 ms
menu.css
467 ms
gk.stuff.css
509 ms
vm.css
506 ms
style1.css
510 ms
mootools-core.js
676 ms
core.js
597 ms
jquery.min.js
19 ms
k2.js
628 ms
vmsite.js
731 ms
mootools-more.js
1029 ms
modal.js
731 ms
gk.scripts.js
800 ms
gk.menu.js
799 ms
engine.js
800 ms
bg_base.jpg
1724 ms
bg_abstract.png
782 ms
logo_sushilines2.png
179 ms
menu_arrow.png
135 ms
tablet_menu_btn.png
134 ms
loader.gif
136 ms
pattern.png
311 ms
is_nav.png
296 ms
font_size.png
295 ms
foie-gras-mangue_202x296.jpg
455 ms
assortisement-tempura_202x296.jpg
506 ms
lunch-saumon_202x296.jpg
496 ms
plateau-22_202x296.jpg
524 ms
maki_202x296.jpg
689 ms
sushi_202x296.jpg
657 ms
sashimi_saumon_thon_202x296.jpg
727 ms
temaki_202x296.jpg
749 ms
rolls_202x296.jpg
840 ms
california_cat_202x296.jpg
876 ms
chirashi-thon-saumon3_202x296.jpg
930 ms
brochette-thon_202x296.jpg
974 ms
gingembre5_202x296.jpg
931 ms
saumon-cheese_202x296.jpg
999 ms
oeufs_202x296.jpg
1108 ms
saumon-avocat_202x296.jpg
1186 ms
saumon-cheese6_202x296.jpg
1187 ms
125-avocat-concombre_202x296.jpg
1214 ms
printemps-thon-avocat_202x296.jpg
1251 ms
glacee-japonaise7_202x296.jpg
1293 ms
sake-cannette_202x296.jpg
1270 ms
california-saumon-cheese_202x296.jpg
1385 ms
foie-gras-mangue_202x296.jpg
1412 ms
maki-gourte-marine_202x296.jpg
1412 ms
SCHAERBEEK3.jpg
1446 ms
LAEKEN2.jpg
1476 ms
IXELLES1.jpg
1522 ms
livraison-smart.png
1650 ms
ouvertur2e.png
2151 ms
tablet.css
114 ms
mobile.css
122 ms
sushiline.png
950 ms
bg_n.png
268 ms
bg_ne.png
267 ms
bg_e.png
266 ms
bg_se.png
266 ms
bg_s.png
263 ms
bg_sw.png
395 ms
bg_w.png
394 ms
bg_nw.png
395 ms
spinner.gif
402 ms
closebox.png
402 ms
sushilines.be 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
<frame> or <iframe> elements do not have a title
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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.
sushilines.be best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Browser errors were logged to the console
sushilines.be SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Page is blocked from indexing
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
EN
FR
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Sushilines.be can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed French language. Our system also found out that Sushilines.be 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.
sushilines.be
Open Graph description is not detected on the main page of Sushilines. 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: