2.2 sec in total
198 ms
1.4 sec
539 ms
Visit indoora.com now to see the best up-to-date Indoora content and also check out these interesting facts you probably never knew about indoora.com
Visit indoora.comWe analyzed Indoora.com page load time and found that the first response time was 198 ms and then it took 2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.
indoora.com performance score
name
value
score
weighting
Value5.1 s
9/100
10%
Value8.9 s
1/100
25%
Value12.5 s
3/100
10%
Value400 ms
68/100
30%
Value0.279
43/100
15%
Value8.5 s
38/100
10%
198 ms
8 ms
29 ms
37 ms
77 ms
Our browser made a total of 107 requests to load all elements on the main page. We found that 47% of them (50 requests) were addressed to the original Indoora.com, 30% (32 requests) were made to Maps.google.com and 9% (10 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (441 ms) belongs to the original domain Indoora.com.
Page size can be reduced by 990.2 kB (14%)
7.1 MB
6.2 MB
In fact, the total size of Indoora.com main page is 7.1 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. 85% 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 6.1 MB which makes up the majority of the site volume.
Potential reduce by 63.0 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 63.0 kB or 85% of the original size.
Potential reduce by 223.6 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. Indoora images are well optimized though.
Potential reduce by 531.0 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 531.0 kB or 69% of the original size.
Potential reduce by 172.6 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. Indoora.com needs all CSS files to be minified and compressed as it can save up to 172.6 kB or 85% of the original size.
Number of requests can be reduced by 37 (39%)
95
58
The browser has sent 95 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Indoora. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 28 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
www.indoora.com
198 ms
wp-emoji-release.min.js
8 ms
css
29 ms
css
37 ms
motioncss.css
77 ms
motioncss-responsive.css
38 ms
font-awesome.css
32 ms
magnific-popup.css
35 ms
fotorama.css
82 ms
style.css
18 ms
responsive.css
28 ms
us_corsa_custom_styles.css
58 ms
jquery.js
48 ms
jquery-migrate.min.js
47 ms
supersized.3.2.7.js
40 ms
jquery.easing.min.js
60 ms
jquery.magnific-popup.js
52 ms
supersized.shutter.js
52 ms
waypoints.min.js
61 ms
imagesloaded.js
61 ms
plugins.js
79 ms
us.widgets.js
70 ms
comment-reply.min.js
64 ms
jquery.parallax.js
68 ms
slick.min.js
70 ms
js
31 ms
jquery.gmap.min.js
78 ms
common.js
41 ms
map.js
41 ms
util.js
41 ms
geocoder.js
40 ms
marker.js
41 ms
logoIndoora1.png
56 ms
websiteMain.jpg
58 ms
parallax.jpg
57 ms
mall2.png
12 ms
retail.png
57 ms
airport.png
59 ms
hotel2.png
60 ms
convention2.png
62 ms
hospital.png
63 ms
museum.png
64 ms
university2.png
60 ms
stadium.png
61 ms
tabletop.jpg
149 ms
fusion48.png
63 ms
fingerprint48.png
62 ms
edkunt.png
143 ms
gerinc.png
441 ms
tnaskali.png
145 ms
oktar.png
140 ms
office.jpg
140 ms
clogo_teknopark-300x200.png
144 ms
LKf8nhXsWg5ybwEGXk8UBQ.woff
50 ms
0XxGQsSc1g4rdRdjJKZrNBsxEYwM7FgeyaSgU71cLG0.woff
52 ms
x-7NZTw0n-ypOAaIE8uSrvesZW2xOQ-xsNqO47m55DA.woff
53 ms
xIAtSaglM8LZOYdGmG1JqQ.woff
53 ms
fontawesome-webfont.woff
205 ms
PIPMHY90P7jtyjpXuZ2cLD8E0i7KZn-EPnyo3HZu7kw.woff
53 ms
lILlYDvubYemzYzN7GbLkHhCUOGz7vYGh680lGh-uXM.woff
53 ms
onion.js
32 ms
openhand_8_8.cur
98 ms
ViewportInfoService.GetViewportInfo
133 ms
stats.js
67 ms
controls.js
41 ms
infowindow.js
61 ms
transparent.png
28 ms
css
90 ms
clogo_sabanci-300x200.png
90 ms
marker.png
51 ms
google4.png
51 ms
mapcnt6.png
33 ms
sv5.png
32 ms
clogo_bilkent-300x200.png
44 ms
tmapctrl.png
47 ms
cb_scout5.png
47 ms
tmapctrl4.png
44 ms
imgs8.png
45 ms
2UX7WLTfW3W8TclTUvlFyQ.woff
38 ms
RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff
32 ms
Hgo13k-tfSpn0qi1SFdUfT8E0i7KZn-EPnyo3HZu7kw.woff
39 ms
d-6IYplOFocCacKzxwXSOD8E0i7KZn-EPnyo3HZu7kw.woff
38 ms
vt
22 ms
vt
54 ms
vt
42 ms
vt
43 ms
vt
52 ms
vt
44 ms
vt
47 ms
vt
60 ms
vt
45 ms
vt
51 ms
vt
47 ms
vt
51 ms
vt
49 ms
vt
58 ms
vt
51 ms
vt
86 ms
vt
51 ms
vt
57 ms
vt
58 ms
vt
62 ms
vt
59 ms
vt
59 ms
clogo_galatasaray2-300x200.png
29 ms
clogo_venesco-300x200.png
19 ms
AuthenticationService.Authenticate
127 ms
indoora.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.
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
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.
indoora.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
General
Impact
Issue
Detected JavaScript libraries
indoora.com SEO score
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 Indoora.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 Indoora.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.
indoora.com
Open Graph description is not detected on the main page of Indoora. 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: