Tools & Wizards About Us
dionex.com screenshot

Report Summary

  • 34

    Performance

    Renders faster than
    54% of other websites

  • 74

    Accessibility

    Visual factors better than
    that of 40% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 76

    SEO

    Google-friendlier than
    35% of websites

dionex.com

Chromatography | Thermo Fisher Scientific - US

Page Load Speed

1.6 sec in total

First Response

48 ms

Resources Loaded

1.2 sec

Page Rendered

395 ms

dionex.com screenshot

About Website

Click here to check amazing Dionex content for United States. Otherwise, check out these important facts you probably never knew about dionex.com

GLE Disclaimer for pages with both RUO and GLE products

Visit dionex.com

Key Findings

We analyzed Dionex.com page load time and found that the first response time was 48 ms and then it took 1.6 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

dionex.com performance score

34

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.1 s

82/100

10%

LCP (Largest Contentful Paint)

Value6.2 s

11/100

25%

SI (Speed Index)

Value4.3 s

75/100

10%

TBT (Total Blocking Time)

Value3,710 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value16.0 s

6/100

10%

Network Requests Diagram

dionex.com

48 ms

chromatography.html

244 ms

launch-f46125d37e44.min.js

26 ms

preload

212 ms

utilities.min.5d3c074c9899f3.js

41 ms

Our browser made a total of 57 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Dionex.com, 81% (46 requests) were made to Thermofisher.com and 4% (2 requests) were made to Consent.trustarc.com. The less responsive or slowest element that took the longest time to load (455 ms) relates to the external source Thermofisher.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 740.2 kB (61%)

Content Size

1.2 MB

After Optimization

466.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Dionex.com 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. 50% of websites need less resources to load. HTML takes 588.4 kB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 505.2 kB

  • Original 588.4 kB
  • After minification 578.4 kB
  • After compression 83.2 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 505.2 kB or 86% of the original size.

Image Optimization

-4%

Potential reduce by 8.5 kB

  • Original 189.7 kB
  • After minification 181.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. Dionex images are well optimized though.

JavaScript Optimization

-53%

Potential reduce by 226.3 kB

  • Original 427.7 kB
  • After minification 427.0 kB
  • After compression 201.4 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 226.3 kB or 53% of the original size.

CSS Optimization

-21%

Potential reduce by 151 B

  • Original 710 B
  • After minification 710 B
  • After compression 559 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. Dionex.com needs all CSS files to be minified and compressed as it can save up to 151 B or 21% of the original size.

Requests Breakdown

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

Requests Now

54

After Optimization

27

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

dionex.com

dionex.com

48 ms

chromatography.html

chromatography.html

244 ms

launch-f46125d37e44.min.js

launch-f46125d37e44.min.js

26 ms

preload

preload

212 ms

utilities.min.5d3c074c9899f3.js

utilities.min.5d3c074c9899f3.js

41 ms

signals.min.js

signals.min.js

51 ms

searchbar.min.js

searchbar.min.js

50 ms

base-jquery.min.js

base-jquery.min.js

47 ms

global-variables.js

global-variables.js

57 ms

base.min.css

base.min.css

74 ms

base-responsive.min.css

base-responsive.min.css

60 ms

base-addons.min.css

base-addons.min.css

65 ms

shared.min.f3691feba184d2c914fdd5230e56ad3a.css

shared.min.f3691feba184d2c914fdd5230e56ad3a.css

98 ms

cq-base.min.css

cq-base.min.css

80 ms

cq-shared.min.js

cq-shared.min.js

90 ms

taqman-hr-meganav.jpg

taqman-hr-meganav.jpg

92 ms

popular2-175x115.gif

popular2-175x115.gif

143 ms

oligos-main-popular.jpg

oligos-main-popular.jpg

146 ms

popular4-175x115.jpg

popular4-175x115.jpg

145 ms

popular5-175x115.jpg

popular5-175x115.jpg

146 ms

index.min.js

index.min.js

43 ms

lc-wells.css

lc-wells.css

146 ms

highlight.js

highlight.js

52 ms

base-bootstrap.min.js

base-bootstrap.min.js

186 ms

base-addons.min.js

base-addons.min.js

177 ms

cq-base.min.js

cq-base.min.js

179 ms

global-functions.js

global-functions.js

177 ms

image.jpeg

image.jpeg

188 ms

user-type

user-type

172 ms

footer-base.min.5d3c074c9899f3.js

footer-base.min.5d3c074c9899f3.js

97 ms

minicart.js

minicart.js

99 ms

identityGlobal.min.js

identityGlobal.min.js

99 ms

us.gif

us.gif

145 ms

token.json

token.json

175 ms

glyphicons-halflings.png

glyphicons-halflings.png

315 ms

loading-wheel-lg.gif

loading-wheel-lg.gif

326 ms

icon-outboundlink.gif

icon-outboundlink.gif

369 ms

video-play-thumbnail-lg.png

video-play-thumbnail-lg.png

313 ms

offers.min.js

offers.min.js

86 ms

chat-launcher.js

chat-launcher.js

86 ms

s_code.min.js

s_code.min.js

138 ms

d2Gy0VcRQ

d2Gy0VcRQ

139 ms

hotjar-4539.js

hotjar-4539.js

301 ms

icons-lt.png

icons-lt.png

323 ms

sprites-icons-document-types-16px.png

sprites-icons-document-types-16px.png

276 ms

WB47393_MK_FP_1400x440%3Athermofisher-smart-dm-web-MD_FP

WB47393_MK_FP_1400x440%3Athermofisher-smart-dm-web-MD_FP

429 ms

notice

notice

200 ms

load

load

283 ms

1572475478878.jpg

1572475478878.jpg

301 ms

1685975031557.jpg

1685975031557.jpg

259 ms

1685975031601.jpg

1685975031601.jpg

111 ms

1685975031670.jpg

1685975031670.jpg

387 ms

1685975032000.jpg

1685975032000.jpg

409 ms

1685975032113.jpg

1685975032113.jpg

455 ms

modules.e5979922753cf3b8b069.js

modules.e5979922753cf3b8b069.js

17 ms

log

log

90 ms

v1.7-3281

v1.7-3281

20 ms

Accessibility Review

dionex.com accessibility score

74

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.

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 IDs are not unique

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

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

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

dionex.com best practices score

58

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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

dionex.com SEO score

76

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

High

Image elements do not have [alt] attributes

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

High

Tap targets are not sized appropriately

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 Dionex.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 Dionex.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

dionex.com

Open Graph data is detected on the main page of Dionex. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: