1.4 sec in total
116 ms
938 ms
341 ms
Welcome to lilly.es homepage info - get ready to check Lilly best content for Spain right away, or after learning these important things about lilly.es
Página de Inicio de Lilly España
Visit lilly.esWe analyzed Lilly.es page load time and found that the first response time was 116 ms and then it took 1.3 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.
lilly.es performance score
name
value
score
weighting
Value3.7 s
29/100
10%
Value5.6 s
17/100
25%
Value6.5 s
39/100
10%
Value2,720 ms
3/100
30%
Value0.425
22/100
15%
Value22.7 s
1/100
10%
116 ms
17 ms
12 ms
8 ms
9 ms
Our browser made a total of 56 requests to load all elements on the main page. We found that 88% of them (49 requests) were addressed to the original Lilly.es, 7% (4 requests) were made to Eucookie.xh1.lilly.com and 4% (2 requests) were made to Statse.webtrendslive.com. The less responsive or slowest element that took the longest time to load (162 ms) relates to the external source Eucookie.xh1.lilly.com.
Page size can be reduced by 789.6 kB (22%)
3.5 MB
2.8 MB
In fact, the total size of Lilly.es main page is 3.5 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 2.7 MB which makes up the majority of the site volume.
Potential reduce by 59.0 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.2 kB, which is 25% 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 59.0 kB or 87% of the original size.
Potential reduce by 165.7 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 421.7 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 421.7 kB or 70% of the original size.
Potential reduce by 143.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. Lilly.es needs all CSS files to be minified and compressed as it can save up to 143.2 kB or 84% of the original size.
Number of requests can be reduced by 21 (39%)
54
33
The browser has sent 54 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 13 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
lilly.es
116 ms
index.aspx
17 ms
styles.css
12 ms
jquery.fancybox-1.3.4.css
8 ms
fancybox.css
9 ms
site.css
20 ms
core.css
21 ms
jquery-1.8.2.min.js
24 ms
init.js
22 ms
jquery.fancybox-1.3.4.pack.js
22 ms
site.js
32 ms
EUCookiesScript.js
122 ms
jquery-1.7.1.min.js
27 ms
jquery.tools.min.js
30 ms
lilly.js
29 ms
MobileOptimization.js
29 ms
tablet.landscape.css
15 ms
tablet.portrait.css
13 ms
mobile.landscape.css
17 ms
mobile.portrait.css
16 ms
bg-grid.jpg
161 ms
jquery.min.js
162 ms
webtrends.js
113 ms
lilly-logo.png
22 ms
lilly2.jpg
24 ms
datos-clave.jpg
24 ms
fundacionlilly_callout_215x101.jpg
21 ms
call-out-memoria-rsc-210-x-100.jpg
26 ms
nuestrosmedicamentos.jpg
26 ms
lillyhistoriaterapeutica_callout.jpg
25 ms
lainvestigacionclinica_callout.jpg
27 ms
fomentodelainvestigacin_callout.jpg
27 ms
diabetes_callout_210x100.jpg
71 ms
neurociencias_callout_210x100.jpg
54 ms
carrousel1.jpg
63 ms
carrousel3_2.jpg
64 ms
voluntariado_lilly_home.jpg
86 ms
lillypades-210x100.jpg
54 ms
twitter.jpg
55 ms
callout_emprendeinhealth_210x100px.jpg
60 ms
farmaindustria-210x100.jpg
60 ms
icon-i-big.gif
64 ms
bg-white-transparent.png
63 ms
red-header.png
69 ms
top-nav.png
73 ms
btn-worldmap.png
72 ms
main-nav-sep.jpg
70 ms
search-btn.png
70 ms
double-helix.png
71 ms
asset_upload_file267_562469.jpg
94 ms
lilly_carouselnav_sprite.png
72 ms
webtrends.hm.js
24 ms
wtid.js
153 ms
GetBanner
102 ms
dcs.gif
152 ms
EUCookiesStylesheet.css
35 ms
lilly.es accessibility score
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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
lilly.es 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.es SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
ES
ES
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lilly.es can be misinterpreted by Google and other search engines. Our service has detected that Spanish is used on the page, and it matches the claimed language. Our system also found out that Lilly.es 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.es
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: