Report Summary

  • 28

    Performance

    Renders faster than
    49% of other websites

  • 98

    Accessibility

    Visual factors better than
    that of 95% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    57% of websites

  • 100

    SEO

    Google-friendlier than
    95% of websites

lilly.ca

Home | Lilly Canada

Page Load Speed

872 ms in total

First Response

51 ms

Resources Loaded

494 ms

Page Rendered

327 ms

lilly.ca screenshot

About Website

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

Key Findings

We 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 10% of websites can load faster.

Performance Metrics

lilly.ca performance score

28

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.9 s

53/100

10%

LCP (Largest Contentful Paint)

Value4.8 s

30/100

25%

SI (Speed Index)

Value5.9 s

48/100

10%

TBT (Total Blocking Time)

Value2,010 ms

7/100

30%

CLS (Cumulative Layout Shift)

Value0.313

37/100

15%

TTI (Time to Interactive)

Value10.6 s

23/100

10%

Network Requests Diagram

lilly.ca

51 ms

index.aspx

24 ms

styles.css

17 ms

jquery.fancybox-1.3.4.css

9 ms

fancybox.css

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 Optimization Overview & Recommendations

Page size can be reduced by 567.3 kB (36%)

Content Size

1.6 MB

After Optimization

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.

HTML Optimization

-87%

Potential reduce by 46.5 kB

  • Original 53.4 kB
  • After minification 36.3 kB
  • After compression 6.9 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.

Image Optimization

-5%

Potential reduce by 44.0 kB

  • Original 883.6 kB
  • After minification 839.6 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.

JavaScript Optimization

-70%

Potential reduce by 337.2 kB

  • Original 480.6 kB
  • After minification 414.4 kB
  • After compression 143.3 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.

CSS Optimization

-85%

Potential reduce by 139.6 kB

  • Original 164.9 kB
  • After minification 129.5 kB
  • After compression 25.3 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.

Requests Breakdown

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

Requests Now

43

After Optimization

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.

Accessibility Review

lilly.ca accessibility score

98

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

lilly.ca best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

lilly.ca SEO score

100

Search Engine Optimization Advices

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

    EN

  • Encoding

    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.

Social Sharing Optimization

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: