736 ms in total
60 ms
465 ms
211 ms
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.comWe analyzed Lillypatientone.com page load time and found that the first response time was 60 ms and then it took 676 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.
lillypatientone.com performance score
name
value
score
weighting
Value4.7 s
13/100
10%
Value6.8 s
7/100
25%
Value4.9 s
65/100
10%
Value370 ms
71/100
30%
Value1
2/100
15%
Value7.4 s
48/100
10%
60 ms
32 ms
11 ms
10 ms
13 ms
Our browser made a total of 34 requests to load all elements on the main page. We found that 76% of them (26 requests) were addressed to the original Lillypatientone.com, 6% (2 requests) were made to Maxcdn.bootstrapcdn.com and 6% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (226 ms) relates to the external source Statse.webtrendslive.com.
Page size can be reduced by 304.4 kB (29%)
1.1 MB
763.6 kB
In fact, the total size of Lillypatientone.com main page is 1.1 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. 20% of websites need less resources to load. Images take 661.2 kB which makes up the majority of the site volume.
Potential reduce by 20.3 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 6.0 kB, which is 23% 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 20.3 kB or 78% of the original size.
Potential reduce by 1.2 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.
Potential reduce by 137.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 137.9 kB or 65% of the original size.
Potential reduce by 145.1 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 145.1 kB or 87% of the original size.
Number of requests can be reduced by 12 (41%)
29
17
The browser has sent 29 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 10 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
lillypatientone.com
60 ms
main.css
32 ms
modernizr.min.js
11 ms
respond.min.js
10 ms
css
13 ms
font-awesome.min.css
6 ms
jquery.min.js
19 ms
core.js
11 ms
webtrends.load.js
12 ms
gtm.js
148 ms
webtrends.min.js
84 ms
search_bg.png
15 ms
patient_one_red_white.svg
17 ms
bg_hcp_index.jpg
83 ms
phone_bg.png
15 ms
brick_one_ico.png
16 ms
box_shadow_brick.png
15 ms
brick_three_ico.png
21 ms
brick_two_ico.png
23 ms
helpful_link.png
23 ms
helpful_link_arrow.png
22 ms
icon-i-big.gif
24 ms
phone_bg_white.png
33 ms
lilly-oncology.svg
30 ms
popup-close_bg.png
29 ms
HelveticaNeueW01-55Roma.woff
36 ms
HelveticaNeueW01-45Ligh.woff
46 ms
HelveticaNeueW01-75Bold.woff
52 ms
fontawesome-webfont.woff
8 ms
webtrends.hm.js
75 ms
wtid.js
226 ms
analytics.js
5 ms
collect
10 ms
print.css
6 ms
lillypatientone.com 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.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
lillypatientone.com 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
Missing source maps for large first-party JavaScript
lillypatientone.com 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 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.
lillypatientone.com
Open Graph description is not detected on the main page of Lilly Patientone. 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: