5.7 sec in total
344 ms
3.9 sec
1.5 sec
Click here to check amazing Info Omnicare content for United States. Otherwise, check out these important facts you probably never knew about info.omnicare.com
Omnicare is a pharmacy services provider for long-term care and post-acute facilities, as well as assisted living or senior living communities.
Visit info.omnicare.comWe analyzed Info.omnicare.com page load time and found that the first response time was 344 ms and then it took 5.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
info.omnicare.com performance score
name
value
score
weighting
Value3.1 s
45/100
10%
Value24.2 s
0/100
25%
Value10.6 s
7/100
10%
Value1,160 ms
22/100
30%
Value0.125
83/100
15%
Value16.7 s
5/100
10%
344 ms
358 ms
336 ms
97 ms
49 ms
Our browser made a total of 131 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Info.omnicare.com, 92% (121 requests) were made to Omnicare.com and 2% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Omnicare.com.
Page size can be reduced by 941.5 kB (10%)
9.3 MB
8.3 MB
In fact, the total size of Info.omnicare.com main page is 9.3 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. 70% of websites need less resources to load. Images take 8.4 MB which makes up the majority of the site volume.
Potential reduce by 80.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. This page needs HTML code to be minified as it can gain 15.8 kB, which is 17% 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 80.3 kB or 85% of the original size.
Potential reduce by 329.1 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. Info Omnicare images are well optimized though.
Potential reduce by 289.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 289.1 kB or 57% of the original size.
Potential reduce by 243.0 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. Info.omnicare.com needs all CSS files to be minified and compressed as it can save up to 243.0 kB or 88% of the original size.
Number of requests can be reduced by 100 (81%)
124
24
The browser has sent 124 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Info 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 67 to 1 for JavaScripts and from 35 to 1 for CSS and as a result speed up the page load time.
info.omnicare.com
344 ms
info.omnicare.com
358 ms
www.omnicare.com
336 ms
gtm.js
97 ms
munchkin.js
49 ms
core.css
173 ms
controlgroup.css
174 ms
checkboxradio.css
119 ms
resizable.css
137 ms
button.css
175 ms
dialog.css
174 ms
ajax-progress.module.css
241 ms
autocomplete-loading.module.css
360 ms
fieldgroup.module.css
239 ms
container-inline.module.css
330 ms
clearfix.module.css
245 ms
details.module.css
331 ms
hidden.module.css
392 ms
item-list.module.css
322 ms
js.module.css
263 ms
nowrap.module.css
336 ms
position-container.module.css
378 ms
progress.module.css
421 ms
reset-appearance.module.css
423 ms
resize.module.css
419 ms
sticky-header.module.css
490 ms
system-status-counter.css
446 ms
system-status-report-counters.css
501 ms
system-status-report-general-info.css
476 ms
tabledrag.module.css
741 ms
tablesort.module.css
602 ms
tree-child.module.css
550 ms
theme.css
553 ms
extlink.css
597 ms
onecol.css
617 ms
filter-validation.css
623 ms
paragraphs.unpublished.css
616 ms
brightcove_extras.css
792 ms
cvs_common_header.css
655 ms
style.min.css
639 ms
modernizr.min.js
906 ms
munchkin.js
14 ms
visitWebPage
385 ms
js
81 ms
analytics.js
20 ms
modernizr-additional-tests.js
552 ms
jquery.min.js
625 ms
collect
15 ms
element.matches.js
770 ms
object.assign.js
810 ms
nodelist.foreach.js
808 ms
css.escape.js
662 ms
es6-promise.auto.min.js
743 ms
once.min.js
745 ms
jquery.once.min.js
906 ms
drupalSettingsLoader.js
771 ms
drupal.js
711 ms
drupal.init.js
1117 ms
main.js
709 ms
version-min.js
746 ms
data-min.js
881 ms
disable-selection-min.js
859 ms
form-min.js
731 ms
jquery-patch-min.js
741 ms
scroll-parent-min.js
761 ms
unique-id-min.js
943 ms
focusable-min.js
831 ms
ie-min.js
884 ms
keycode-min.js
939 ms
plugin-min.js
927 ms
safe-active-element-min.js
781 ms
safe-blur-min.js
896 ms
widget-min.js
865 ms
controlgroup-min.js
838 ms
form-reset-mixin-min.js
941 ms
labels-min.js
962 ms
mouse-min.js
889 ms
checkboxradio-min.js
898 ms
draggable-min.js
852 ms
resizable-min.js
902 ms
button-min.js
826 ms
dialog-min.js
867 ms
index.umd.min.js
877 ms
main.min.js
851 ms
extlink.js
694 ms
jquery.once.bc.js
741 ms
progress.js
661 ms
loadjs.min.js
1079 ms
ajax.js
810 ms
ajax.js
1030 ms
cnv
4 ms
ajax.js
902 ms
jquery.form.min.js
901 ms
base.js
894 ms
ajax_view.js
796 ms
filter-validation.js
936 ms
debounce.js
868 ms
displace.js
840 ms
jquery.tabbable.shim.js
819 ms
position.js
835 ms
dialog.js
832 ms
dialog.position.js
799 ms
dialog.jquery-ui.js
771 ms
dialog.ajax.js
893 ms
brightcove_extras.js
818 ms
jquery.actual.min.js
719 ms
cvs_common_header.js
701 ms
JQIkp2DTo
658 ms
CVSHealthSans-Regular.woff
703 ms
CVSHealthSans-Medium.woff
722 ms
CVSHealthSans-Bold.woff
937 ms
logo.svg
704 ms
cvs-omnicare-who-we-are-hero-sm.jpg
815 ms
cvs-omnicare-who-we-serve-hero-image-01-sm.png
767 ms
cvs-omnicare-what-we-offer-hero-image-01-sm.jpg
921 ms
AdobeStock_192319523_0.jpeg
928 ms
cvs-omnicare-doctor-pictogram.png
799 ms
cvs-omnicare-nurse-blue-scrubs.png
873 ms
cvs-omnicare-physical-therapy2x.png
722 ms
cvs-omnicare-nurse-and-senior-citizen%402x.png
803 ms
cvs-omnicare-senior-with-family%402x.png
838 ms
cvs-omnicare-senior-citizens%402x.png
949 ms
cvs-omnicare-pharmacist-pictogram-02_0.png
836 ms
cvs-omnicare-what-we-offer-financial-value-pictogram-01%402x.png
911 ms
cvs-omnicare-nurse-with-phone-pictogram-group%402x.png
761 ms
Group%205088%402x.png
793 ms
Explore-Our-Products-Services-and-Tools-Homepage.jpg
686 ms
cvs-omnicare-doctor-nurse-nursing-station%402x.png
684 ms
cvs-omnicare-switching-pictogram%402x.png
777 ms
down-arrow-black.svg
668 ms
social-linkedin-red.svg
845 ms
info.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-*] attributes do not have valid values
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
Image elements do not have [alt] attributes
info.omnicare.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
info.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
Image elements do not have [alt] attributes
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 Info.omnicare.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 Info.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.
info.omnicare.com
Open Graph description is not detected on the main page of Info 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: