Tools & Wizards About Us
lillypad.lilly.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

lillypad.lilly.com

Lilly.com | Eli Lilly and Company

Page Load Speed

12.1 sec in total

First Response

1.5 sec

Resources Loaded

10 sec

Page Rendered

535 ms

lillypad.lilly.com screenshot

About Website

Visit lillypad.lilly.com now to see the best up-to-date Lilly Pad content for India and also check out these interesting facts you probably never knew about lillypad.lilly.com

Lilly unites caring with discovery to create medicines that make life better for people around the world.

Visit lillypad.lilly.com

Key Findings

We analyzed Lillypad.lilly.com page load time and found that the first response time was 1.5 sec and then it took 10.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

lillypad.lilly.com performance score

0

Network Requests Diagram

lillypad.lilly.com

1530 ms

css

23 ms

magnific-popup.css

91 ms

sstyle-refresh.css

239 ms

modernizr-2.6.2.min.js

95 ms

Our browser made a total of 80 requests to load all elements on the main page. We found that 68% of them (54 requests) were addressed to the original Lillypad.lilly.com, 4% (3 requests) were made to Stats.g.doubleclick.net and 4% (3 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (8 sec) belongs to the original domain Lillypad.lilly.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.6 MB (15%)

Content Size

10.2 MB

After Optimization

8.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Lillypad.lilly.com main page is 10.2 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. 50% of websites need less resources to load. Images take 9.0 MB which makes up the majority of the site volume.

HTML Optimization

-91%

Potential reduce by 213.4 kB

  • Original 235.3 kB
  • After minification 235.0 kB
  • After compression 21.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. 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 213.4 kB or 91% of the original size.

Image Optimization

-8%

Potential reduce by 683.0 kB

  • Original 9.0 MB
  • After minification 8.3 MB

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 Pad images are well optimized though.

JavaScript Optimization

-67%

Potential reduce by 388.3 kB

  • Original 578.7 kB
  • After minification 501.8 kB
  • After compression 190.4 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 388.3 kB or 67% of the original size.

CSS Optimization

-91%

Potential reduce by 287.7 kB

  • Original 316.5 kB
  • After minification 179.1 kB
  • After compression 28.8 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. Lillypad.lilly.com needs all CSS files to be minified and compressed as it can save up to 287.7 kB or 91% of the original size.

Requests Breakdown

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

Requests Now

72

After Optimization

36

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

lillypad.lilly.com

lillypad.lilly.com

1530 ms

css

css

23 ms

magnific-popup.css

magnific-popup.css

91 ms

sstyle-refresh.css

sstyle-refresh.css

239 ms

modernizr-2.6.2.min.js

modernizr-2.6.2.min.js

95 ms

jquery-1.10.2.min.js

jquery-1.10.2.min.js

175 ms

jquery-migrate-1.2.1.js

jquery-migrate-1.2.1.js

142 ms

jquery.magnific-popup.min.js

jquery.magnific-popup.min.js

150 ms

foundation.js

foundation.js

157 ms

foundation.dropdown.js

foundation.dropdown.js

158 ms

foundation.forms.js

foundation.forms.js

222 ms

foundation.section.modified.js

foundation.section.modified.js

226 ms

foundation.topbar.js

foundation.topbar.js

248 ms

chosen.jquery.min.js

chosen.jquery.min.js

249 ms

foundation.reveal.js

foundation.reveal.js

248 ms

wpbase.js

wpbase.js

378 ms

history.js

history.js

371 ms

underscore.js

underscore.js

373 ms

masonry.pkgd.min.js

masonry.pkgd.min.js

371 ms

velocity.min.js

velocity.min.js

373 ms

imagesloaded.pkgd.min.js

imagesloaded.pkgd.min.js

374 ms

placeholders.min.js

placeholders.min.js

375 ms

oct.js

oct.js

3 ms

conversion.js

conversion.js

21 ms

css

css

19 ms

dc.js

dc.js

99 ms

analytics.js

analytics.js

97 ms

LillyPad_Lilly.png

LillyPad_Lilly.png

75 ms

Boxing-Ring_608x608.jpg

Boxing-Ring_608x608.jpg

787 ms

Lilly_RareDisease2016_Featured.jpg

Lilly_RareDisease2016_Featured.jpg

671 ms

RD_tile-642x642.png

RD_tile-642x642.png

1103 ms

Mars-Thinkstock.jpg

Mars-Thinkstock.jpg

2775 ms

GoldenStatuettes.jpg

GoldenStatuettes.jpg

2855 ms

OperationsManager_FeaturedImage.jpg

OperationsManager_FeaturedImage.jpg

1175 ms

Diversity-hexagons-642x642.png

Diversity-hexagons-642x642.png

2693 ms

EU-chambers.jpg

EU-chambers.jpg

1077 ms

LillyChemist3.jpg

LillyChemist3.jpg

2406 ms

LuWanna-3.png

LuWanna-3.png

2029 ms

CHA-Ambassador-With-Child-2015-crop.png

CHA-Ambassador-With-Child-2015-crop.png

2753 ms

ed-title.png

ed-title.png

4942 ms

ChildrenWithFlowers.jpg

ChildrenWithFlowers.jpg

4674 ms

LillyScientist1.jpg

LillyScientist1.jpg

3228 ms

RyanReed.jpg

RyanReed.jpg

4352 ms

Tile-Image_642x642_V2.jpg

Tile-Image_642x642_V2.jpg

4482 ms

WCDWrapUpCollage2-642x642.jpg

WCDWrapUpCollage2-642x642.jpg

3635 ms

Drug-Discovery-by-the-Numbers-Thumbnail_608x608.jpg

Drug-Discovery-by-the-Numbers-Thumbnail_608x608.jpg

7034 ms

LillyEngineer1.jpg

LillyEngineer1.jpg

4668 ms

Grandpa-standard-image-642x642.jpg

Grandpa-standard-image-642x642.jpg

5167 ms

Lilly_WCD-Hand-A_v1-642x642.jpg

Lilly_WCD-Hand-A_v1-642x642.jpg

5231 ms

70-642x642.jpg

70-642x642.jpg

5385 ms

TB-in-Russia.jpg

TB-in-Russia.jpg

6670 ms

Thinkstock_Meeting-Of-Support-Group.jpg

Thinkstock_Meeting-Of-Support-Group.jpg

5886 ms

Lilly-Espana-welcome.png

Lilly-Espana-welcome.png

6249 ms

CarrieFishersFamily.jpg

CarrieFishersFamily.jpg

8000 ms

Thinkstock_Radio-Announcer.jpg

Thinkstock_Radio-Announcer.jpg

7541 ms

WhoWeAre_Investigator.jpg

WhoWeAre_Investigator.jpg

6881 ms

Quality_FionnulaWalsh.jpg

Quality_FionnulaWalsh.jpg

7152 ms

1-02-642x642.png

1-02-642x642.png

7950 ms

9k-RPmcnxYEPm8CNFsH2gg.woff

9k-RPmcnxYEPm8CNFsH2gg.woff

72 ms

wkfQbvfT_02e2IWO3yYueQ.woff

wkfQbvfT_02e2IWO3yYueQ.woff

76 ms

jObgDQiPUtmACAaaK3pMGz8E0i7KZn-EPnyo3HZu7kw.woff

jObgDQiPUtmACAaaK3pMGz8E0i7KZn-EPnyo3HZu7kw.woff

77 ms

aleo-regular-webfont.woff

aleo-regular-webfont.woff

7728 ms

lilly.woff

lilly.woff

7740 ms

collect

collect

37 ms

collect

collect

115 ms

__utm.gif

__utm.gif

28 ms

sdk.js

sdk.js

239 ms

widgets.js

widgets.js

20 ms

adsct

adsct

183 ms

adsct

adsct

117 ms

insight.min.js

insight.min.js

111 ms

fbevents.js

fbevents.js

167 ms

143 ms

61 ms

59 ms

xd_arbiter.php

xd_arbiter.php

154 ms

xd_arbiter.php

xd_arbiter.php

277 ms

24 ms

47 ms

12 ms

SEO Factors

lillypad.lilly.com SEO score

0

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 Lillypad.lilly.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 Lillypad.lilly.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

lillypad.lilly.com

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