Tools & Wizards About Us
whistler-alpenglow.com screenshot

Report Summary

  • 25

    Performance

    Renders faster than
    44% of other websites

  • 87

    Accessibility

    Visual factors better than
    that of 66% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

whistler-alpenglow.com

Whistler Vacation Rentals, Condos & Lodging | Vacasa

Page Load Speed

2.8 sec in total

First Response

81 ms

Resources Loaded

2.1 sec

Page Rendered

582 ms

whistler-alpenglow.com screenshot

About Website

Welcome to whistler-alpenglow.com homepage info - get ready to check Whistler Alpenglow best content right away, or after learning these important things about whistler-alpenglow.com

Find lodging and condo rentals in Whistler here. Full-service and complete with hot tubs, fireplace, and ski-in/ski-out amenities. Book your vacation rental here.

Visit whistler-alpenglow.com

Key Findings

We analyzed Whistler-alpenglow.com page load time and found that the first response time was 81 ms and then it took 2.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

whistler-alpenglow.com performance score

25

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.7 s

13/100

10%

LCP (Largest Contentful Paint)

Value7.2 s

5/100

25%

SI (Speed Index)

Value5.7 s

52/100

10%

TBT (Total Blocking Time)

Value2,060 ms

7/100

30%

CLS (Cumulative Layout Shift)

Value0.005

100/100

15%

TTI (Time to Interactive)

Value17.1 s

4/100

10%

Network Requests Diagram

whistler-alpenglow.com

81 ms

www.resortquestwhistler.com

252 ms

Whistler

750 ms

otSDKStub.js

25 ms

01903179-cfbb-793a-9590-7dc13a4517e4.json

24 ms

