927 ms in total
51 ms
750 ms
126 ms
Welcome to sands.com homepage info - get ready to check Sands best content for United States right away, or after learning these important things about sands.com
Las Vegas Sands Corporation is the world leader in developing and operating international, world-class integrated resorts.
Visit sands.comWe analyzed Sands.com page load time and found that the first response time was 51 ms and then it took 876 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.
sands.com performance score
name
value
score
weighting
Value2.5 s
67/100
10%
Value5.6 s
17/100
25%
Value4.1 s
79/100
10%
Value980 ms
28/100
30%
Value0
100/100
15%
Value10.6 s
23/100
10%
51 ms
13 ms
24 ms
51 ms
24 ms
Our browser made a total of 31 requests to load all elements on the main page. We found that 90% of them (28 requests) were addressed to the original Sands.com, 6% (2 requests) were made to Nexus.ensighten.com and 3% (1 request) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (131 ms) belongs to the original domain Sands.com.
Page size can be reduced by 1.3 MB (20%)
6.4 MB
5.1 MB
In fact, the total size of Sands.com main page is 6.4 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. 85% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 4.9 MB which makes up the majority of the site volume.
Potential reduce by 15.8 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 15.8 kB or 79% of the original size.
Potential reduce by 198.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. Sands images are well optimized though.
Potential reduce by 659.6 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 659.6 kB or 70% of the original size.
Potential reduce by 430.7 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. Sands.com needs all CSS files to be minified and compressed as it can save up to 430.7 kB or 84% of the original size.
Number of requests can be reduced by 8 (28%)
29
21
The browser has sent 29 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Sands. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 6 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
www.sands.com
51 ms
bootstrap.min.css
13 ms
font-awesome.min.css
24 ms
main.min.css
51 ms
t01a.min.css
24 ms
jquery-1.11.1.min.js
25 ms
head.min.js
25 ms
main.min.js
131 ms
sands_logo_gold_173x73-72dpi3.png
106 ms
comment-bubble-icon.png
107 ms
facebook-icon.png
109 ms
tweeter-icon.png
107 ms
linkin-icon.png
106 ms
instagram.png
107 ms
main-img11.png
109 ms
main-img21.png
110 ms
main-img31.png
113 ms
main-img41.png
110 ms
main-img51.png
109 ms
main-img61.png
114 ms
main-SCC-St-Regis-rendering-1663x626.jpg
116 ms
lvs-sands.jpg
111 ms
icon_sprite_sm.png
116 ms
lvs-sands-care.jpg
112 ms
sands-confidential.png
112 ms
sands-stock-exchange.jpg
114 ms
ajax-loader.gif
31 ms
Bootstrap.js
17 ms
fontawesome-webfont.woff
34 ms
analytics.js
22 ms
serverComponent.php
34 ms
sands.com accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
button, link, and menuitem elements do not have accessible names.
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
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
sands.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
sands.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
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Sands.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Sands.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.
sands.com
Open Graph description is not detected on the main page of Sands. 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: