Tools & Wizards About Us
agilent.ca screenshot

Report Summary

  • 9

    Performance

    Renders faster than
    23% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

agilent.ca

Chemical Analysis, Life Sciences, and Diagnostics | Agilent

Page Load Speed

1.6 sec in total

First Response

32 ms

Resources Loaded

1.3 sec

Page Rendered

272 ms

agilent.ca screenshot

About Website

Visit agilent.ca now to see the best up-to-date Agilent content and also check out these interesting facts you probably never knew about agilent.ca

Agilent delivers complete scientific solutions, helping customers achieve superior outcomes in their labs, clinics, business and the world they seek to improve.

Visit agilent.ca

Key Findings

We analyzed Agilent.ca page load time and found that the first response time was 32 ms and then it took 1.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.

Performance Metrics

agilent.ca performance score

9

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.8 s

55/100

10%

LCP (Largest Contentful Paint)

Value12.4 s

0/100

25%

SI (Speed Index)

Value12.5 s

3/100

10%

TBT (Total Blocking Time)

Value12,270 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.426

22/100

15%

TTI (Time to Interactive)

Value29.4 s

0/100

10%

Network Requests Diagram

agilent.ca

32 ms

www.agilent.com

318 ms

ruxitagentjs_A7NQVfghqrx_10303241106123517.js

63 ms

otSDKStub.js

36 ms

ot-banner.js

36 ms

Our browser made a total of 77 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Agilent.ca, 96% (74 requests) were made to Agilent.com and 1% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (334 ms) relates to the external source Seahorseinfo.agilent.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 700.4 kB (57%)

Content Size

1.2 MB

After Optimization

522.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Agilent.ca main page is 1.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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 739.2 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 124.5 kB

  • Original 161.3 kB
  • After minification 143.5 kB
  • After compression 36.8 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 17.8 kB, which is 11% 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 124.5 kB or 77% of the original size.

Image Optimization

-2%

Potential reduce by 3.2 kB

  • Original 146.7 kB
  • After minification 143.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. Agilent images are well optimized though.

JavaScript Optimization

-62%

Potential reduce by 461.1 kB

  • Original 739.2 kB
  • After minification 689.8 kB
  • After compression 278.0 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 461.1 kB or 62% of the original size.

CSS Optimization

-64%

Potential reduce by 111.7 kB

  • Original 175.6 kB
  • After minification 158.6 kB
  • After compression 63.9 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. Agilent.ca needs all CSS files to be minified and compressed as it can save up to 111.7 kB or 64% of the original size.

Requests Breakdown

Number of requests can be reduced by 50 (78%)

Requests Now

64

After Optimization

14

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

agilent.ca

agilent.ca

32 ms

www.agilent.com

www.agilent.com

318 ms

ruxitagentjs_A7NQVfghqrx_10303241106123517.js

ruxitagentjs_A7NQVfghqrx_10303241106123517.js

63 ms

otSDKStub.js

otSDKStub.js

36 ms

ot-banner.js

ot-banner.js

36 ms

gtm.js

gtm.js

104 ms

jquery-ui.min.css

jquery-ui.min.css

40 ms

jquery-ui.theme.min.css

jquery-ui.theme.min.css

34 ms

homeStyle.css

homeStyle.css

36 ms

style.css

style.css

44 ms

googleFont.css

googleFont.css

42 ms

jquery.bxslider.css

jquery.bxslider.css

53 ms

selectric.css

selectric.css

146 ms

globalHeaderFooter.css

globalHeaderFooter.css

56 ms

globalHeaderFlyout.css

globalHeaderFlyout.css

65 ms

typeahead.css

typeahead.css

55 ms

selectric.css

selectric.css

64 ms

connect.js

connect.js

297 ms

jquery.js

jquery.js

67 ms

jquery-ui.min.js

jquery-ui.min.js

64 ms

browserdetector.js

browserdetector.js

61 ms

bootstrap_002.js

bootstrap_002.js

62 ms

bootstrap.js

bootstrap.js

64 ms

jquery_002.js

jquery_002.js

65 ms

jquery.dataTables.columnFilter.js