Our browser made a total of 63 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Whistler-alpenglow.com, 54% (34 requests) were made to Cms-assets.boise.vacasa.com and 8% (5 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (914 ms) relates to the external source Vacasa.imgix.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 275.1 kB (22%)

Content Size

1.3 MB

After Optimization

991.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Whistler-alpenglow.com main page is 1.3 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 560.2 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 273.5 kB

  • Original 338.1 kB
  • After minification 300.5 kB
  • After compression 64.6 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. This page needs HTML code to be minified as it can gain 37.6 kB, which is 11% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 273.5 kB or 81% of the original size.

Image Optimization

-0%

Potential reduce by 140 B

  • Original 560.2 kB
  • After minification 560.0 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. Whistler Alpenglow images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 543 B

  • Original 308.8 kB
  • After minification 308.8 kB
  • After compression 308.2 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. This website has mostly compressed JavaScripts.

CSS Optimization

-1%

Potential reduce by 876 B

  • Original 59.9 kB
  • After minification 59.9 kB
  • After compression 59.0 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. Whistler-alpenglow.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 35 (66%)

Requests Now

53

After Optimization

18

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

whistler-alpenglow.com

whistler-alpenglow.com

81 ms

www.resortquestwhistler.com

www.resortquestwhistler.com

252 ms

Whistler

Whistler

750 ms

otSDKStub.js

otSDKStub.js

25 ms

01903179-cfbb-793a-9590-7dc13a4517e4.json

01903179-cfbb-793a-9590-7dc13a4517e4.json

24 ms

location

location

60 ms

datadog-rum.js

datadog-rum.js

58 ms

polyfills.911792441c29.js

polyfills.911792441c29.js

56 ms

commonstuff.116b1a7b9991.js

commonstuff.116b1a7b9991.js

75 ms

jquery.min.js

jquery.min.js

65 ms

17277872316.js

17277872316.js

84 ms

popper.min.js

popper.min.js

82 ms

bootstrap.min.js

bootstrap.min.js

82 ms

slick.min.js

slick.min.js

163 ms

jquery-ui.min.26fd66829059.js

jquery-ui.min.26fd66829059.js

57 ms

datepicker.min.1ef3abddeccf.js

datepicker.min.1ef3abddeccf.js

57 ms

datepicker.lang.edb3f71b486c.js

datepicker.lang.edb3f71b486c.js

58 ms

ls.unveilhooks.min.5ab31e16b8ac.js

ls.unveilhooks.min.5ab31e16b8ac.js

56 ms

ls.bgset.min.8a87b83c24b8.js

ls.bgset.min.8a87b83c24b8.js

73 ms

ls.rias.min.6f9025e45d53.js

ls.rias.min.6f9025e45d53.js

74 ms

ls.object-fit.min.68dde06f9860.js

ls.object-fit.min.68dde06f9860.js

73 ms

lazysizes.min.96201abb6228.js

lazysizes.min.96201abb6228.js

74 ms

css

css

82 ms

vacasa-wire.1a0e1d908faf.css

vacasa-wire.1a0e1d908faf.css

75 ms

font-awesome.min.css

font-awesome.min.css

163 ms

oscar.7a0b842b7c0f.css

oscar.7a0b842b7c0f.css

74 ms

slick.min.css

slick.min.css

162 ms

slick-theme.min.css

slick-theme.min.css

162 ms

jquery-ui.min.c8cf7e102f44.css

jquery-ui.min.c8cf7e102f44.css

80 ms

datepicker.d55b9105ba5f.css

datepicker.d55b9105ba5f.css

80 ms

vacasa.5696ca8d2ae5.css

vacasa.5696ca8d2ae5.css

80 ms

place_page_v2.3a033ba6e8c8.css

place_page_v2.3a033ba6e8c8.css

80 ms

idp_auth.e403fc1bcefb.css

idp_auth.e403fc1bcefb.css

142 ms

idp_auth.abec5526ec4c.js

idp_auth.abec5526ec4c.js

158 ms

navbar_idp.52f70c906aef.js

navbar_idp.52f70c906aef.js

159 ms

otBannerSdk.js

otBannerSdk.js

33 ms

hero_search.0f83bd195158.js

hero_search.0f83bd195158.js

110 ms

accordion.09cff2975204.js

accordion.09cff2975204.js

83 ms

analytics.min.js

analytics.min.js

395 ms

gtm.js

gtm.js

137 ms

icon-nav-menu-white.e5b603f6fb0a.svg

icon-nav-menu-white.e5b603f6fb0a.svg

73 ms

Vacasa_horizontal_logo_white.d71744b795cf.svg

Vacasa_horizontal_logo_white.d71744b795cf.svg

59 ms

vacasa.b67b580d790e.js

vacasa.b67b580d790e.js

56 ms

140x32_Vacasa_Logo_Horizontal_Blue.898f70a0d30e.svg

140x32_Vacasa_Logo_Horizontal_Blue.898f70a0d30e.svg

57 ms

icon-sml-phone.1eecd26a74d0.svg

icon-sml-phone.1eecd26a74d0.svg

59 ms

ccpa-privacy-options.8051dee1dd72.svg

ccpa-privacy-options.8051dee1dd72.svg

57 ms

Instagram.69fc3b5c96cc.svg

Instagram.69fc3b5c96cc.svg

65 ms

Facebook-round.f552966a3751.svg

Facebook-round.f552966a3751.svg

66 ms

Twitter-X.2fd93c5b6721.svg

Twitter-X.2fd93c5b6721.svg

64 ms

LinkedIn.faba117dba43.svg

LinkedIn.faba117dba43.svg

64 ms

Youtube.0ab1501eb613.svg

Youtube.0ab1501eb613.svg

62 ms

a4978460394.html

a4978460394.html

84 ms

Calluna-Regular.c311a16ee279.otf

Calluna-Regular.c311a16ee279.otf

14 ms

ijwGs572Xtc6ZYQws9YVwllKVG8qX1oyOymuyJ6JxAct.ttf

ijwGs572Xtc6ZYQws9YVwllKVG8qX1oyOymuyJ6JxAct.ttf

62 ms

ijwGs572Xtc6ZYQws9YVwllKVG8qX1oyOymu8Z6JxAct.ttf

ijwGs572Xtc6ZYQws9YVwllKVG8qX1oyOymu8Z6JxAct.ttf

84 ms

ijwGs572Xtc6ZYQws9YVwllKVG8qX1oyOymulp6JxAct.ttf

ijwGs572Xtc6ZYQws9YVwllKVG8qX1oyOymulp6JxAct.ttf

86 ms

ijwGs572Xtc6ZYQws9YVwllKVG8qX1oyOymuJJmJxAct.ttf

ijwGs572Xtc6ZYQws9YVwllKVG8qX1oyOymuJJmJxAct.ttf

87 ms

ijwGs572Xtc6ZYQws9YVwllKVG8qX1oyOymuFpmJxAct.ttf

ijwGs572Xtc6ZYQws9YVwllKVG8qX1oyOymuFpmJxAct.ttf

86 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

25 ms

2941.jpg

2941.jpg

914 ms

Condo_abrVxqP.png

Condo_abrVxqP.png

20 ms

Studio_final_tjdOe2d.png

Studio_final_tjdOe2d.png

20 ms

ui-icons.17075f1bfe60.svg

ui-icons.17075f1bfe60.svg

3 ms

Accessibility Review

whistler-alpenglow.com accessibility score

87

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

button, link, and menuitem elements do not have accessible names.

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

whistler-alpenglow.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

whistler-alpenglow.com SEO score

85

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

Content Best Practices

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

Impact

Issue

High

Image elements do not have [alt] attributes

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

High

Tap targets are not sized appropriately

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 Whistler-alpenglow.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 Whistler-alpenglow.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

whistler-alpenglow.com

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