3.8 sec in total
352 ms
3.2 sec
263 ms
Welcome to lillian-too.com homepage info - get ready to check Lillian Too best content for Russia right away, or after learning these important things about lillian-too.com
Lillian Too's Official Website
Visit lillian-too.comWe analyzed Lillian-too.com page load time and found that the first response time was 352 ms and then it took 3.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
lillian-too.com performance score
name
value
score
weighting
Value2.3 s
74/100
10%
Value2.4 s
91/100
25%
Value3.6 s
87/100
10%
Value0 ms
100/100
30%
Value0.095
91/100
15%
Value2.5 s
98/100
10%
352 ms
1547 ms
1691 ms
36 ms
120 ms
Our browser made a total of 54 requests to load all elements on the main page. We found that 94% of them (51 requests) were addressed to the original Lillian-too.com, 4% (2 requests) were made to Google-analytics.com and 2% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Lillian-too.com.
Page size can be reduced by 176.5 kB (28%)
624.8 kB
448.3 kB
In fact, the total size of Lillian-too.com main page is 624.8 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. 20% of websites need less resources to load. Images take 410.5 kB which makes up the majority of the site volume.
Potential reduce by 42.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. This page needs HTML code to be minified as it can gain 30.6 kB, which is 66% 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 42.1 kB or 91% of the original size.
Potential reduce by 25.4 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. Lillian Too images are well optimized though.
Potential reduce by 106.6 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 106.6 kB or 65% of the original size.
Potential reduce by 2.4 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. Lillian-too.com needs all CSS files to be minified and compressed as it can save up to 2.4 kB or 75% of the original size.
Number of requests can be reduced by 22 (42%)
53
31
The browser has sent 53 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Lillian Too. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 6 to 1 for JavaScripts and as a result speed up the page load time.
lillian-too.com
352 ms
ltstyle.css
1547 ms
prototype.js
1691 ms
jquery.min.js
36 ms
index.html
120 ms
logo.jpg
103 ms
topnavi_home.jpg
103 ms
topnavi_faq.jpg
129 ms
topnavi_guestbook.jpg
151 ms
bg_navline.jpg
149 ms
mnavi_left.jpg
797 ms
mnavi_meetlillian.jpg
799 ms
mnavi_whatsnew.jpg
797 ms
mnavi_seminars.jpg
200 ms
mnavi_books.jpg
220 ms
mnavi_news.jpg
221 ms
mnavi_fstips.jpg
270 ms
mnavi_aboutfs.jpg
293 ms
mnavi_right.jpg
293 ms
cnt_bg_2col.gif
343 ms
tit_main_latest.jpg
365 ms
tit_main_courses.jpg
367 ms
fs_interior_2016.jpg
414 ms
btn_readmore.jpg
438 ms
cnt_div.gif
439 ms
horoscope_2016_thumb.jpg
487 ms
bnr_main_mpc2014.jpg
512 ms
bnr_lt_sfs2016_side.jpg
664 ms
facebook_badge01.jpg
560 ms
ltmandala.jpg
586 ms
rightbnr_fsw_ipad02.jpg
634 ms
sidebnr_lilliantoday.jpg
732 ms
btn_viewphotos.jpg
707 ms
tit_side_lillianlinks.jpg
736 ms
bullet_red.gif
778 ms
footer_bg.gif
805 ms
footer_home.jpg
808 ms
footer_meetlillian.jpg
850 ms
footer_whatsnew.jpg
857 ms
ga.js
29 ms
footer_seminars.jpg
849 ms
__utm.gif
12 ms
banner_slides.css
773 ms
jquery.min.js
864 ms
jquery.easing.1.3.js
792 ms
slides.min.jquery.js
807 ms
footer_books.jpg
795 ms
footer_news.jpg
795 ms
footer_fstips.jpg
746 ms
footer_aboutfs.jpg
765 ms
footer_faq.jpg
786 ms
footer_guestbook.jpg
745 ms
footer_copyright.jpg
724 ms
bnr_ltcom_3d16.jpg
246 ms
lillian-too.com 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
Links do not have a discernible name
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
lillian-too.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
lillian-too.com 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
N/A
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lillian-too.com 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) and no language is claimed in <html> or <meta> tags either. Our system also found out that Lillian-too.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.
lillian-too.com
Open Graph description is not detected on the main page of Lillian Too. 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: