Tools & Wizards About Us
escapewhistler.com screenshot

Report Summary

  • 33

    Performance

    Renders faster than
    53% of other websites

  • 87

    Accessibility

    Visual factors better than
    that of 67% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 100

    SEO

    Google-friendlier than
    95% of websites

escapewhistler.com

Escape! Whistler | Whistler's Original Escape Rooms

Page Load Speed

1.5 sec in total

First Response

52 ms

Resources Loaded

624 ms

Page Rendered

794 ms

escapewhistler.com screenshot

About Website

Visit escapewhistler.com now to see the best up-to-date Escape Whistler content and also check out these interesting facts you probably never knew about escapewhistler.com

Whistler's Original Escape Room facility and best indoor activity. A real-life gaming experience fun for everyone. Book your adventure today!

Visit escapewhistler.com

Key Findings

We analyzed Escapewhistler.com page load time and found that the first response time was 52 ms and then it took 1.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.

Performance Metrics

escapewhistler.com performance score

33

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.5 s

35/100

10%

LCP (Largest Contentful Paint)

Value6.8 s

7/100

25%

SI (Speed Index)

Value4.9 s

65/100

10%

TBT (Total Blocking Time)

Value1,380 ms

16/100

30%

CLS (Cumulative Layout Shift)

Value0.019

100/100

15%

TTI (Time to Interactive)

Value11.4 s

19/100

10%

Network Requests Diagram

escapewhistler.com

52 ms

escapewhistler.com

49 ms

css

108 ms

autoptimize_784ed517c0f480a952761b017a37e703.css

27 ms

autoptimize_single_dbfe0642d25ecc18a8c281e6e6b9000b.css

94 ms

Our browser made a total of 42 requests to load all elements on the main page. We found that 50% of them (21 requests) were addressed to the original Escapewhistler.com, 24% (10 requests) were made to Fonts.gstatic.com and 7% (3 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (218 ms) relates to the external source Static.hotjar.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 312.3 kB (41%)

Content Size

755.3 kB

After Optimization

442.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Escapewhistler.com main page is 755.3 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 80% 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 318.1 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 133.9 kB

  • Original 162.5 kB
  • After minification 162.4 kB
  • After compression 28.5 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 133.9 kB or 82% of the original size.

Image Optimization

-8%

Potential reduce by 5.0 kB

  • Original 61.1 kB
  • After minification 56.1 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. Escape Whistler images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 63 B

  • Original 318.1 kB
  • After minification 318.1 kB
  • After compression 318.1 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

-81%

Potential reduce by 173.3 kB

  • Original 213.5 kB
  • After minification 40.4 kB
  • After compression 40.2 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. Escapewhistler.com needs all CSS files to be minified and compressed as it can save up to 173.3 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 18 (75%)

Requests Now

24

After Optimization

6

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

escapewhistler.com

escapewhistler.com

52 ms

escapewhistler.com

escapewhistler.com

49 ms

css

css

108 ms

autoptimize_784ed517c0f480a952761b017a37e703.css

autoptimize_784ed517c0f480a952761b017a37e703.css

27 ms

autoptimize_single_dbfe0642d25ecc18a8c281e6e6b9000b.css

autoptimize_single_dbfe0642d25ecc18a8c281e6e6b9000b.css

94 ms

autoptimize_single_c6f05239f8d6eb10da2c23dd4167f446.css

autoptimize_single_c6f05239f8d6eb10da2c23dd4167f446.css

104 ms

autoptimize_single_70923910c1152ac0518583e3f6b5c1c9.css

autoptimize_single_70923910c1152ac0518583e3f6b5c1c9.css

104 ms

autoptimize_single_0b6ce8431715a8171170ce2156305636.css

autoptimize_single_0b6ce8431715a8171170ce2156305636.css

101 ms

autoptimize_single_1b5c04410d89c74460364b3bcd3037b9.css

autoptimize_single_1b5c04410d89c74460364b3bcd3037b9.css

107 ms

autoptimize_single_4d94da6d29a689e36eed5d0a936052c6.css

autoptimize_single_4d94da6d29a689e36eed5d0a936052c6.css

100 ms

autoptimize_single_f1082046a6324a88f1b113a9ef859269.css

autoptimize_single_f1082046a6324a88f1b113a9ef859269.css

110 ms

autoptimize_single_55ceaa980548c2b3a97ebd1d90b770a2.css

autoptimize_single_55ceaa980548c2b3a97ebd1d90b770a2.css

104 ms

js

js

121 ms

jquery.min.js

jquery.min.js

118 ms

lazysizes.min.js

lazysizes.min.js

100 ms

autoptimize_eaa9e5716f0f78d38d029d2afc276be6.js

autoptimize_eaa9e5716f0f78d38d029d2afc276be6.js

114 ms

js

js

142 ms

hotjar-1983673.js

hotjar-1983673.js

218 ms

EW-long-trans-500.png

EW-long-trans-500.png

129 ms

MAAAAASUVORK5CYII=

MAAAAASUVORK5CYII=

112 ms

7y2XIhEdetsAAAAASUVORK5CYII=

7y2XIhEdetsAAAAASUVORK5CYII=

111 ms

checkout.js

checkout.js

199 ms

background-white-maze.png

background-white-maze.png

123 ms

S6u9w4BMUTPHh50XSwiPHA.ttf

S6u9w4BMUTPHh50XSwiPHA.ttf

52 ms

S6u9w4BMUTPHh6UVSwiPHA.ttf

S6u9w4BMUTPHh6UVSwiPHA.ttf

79 ms

S6uyw4BMUTPHjx4wWw.ttf

S6uyw4BMUTPHjx4wWw.ttf

91 ms

S6u9w4BMUTPHh7USSwiPHA.ttf

S6u9w4BMUTPHh7USSwiPHA.ttf

95 ms

S6u8w4BMUTPHh30AXC-v.ttf

S6u8w4BMUTPHh30AXC-v.ttf

93 ms

fa-solid-900.woff

fa-solid-900.woff

210 ms

fa-regular-400.woff

fa-regular-400.woff

197 ms

fa-brands-400.woff

fa-brands-400.woff

211 ms

S6u8w4BMUTPHjxsAXC-v.ttf

S6u8w4BMUTPHjxsAXC-v.ttf

93 ms

S6u_w4BMUTPHjxsI9w2_Gwfo.ttf

S6u_w4BMUTPHjxsI9w2_Gwfo.ttf

92 ms

S6u-w4BMUTPHjxsIPx-oPCc.ttf

S6u-w4BMUTPHjxsIPx-oPCc.ttf

92 ms

S6u_w4BMUTPHjxsI5wq_Gwfo.ttf

S6u_w4BMUTPHjxsI5wq_Gwfo.ttf

93 ms

S6u_w4BMUTPHjxsI3wi_Gwfo.ttf

S6u_w4BMUTPHjxsI3wi_Gwfo.ttf

194 ms

jupiterx.woff

jupiterx.woff

195 ms

EW-lock-trans-500.png

EW-lock-trans-500.png

37 ms

js

js

64 ms

analytics.js

analytics.js

56 ms

modules.2472296d2d26f0040059.js

modules.2472296d2d26f0040059.js

89 ms

collect

collect

102 ms

Accessibility Review

escapewhistler.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

[aria-hidden="true"] elements contain focusable descendents

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

Buttons do not have an accessible name

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

escapewhistler.com best practices score

75

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

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

escapewhistler.com SEO score

100

Search Engine Optimization Advices

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 Escapewhistler.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 Escapewhistler.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

escapewhistler.com

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