jquery.dataTables.columnFilter.js

68 ms

analytics.js

analytics.js

64 ms

jquery.selectric.js

jquery.selectric.js

70 ms

globalHeaderFlyoutScript.js

globalHeaderFlyoutScript.js

69 ms

jquery.cookie.js

jquery.cookie.js

198 ms

typeahead-agilent.js

typeahead-agilent.js

88 ms

typeahead.min.js

typeahead.min.js

89 ms

bootstrap-select.js

bootstrap-select.js

88 ms

hogan-2.0.js

hogan-2.0.js

138 ms

jwplayer.js

jwplayer.js

138 ms

script.js

script.js

137 ms

homepage_analytics.js

homepage_analytics.js

196 ms

panzoom.js

panzoom.js

194 ms

jquery.bxslider.min.js

jquery.bxslider.min.js

197 ms

updated.css

updated.css

206 ms

globalHeaderLayoutScript.js

globalHeaderLayoutScript.js

177 ms

jquery-scrolltofixed-min.js

jquery-scrolltofixed-min.js

175 ms

jquery.lazyload.min.js

jquery.lazyload.min.js

184 ms

acton.js

acton.js

169 ms

icon-agilent-logo-white-white-2x.png

icon-agilent-logo-white-white-2x.png

97 ms

icon-agilent-spark-1x.png

icon-agilent-spark-1x.png

22 ms

header_icon_cart.png

header_icon_cart.png

20 ms

CrossLab-brands-agilent.svg

CrossLab-brands-agilent.svg

17 ms

thumbnailSeprator.png

thumbnailSeprator.png

21 ms

loader2.gif

loader2.gif

30 ms

blank.gif

blank.gif

20 ms

btn_more_EN_normal.png

btn_more_EN_normal.png

23 ms

footer_social-1_connect.png

footer_social-1_connect.png

22 ms

roboto-regular.woff

roboto-regular.woff

84 ms

robotocondensed-light.woff

robotocondensed-light.woff

82 ms

footer_social-8_iconseparator.png

footer_social-8_iconseparator.png

202 ms

Common_agilentSocialhub.png

Common_agilentSocialhub.png

205 ms

icon-agilent-logo-white-white-2x.png

icon-agilent-logo-white-white-2x.png

211 ms

footer_icon_location.png

footer_icon_location.png

201 ms

icomoon.woff

icomoon.woff

200 ms

robotocondensed-regular.woff

robotocondensed-regular.woff

199 ms

fa-light-300.woff

fa-light-300.woff

203 ms

fa-regular-400.woff

fa-regular-400.woff

205 ms

fa-solid-900.woff

fa-solid-900.woff

200 ms

roboto-medium.woff

roboto-medium.woff

200 ms

robotocondensed-bold.woff

robotocondensed-bold.woff

204 ms

footer_icon_email.png

footer_icon_email.png

178 ms

footer_icon_phone.png

footer_icon_phone.png

178 ms

fa-brands-400.woff

fa-brands-400.woff

180 ms

searchdropdowns

searchdropdowns

201 ms

dropdown-arrow.png

dropdown-arrow.png

63 ms

10967

10967

334 ms

btn_more_EN_hover.png

btn_more_EN_hover.png

43 ms

bx_loader.gif

bx_loader.gif

29 ms

infinityiii_1400x645.jpg

infinityiii_1400x645.jpg

28 ms

272x153-highlightbannergcwfcolumn.png

272x153-highlightbannergcwfcolumn.png

12 ms

luma_highlight_272x153.jpg

luma_highlight_272x153.jpg

10 ms

272x153-highlightbanner-gcmscolumnsandsupplies.png

272x153-highlightbanner-gcmscolumnsandsupplies.png

18 ms

Accessibility Review

agilent.ca accessibility score

84

Accessibility Issues

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

High

[aria-hidden="true"] elements contain focusable descendents

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

[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

High

<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

High

Links do not have a discernible name

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

agilent.ca best practices score

67

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

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

agilent.ca SEO score

77

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

High

robots.txt is not valid

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

    N/A

  • Encoding

    UTF-8

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

agilent.ca

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