14.7 sec in total
455 ms
13.6 sec
586 ms
Click here to check amazing IMind content for Russia. Otherwise, check out these important facts you probably never knew about imind.com
Secure HD quality videocall. Host 4-hour-long meetings for free. See who is entering the conference. Share multiple screens simultaneously. Record meetings.
Visit imind.comWe analyzed Imind.com page load time and found that the first response time was 455 ms and then it took 14.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
imind.com performance score
name
value
score
weighting
Value5.6 s
5/100
10%
Value6.9 s
6/100
25%
Value7.1 s
31/100
10%
Value700 ms
42/100
30%
Value0.13
81/100
15%
Value9.1 s
33/100
10%
455 ms
771 ms
593 ms
291 ms
736 ms
Our browser made a total of 50 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Imind.com, 66% (33 requests) were made to Us.imind.com and 10% (5 requests) were made to Maps.googleapis.com. The less responsive or slowest element that took the longest time to load (10.9 sec) relates to the external source Us.imind.com.
Page size can be reduced by 2.3 MB (73%)
3.2 MB
858.5 kB
In fact, the total size of Imind.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. 30% of websites need less resources to load. Javascripts take 2.5 MB which makes up the majority of the site volume.
Potential reduce by 19.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. This page needs HTML code to be minified as it can gain 5.0 kB, which is 20% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 19.5 kB or 77% of the original size.
Potential reduce by 26.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. IMind images are well optimized though.
Potential reduce by 1.9 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.9 MB or 78% of the original size.
Potential reduce by 356.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. Imind.com needs all CSS files to be minified and compressed as it can save up to 356.4 kB or 89% of the original size.
Number of requests can be reduced by 30 (68%)
44
14
The browser has sent 44 CSS, Javascripts, AJAX and image requests in order to completely render the main page of IMind. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 31 to 1 for JavaScripts and as a result speed up the page load time.
imind.com
455 ms
us.imind.com
771 ms
all.css
593 ms
menu.css
291 ms
jquery-1.10.1.min.js
736 ms
jquery-migrate-1.2.1.min.js
295 ms
js
69 ms
jquery-ui.js
2359 ms
jquery.main.js
493 ms
iMind.js
606 ms
iMind.CMS.js
395 ms
jquery.coda-slider-2.0.js
610 ms
jquery.cookie.js
610 ms
jquery.mvc.js
695 ms
jquery.go.js
795 ms
jquery.swfobject.1-1-1.js
794 ms
jquery.easing.1.3.js
806 ms
jquery.jqtransform.js
874 ms
jquery.limitmaxlength.js
1264 ms
iMind.CMS.Messages.js
1361 ms
iMind2XApi.js
1264 ms
Create2XUserStory.js
963 ms
Client2XLoginStory.js
1006 ms
menu.js
1156 ms
kernel.css
2063 ms
kernel.js
10881 ms
maincnt.js
1350 ms
conversion.js
42 ms
common.js
104 ms
util.js
190 ms
stats.js
160 ms
AuthenticationService.Authenticate
182 ms
dc.js
227 ms
img-visual-2.1.png
908 ms
181374b9d7bd960759fa2fe9cf27d5b9.png
316 ms
ad34289981c7ab7258de1bb916322bc8.png
199 ms
56498f4e8b9d4b1d6519bd7765b4afd5.png
198 ms
85eaf3ba0b6153feff6f13dffdcfe6fe.png
314 ms
gtm.js
219 ms
sprite.png
1459 ms
ga.js
173 ms
watch.js
116 ms
338 ms
pfsquaresanspro-medium-webfont.woff
1032 ms
pfsquaresansproregular-webfont.woff
153 ms
inpage_linkid.js
84 ms
480 ms
__utm.gif
155 ms
__utm.gif
84 ms
__utm.gif
112 ms
imind.com 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
button, link, and menuitem elements do not have accessible names.
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
[id] attributes on active, focusable elements are not unique
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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.
imind.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
General
Impact
Issue
Detected JavaScript libraries
imind.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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Imind.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Imind.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.
imind.com
Open Graph description is not detected on the main page of IMind. 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: