784 ms in total
41 ms
544 ms
199 ms
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.caWe 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.
dexilant.ca performance score
name
value
score
weighting
Value3.3 s
39/100
10%
Value11.1 s
0/100
25%
Value5.1 s
61/100
10%
Value960 ms
29/100
30%
Value0.017
100/100
15%
Value8.1 s
42/100
10%
41 ms
43 ms
53 ms
6 ms
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 size can be reduced by 57.4 kB (10%)
579.9 kB
522.5 kB
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.
Potential reduce by 16.7 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.
Potential reduce by 40.7 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.
Potential reduce by 34 B
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.
Potential reduce by 0 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.
Number of requests can be reduced by 4 (19%)
21
17
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.
dexilant.ca
41 ms
dexilant.ca
43 ms
www.dexilant.ca
53 ms
gateway
6 ms
OtAutoBlock.js
55 ms
otSDKStub.js
65 ms
qik5boy.css
170 ms
css
33 ms
headscripts
64 ms
validationscripts
46 ms
scripts
62 ms
01901036-8a03-786d-9ca5-d5c698362793.json
24 ms
location
44 ms
p.css
28 ms
icon-menu-hamburger.svg
67 ms
logo_dexilant.svg
25 ms
icon-menu-close.svg
19 ms
hero_gateway-desktop.png
33 ms
dexilant-din.png
109 ms
bg-blue.png
23 ms
dexilant-logo-footer.png
26 ms
takeda-logo-footer.png
33 ms
logo_paab.png
109 ms
logo_takeda.svg
40 ms
logo_imc.png
39 ms
d
5 ms
d
11 ms
d
10 ms
OpenSans-Bold.ttf
47 ms
OpenSans-ExtraBold.ttf
81 ms
OpenSans-Semibold.ttf
70 ms
OpenSans-Regular.ttf
108 ms
OpenSans-Light.ttf
72 ms
dexilant.ca accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
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
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
Form elements do not have associated labels
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
dexilant.ca best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
dexilant.ca 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
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
EN
N/A
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.
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: