3.9 sec in total
469 ms
3 sec
358 ms
Click here to check amazing Sansai content for Australia. Otherwise, check out these important facts you probably never knew about sansai.com.au
Shop powered by PrestaShop
Visit sansai.com.auWe analyzed Sansai.com.au page load time and found that the first response time was 469 ms and then it took 3.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
sansai.com.au performance score
name
value
score
weighting
Value6.2 s
3/100
10%
Value75.2 s
0/100
25%
Value15.7 s
0/100
10%
Value1,910 ms
8/100
30%
Value0.424
23/100
15%
Value9.5 s
30/100
10%
469 ms
25 ms
38 ms
377 ms
128 ms
Our browser made a total of 111 requests to load all elements on the main page. We found that 59% of them (66 requests) were addressed to the original Sansai.com.au, 15% (17 requests) were made to Maps.googleapis.com and 8% (9 requests) were made to Maps.gstatic.com. The less responsive or slowest element that took the longest time to load (1 sec) belongs to the original domain Sansai.com.au.
Page size can be reduced by 1.2 MB (30%)
3.9 MB
2.7 MB
In fact, the total size of Sansai.com.au main page is 3.9 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. 65% of websites need less resources to load. Images take 2.3 MB which makes up the majority of the site volume.
Potential reduce by 82.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 82.5 kB or 76% of the original size.
Potential reduce by 62.1 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. Sansai images are well optimized though.
Potential reduce by 823.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 823.4 kB or 67% of the original size.
Potential reduce by 205.6 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. Sansai.com.au needs all CSS files to be minified and compressed as it can save up to 205.6 kB or 84% of the original size.
Number of requests can be reduced by 62 (62%)
100
38
The browser has sent 100 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Sansai. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 29 to 1 for JavaScripts and from 25 to 1 for CSS and as a result speed up the page load time.
index.php
469 ms
css
25 ms
css
38 ms
bootstrap.css
377 ms
bootstrap-responsive.css
128 ms
global.css
251 ms
jquery.autocomplete.css
130 ms
product_list.css
130 ms
blocksearch.css
181 ms
homefeatured.css
189 ms
blocknewsletter.css
191 ms
blocklanguages.css
192 ms
blockcart.css
243 ms
blockuserinfo.css
252 ms
blockspecials.css
253 ms
productcomments.css
254 ms
blockwishlist.css
304 ms
style.css
311 ms
crossselling.css
312 ms
mailalerts.css
314 ms
blockleotopmenu.css
315 ms
styles.css
365 ms
five-steps.css
438 ms
browser.css
382 ms
skin.css
383 ms
jquery-1.7.2.min.js
611 ms
jquery-migrate-1.2.1.js
434 ms
jquery.easing.js
439 ms
tools.js
440 ms
jquery.autocomplete.js
496 ms
ajax-cart.js
559 ms
ajax-wishlist.js
498 ms
crossselling.js
498 ms
jquery.scrollTo.js
558 ms
jquery.serialScroll.js
560 ms
bootstrap.js
683 ms
addthis_widget.js
10 ms
js
102 ms
5831eba7-422e-4e95-911e-fa20eba8d0e8
670 ms
pluginDetect.js
563 ms
analytics.js
7 ms
collect
12 ms
bg_background.png
64 ms
logo.jpg
63 ms
980_340_6b45531909c7f51bc7f44aae96c78a5f.jpg
337 ms
980_340_ab938a82f86788f4400fcd41278f40e2.jpg
499 ms
980_340_f3645a5595b4ec5c9d4cf44c218c253c.jpg
404 ms
980_340_056ded02bc37b270ee5399ce79125d30.jpg
437 ms
980_340_93a55cf8a3d46e8391af814f37d46171.jpg
260 ms
NewArrivals.jpg
258 ms
register1.jpg
288 ms
622-home_default.jpg
336 ms
618-home_default.jpg
354 ms
577-home_default.jpg
404 ms
554-home_default.jpg
405 ms
595-home_default.jpg
409 ms
597-home_default.jpg
438 ms
625-home_default.jpg
439 ms
630-home_default.jpg
440 ms
pattern3.png
1043 ms
logo.png
396 ms
search-pic.png
399 ms
border.png
392 ms
login_blue.gif
391 ms
ODelI1aHBYDBqgeIAH2zlNzbP97U9sKh0jjxbPbfOKg.ttf
14 ms
toadOcfmlt9b38dHJxOBGEMbjGELOEJD5J8DUmxkO-A.ttf
18 ms
toadOcfmlt9b38dHJxOBGLsbIrGiHa6JIepkyt5c0A0.ttf
142 ms
toadOcfmlt9b38dHJxOBGBPPOa1q11iOmmM9mDHHHX4.ttf
17 ms
arrow-control.png
443 ms
bg_nav.png
445 ms
background.png
438 ms
bg_h4.png
438 ms
bullet-li.png
438 ms
helveticaneue.ttf
364 ms
vni-helve-condense.ttf
369 ms
index.php
741 ms
index.php
854 ms
300lo.json
40 ms
counter.5524cceca805eb4b9b2b.js
24 ms
sh.8e5f85691f9aaa082472a194.html
48 ms
shares.json
51 ms
common.js
32 ms
map.js
54 ms
util.js
95 ms
marker.js
51 ms
StaticMapService.GetMapImage
140 ms
onion.js
20 ms
ViewportInfoService.GetViewportInfo
47 ms
stats.js
42 ms
controls.js
52 ms
infowindow.js
19 ms
transparent.png
82 ms
css
96 ms
vt
48 ms
vt
47 ms
vt
47 ms
vt
48 ms
vt
45 ms
spotlight-poi.png
46 ms
google4.png
47 ms
mapcnt6.png
68 ms
sv5.png
68 ms
tmapctrl.png
54 ms
cb_scout5.png
55 ms
tmapctrl4.png
62 ms
imgs8.png
62 ms
AuthenticationService.Authenticate
134 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
25 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
32 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
46 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
47 ms
sansai.com.au 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.
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.
sansai.com.au best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
sansai.com.au SEO score
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 Sansai.com.au 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 Sansai.com.au 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.
sansai.com.au
Open Graph description is not detected on the main page of Sansai. 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: