Tools & Wizards About Us
dexilant.ca screenshot

Report Summary

  • 38

    Performance

    Renders faster than
    57% of other websites

  • 79

    Accessibility

    Visual factors better than
    that of 47% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

dexilant.ca

Please Enter Your DIN | DEXILANT® (dexlansoprazole)

Page Load Speed

784 ms in total

First Response

41 ms

Resources Loaded

544 ms

Page Rendered

199 ms

dexilant.ca screenshot

About Website

Click here to check amazing DEXILANT content. Otherwise, check out these important facts you probably never knew about dexilant.ca

Due to Canadian regulations, you are required to sign in to access information about Takeda Canada's products and professional and patient support. Sign in here.

Visit dexilant.ca

Key Findings

We analyzed Dexilant.ca page load time and found that the first response time was 41 ms and then it took 743 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.

Performance Metrics

dexilant.ca performance score

38

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

39/100

10%

LCP (Largest Contentful Paint)

Value11.1 s

0/100

25%

SI (Speed Index)

Value5.1 s

61/100

10%

TBT (Total Blocking Time)

Value960 ms

29/100

30%

CLS (Cumulative Layout Shift)

Value0.017

100/100

15%

TTI (Time to Interactive)

Value8.1 s

42/100

10%

Network Requests Diagram

dexilant.ca

41 ms

dexilant.ca

43 ms

www.dexilant.ca

53 ms

gateway

6 ms

OtAutoBlock.js

55 ms

Our browser made a total of 33 requests to load all elements on the main page. We found that 73% of them (24 requests) were addressed to the original Dexilant.ca, 12% (4 requests) were made to Use.typekit.net and 9% (3 requests) were made to Cdn.cookielaw.org. The less responsive or slowest element that took the longest time to load (170 ms) relates to the external source Use.typekit.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 57.4 kB (10%)

Content Size

579.9 kB

After Optimization

522.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Dexilant.ca main page is 579.9 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. 40% of websites need less resources to load. Images take 549.6 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 16.7 kB

  • Original 21.1 kB
  • After minification 15.8 kB
  • After compression 4.4 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 5.3 kB, which is 25% 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 16.7 kB or 79% of the original size.

Image Optimization

-7%

Potential reduce by 40.7 kB

  • Original 549.6 kB
  • After minification 508.9 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. DEXILANT images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 45 B

  • Original 9.2 kB
  • After minification 9.2 kB
  • After compression 9.2 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. This website has mostly compressed JavaScripts.

CSS Optimization

-0%

Potential reduce by 0 B

  • Original 5 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.

Requests Breakdown

Number of requests can be reduced by 4 (19%)

Requests Now

21

After Optimization

17

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 21 CSS, Javascripts, AJAX and image requests in order to completely render the main page of DEXILANT. 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 as a result speed up the page load time.

Network Requests Diagram

dexilant.ca

dexilant.ca

41 ms

dexilant.ca

dexilant.ca

43 ms

www.dexilant.ca

www.dexilant.ca

53 ms

gateway

gateway

6 ms

OtAutoBlock.js

OtAutoBlock.js

55 ms

otSDKStub.js

otSDKStub.js

65 ms

qik5boy.css

qik5boy.css

170 ms

css

css

33 ms

headscripts

headscripts

64 ms

validationscripts

validationscripts

46 ms

scripts

scripts

62 ms

01901036-8a03-786d-9ca5-d5c698362793.json

01901036-8a03-786d-9ca5-d5c698362793.json

24 ms

location

location

44 ms

p.css

p.css

28 ms

icon-menu-hamburger.svg

icon-menu-hamburger.svg

67 ms

logo_dexilant.svg

logo_dexilant.svg

25 ms

icon-menu-close.svg

icon-menu-close.svg

19 ms

hero_gateway-desktop.png

hero_gateway-desktop.png

33 ms

dexilant-din.png

dexilant-din.png

109 ms

bg-blue.png

bg-blue.png

23 ms

dexilant-logo-footer.png

dexilant-logo-footer.png

26 ms

takeda-logo-footer.png

takeda-logo-footer.png

33 ms

logo_paab.png

logo_paab.png

109 ms

logo_takeda.svg

logo_takeda.svg

40 ms

logo_imc.png

logo_imc.png

39 ms

d

d

5 ms

d

d

11 ms

d

d

10 ms

OpenSans-Bold.ttf

OpenSans-Bold.ttf

47 ms

OpenSans-ExtraBold.ttf

OpenSans-ExtraBold.ttf

81 ms

OpenSans-Semibold.ttf

OpenSans-Semibold.ttf

70 ms

OpenSans-Regular.ttf

OpenSans-Regular.ttf

108 ms

OpenSans-Light.ttf

OpenSans-Light.ttf

72 ms

Accessibility Review

dexilant.ca accessibility score

79

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

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

Form elements do not have associated labels

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

dexilant.ca best practices score

75

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

High

Browser errors were logged to the console

SEO Factors

dexilant.ca SEO score

86

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

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

dexilant.ca

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