5.7 sec in total
448 ms
4.9 sec
318 ms
Welcome to lilio.pl homepage info - get ready to check LILIO best content for Poland right away, or after learning these important things about lilio.pl
Ręcznie robione prezenty, dodatki i dekoracje do domu - piękne rękodzieło robione w Polsce - figurki dekoracyjne aniołów, bombki choinkowe.
Visit lilio.plWe analyzed Lilio.pl page load time and found that the first response time was 448 ms and then it took 5.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
lilio.pl performance score
name
value
score
weighting
Value4.3 s
18/100
10%
Value8.6 s
1/100
25%
Value10.1 s
9/100
10%
Value6,550 ms
0/100
30%
Value0
100/100
15%
Value26.6 s
0/100
10%
448 ms
483 ms
1441 ms
45 ms
643 ms
Our browser made a total of 94 requests to load all elements on the main page. We found that 36% of them (34 requests) were addressed to the original Lilio.pl, 11% (10 requests) were made to Cdn.listagram.com and 9% (8 requests) were made to Embed.tawk.to. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Lilio.pl.
Page size can be reduced by 2.5 MB (74%)
3.3 MB
882.9 kB
In fact, the total size of Lilio.pl main page is 3.3 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. 75% 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. HTML takes 2.4 MB which makes up the majority of the site volume.
Potential reduce by 2.4 MB
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 2.2 MB, which is 92% 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 2.4 MB or 98% of the original size.
Potential reduce by 51.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. Obviously, LILIO needs image optimization as it can save up to 51.8 kB or 21% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 26.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. This website has mostly compressed JavaScripts.
Potential reduce by 2.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. Lilio.pl has all CSS files already compressed.
Number of requests can be reduced by 49 (74%)
66
17
The browser has sent 66 CSS, Javascripts, AJAX and image requests in order to completely render the main page of LILIO. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 33 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
lilio.pl
448 ms
lilio.pl
483 ms
www.lilio.pl
1441 ms
css2
45 ms
inpost-geowidget.css
643 ms
inpost-geowidget.js
860 ms
js
79 ms
93d3a2eb562c41a4af1eafcd6c8f7025.css
419 ms
api.js
50 ms
jquery.min.js
34 ms
jquery-ui.min.js
47 ms
jquery.lazy.min.js
62 ms
jquery.lazy.plugins.min.js
63 ms
photoswipe.min.js
63 ms
photoswipe-ui-default.min.js
62 ms
463fb6fecc637b74c1645b1858528226.js
424 ms
fbevents.js
140 ms
gtm.js
139 ms
recaptcha__en.js
181 ms
93d3a2eb562c41a4af1eafcd6c8f7025.css
350 ms
coin.svg
148 ms
phone.svg
320 ms
mail.svg
447 ms
aHR0cHM6Ly93d3cubGlsaW8ucGwvZmlsZXMvc2xpZGVyeS1ob21lL3NsaWRlci1ob21lLW1vYi5qcGc=.webp
680 ms
aHR0cHM6Ly93d3cubGlsaW8ucGwvZmlsZXMvYWRtaW4vb3BpbmllL2thdGFyenluYS1ncm9jaG93c2thLmpwZw==.webp
509 ms
aHR0cHM6Ly93d3cubGlsaW8ucGwvZmlsZXMvYWRtaW4vb3BpbmllL21hcnplbmEtcGx1dGEuanBn.webp
447 ms
aHR0cHM6Ly93d3cubGlsaW8ucGwvZmlsZXMvYWRtaW4vb3BpbmllL2V3YS16bXJvd2thLmpwZw==.webp
508 ms
aHR0cHM6Ly93d3cubGlsaW8ucGwvZmlsZXMvYWRtaW4vb3BpbmllL21vbmlrYS1jaHJhcGVrLmpwZw==.webp
508 ms
aHR0cHM6Ly93d3cubGlsaW8ucGwvZmlsZXMvYWRtaW4vb3BpbmllL2dyYXp5bmEtYW50b3N6ZXdza2EuanBn.webp
658 ms
aHR0cHM6Ly93d3cubGlsaW8ucGwvZmlsZXMvYWRtaW4vb3BpbmllL21pLWthLmpwZw==.webp
660 ms
aHR0cHM6Ly93d3cubGlsaW8ucGwvZmlsZXMvYWRtaW4vb3BpbmllL2FybGV0dGEtZG9sLmpwZw==.webp
679 ms
aHR0cHM6Ly93d3cubGlsaW8ucGwvZmlsZXMvYWRtaW4vb3BpbmllL21hZ2RhLWphbmN6eW5za2EuanBn.webp
679 ms
aHR0cHM6Ly93d3cubGlsaW8ucGwvZmlsZXMvYWRtaW4vb3BpbmllL2Vsd2lyYS1kb2xvd3kuanBn.webp
678 ms
aHR0cHM6Ly93d3cubGlsaW8ucGwvZmlsZXMvYWRtaW4vb3BpbmllL21vbmlrYS1rdWpkYS5qcGc=.webp
717 ms
aHR0cHM6Ly93d3cubGlsaW8ucGwvZmlsZXMvYWRtaW4vb3BpbmllL21hZ2RhLWhyZWN6eW5za2EuanBn.webp
716 ms
aHR0cHM6Ly93d3cubGlsaW8ucGwvZmlsZXMvYWRtaW4vb3BpbmllL3JhZmFsLWtseXNpbnNraS5qcGc=.webp
795 ms
aHR0cHM6Ly93d3cubGlsaW8ucGwvZmlsZXMvYWRtaW4vb3BpbmllL2JlYXRhLWtvdGVja2EuanBn.webp
796 ms
aHR0cHM6Ly93d3cubGlsaW8ucGwvZmlsZXMvYWRtaW4vb3BpbmllL2JhcmJhcmEtc3p5cnVnYS5qcGc=.webp
795 ms
aHR0cHM6Ly93d3cubGlsaW8ucGwvZmlsZXMvYWRtaW4vb3BpbmllL2dvc2lhLXNvYmllcmFqLmpwZw==.webp
808 ms
aHR0cHM6Ly93d3cubGlsaW8ucGwvZmlsZXMvYWRtaW4vb3BpbmllL2Rvcm90YS1yeWJhY3p5ay5qcGc=.webp
837 ms
aHR0cHM6Ly93d3cubGlsaW8ucGwvdGhlbWVzL2xpbGlvL2Fzc2V0cy9pbWcvaWNvbnMvcGludGVyZXN0LnN2Zw==.svg
837 ms
aHR0cHM6Ly93d3cubGlsaW8ucGwvdGhlbWVzL2xpbGlvL2Fzc2V0cy9pbWcvaWNvbnMvZmFjZWJvb2suc3Zn.svg
912 ms
aHR0cHM6Ly93d3cubGlsaW8ucGwvdGhlbWVzL2xpbGlvL2Fzc2V0cy9pbWcvaWNvbnMveW91dHViZS5zdmc=.svg
911 ms
aHR0cHM6Ly93d3cubGlsaW8ucGwvdGhlbWVzL2xpbGlvL2Fzc2V0cy9pbWcvaWNvbnMvaW5zdGFncmFtLnN2Zw==.svg
914 ms
aHR0cHM6Ly93d3cubGlsaW8ucGwvZmlsZXMvYWRtaW4vcGxhdG5vc2NpLWZvb3Rlci10cGF5LmpwZw==.webp
943 ms
iconmonstr-quote-12.svg
869 ms
arrow-top.svg
872 ms
MaterialIcons-Regular.woff
985 ms
listagram.js
337 ms
js
108 ms
destination
231 ms
sdk.js
84 ms
default
461 ms
anchor
150 ms
sdk.js
110 ms
styles__ltr.css
65 ms
recaptcha__en.js
89 ms
166 ms
181 ms
e4c746a1-b967-4cb7-a95b-e3aeb5651827.json
317 ms
listagram.css
450 ms
OS4jJSgmcHxk24mPNVLLuJfLsxLv_4nnTDIIah-C-70.js
125 ms
webworker.js
149 ms
logo_48.png
111 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
43 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
51 ms
KFOlCnqEu92Fr1MmYUtfBBc9.ttf
57 ms
31 ms
22 ms
21 ms
recaptcha__en.js
11 ms
366 ms
arrow-top.svg
526 ms
logo_gmc-logo2.png
343 ms
theme_2_wYi1vxf.css
4 ms
580ae900e366.js
293 ms
css
18 ms
arrow_with_shadow.png
326 ms
wheel_shadow_inside.png
327 ms
wheel_shadow_outside.png
326 ms
small_logo_gmc-logo2.png
398 ms
image_heart01-invert_pattern100.png
325 ms
arrow_arrow_with_shadow_feminine.png
344 ms
image_custom_wheel_shadow_inside.png
336 ms
image_custom_wheel_shadow_outside.png
335 ms
rotator_wheel_feminine.png
534 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf
7 ms
twk-event-polyfill.js
193 ms
twk-main.js
104 ms
twk-vendor.js
159 ms
twk-chunk-vendors.js
226 ms
twk-chunk-common.js
181 ms
twk-runtime.js
98 ms
twk-app.js
151 ms
lilio.pl 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.
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
Links do not have a discernible name
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.
lilio.pl 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
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
lilio.pl SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
PL
PL
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lilio.pl can be misinterpreted by Google and other search engines. Our service has detected that Polish is used on the page, and it matches the claimed language. Our system also found out that Lilio.pl 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.
lilio.pl
Open Graph data is detected on the main page of LILIO. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: