1 sec in total
80 ms
730 ms
197 ms
Welcome to ir.omnicare.com homepage info - get ready to check IR Omnicare best content for United States right away, or after learning these important things about ir.omnicare.com
Benefit from an all-in-one workflow solution that identifies shareholders, gauges sentiment, optimizes investor engagement & more with Nasdaq IR Intelligence.
Visit ir.omnicare.comWe analyzed Ir.omnicare.com page load time and found that the first response time was 80 ms and then it took 927 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.
ir.omnicare.com performance score
name
value
score
weighting
Value5.2 s
8/100
10%
Value31.5 s
0/100
25%
Value20.6 s
0/100
10%
Value4,560 ms
0/100
30%
Value0.031
100/100
15%
Value32.2 s
0/100
10%
80 ms
201 ms
12 ms
194 ms
74 ms
Our browser made a total of 39 requests to load all elements on the main page. We found that 15% of them (6 requests) were addressed to the original Ir.omnicare.com, 38% (15 requests) were made to Omnicare.com and 23% (9 requests) were made to Media.corporate-ir.net. The less responsive or slowest element that took the longest time to load (201 ms) belongs to the original domain Ir.omnicare.com.
Page size can be reduced by 560.6 kB (62%)
901.1 kB
340.6 kB
In fact, the total size of Ir.omnicare.com main page is 901.1 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. 35% of websites need less resources to load. Javascripts take 484.9 kB which makes up the majority of the site volume.
Potential reduce by 42.9 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 42.9 kB or 71% of the original size.
Potential reduce by 2.0 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. Obviously, IR Omnicare needs image optimization as it can save up to 2.0 kB or 26% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 314.1 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 314.1 kB or 65% of the original size.
Potential reduce by 201.5 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. Ir.omnicare.com needs all CSS files to be minified and compressed as it can save up to 201.5 kB or 58% of the original size.
Number of requests can be reduced by 16 (48%)
33
17
The browser has sent 33 CSS, Javascripts, AJAX and image requests in order to completely render the main page of IR Omnicare. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 5 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
ir.omnicare.com
80 ms
phoenix.zhtml
201 ms
HttpCombiner.ashx
12 ms
OmniStyles.css
194 ms
icons.css
74 ms
ccbnIR.css
72 ms
ccbnFonts.css
130 ms
addthis_widget.js
16 ms
HttpCombiner.ashx
20 ms
s_code.js
18 ms
CoreClientCode.js
64 ms
toolkit_print_t.gif
60 ms
300lo.json
43 ms
omniLogo.gif
54 ms
headerWave.gif
69 ms
dottedBlue.gif
70 ms
investorToolkitTop.png
70 ms
iconFolder.png
72 ms
investorToolkitBot.png
71 ms
subGradientBlue.gif
70 ms
pill_wheel_bluesub.gif
71 ms
curveTop.gif
73 ms
curveBot.gif
73 ms
footerGradient.gif
73 ms
bulletBlkExp.png
73 ms
toolkit_emailPg_t.gif
20 ms
email_trans.gif
70 ms
toolkit_rss_t.gif
21 ms
iconRSS.png
71 ms
spacer.gif
25 ms
printer.gif
21 ms
icon_emailAlert.gif
25 ms
powered_edgar_online.gif
25 ms
sh.8e5f85691f9aaa082472a194.html
47 ms
AEAAQQBCAEMARABFAEYARwBIAEkASgBLAEwATQBOAE8AUABRAFIAUwBUAFUAVgBXAFgAWQBaAFsAXABdAF4AXwBgAGEBAgDEAKYAxQCrAIIAwgDYAMYA5AC+ALAA5gC2ALcAtAC1AIcAsgCzANkAjADlAL8AsQDnALsBAwCjAIQAhQC9AJYA6ACGAI4AiwCdAKkApAEEAIoBBQCDAJMA8gDzAI0AlwCIAQYA3gDxAJ4AqgD1APQA9gCiAK0AyQDHAK4AYgBjAJAAZADLAGUAyADKAM8AzADNAM4A6QBmANMA0ADRAK8AZwDwAJEA1gDUANUAaADrAO0AiQBqAGkAawBtAGwAbgCgAG8AcQBwAHIAcwB1AHQAdgB3AOoAeAB6AHkAewB9AHwAuAChAH8AfgCAAIEA7ADuALoA1wDiAOMA4QDbANwA3QDgAN8AvADvAMAAwQRFdXJvB3VuaTAwQTAHdW5pMDBBRAZtYWNyb24OcGVyaW9kY2VudGVyZWQAAAAACTEwMTY4NDQ1NwAkMjBFQjA1NTVGRkNGNDI4QkJEQjA1NkFGMDFENzdFRkRBNkNBAAAA
18 ms
font1bold.ttf
114 ms
o68BiHnhg8EpM1hCm9A1ZfN6EDidy30UWh3A2w26BZ9h74j8Saq6Ysfwi7ooUd0nLXOqAPOeL6dArZnVnGqoUf8Tyruhgeh2lFX6J4LYo7moCIB1CrEj6wNcPOLvWTatkuUVc5Mt3vAqtpwX9i7lVBiFtEnp6E3qbfR0KZnjw4vkcPoCJNZ1DyVfCJDWY3meCCSOpNZvTaG58oxh2My8vTyKySG16l+ycU2KplZD2kOjqwwMK0h8vpqQGWLpzKi2Lfh9WLjNnaCgHVcPugAAA=
41 ms
font1edit.ttf
144 ms
s77737134050112
10 ms
ir.omnicare.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
[aria-hidden="true"] elements contain focusable descendents
ARIA IDs are not unique
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
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
ir.omnicare.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
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
ir.omnicare.com 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
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
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ir.omnicare.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 Ir.omnicare.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.
ir.omnicare.com
Open Graph description is not detected on the main page of IR Omnicare. 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: