2.2 sec in total
260 ms
1.8 sec
151 ms
Welcome to lillenium.fr homepage info - get ready to check Lillenium best content right away, or after learning these important things about lillenium.fr
Visit lillenium.frWe analyzed Lillenium.fr page load time and found that the first response time was 260 ms and then it took 2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.
lillenium.fr performance score
name
value
score
weighting
Value2.6 s
65/100
10%
Value0
0/100
25%
Value3.7 s
85/100
10%
Value730 ms
41/100
30%
Value0.005
100/100
15%
Value9.8 s
28/100
10%
260 ms
34 ms
97 ms
50 ms
54 ms
Our browser made a total of 77 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Lillenium.fr, 42% (32 requests) were made to Static.parastorage.com and 12% (9 requests) were made to Frog.wix.com. The less responsive or slowest element that took the longest time to load (516 ms) relates to the external source Static.wixstatic.com.
Page size can be reduced by 2.1 MB (67%)
3.1 MB
1.1 MB
In fact, the total size of Lillenium.fr main page is 3.1 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. Javascripts take 2.8 MB which makes up the majority of the site volume.
Potential reduce by 476 B
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 164 B, which is 20% 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 476 B or 59% of the original size.
Potential reduce by 9.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. Lillenium images are well optimized though.
Potential reduce by 2.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 2.0 MB or 73% of the original size.
Potential reduce by 44.1 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. Lillenium.fr needs all CSS files to be minified and compressed as it can save up to 44.1 kB or 84% of the original size.
Number of requests can be reduced by 50 (70%)
71
21
The browser has sent 71 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Lillenium. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 38 to 1 for JavaScripts and as a result speed up the page load time.
lillenium.fr
260 ms
lillenium
34 ms
bt
97 ms
require.min.js
50 ms
main-r.min.js
54 ms
viewer.css
53 ms
dynamicmodel
35 ms
ee2a72_2ceb3744f035c9e4df415e5a23bf4b2e_59.json.z
482 ms
ee2a72_ab170dc33372b73cc6e714b6440f1354_59.json.z
465 ms
ugc-viewer
186 ms
bt
193 ms
skins.min.js
182 ms
components.min.js
57 ms
utils.min.js
55 ms
core.min.js
185 ms
react-with-addons.min.js
176 ms
lodash.min.js
35 ms
TweenMax.min.js
53 ms
layout.min.js
180 ms
tpa.min.js
177 ms
fonts.min.js
176 ms
animations.min.js
182 ms
swfobject.min.js
178 ms
mousetrap.min.js
179 ms
tweenEngine.min.js
181 ms
DrawSVGPlugin.min.js
183 ms
react-dom.min.js
183 ms
ScrollToPlugin.min.js
183 ms
widgets.min.js
184 ms
experiment.js
183 ms
render.min.js
184 ms
wixappsCore.min.js
185 ms
wixappsBuilder.min.js
183 ms
zepto.min.js
183 ms
color.min.js
183 ms
react-dom-server.min.js
43 ms
bt
110 ms
bt
259 ms
wf_label_static.png
129 ms
css
128 ms
latin.css
126 ms
ee2a72_ca37edb488b0a67873941270405fa013.html
173 ms
ee2a72_8c777c16298276e7b2dd274abce42390.html
344 ms
ee2a72_fdb0a2eee92bb514739c92eab8e7647d.html
340 ms
worker
163 ms
ee2a72_7c0bc3280d29453b8635f044805188fe.jpg
357 ms
da00086a27cc2c52ec7a11ec468c4d29.wix_mp
47 ms
ee2a72_c45731ffee7146ba866eb207626270de.jpg
325 ms
ee2a72_a55b37ecd92140609ccf54d81928ac7f.jpg
284 ms
ee2a72_1759e6bd469546398eb47c4da4ccc9d4.jpg
516 ms
3ba48f6dde3eec5c30a46f1337500f50.wix_mp
88 ms
bt
81 ms
bt
81 ms
bt
81 ms
BG91x1.jpg
80 ms
dc.js
112 ms
like.php
244 ms
wix.min.js
85 ms
router.js
23 ms
routing
161 ms
b76e826.js
83 ms
6d6de05.js
82 ms
oIwdBjO99oH_APMcy7EuWPesZW2xOQ-xsNqO47m55DA.ttf
156 ms
EcjpF2hW5gSZ4M16YLdG850EAVxt0G0biEntp43Qt6E.ttf
191 ms
__utm.gif
53 ms
adsbygoogle.js
25 ms
ga-audiences
63 ms
qeKvIRsJabD.js
366 ms
LVx-xkvaJ0b.png
401 ms
ca-pub-6607391482928793.js
182 ms
zrt_lookup.html
56 ms
show_ads_impl.js
56 ms
ugc-viewer
152 ms
ads
62 ms
ads
37 ms
osd.js
11 ms
hit.xiti
206 ms
lillenium.fr best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Page has valid source maps
Issues were logged in the Issues panel in Chrome Devtools
lillenium.fr SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Document doesn't have a <title> element
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
robots.txt is not valid
N/A
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lillenium.fr 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 Lillenium.fr 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.
lillenium.fr
Open Graph description is not detected on the main page of Lillenium. 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: