3.1 sec in total
216 ms
2.3 sec
674 ms
Visit escroom101.com now to see the best up-to-date Esc Room 101 content and also check out these interesting facts you probably never knew about escroom101.com
The ultimate Escape The Room experience in Phoenix now. Many themes but just one exit . Be ready with your team and get out before your times end.
Visit escroom101.comWe analyzed Escroom101.com page load time and found that the first response time was 216 ms and then it took 2.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
escroom101.com performance score
name
value
score
weighting
Value3.6 s
31/100
10%
Value5.2 s
23/100
25%
Value10.8 s
6/100
10%
Value2,480 ms
4/100
30%
Value0.474
18/100
15%
Value14.3 s
9/100
10%
216 ms
489 ms
43 ms
56 ms
228 ms
Our browser made a total of 82 requests to load all elements on the main page. We found that 48% of them (39 requests) were addressed to the original Escroom101.com, 16% (13 requests) were made to Fonts.gstatic.com and 12% (10 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (807 ms) belongs to the original domain Escroom101.com.
Page size can be reduced by 407.4 kB (13%)
3.2 MB
2.8 MB
In fact, the total size of Escroom101.com main page is 3.2 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. 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. Images take 2.4 MB which makes up the majority of the site volume.
Potential reduce by 48.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 48.1 kB or 81% of the original size.
Potential reduce by 31.7 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. Esc Room 101 images are well optimized though.
Potential reduce by 211.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 211.2 kB or 38% of the original size.
Potential reduce by 116.4 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. Escroom101.com needs all CSS files to be minified and compressed as it can save up to 116.4 kB or 72% of the original size.
Number of requests can be reduced by 33 (51%)
65
32
The browser has sent 65 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Esc Room 101. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 24 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
escroom101.com
216 ms
escroom101.com
489 ms
css
43 ms
css
56 ms
bootstrap.min.css
228 ms
font-awesome.min.css
271 ms
carousel.css
210 ms
animate.css
337 ms
style.css
273 ms
font-awesome.min.css
45 ms
simple-lightbox.min.css
213 ms
js
90 ms
api.js
58 ms
jquery.min.js
466 ms
bootstrap.min.js
465 ms
carousel.js
464 ms
animate.js
333 ms
custom.js
464 ms
simple-lightbox.min.js
465 ms
simple-lightbox.jquery.min.js
466 ms
fbevents.js
130 ms
Preloader.gif
191 ms
101logo.png
127 ms
prisoner-of-war.jpg
374 ms
mad-scientist.jpg
332 ms
a7a0ce32f2cea14395283d9c95619716.jpg
332 ms
WhatsApp-Image-2020-07-17-at-10_41_59-AM.jpeg
331 ms
38f8f673-a0b7-4f0d-a117-5743656834cf1.jpg
188 ms
d08aba02-3d8c-46b1-a5f8-b6776a8450e8.jpg
373 ms
videos-21.jpg
373 ms
videos-81.jpeg
516 ms
videos-91.jpg
515 ms
1_(1)1.jpg
515 ms
1_(2)1.jpg
648 ms
1_(3)1.jpg
648 ms
1_(4)1.jpg
637 ms
1_(5)1.jpg
647 ms
1_(6)1.jpg
648 ms
COLLAGE1.jpg
637 ms
COLLAGE4.jpg
781 ms
2.jpg
722 ms
3.jpg
807 ms
person.jpg
722 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
151 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
293 ms
KFOlCnqEu92Fr1MmSU5fBBc9.ttf
338 ms
KFOlCnqEu92Fr1MmWUlfBBc9.ttf
338 ms
KFOlCnqEu92Fr1MmYUtfBBc9.ttf
338 ms
fontawesome-webfont.woff
87 ms
fontawesome-webfont.woff
769 ms
recaptcha__en.js
339 ms
embed
316 ms
page.php
314 ms
tDbK2oqRg1oM3QBjjcaDkOr4nAfcGw.ttf
245 ms
tDbX2oqRg1oM3QBjjcaDkOr4lLz5CwOnTQ.ttf
242 ms
tDbI2oqRg1oM3QBjjcaDkOr9rAA.ttf
245 ms
tDbV2oqRg1oM3QBjjcaDkOJGiRD7OwQ.ttf
246 ms
KFOkCnqEu92Fr1Mu51xIIzc.ttf
247 ms
HADo6_noYei.css
151 ms
DzCBGzwb7Ip.js
160 ms
teTZ2tZqwkq.js
193 ms
BECqV_OB-Tv.js
194 ms
Mqs3unI9QGi.js
199 ms
p55HfXW__mM.js
202 ms
gVGw2Qd_OEw.js
202 ms
q4SZVAjzsaO.js
203 ms
js
251 ms
anchor
141 ms
277575063_384475027020910_3406096011517941328_n.png
70 ms
au-WAC02DB-.js
35 ms
277667718_384475023687577_4598654450484919755_n.png
46 ms
UXtr_j2Fwe-.png
30 ms
styles__ltr.css
9 ms
recaptcha__en.js
23 ms
IDLZ5bdCrEGdGR5FKKZfiIWvV7rMSlbAHUEzxUIOBQg.js
22 ms
webworker.js
75 ms
logo_48.png
15 ms
recaptcha__en.js
30 ms
404error
249 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
4 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
7 ms
KFOlCnqEu92Fr1MmYUtfBBc9.ttf
6 ms
escroom101.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
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
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
escroom101.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
escroom101.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
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 Escroom101.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 Escroom101.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.
escroom101.com
Open Graph description is not detected on the main page of Esc Room 101. 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: