3.2 sec in total
196 ms
2.6 sec
440 ms
Welcome to room.run homepage info - get ready to check Room best content for Israel right away, or after learning these important things about room.run
פורטל חדרי בריחה שמביא את משחקי ההרפתקה אל המציאות. להזמנת חדר בריחה לקבוצות גדולות או קטנות צרו עמנו קשר עוד היום
Visit room.runWe analyzed Room.run page load time and found that the first response time was 196 ms and then it took 3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
room.run performance score
name
value
score
weighting
Value5.9 s
4/100
10%
Value7.5 s
4/100
25%
Value15.7 s
0/100
10%
Value880 ms
32/100
30%
Value0.046
99/100
15%
Value19.1 s
3/100
10%
196 ms
225 ms
726 ms
176 ms
248 ms
Our browser made a total of 48 requests to load all elements on the main page. We found that 79% of them (38 requests) were addressed to the original Room.run, 10% (5 requests) were made to Cdnjs.cloudflare.com and 4% (2 requests) were made to Cdn.rawgit.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Room.run.
Page size can be reduced by 1.9 MB (54%)
3.6 MB
1.7 MB
In fact, the total size of Room.run main page is 3.6 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. 60% of websites need less resources to load. Javascripts take 2.2 MB which makes up the majority of the site volume.
Potential reduce by 167.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 167.5 kB or 86% of the original size.
Potential reduce by 63.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. Room images are well optimized though.
Potential reduce by 1.7 MB
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 1.7 MB or 76% of the original size.
Potential reduce by 28.3 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. Room.run needs all CSS files to be minified and compressed as it can save up to 28.3 kB or 77% of the original size.
Number of requests can be reduced by 16 (37%)
43
27
The browser has sent 43 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Room. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 4 to 1 for JavaScripts and from 14 to 1 for CSS and as a result speed up the page load time.
room.run
196 ms
www.room.run
225 ms
home
726 ms
main-8741e63bca7d9066b9eb.css
176 ms
theme.min.css
248 ms
app.css
174 ms
font-awesome.min.css
32 ms
react-star-rating.css
168 ms
react-select.css
175 ms
shepherd-theme-arrows.css
181 ms
react-datepicker.css
256 ms
rc-slider.css
257 ms
inputgeosuggest.css
258 ms
index.css
58 ms
hint.min.css
42 ms
slick.css
41 ms
js
86 ms
Chart.min.js
43 ms
main-8741e63bca7d9066b9eb.js
731 ms
c91c2c5307058f9ab5ff69811b159be5.png
225 ms
KgbStillWatching.jpg
230 ms
TrappedInTime.jpg
156 ms
indiana-jones.jpeg
297 ms
OperationSaffron.jpg
214 ms
BankRobbery.jpg
221 ms
Saw.jpg
293 ms
prison-break.jpeg
446 ms
the-ring.jpeg
381 ms
Anthrax.jpg
311 ms
the-secret-of-the-gallery.jpeg
1119 ms
IranianThreat.jpg
369 ms
RealDetective.jpg
394 ms
TheDarkOrder.jpg
449 ms
boardwalk-empire.jpeg
463 ms
da-vinci-code.jpeg
1122 ms
paranormal-activity.png
1118 ms
fifth-element.jpeg
1123 ms
the-exorcist.jpeg
1119 ms
dexter.jpeg
1120 ms
PharoahsCurse.jpg
1122 ms
TheOtherSide.jpg
1123 ms
mystery-of-maya.jpeg
1123 ms
lasvegas.jpeg
1123 ms
museum-at-night.jpeg
1124 ms
fontawesome-webfont.woff
34 ms
slick.woff
4 ms
analytics.js
156 ms
bootstrap-rtl.min.css
120 ms
room.run accessibility score
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
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
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
Links do not have a discernible name
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
List items (<li>) are not contained within <ul> or <ol> parent elements.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Some elements have a [tabindex] value greater than 0
room.run 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
Page has valid source maps
room.run 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
Tap targets are not sized appropriately
IW
HE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Room.run can be misinterpreted by Google and other search engines. Our service has detected that Hebrew is used on the page, and it does not match the claimed language. Our system also found out that Room.run 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.
room.run
Open Graph data is detected on the main page of Room. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: