1.3 sec in total
82 ms
868 ms
393 ms
Welcome to imr.org homepage info - get ready to check IMR best content right away, or after learning these important things about imr.org
Visit imr.orgWe analyzed Imr.org page load time and found that the first response time was 82 ms and then it took 1.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.
imr.org performance score
name
value
score
weighting
Value3.0 s
50/100
10%
Value6.0 s
13/100
25%
Value4.8 s
66/100
10%
Value430 ms
65/100
30%
Value0.011
100/100
15%
Value7.1 s
51/100
10%
82 ms
168 ms
59 ms
70 ms
78 ms
Our browser made a total of 52 requests to load all elements on the main page. We found that 48% of them (25 requests) were addressed to the original Imr.org, 42% (22 requests) were made to Fonts.gstatic.com and 8% (4 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (394 ms) relates to the external source Jobs.ourcareerpages.com.
Page size can be reduced by 306.7 kB (41%)
744.5 kB
437.8 kB
In fact, the total size of Imr.org main page is 744.5 kB. 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. HTML takes 347.0 kB which makes up the majority of the site volume.
Potential reduce by 304.3 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 304.3 kB or 88% of the original size.
Potential reduce by 1.5 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. IMR images are well optimized though.
Potential reduce by 765 B
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 68 B
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. Imr.org has all CSS files already compressed.
Number of requests can be reduced by 21 (78%)
27
6
The browser has sent 27 CSS, Javascripts, AJAX and image requests in order to completely render the main page of IMR. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
imr.org
82 ms
imr.org
168 ms
8cee8fce214c3069d04f14c29a855e96.css
59 ms
2f41a11c37a2b1a689f5e106035ef379.css
70 ms
2f35c23d0dbe20f87463723acd4a5571.css
78 ms
b5ad16da78ec1b6559b467e3ddf4b383.js
140 ms
jquery.min.js
109 ms
b95bcb81cfb44acd5f318ccad439f5dd.js
82 ms
8846403821e72fc0855a8a605eaa625e.js
87 ms
d3d46e1d3eeb05951462ec931c2235f8.js
96 ms
cff6ef3535a2a773d2f930cc9e059893.js
107 ms
10d17eac0aa51a7be269e6357b0d6f96.css
108 ms
cc4cc2bce663f6b898e53c24d8baeabd.js
197 ms
9fa8be8b5ff3a87d28b2943f5a8a6e5f.js
122 ms
cc875c68ea77aa66a50194109f718e6c.js
134 ms
652dc95ec031963876b378b154178321.js
133 ms
fcde49da437dfbc3c0891dfe8f2a4924.js
198 ms
css2
25 ms
css2
38 ms
css2
40 ms
css2
41 ms
style.css
74 ms
ccp_jobs.aspx
394 ms
et-divi-dynamic-7-late.css
97 ms
imr-bg.png
105 ms
img57481fd78868f.jpg
97 ms
imr_veteran_003.jpg
268 ms
TK3_WkUHHAIjg75cFRf3bXL8LICs1_FvsUhiYw.woff
266 ms
TK3_WkUHHAIjg75cFRf3bXL8LICs1_FvsUhiYA.ttf
272 ms
TK3_WkUHHAIjg75cFRf3bXL8LICs18NvsUhiYw.woff
274 ms
TK3_WkUHHAIjg75cFRf3bXL8LICs18NvsUhiYA.ttf
275 ms
TK3_WkUHHAIjg75cFRf3bXL8LICs169vsUhiYw.woff
272 ms
TK3_WkUHHAIjg75cFRf3bXL8LICs169vsUhiYA.ttf
273 ms
TK3_WkUHHAIjg75cFRf3bXL8LICs13FvsUhiYw.woff
272 ms
TK3_WkUHHAIjg75cFRf3bXL8LICs13FvsUhiYA.ttf
299 ms
TK3_WkUHHAIjg75cFRf3bXL8LICs1y9osUhiYw.woff
298 ms
TK3_WkUHHAIjg75cFRf3bXL8LICs1y9osUhiYA.ttf
299 ms
TK3_WkUHHAIjg75cFRf3bXL8LICs1xZosUhiYw.woff
298 ms
TK3_WkUHHAIjg75cFRf3bXL8LICs1xZosUhiYA.ttf
299 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVQ.woff
211 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVc.ttf
212 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVQ.woff
213 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVc.ttf
213 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVQ.woff
212 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVc.ttf
213 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVQ.woff
214 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVc.ttf
214 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4uaVQ.woff
214 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4uaVc.ttf
214 ms
modules.woff
215 ms
logo.png
104 ms
4fff6a013a544ffbd26d8845589d59cb.css
33 ms
imr.org 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.
imr.org best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
imr.org 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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Imr.org 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 Imr.org 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.
imr.org
Open Graph description is not detected on the main page of IMR. 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: