9 sec in total
1.2 sec
7.1 sec
629 ms
Visit sandz.com now to see the best up-to-date Sandz content and also check out these interesting facts you probably never knew about sandz.com
Visit sandz.comWe analyzed Sandz.com page load time and found that the first response time was 1.2 sec and then it took 7.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
sandz.com performance score
name
value
score
weighting
Value6.8 s
2/100
10%
Value10.7 s
0/100
25%
Value13.6 s
2/100
10%
Value350 ms
73/100
30%
Value0.005
100/100
15%
Value13.8 s
10/100
10%
1214 ms
474 ms
715 ms
721 ms
35 ms
Our browser made a total of 76 requests to load all elements on the main page. We found that 89% of them (68 requests) were addressed to the original Sandz.com, 4% (3 requests) were made to Fonts.gstatic.com and 3% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (2.4 sec) belongs to the original domain Sandz.com.
Page size can be reduced by 400.7 kB (13%)
3.0 MB
2.6 MB
In fact, the total size of Sandz.com main page is 3.0 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. Images take 2.9 MB which makes up the majority of the site volume.
Potential reduce by 112.0 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 112.0 kB or 82% of the original size.
Potential reduce by 288.7 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. Sandz images are well optimized though.
Number of requests can be reduced by 29 (41%)
70
41
The browser has sent 70 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Sandz. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 15 to 1 for JavaScripts and from 16 to 1 for CSS and as a result speed up the page load time.
sandz.com
1214 ms
styles.css
474 ms
wpcf7-redirect-frontend.min.css
715 ms
font-awesome.min.css
721 ms
css
35 ms
ex_s_lick.css
738 ms
ex_s_lick-theme.css
746 ms
animate.css
766 ms
style.css
768 ms
style-sidebyside.css
953 ms
horiz-style.css
959 ms
dark.css
983 ms
style.css
992 ms
flatsome.css
1281 ms
style.css
1015 ms
style.css
1190 ms
css
32 ms
jquery.min.js
1441 ms
jquery-migrate.min.js
1228 ms
gtm4wp-form-move-tracker.js
1239 ms
js
60 ms
index.js
1034 ms
index.js
1200 ms
wpcf7r-fe.js
1443 ms
flatsome-live-search.js
1444 ms
scripts.js
1443 ms
wp-polyfill-inert.min.js
1444 ms
regenerator-runtime.min.js
1445 ms
wp-polyfill.min.js
1459 ms
hoverIntent.min.js
1538 ms
flatsome.js
2012 ms
SANDZ-logo.png
252 ms
SLIDER-1-FINAL.jpg
1035 ms
slide3-bg.jpg
1035 ms
Webinar.jpg
1984 ms
btnbanner-book-a-live-demo.jpg
411 ms
btnbanner-explore-what-works-for-you.jpg
504 ms
btnbanner-request-a-callback.jpg
657 ms
slide-bg-2.jpg
1072 ms
Infrastructure-Modernization_NN-300x239.png
1149 ms
Modern-Data-Protection-and-Security_nn-300x239.png
1034 ms
Platform-Modernization_11-300x239.png
1257 ms
Application-Data-Modernization_NN-300x239.png
1280 ms
bgnnn-1024x588.jpg
1281 ms
New-partners_0014_arrosoft.jpg
1598 ms
New-partners_0012_atempo.jpg
1657 ms
New-partners_0013_asigra.jpg
1505 ms
New-partners_0011_cristie.jpg
1765 ms
New-partners_0010_dell.jpg
1524 ms
New-partners_0009_hpe.jpg
1746 ms
New-partners_0008_ibm.jpg
1783 ms
New-partners_0007_nutanix.jpg
2101 ms
New-partners_0006_quantum.jpg
2136 ms
New-partners_0004_tiger.jpg
1982 ms
New-partners_0002_yugabyte.jpg
2267 ms
New-partners_0003_veeam.jpg
2044 ms
vm.jpg
2211 ms
New-partners_0001_zadara.jpg
2229 ms
0000_zerto.jpg
2191 ms
book-live-demo-1-300x300.png
2229 ms
Explore-300x300.png
2266 ms
Callback-300x300.png
2341 ms
Navigating-Industry-Changes-with-Sandz-Infrastructure-as-a-Service-300x169.jpg
2360 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf
32 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aX8.ttf
45 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aX8.ttf
45 ms
fl-icons.ttf
2399 ms
xfbml.customerchat.js
43 ms
Airgap-Webinar-300x182.png
2421 ms
modernizatiON-300x188.png
2390 ms
The-Future-of-Data-Services-for-the-Digital-Enterprise-300x188.png
2391 ms
Build-a-Future-Ready-Infrastructure-300x188.png
2282 ms
Controlling-Your-Data-300x192.png
2205 ms
Protect-Your-Last-Line-of-Defense-300x188.png
2107 ms
353 ms
Securing-the-Anywhere-Workspace-2048x1280-1-300x188.png
1809 ms
sandz.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
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.
sandz.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
sandz.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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 Sandz.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 Sandz.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.
sandz.com
Open Graph description is not detected on the main page of Sandz. 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: