Tools & Wizards About Us
valeant.com screenshot

Report Summary

  • 47

    Performance

    Renders faster than
    65% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

valeant.com

Home | Bausch Health

Page Load Speed

1.4 sec in total

First Response

296 ms

Resources Loaded

918 ms

Page Rendered

188 ms

valeant.com screenshot

About Website

Visit valeant.com now to see the best up-to-date Valeant content for United States and also check out these interesting facts you probably never knew about valeant.com

Learn about Bausch Health, a global company whose mission is to improve people’s lives with our health care products.

Visit valeant.com

Key Findings

We analyzed Valeant.com page load time and found that the first response time was 296 ms and then it took 1.1 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.

Performance Metrics

valeant.com performance score

47

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.2 s

19/100

10%

LCP (Largest Contentful Paint)

Value8.3 s

2/100

25%

SI (Speed Index)

Value4.6 s

71/100

10%

TBT (Total Blocking Time)

Value460 ms

62/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value8.5 s

38/100

10%

Network Requests Diagram

www.valeant.com

296 ms

default.css

5 ms

module.css

14 ms

skin.css

11 ms

searchskinobjectpreview.css

13 ms

Our browser made a total of 55 requests to load all elements on the main page. We found that 62% of them (34 requests) were addressed to the original Valeant.com, 24% (13 requests) were made to Valeant.q4web.com and 7% (4 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (311 ms) relates to the external source Valeant.q4web.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.0 MB (66%)

Content Size

1.5 MB

After Optimization

510.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Valeant.com main page is 1.5 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. 65% of websites need less resources to load. Javascripts take 1.2 MB which makes up the majority of the site volume.

HTML Optimization

-69%

Potential reduce by 17.3 kB

  • Original 25.2 kB
  • After minification 23.7 kB
  • After compression 7.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 17.3 kB or 69% of the original size.

Image Optimization

-2%

Potential reduce by 2.8 kB

  • Original 152.0 kB
  • After minification 149.2 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. Valeant images are well optimized though.

JavaScript Optimization

-72%

Potential reduce by 828.9 kB

  • Original 1.2 MB
  • After minification 1.1 MB
  • After compression 325.9 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 828.9 kB or 72% of the original size.

CSS Optimization

-85%

Potential reduce by 163.4 kB

  • Original 191.2 kB
  • After minification 133.1 kB
  • After compression 27.8 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. Valeant.com needs all CSS files to be minified and compressed as it can save up to 163.4 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 39 (75%)

Requests Now

52

After Optimization

13

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 52 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Valeant. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 26 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

www.valeant.com

www.valeant.com

296 ms

default.css

default.css

5 ms

module.css

module.css

14 ms

skin.css

skin.css

11 ms

searchskinobjectpreview.css

searchskinobjectpreview.css

13 ms

jquery.js

jquery.js

13 ms

jquery-migrate.js

jquery-migrate.js

34 ms

jquery-ui.js

jquery-ui.js

37 ms

ga.js

ga.js

95 ms

WebResource.axd

WebResource.axd

7 ms

Telerik.Web.UI.WebResource.axd

Telerik.Web.UI.WebResource.axd

10 ms

dnn.js

dnn.js

20 ms

dnn.modalpopup.js

dnn.modalpopup.js

9 ms

jquery.hoverintent.min.js

jquery.hoverintent.min.js

22 ms

dnn.servicesframework.js

dnn.servicesframework.js

25 ms

dnn.jquery.js

dnn.jquery.js

26 ms

searchskinobjectpreview.js

searchskinobjectpreview.js

23 ms

dnncore.js

dnncore.js

31 ms

skin.js

skin.js

22 ms

initWidgets.js

initWidgets.js

22 ms

valeant_logo.jpg

valeant_logo.jpg

22 ms

Valeant%20Now%20Button%20-%20293px%20Wide.png

Valeant%20Now%20Button%20-%20293px%20Wide.png

23 ms

default.aspx

default.aspx

311 ms

DotNetNukeAjaxShared.js

DotNetNukeAjaxShared.js

45 ms

_Incapsula_Resource

_Incapsula_Resource

44 ms

bg-search.jpg

bg-search.jpg

11 ms

valeant_campaign_01.jpg

valeant_campaign_01.jpg

47 ms

bg-purple-top-campaign.png

bg-purple-top-campaign.png

12 ms

raquo.png

raquo.png

41 ms

button-round-right.png

button-round-right.png

44 ms

button-round-left.png

button-round-left.png

42 ms

bg-home-bottom-wrap.jpg

bg-home-bottom-wrap.jpg

42 ms

KlavikaWebBasicRegular.woff

KlavikaWebBasicRegular.woff

44 ms

KlavikaWebBasicMedium.woff

KlavikaWebBasicMedium.woff

42 ms

widgets.js

widgets.js

40 ms

__utm.gif

__utm.gif

27 ms

_Incapsula_Resource

_Incapsula_Resource

12 ms

jquery-ui-1.7.2.custom.css

jquery-ui-1.7.2.custom.css

10 ms

jquery.fancybox-1.3.4.css

jquery.fancybox-1.3.4.css

12 ms

default.css

default.css

14 ms

global_9181.css

global_9181.css

20 ms

client_9122.css

client_9122.css

22 ms

jquery-1.7.1.min.js

jquery-1.7.1.min.js

13 ms

jquery-ui-1.8.16.custom.min.js

jquery-ui-1.8.16.custom.min.js

13 ms

jquery.easing-1.3.pack.js

jquery.easing-1.3.pack.js

14 ms

jquery.mousewheel-3.0.4.pack.js

jquery.mousewheel-3.0.4.pack.js

15 ms

jquery.fancybox-1.3.4.pack.js

jquery.fancybox-1.3.4.pack.js

14 ms

q4utils-1.0.0.js

q4utils-1.0.0.js

15 ms

json2.js

json2.js

14 ms

Date.js

Date.js

13 ms

doctracking.js

doctracking.js

13 ms

analytics.js

analytics.js

28 ms

breadcrumbLine.png

breadcrumbLine.png

12 ms

collect

collect

24 ms

print.css

print.css

3 ms

Accessibility Review

valeant.com accessibility score

84

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

valeant.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

valeant.com SEO score

92

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Valeant.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 Valeant.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.

Social Sharing Optimization

valeant.com

Open Graph description is not detected on the main page of Valeant. 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: