Tools & Wizards About Us
trapped.ca screenshot

Report Summary

  • 47

    Performance

    Renders faster than
    65% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 54% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

trapped.ca

Trapped | Premium Escape Rooms | Real Life Escape Game

Page Load Speed

1.1 sec in total

First Response

25 ms

Resources Loaded

690 ms

Page Rendered

352 ms

trapped.ca screenshot

About Website

Click here to check amazing Trapped content for Canada. Otherwise, check out these important facts you probably never knew about trapped.ca

Trapped, one of the largest real-life room escape games world wide, offering premium escape rooms in multiple locations across the globe.

Visit trapped.ca

Key Findings

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

Performance Metrics

trapped.ca performance score

47

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.8 s

56/100

10%

LCP (Largest Contentful Paint)

Value4.3 s

41/100

25%

SI (Speed Index)

Value7.6 s

25/100

10%

TBT (Total Blocking Time)

Value410 ms

67/100

30%

CLS (Cumulative Layout Shift)

Value0.467

19/100

15%

TTI (Time to Interactive)

Value6.8 s

55/100

10%

Network Requests Diagram

trapped.ca

25 ms

trapped.com

82 ms

css

43 ms

css

68 ms

main.css

46 ms

Our browser made a total of 30 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Trapped.ca, 63% (19 requests) were made to Trapped.com and 13% (4 requests) were made to Player.vimeo.com. The less responsive or slowest element that took the longest time to load (278 ms) relates to the external source Trapped.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 20.1 kB (8%)

Content Size

254.9 kB

After Optimization

234.8 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Trapped.ca main page is 254.9 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. 40% of websites need less resources to load. Images take 137.3 kB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 13.4 kB

  • Original 18.0 kB
  • After minification 16.1 kB
  • After compression 4.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. 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 13.4 kB or 74% of the original size.

Image Optimization

-5%

Potential reduce by 6.4 kB

  • Original 137.3 kB
  • After minification 130.9 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. Trapped images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 269 B

  • Original 99.6 kB
  • After minification 99.6 kB
  • After compression 99.4 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.

Requests Breakdown

Number of requests can be reduced by 10 (45%)

Requests Now

22

After Optimization

12

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

trapped.ca

trapped.ca

25 ms

trapped.com

trapped.com

82 ms

css

css

43 ms

css

css

68 ms

main.css

main.css

46 ms

style.css

style.css

64 ms

modernizr.js

modernizr.js

66 ms

vendor.js

vendor.js

129 ms

main.js

main.js

61 ms

slick.js

slick.js

61 ms

index.js

index.js

260 ms

js

js

65 ms

199715272

199715272

161 ms

logo-horizontal.png

logo-horizontal.png

190 ms

full-logo.png

full-logo.png

190 ms

scroll.png

scroll.png

188 ms

lineSeparatorWhite.png

lineSeparatorWhite.png

188 ms

gradient.png

gradient.png

188 ms

escape_maze.jpg

escape_maze.jpg

189 ms

separatorBlack.png

separatorBlack.png

233 ms

lineSeparatorBlack.png

lineSeparatorBlack.png

233 ms

font

font

64 ms

font

font

73 ms

icomoon.woff

icomoon.woff

87 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

278 ms

199715272

199715272

234 ms

40054052

40054052

1 ms

froogaloop2.min.js

froogaloop2.min.js

48 ms

40054052

40054052

208 ms

api.js

api.js

15 ms

Accessibility Review

trapped.ca accessibility score

83

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 progressbar 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

<frame> or <iframe> elements do not have a title

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

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

trapped.ca best practices score

67

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

trapped.ca 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 Trapped.ca 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 Trapped.ca 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

trapped.ca

Open Graph description is not detected on the main page of Trapped. 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: