4.7 sec in total
180 ms
3.7 sec
871 ms
Click here to check amazing Lila Story content. Otherwise, check out these important facts you probably never knew about lilastory.com
Lila Martinez Animation Storyboard Director Portfolio
Visit lilastory.comWe analyzed Lilastory.com page load time and found that the first response time was 180 ms and then it took 4.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
lilastory.com performance score
name
value
score
weighting
Value3.7 s
30/100
10%
Value14.6 s
0/100
25%
Value12.0 s
4/100
10%
Value140 ms
95/100
30%
Value0.063
97/100
15%
Value10.3 s
25/100
10%
180 ms
170 ms
96 ms
32 ms
82 ms
Our browser made a total of 151 requests to load all elements on the main page. We found that 97% of them (147 requests) were addressed to the original Lilastory.com, 1% (2 requests) were made to Fonts.googleapis.com and 1% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (785 ms) belongs to the original domain Lilastory.com.
Page size can be reduced by 576.1 kB (10%)
5.8 MB
5.3 MB
In fact, the total size of Lilastory.com main page is 5.8 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. 85% 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 5.6 MB which makes up the majority of the site volume.
Potential reduce by 52.2 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 23.2 kB, which is 40% 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 52.2 kB or 91% of the original size.
Potential reduce by 494.1 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. Lila Story images are well optimized though.
Potential reduce by 17.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 17.4 kB or 19% of the original size.
Potential reduce by 12.5 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. Lilastory.com needs all CSS files to be minified and compressed as it can save up to 12.5 kB or 36% of the original size.
Number of requests can be reduced by 34 (23%)
145
111
The browser has sent 145 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Lila Story. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 19 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.
lilastory.com
180 ms
site
170 ms
96 ms
css
32 ms
skeleton.css
82 ms
reset.css
149 ms
style.css
160 ms
social.css
158 ms
flexslider.css
162 ms
prettyPhoto.css
163 ms
font-awesome.css
164 ms
shortcodes.css
226 ms
media.css
238 ms
mediumaquamarine.css
244 ms
jquery.min.js
23 ms
jquery.form.js
237 ms
jquery.queryloader2.js
234 ms
modernizr-2.6.2.min.js
302 ms
jquery.fitvids.js
315 ms
jquery.appear.js
315 ms
jquery.slabtext.min.js
316 ms
jquery.fittext.js
315 ms
jquery.easing.min.js
319 ms
jquery.parallax-1.1.3.js
375 ms
jquery.prettyPhoto.js
394 ms
jquery.sticky.js
395 ms
selectnav.min.js
396 ms
SmoothScroll.js
400 ms
jquery.flexslider-min.js
399 ms
isotope.js
459 ms
bootstrap-modal.js
498 ms
shortcodes.js
500 ms
scripts.js
501 ms
logo_logo.png
553 ms
portfolio02_40.jpg
777 ms
portfolio02_44.jpg
679 ms
portfolio02_39.jpg
758 ms
portfolio02_41.jpg
697 ms
portfolio02_42.jpg
703 ms
portfolio02_43.jpg
785 ms
portfolio02_35.jpg
752 ms
portfolio02_34.jpg
637 ms
portfolio02_36.jpg
707 ms
css
16 ms
portfolio02_37.jpg
754 ms
portfolio02_38.jpg
704 ms
portfolio02_30.jpg
707 ms
portfolio02_31.jpg
708 ms
portfolio02_29.jpg
758 ms
portfolio02_32.jpg
783 ms
portfolio02_28.jpg
712 ms
portfolio02_27.jpg
717 ms
portfolio02_22.jpg
715 ms
portfolio02_21.jpg
694 ms
BebasNeue-webfont.woff
724 ms
TK3_WkUHHAIjg75cFRf3bXL8LICs1_FvsUZiYA.ttf
18 ms
fontawesome-webfont.woff
727 ms
portfolio02_23.jpg
726 ms
portfolio02_24.jpg
751 ms
portfolio02_19.jpg
756 ms
portfolio02_16.jpg
778 ms
portfolio02_20.jpg
739 ms
portfolio02_13.jpg
716 ms
portfolio02_17.jpg
715 ms
portfolio02_18.jpg
741 ms
portfolio02_07.jpg
754 ms
portfolio01_05.jpg
777 ms
portfolio02_01.jpg
694 ms
portfolio01_06.jpg
690 ms
client18.png
461 ms
client17.png
477 ms
client16.png
483 ms
client14.png
484 ms
client19.png
483 ms
client15.png
476 ms
client10.png
465 ms
client20.png
475 ms
client4.png
486 ms
client5.png
486 ms
client12.png
483 ms
logo_white.png
481 ms
homewall.jpg
674 ms
loader.gif
470 ms
parallax_ref.jpg
561 ms
pattern.png
483 ms
parallax_rep.jpg
562 ms
mail.png
481 ms
email.png
520 ms
twitter.png
492 ms
instagram.png
486 ms
imdb.png
534 ms
linkedin.png
558 ms
backtotop.png
558 ms
homewall.jpg
696 ms
logo_logo.png
493 ms
loader.gif
533 ms
portfolio02_40.jpg
531 ms
portfolio02_44.jpg
561 ms
portfolio02_39.jpg
559 ms
portfolio02_41.jpg
552 ms
portfolio02_42.jpg
539 ms
portfolio02_43.jpg
527 ms
portfolio02_35.jpg
562 ms
portfolio02_34.jpg
560 ms
portfolio02_37.jpg
564 ms
portfolio02_36.jpg
597 ms
portfolio02_38.jpg
536 ms
portfolio02_30.jpg
552 ms
portfolio02_31.jpg
563 ms
portfolio02_28.jpg
560 ms
portfolio02_29.jpg
557 ms
portfolio02_32.jpg
593 ms
portfolio02_27.jpg
538 ms
portfolio02_22.jpg
550 ms
portfolio02_21.jpg
556 ms
portfolio02_23.jpg
559 ms
portfolio02_19.jpg
560 ms
portfolio02_24.jpg
536 ms
portfolio02_16.jpg
512 ms
portfolio02_20.jpg
549 ms
portfolio02_13.jpg
505 ms
portfolio02_07.jpg
483 ms
portfolio02_17.jpg
486 ms
portfolio02_18.jpg
508 ms
portfolio01_05.jpg
506 ms
portfolio02_01.jpg
500 ms
portfolio01_06.jpg
513 ms
client14.png
483 ms
client18.png
483 ms
client16.png
505 ms
client17.png
471 ms
client19.png
500 ms
client10.png
483 ms
parallax_ref.jpg
483 ms
client20.png
483 ms
pattern.png
459 ms
client15.png
468 ms
client4.png
481 ms
client5.png
488 ms
client12.png
481 ms
parallax_rep.jpg
556 ms
logo_white.png
459 ms
mail.png
468 ms
email.png
478 ms
twitter.png
483 ms
imdb.png
482 ms
linkedin.png
491 ms
instagram.png
473 ms
backtotop.png
513 ms
arrow_left.png
87 ms
arrow_right.png
86 ms
lilastory.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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Some elements have a [tabindex] value greater than 0
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
lilastory.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
lilastory.com SEO score
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
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lilastory.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Lilastory.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.
lilastory.com
Open Graph description is not detected on the main page of Lila Story. 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: