872 ms in total
51 ms
494 ms
327 ms
Visit lilly.ca now to see the best up-to-date Lilly content for Canada and also check out these interesting facts you probably never knew about lilly.ca
Home page for Eli Lilly and Company in Canada
Visit lilly.caWe analyzed Lilly.ca page load time and found that the first response time was 51 ms and then it took 821 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.
lilly.ca performance score
name
value
score
weighting
Value2.9 s
53/100
10%
Value4.8 s
30/100
25%
Value5.9 s
48/100
10%
Value2,010 ms
7/100
30%
Value0.313
37/100
15%
Value10.6 s
23/100
10%
51 ms
24 ms
17 ms
9 ms
10 ms
Our browser made a total of 45 requests to load all elements on the main page. We found that 96% of them (43 requests) were addressed to the original Lilly.ca, 2% (1 request) were made to S.webtrends.com and 2% (1 request) were made to Statse.webtrendslive.com. The less responsive or slowest element that took the longest time to load (152 ms) relates to the external source Statse.webtrendslive.com.
Page size can be reduced by 567.3 kB (36%)
1.6 MB
1.0 MB
In fact, the total size of Lilly.ca main page is 1.6 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. 60% of websites need less resources to load. Images take 883.6 kB which makes up the majority of the site volume.
Potential reduce by 46.5 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.1 kB, which is 32% 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 46.5 kB or 87% of the original size.
Potential reduce by 44.0 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. Lilly images are well optimized though.
Potential reduce by 337.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 337.2 kB or 70% of the original size.
Potential reduce by 139.6 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. Lilly.ca needs all CSS files to be minified and compressed as it can save up to 139.6 kB or 85% of the original size.
Number of requests can be reduced by 19 (44%)
43
24
The browser has sent 43 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Lilly. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
lilly.ca
51 ms
index.aspx
24 ms
styles.css
17 ms
jquery.fancybox-1.3.4.css
9 ms
fancybox.css
10 ms
site.css
13 ms
core.css
9 ms
jquery-1.8.2.min.js
21 ms
init.js
18 ms
jquery.fancybox-1.3.4.pack.js
19 ms
site.js
26 ms
custom.css
17 ms
jquery-1.7.1.min.js
20 ms
jquery.tools.min.js
33 ms
lilly.js
24 ms
MobileOptimization.js
23 ms
tablet.landscape.css
17 ms
tablet.portrait.css
26 ms
mobile.landscape.css
29 ms
mobile.portrait.css
26 ms
webtrends.js
114 ms
bg-grid.jpg
18 ms
lilly-logo.png
17 ms
Carousel-Promise-Make-Life-Better.jpg
33 ms
Carousel-Promise-Discovery.jpg
34 ms
Carousel-Global-Communities.jpg
30 ms
homepage_callout_lilly_giving_210px115px.jpg
18 ms
homepage_callout_diversity_210px115px.jpg
18 ms
homepage_callout_invsestors_289px36px.jpg
28 ms
Lilly-Pro-Button-No-Border-291x67.jpg
32 ms
homepage_callout_LillyPad_95px115px.png
30 ms
homepage_callout_community_hands_188px115px.jpg
34 ms
homepage_callout_key_facts_458px240px.JPG
43 ms
icon-i-big.gif
40 ms
bg-white-transparent.png
40 ms
red-header.png
40 ms
top-nav.png
42 ms
btn-worldmap.png
43 ms
main-nav-sep.jpg
46 ms
search-btn.png
45 ms
double-helix.png
48 ms
lilly_carouselnav_sprite.png
47 ms
bg-nav-current.gif
47 ms
webtrends.hm.js
59 ms
wtid.js
152 ms
lilly.ca accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
lilly.ca best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
lilly.ca SEO score
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
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lilly.ca 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 Lilly.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.
lilly.ca
Open Graph description is not detected on the main page of Lilly. 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: