2.4 sec in total
163 ms
1.6 sec
686 ms
Visit lily.am now to see the best up-to-date Lily content and also check out these interesting facts you probably never knew about lily.am
Lily - Kids Interactive Table - Interactive Learning Games Multitouch - Waiting room furniture
Visit lily.amWe analyzed Lily.am page load time and found that the first response time was 163 ms and then it took 2.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
lily.am performance score
163 ms
72 ms
79 ms
33 ms
40 ms
Our browser made a total of 67 requests to load all elements on the main page. We found that 72% of them (48 requests) were addressed to the original Lily.am, 12% (8 requests) were made to Maps.googleapis.com and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (353 ms) relates to the external source Google.com.
Page size can be reduced by 1.3 MB (52%)
2.5 MB
1.2 MB
In fact, the total size of Lily.am main page is 2.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. 60% of websites need less resources to load. Javascripts take 1.4 MB which makes up the majority of the site volume.
Potential reduce by 8.8 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 8.8 kB or 66% of the original size.
Potential reduce by 35.8 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. Lily images are well optimized though.
Potential reduce by 1.0 MB
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 1.0 MB or 72% of the original size.
Potential reduce by 255.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. Lily.am needs all CSS files to be minified and compressed as it can save up to 255.2 kB or 82% of the original size.
Number of requests can be reduced by 26 (40%)
65
39
The browser has sent 65 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Lily. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 23 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
lily.am
163 ms
main_v2.css
72 ms
jquery-ui-1.10.3.custom.min.css
79 ms
pricing-table.css
33 ms
jquery.bxslider.css
40 ms
jquery-1.9.1.js
271 ms
jquery-ui-1.10.3.custom.min.js
220 ms
modernizr.js
89 ms
conditional.js
66 ms
polyfiller.js
125 ms
jquery.bxslider.min.js
99 ms
main.js
91 ms
analytics.js
28 ms
lily_logo_nav.png
109 ms
embed
353 ms
home_bg_small.jpg
229 ms
img_play.png
98 ms
img_learn.png
97 ms
img_engage.png
92 ms
icon_retail.png
77 ms
icon_hospitality.png
93 ms
icon_education.png
91 ms
icon_healthcare.png
106 ms
client_macdonalds.jpg
106 ms
client_td.jpg
106 ms
client_disney.jpg
119 ms
client_dell.jpg
123 ms
client_intel.jpg
122 ms
client_novotel.jpg
122 ms
client_sony.jpg
121 ms
client_atlantis.jpg
145 ms
client_sofitel.jpg
138 ms
client_lenovo.jpg
137 ms
App_numbers.jpg
137 ms
App_match.jpg
148 ms
App_words.jpg
154 ms
App_sudoku.jpg
153 ms
App_shape.jpg
193 ms
App_quiz.jpg
194 ms
App_airhockey.jpg
193 ms
App_curling.jpg
193 ms
social_fb.png
193 ms
social_twitter.png
214 ms
social_linkedin.png
217 ms
social_mail.png
212 ms
social_youtube.png
211 ms
collect
34 ms
mG8JkzN1Emo
102 ms
shim.css
163 ms
dom-extend.js
171 ms
geolocation.js
203 ms
www-embed-player-vflfNyN_r.css
87 ms
www-embed-player.js
119 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
25 ms
ad_status.js
107 ms
js
315 ms
init_embed.js
108 ms
widget_v2.134.js
17 ms
common.js
114 ms
map.js
159 ms
google4.png
99 ms
overlay.js
96 ms
util.js
149 ms
onion.js
148 ms
search_impl.js
148 ms
lily.am
126 ms
stats.js
50 ms
lily.am SEO score
N/A
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lily.am can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Lily.am 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.
lily.am
Open Graph description is not detected on the main page of Lily. 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: