7.8 sec in total
681 ms
4 sec
3.1 sec
Visit imaginaris.ee now to see the best up-to-date Imaginaris content for Russia and also check out these interesting facts you probably never knew about imaginaris.ee
Our escape rooms are full of magic and adventure. Everyone can find an interesting exit game for themselves. We have horror, science, fantasy and escape rooms for the kids.
Visit imaginaris.eeWe analyzed Imaginaris.ee page load time and found that the first response time was 681 ms and then it took 7.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
imaginaris.ee performance score
name
value
score
weighting
Value2.1 s
81/100
10%
Value18.8 s
0/100
25%
Value13.9 s
1/100
10%
Value10,880 ms
0/100
30%
Value0.019
100/100
15%
Value30.6 s
0/100
10%
681 ms
194 ms
343 ms
220 ms
558 ms
Our browser made a total of 130 requests to load all elements on the main page. We found that 42% of them (55 requests) were addressed to the original Imaginaris.ee, 41% (53 requests) were made to Maps.googleapis.com and 3% (4 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (2.4 sec) belongs to the original domain Imaginaris.ee.
Page size can be reduced by 265.3 kB (6%)
4.6 MB
4.3 MB
In fact, the total size of Imaginaris.ee main page is 4.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. 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 4.2 MB which makes up the majority of the site volume.
Potential reduce by 239.7 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 239.7 kB or 81% of the original size.
Potential reduce by 22.2 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. Imaginaris images are well optimized though.
Potential reduce by 1.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. This website has mostly compressed JavaScripts.
Potential reduce by 2.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. Imaginaris.ee has all CSS files already compressed.
Number of requests can be reduced by 45 (38%)
118
73
The browser has sent 118 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Imaginaris. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 27 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
imaginaris.ee
681 ms
js
194 ms
intlTelInput.css
343 ms
swiper-bundle.min.css
220 ms
main.css
558 ms
fix.css
356 ms
email-decode.min.js
87 ms
jquery.min.js
247 ms
map.js
229 ms
js
288 ms
jquery.min.js
240 ms
yii.js
317 ms
yii.validation.js
328 ms
utils.js
773 ms
intlTelInput.min.js
648 ms
yii.activeForm.js
648 ms
script.js
645 ms
swiper-bundle.min.css
141 ms
analytics.js
133 ms
swiper-bundle.min.js
67 ms
collect
16 ms
collect
41 ms
ga-audiences
47 ms
fbevents.js
226 ms
noise.png
983 ms
en.svg
417 ms
ee.svg
419 ms
ru.svg
415 ms
line.svg
515 ms
main.css
779 ms
main-bg.jpg
789 ms
b5b86efdc07418bb49586b2925b7d053.jpg
782 ms
05deb1763b2b80e36f1d1e3760554023.jpg
787 ms
b3b2a75087298078b9aeef523e98f6e4.jpg
790 ms
98abb282ec0846c824d7855e397b65c6.jpg
1289 ms
e7dee7824781d5f323c4764247e23f62.jpg
1211 ms
line-frame-2.svg
1034 ms
affect.png
995 ms
partner-2.png
1291 ms
line-frame-1.svg
1206 ms
rob-1.png
1309 ms
party.png
1213 ms
birthday.png
1390 ms
corporate.png
1388 ms
gift.png
1632 ms
bg.png
1888 ms
about.jpg
1812 ms
about-line.png
1633 ms
tripadvisor.svg
1628 ms
arrow-left.svg
1630 ms
plus.svg
1754 ms
bg-1.png
1997 ms
loader.svg
1763 ms
map-find.svg
1764 ms
map-mask.png
2352 ms
map-mob.png
1979 ms
PAJJhLM6sSoWKfWCAAwDAjgbRAAB42mNgYGBkAIIbCZo5IPrmUn0hGA0AO8EFTQAA
13 ms
SFProDisplay-Regular.ttf
2226 ms
SFProDisplay-Bold.ttf
2282 ms
Gilroy-ExtraBold.otf
2114 ms
541006187167792
134 ms
gen_204
155 ms
SFProDisplay-Black.ttf
2306 ms
common.js
184 ms
util.js
243 ms
map.js
239 ms
marker.js
238 ms
SFProDisplay-Light.ttf
2323 ms
en.png
2051 ms
ee.png
2035 ms
ru.png
2053 ms
openhand_8_8.cur
143 ms
onion.js
106 ms
ViewportInfoService.GetViewportInfo
188 ms
playvr.png
1749 ms
flags.png
2043 ms
marker.svg
1856 ms
AuthenticationService.Authenticate
89 ms
vt
34 ms
vt
58 ms
vt
47 ms
vt
68 ms
vt
62 ms
vt
66 ms
vt
93 ms
vt
79 ms
vt
85 ms
vt
92 ms
vt
103 ms
vt
106 ms
vt
116 ms
vt
143 ms
vt
147 ms
vt
140 ms
vt
137 ms
vt
148 ms
vt
152 ms
vt
170 ms
vt
172 ms
vt
165 ms
vt
168 ms
vt
167 ms
vt
181 ms
vt
210 ms
vt
219 ms
vt
216 ms
vt
205 ms
vt
211 ms
vt
221 ms
vt
241 ms
vt
251 ms
vt
243 ms
vt
252 ms
vt
309 ms
vt
249 ms
QuotaService.RecordEvent
284 ms
vt
237 ms
vt
231 ms
vt
224 ms
vt
260 ms
vt
252 ms
controls.js
3 ms
transparent.png
74 ms
css
90 ms
css
97 ms
KFOmCnqEu92Fr1Mu4mxPKTU1Kg.ttf
17 ms
KFOlCnqEu92Fr1MmEU9fBBc9AMP6lQ.ttf
25 ms
KFOlCnqEu92Fr1MmSU5fBBc9AMP6lQ.ttf
44 ms
KFOlCnqEu92Fr1MmWUlfBBc9AMP6lQ.ttf
45 ms
transparent.png
12 ms
imaginaris.ee 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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
imaginaris.ee best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
imaginaris.ee 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
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 Imaginaris.ee 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 Imaginaris.ee 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.
imaginaris.ee
Open Graph data is detected on the main page of Imaginaris. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: