Tools & Wizards About Us
lillypatientone.com screenshot

Report Summary

  • 30

    Performance

    Renders faster than
    50% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 61% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

lillypatientone.com

Financial Assistance Options | Lilly Oncology Support Center

Page Load Speed

1.3 sec in total

First Response

35 ms

Resources Loaded

1 sec

Page Rendered

208 ms

lillypatientone.com screenshot

About Website

Click here to check amazing Lilly Patientone content. Otherwise, check out these important facts you probably never knew about lillypatientone.com

Learn more about financial assistance options, reimbursement, savings card programs and more for qualifying patients through the Lilly Oncology Support Center.

Visit lillypatientone.com

Key Findings

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

Performance Metrics

lillypatientone.com performance score

30

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.7 s

2/100

10%

LCP (Largest Contentful Paint)

Value7.5 s

4/100

25%

SI (Speed Index)

Value6.7 s

36/100

10%

TBT (Total Blocking Time)

Value820 ms

35/100

30%

CLS (Cumulative Layout Shift)

Value0.163

72/100

15%

TTI (Time to Interactive)

Value8.5 s

38/100

10%

Network Requests Diagram

lillypatientone.com

35 ms

oncologysupport.lilly.com

242 ms

syrenis-cookie-management.css

55 ms

gtm.js

62 ms

loader.js

109 ms

Our browser made a total of 20 requests to load all elements on the main page. We found that 5% of them (1 request) were addressed to the original Lillypatientone.com, 75% (15 requests) were made to Oncologysupport.lilly.com and 10% (2 requests) were made to Dscrutpyu4zff.cloudfront.net. The less responsive or slowest element that took the longest time to load (649 ms) relates to the external source Oncologysupport.lilly.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 106.5 kB (19%)

Content Size

567.0 kB

After Optimization

460.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Lillypatientone.com main page is 567.0 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. 25% of websites need less resources to load. Images take 465.1 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 32.8 kB

  • Original 41.9 kB
  • After minification 40.6 kB
  • After compression 9.1 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 32.8 kB or 78% of the original size.

Image Optimization

-6%

Potential reduce by 28.8 kB

  • Original 465.1 kB
  • After minification 436.3 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 Patientone images are well optimized though.

JavaScript Optimization

-73%

Potential reduce by 35.2 kB

  • Original 48.1 kB
  • After minification 48.1 kB
  • After compression 12.9 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 35.2 kB or 73% of the original size.

CSS Optimization

-82%

Potential reduce by 9.6 kB

  • Original 11.8 kB
  • After minification 10.0 kB
  • After compression 2.2 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. Lillypatientone.com needs all CSS files to be minified and compressed as it can save up to 9.6 kB or 82% of the original size.

Requests Breakdown

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

Requests Now

14

After Optimization

7

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

lillypatientone.com

lillypatientone.com

35 ms

oncologysupport.lilly.com

oncologysupport.lilly.com

242 ms

syrenis-cookie-management.css

syrenis-cookie-management.css

55 ms

gtm.js

gtm.js

62 ms

loader.js

loader.js

109 ms

syrenis-cookie-management.js

syrenis-cookie-management.js

152 ms

08c9f8d.css

08c9f8d.css

230 ms

47a483f.css

47a483f.css

341 ms

939182f.js

939182f.js

129 ms

ac5e57b.js

ac5e57b.js

112 ms

57e75ed.js

57e75ed.js

192 ms

d4e4214.js

d4e4214.js

560 ms

e49bd4f.js

e49bd4f.js

416 ms

h-0_lilly-oncology-support.jpg

h-0_lilly-oncology-support.jpg

503 ms

h-0_choose-product.jpg

h-0_choose-product.jpg

649 ms

privacyoptions.png

privacyoptions.png

546 ms

roboto-v18-latin-regular.bafb105.woff

roboto-v18-latin-regular.bafb105.woff

171 ms

roboto-v18-latin-500.de8b743.woff

roboto-v18-latin-500.de8b743.woff

127 ms

roboto-v18-latin-300.a1471d1.woff

roboto-v18-latin-300.a1471d1.woff

262 ms

roboto-v18-latin-700.cf6613d.woff

roboto-v18-latin-700.cf6613d.woff

311 ms

Accessibility Review

lillypatientone.com accessibility score

86

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.

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

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best Practices

lillypatientone.com best practices score

92

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

Missing source maps for large first-party JavaScript

SEO Factors

lillypatientone.com SEO score

90

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

Image elements do not have [alt] attributes

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lillypatientone.com 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 Lillypatientone.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

lillypatientone.com

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