5.1 sec in total
968 ms
3.8 sec
287 ms
Click here to check amazing Lil Ollo content. Otherwise, check out these important facts you probably never knew about lilollo.com
We create beautiful, fun and engaging products to help young language learners and their grown-ups. Lil’ollo is for you, whether you are speaking several languages fluently at home or just getting sta...
Visit lilollo.comWe analyzed Lilollo.com page load time and found that the first response time was 968 ms and then it took 4.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
lilollo.com performance score
name
value
score
weighting
Value5.4 s
6/100
10%
Value26.4 s
0/100
25%
Value16.4 s
0/100
10%
Value1,630 ms
12/100
30%
Value0.022
100/100
15%
Value26.4 s
0/100
10%
968 ms
79 ms
242 ms
223 ms
41 ms
Our browser made a total of 80 requests to load all elements on the main page. We found that 80% of them (64 requests) were addressed to the original Lilollo.com, 6% (5 requests) were made to Fonts.googleapis.com and 4% (3 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (968 ms) belongs to the original domain Lilollo.com.
Page size can be reduced by 196.5 kB (14%)
1.5 MB
1.3 MB
In fact, the total size of Lilollo.com main page is 1.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. 70% of websites need less resources to load. Javascripts take 713.8 kB which makes up the majority of the site volume.
Potential reduce by 96.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. 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 96.0 kB or 79% of the original size.
Potential reduce by 658 B
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. Lil Ollo images are well optimized though.
Potential reduce by 98.0 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 98.0 kB or 14% of the original size.
Potential reduce by 1.9 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. Lilollo.com has all CSS files already compressed.
Number of requests can be reduced by 65 (89%)
73
8
The browser has sent 73 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Lil Ollo. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 39 to 1 for JavaScripts and from 28 to 1 for CSS and as a result speed up the page load time.
lilollo.com
968 ms
fn3x1.css
79 ms
fn3x1.css
242 ms
fn3x1.css
223 ms
css
41 ms
fn3x1.css
226 ms
fn3x1.css
232 ms
fn3x1.css
235 ms
fn3x1.css
236 ms
fn3x1.css
295 ms
fn3x1.css
378 ms
fn3x1.css
308 ms
fn3x1.css
396 ms
fn3x1.css
402 ms
style.css
319 ms
fn3x1.css
367 ms
fn3x1.css
390 ms
css2
38 ms
css2
36 ms
css2
35 ms
fn3x1.css
407 ms
jquery.min.js
513 ms
jquery-migrate.min.js
449 ms
jquery.blockUI.min.js
459 ms
add-to-cart.min.js
460 ms
js.cookie.min.js
470 ms
woocommerce.min.js
472 ms
woocommerce-add-to-cart.js
529 ms
ultimate-params.min.js
535 ms
jquery-appear.min.js
536 ms
custom.min.js
548 ms
sweetalert2.min.js
272 ms
sweetalert2.min.css
464 ms
promise.min.js
41 ms
classic-10_7.css
32 ms
mc-validate.js
55 ms
css
44 ms
fn3x1.css
629 ms
fn5ad.css
630 ms
fn5ad.css
630 ms
fn3x1.css
630 ms
fn3x1.css
630 ms
rbtools.min.js
737 ms
rs6.min.js
738 ms
sourcebuster.min.js
706 ms
order-attribution.min.js
705 ms
mailchimp-woocommerce-public.min.js
705 ms
info-box.min.js
641 ms
gsap.min.js
600 ms
ScrollToPlugin.min.js
597 ms
ScrollMagic.min.js
590 ms
animation.gsap.min.js
588 ms
main.js
586 ms
cart-fragments.min.js
563 ms
js_composer_front.min.js
601 ms
isotope.pkgd.min.js
592 ms
packery-mode.pkgd.min.js
580 ms
imagesloaded.pkgd.min.js
526 ms
underscore.min.js
507 ms
vc-waypoints.min.js
506 ms
vc_grid.min.js
553 ms
video.min.js
763 ms
video-js-youtube.js
543 ms
player.min.js
519 ms
main.min.js
517 ms
Lilollo-Logo-Final.png
379 ms
dummy.png
434 ms
global-local-earth-day-activities-1024x455.jpg
704 ms
Pandemic-Adventure-Pack-top-image-copy-1024x455.jpg
703 ms
Childrens_mental_health-1024x455.jpg
457 ms
lillolo-logo-e1519660701958.png
462 ms
S6uyw4BMUTPHvxo.woff
75 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVQ.woff
76 ms
linea.woff
461 ms
bc067f3ba4d17e2cdc003ac81.js
108 ms
Defaults.woff
414 ms
sdk.js
86 ms
KFOmCnqEu92Fr1Mu4mxM.woff
21 ms
fa-brands-400.ttf
464 ms
sdk.js
21 ms
lilollo.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
lilollo.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
lilollo.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lilollo.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 Lilollo.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.
lilollo.com
Open Graph data is detected on the main page of Lil Ollo. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: