8.3 sec in total
37 ms
2.1 sec
6.2 sec
Click here to check amazing Whistler Luxury Portfolio content. Otherwise, check out these important facts you probably never knew about whistlerluxuryportfolio.com
Whistler Luxury Portfolio showcases luxury properties of The Whistler Real Estate Company Ltd., partnered with Luxury Portfolio Fine Property Collection™.
Visit whistlerluxuryportfolio.comWe analyzed Whistlerluxuryportfolio.com page load time and found that the first response time was 37 ms and then it took 8.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
whistlerluxuryportfolio.com performance score
name
value
score
weighting
Value4.0 s
24/100
10%
Value4.9 s
28/100
25%
Value5.6 s
53/100
10%
Value3,690 ms
1/100
30%
Value0.11
87/100
15%
Value17.0 s
4/100
10%
37 ms
230 ms
76 ms
40 ms
197 ms
Our browser made a total of 101 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Whistlerluxuryportfolio.com, 36% (36 requests) were made to Sfo3.digitaloceanspaces.com and 33% (33 requests) were made to Whistlerrealestate.ca. The less responsive or slowest element that took the longest time to load (1.5 sec) relates to the external source Sfo3.digitaloceanspaces.com.
Page size can be reduced by 697.9 kB (3%)
24.1 MB
23.4 MB
In fact, the total size of Whistlerluxuryportfolio.com main page is 24.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. Only a small number of websites need less resources to load. Images take 23.7 MB which makes up the majority of the site volume.
Potential reduce by 158.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 158.8 kB or 82% of the original size.
Potential reduce by 537.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. Whistler Luxury Portfolio images are well optimized though.
Potential reduce by 1.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. This website has mostly compressed JavaScripts.
Potential reduce by 5 B
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. Whistlerluxuryportfolio.com has all CSS files already compressed.
Number of requests can be reduced by 44 (49%)
90
46
The browser has sent 90 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Whistler Luxury Portfolio. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 32 to 1 for JavaScripts and from 14 to 1 for CSS and as a result speed up the page load time.
whistlerluxuryportfolio.com
37 ms
230 ms
js
76 ms
extendify-utilities.css
40 ms
bootstrap-select.min.css
197 ms
all.min.css
224 ms
icons.css
193 ms
jquery-ui.min.css
189 ms
radio-checkbox-min.css
194 ms
bootstrap-datepicker.min.css
66 ms
main.css
115 ms
style.css
194 ms
tdg8mjf.css
109 ms
global.css
201 ms
frontend-gtag.min.js
200 ms
jquery.min.js
199 ms
jquery-migrate.min.js
198 ms
js
106 ms
gtm4wp-form-move-tracker.js
219 ms
bootstrap.bundle.min.js
376 ms
bootstrap-select.min.js
383 ms
modernizr.custom.js
383 ms
slideout.min.js
382 ms
lightbox.min.js
375 ms
theia-sticky-sidebar.min.js
375 ms
slick.min.js
605 ms
core.min.js
605 ms
mouse.min.js
603 ms
slider.min.js
604 ms
custom.js
602 ms
api.js
52 ms
image-map-resizer.min.js
602 ms
index.js
620 ms
lc-exit-intent.js
33 ms
lc-ga-tags.js
37 ms
lc-device.js
38 ms
lc-input-error.js
44 ms
css
46 ms
p.css
116 ms
js
284 ms
gtm.js
283 ms
logo-black.svg
675 ms
Whistler-South.png
796 ms
Whistler-Central.png
795 ms
Whistler-Village-Benchlands-300x199.png
739 ms
Whistler-North.png
739 ms
Pemberton2-300x233.png
738 ms
Whistler-300x233.png
794 ms
badge-about-us.png
795 ms
badge-our-agents.png
806 ms
logo-lp.png
806 ms
2947-High-Point-Drive-1.jpg
1050 ms
3824-Sunridge-Drive-1.jpg
1060 ms
8891-Pemberton-Meadows-Road-1.jpg
1087 ms
6805-Crabapple-Drive-1.jpg
1133 ms
1600-Southlands-Lane-1.jpg
1209 ms
4673-Blackcomb-Way-1.jpg
1274 ms
3801-Sunridge-Place-1.jpg
1127 ms
3113-Hillcrest-Lane-1.jpg
1140 ms
7452-Treetop-Lane-1.jpg
1288 ms
37-4617-Blackcomb-Way-1.jpg
1206 ms
3565-Falcon-Crescent-1.jpg
1211 ms
6677-Crabapple-Drive-1.jpg
1293 ms
3220-Peak-Drive-1.jpg
1356 ms
3278-Archibald-Way-1.jpg
1354 ms
7448-Treetop-Lane-1.jpg
1357 ms
6-4750-Glacier-Drive-1.jpg
1352 ms
7631-Pemberton-Meadows-Road-1.jpg
1368 ms
6187-Eagle-Drive-1.jpg
1372 ms
25-7124-Nancy-Greene-Drive-1.jpg
1433 ms
5459-Stonebridge-Place-1.jpg
1441 ms
1625-Southlands-Lane-1.jpg
1437 ms
logo-leading.png
1428 ms
logo-lpi.png
1449 ms
logo-leading_2x-min.png
1447 ms
logo-luxuryportfolio_2x-min.png
1501 ms
logo-mls-reciprocity_2x-min.png
1505 ms
logo-black-large-1.svg
337 ms
KFOlCnqEu92Fr1MmWUlfBBc9.ttf
249 ms
KFOlCnqEu92Fr1MmYUtfBBc9.ttf
302 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
327 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
314 ms
KFOlCnqEu92Fr1MmSU5fBBc9.ttf
327 ms
KFOkCnqEu92Fr1MmgVxIIzc.ttf
327 ms
tracking.js
115 ms
recaptcha__en.js
103 ms
prev.png
130 ms
next.png
40 ms
loading.gif
112 ms
close.png
42 ms
anchor
49 ms
anchor
45 ms
styles__ltr.css
4 ms
recaptcha__en.js
14 ms
oN6JOQxO2CZdhDuvURgc1WDqFpXrbMZ6mY5cTBya2tA.js
68 ms
webworker.js
73 ms
logo_48.png
36 ms
recaptcha__en.js
61 ms
KFOmCnqEu92Fr1Mu4mxM.woff
4 ms
KFOlCnqEu92Fr1MmEU9fBBc-.woff
7 ms
KFOlCnqEu92Fr1MmYUtfBBc-.woff
6 ms
whistlerluxuryportfolio.com accessibility score
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
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
whistlerluxuryportfolio.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
whistlerluxuryportfolio.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
robots.txt is not valid
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Whistlerluxuryportfolio.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 Whistlerluxuryportfolio.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.
whistlerluxuryportfolio.com
Open Graph description is not detected on the main page of Whistler Luxury Portfolio. 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: