31 sec in total
1.3 sec
29.1 sec
640 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.3 sec and then it took 29.8 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster. Unfortunately, there were 3 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
sandz.com performance score
name
value
score
weighting
Value10.0 s
0/100
10%
Value11.7 s
0/100
25%
Value26.9 s
0/100
10%
Value820 ms
35/100
30%
Value0.004
100/100
15%
Value65.3 s
0/100
10%
1288 ms
771 ms
835 ms
875 ms
37 ms
Our browser made a total of 82 requests to load all elements on the main page. We found that 84% of them (69 requests) were addressed to the original Sandz.com, 4% (3 requests) were made to Fonts.googleapis.com and 4% (3 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (20.3 sec) belongs to the original domain Sandz.com.
Page size can be reduced by 334.3 kB (13%)
2.6 MB
2.2 MB
In fact, the total size of Sandz.com main page is 2.6 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. 60% of websites need less resources to load. Images take 2.4 MB which makes up the majority of the site volume.
Potential reduce by 99.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. 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 99.4 kB or 81% of the original size.
Potential reduce by 234.8 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.
Potential reduce by 50 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.
Number of requests can be reduced by 38 (51%)
74
36
The browser has sent 74 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 17 to 1 for JavaScripts and from 23 to 1 for CSS and as a result speed up the page load time.
sandz.com
1288 ms
styles.css
771 ms
wpcf7-redirect-frontend.min.css
835 ms
font-awesome.min.css
875 ms
css
37 ms
ex_s_lick.css
873 ms
ex_s_lick-theme.css
1547 ms
animate.css
1556 ms
style.css
1597 ms
style-sidebyside.css
1708 ms
horiz-style.css
1764 ms
dark.css
1780 ms
elementor-icons.min.css
2357 ms
frontend-lite.min.css
2446 ms
swiper.min.css
2531 ms
post-899.css
2618 ms
main.css
2613 ms
global.css
2700 ms
style.css
3108 ms
flatsome.css
3557 ms
style.css
3335 ms
style.css
3417 ms
css
36 ms
css
34 ms
jquery.min.js
3777 ms
jquery-migrate.min.js
3470 ms
gtm4wp-form-move-tracker.js
3974 ms
js
64 ms
index.js
4270 ms
index.js
4560 ms
wpcf7r-fe.js
4525 ms
flatsome-live-search.js
4736 ms
scripts.js
4996 ms
wp-polyfill-inert.min.js
4995 ms
regenerator-runtime.min.js
5046 ms
wp-polyfill.min.js
5337 ms
hoverIntent.min.js
5373 ms
flatsome.js
6093 ms
SANDZ-logo.png
1599 ms
SLIDER-1-FINAL.jpg
2863 ms
slide3-bg.jpg
3365 ms
Webinar.jpg
4788 ms
btnbanner-book-a-live-demo.jpg
2326 ms
btnbanner-explore-what-works-for-you.jpg
2627 ms
btnbanner-request-a-callback.jpg
2842 ms
slide-bg-2.jpg
7314 ms
Infrastructure-Modernization_NN-300x239.png
3648 ms
Modern-Data-Protection-and-Security_nn-300x239.png
3836 ms
Platform-Modernization_11-300x239.png
4085 ms
Application-Data-Modernization_NN-300x239.png
4489 ms
bgnnn-1024x588.jpg
5113 ms
New-partners_0014_arrosoft.jpg
5279 ms
New-partners_0012_atempo.jpg
5841 ms
New-partners_0013_asigra.jpg
6368 ms
New-partners_0011_cristie.jpg
6313 ms
New-partners_0010_dell.jpg
6758 ms
New-partners_0009_hpe.jpg
6780 ms
New-partners_0008_ibm.jpg
7744 ms
New-partners_0007_nutanix.jpg
7922 ms
New-partners_0006_quantum.jpg
8426 ms
New-partners_0004_tiger.jpg
8522 ms
New-partners_0002_yugabyte.jpg
8726 ms
New-partners_0003_veeam.jpg
9233 ms
vm.jpg
8537 ms
js
85 ms
analytics.js
34 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf
75 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aX8.ttf
76 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aX8.ttf
77 ms
xfbml.customerchat.js
32 ms
fl-icons.ttf
8736 ms
86 ms
collect
69 ms
collect
37 ms
New-partners_0001_zadara.jpg
9644 ms
0000_zerto.jpg
10406 ms
book-live-demo-1-300x300.png
8868 ms
Explore-300x300.png
8726 ms
Callback-300x300.png
8748 ms
modernizatiON.png
20259 ms
The-Future-of-Data-Services-for-the-Digital-Enterprise.png
19966 ms
Build-a-Future-Ready-Infrastructure.png
19935 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: