Report Summary

  • 19

    Performance

    Renders faster than
    36% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

wlasvegas.com

Marriott Hotels in Las Vegas | Marriott Bonvoy

Page Load Speed

8.1 sec in total

First Response

3 sec

Resources Loaded

4.4 sec

Page Rendered

663 ms

wlasvegas.com screenshot

About Website

Visit wlasvegas.com now to see the best up-to-date W Las Vegas content for United States and also check out these interesting facts you probably never knew about wlasvegas.com

Visit Las Vegas your way! Explore restaurants, local attractions and things to do in your favorite Las Vegas neighborhoods as a Marriott Bonvoy Hotel guest.

Visit wlasvegas.com

Key Findings

We analyzed Wlasvegas.com page load time and found that the first response time was 3 sec and then it took 5.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

wlasvegas.com performance score

19

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.4 s

16/100

10%

LCP (Largest Contentful Paint)

Value6.5 s

9/100

25%

SI (Speed Index)

Value26.3 s

0/100

10%

TBT (Total Blocking Time)

Value15,380 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value49.7 s

0/100

10%

Network Requests Diagram

las-vegas.mi

3043 ms

marriottCommon.js

85 ms

6e15e9b645406f938b23f5e9f0ee55b0f0aafa2feb045

47 ms

ruxitagentjs_ICA7NQVfhqrux_10297240712040816.js

118 ms

launch-EN1ce795381cea451fa40478e502ecce2f.min.js

24 ms

Our browser made a total of 35 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Wlasvegas.com, 17% (6 requests) were made to Cache.marriott.com and 14% (5 requests) were made to S7d1.scene7.com. The less responsive or slowest element that took the longest time to load (3 sec) relates to the external source Marriott.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.4 MB (68%)

Content Size

2.1 MB

After Optimization

667.5 kB

In fact, the total size of Wlasvegas.com main page is 2.1 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. 75% 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. Javascripts take 1.5 MB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 367.5 kB

  • Original 422.6 kB
  • After minification 380.4 kB
  • After compression 55.1 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 367.5 kB or 87% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 225.6 kB
  • After minification 225.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. W Las Vegas images are well optimized though.

JavaScript Optimization

-74%

Potential reduce by 1.1 MB

  • Original 1.5 MB
  • After minification 1.5 MB
  • After compression 386.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 1.1 MB or 74% of the original size.

Requests Breakdown

Number of requests can be reduced by 20 (69%)

Requests Now

29

After Optimization

9

The browser has sent 29 CSS, Javascripts, AJAX and image requests in order to completely render the main page of W Las Vegas. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 21 to 1 for JavaScripts and as a result speed up the page load time.

Accessibility Review

wlasvegas.com accessibility score

84

Accessibility Issues

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

High

[role] values are not valid

High

[aria-*] attributes do not have valid values

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

High

Links do not have a discernible name

Best Practices

wlasvegas.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

wlasvegas.com SEO score

86

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Wlasvegas.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 Wlasvegas.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.

Social Sharing Optimization

Open Graph data is detected on the main page of W Las Vegas. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: