5.2 sec in total
380 ms
3.9 sec
938 ms
Welcome to lile.ge homepage info - get ready to check Lile best content right away, or after learning these important things about lile.ge
ნატურალური ქართული თაფლი ლილე კახეთიდან
Visit lile.geWe analyzed Lile.ge page load time and found that the first response time was 380 ms and then it took 4.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
lile.ge performance score
name
value
score
weighting
Value4.1 s
21/100
10%
Value6.5 s
9/100
25%
Value15.1 s
1/100
10%
Value100 ms
98/100
30%
Value0.64
9/100
15%
Value5.0 s
77/100
10%
380 ms
199 ms
207 ms
216 ms
295 ms
Our browser made a total of 71 requests to load all elements on the main page. We found that 90% of them (64 requests) were addressed to the original Lile.ge, 4% (3 requests) were made to Fonts.gstatic.com and 3% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (2 sec) belongs to the original domain Lile.ge.
Page size can be reduced by 331.5 kB (12%)
2.7 MB
2.4 MB
In fact, the total size of Lile.ge main page is 2.7 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. 50% of websites need less resources to load. Images take 2.3 MB which makes up the majority of the site volume.
Potential reduce by 21.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 4.0 kB, which is 15% 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 21.1 kB or 79% of the original size.
Potential reduce by 42.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. Lile images are well optimized though.
Potential reduce by 202.5 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 202.5 kB or 67% of the original size.
Potential reduce by 65.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. Lile.ge needs all CSS files to be minified and compressed as it can save up to 65.1 kB or 81% of the original size.
Number of requests can be reduced by 26 (41%)
63
37
The browser has sent 63 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Lile. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 15 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.
lile.ge
380 ms
style.css
199 ms
font-awesome.min.css
207 ms
font.css
216 ms
ga.js
295 ms
jquery_004.js
294 ms
jquery-migrate-1.js
216 ms
jquery.js
293 ms
scroll_to_top.js
293 ms
script.js
293 ms
sForm.js
301 ms
jquery_005.js
384 ms
superfish.js
388 ms
jquery_002.js
390 ms
touchTouch.js
389 ms
camera.js
388 ms
jquery_003.js
390 ms
owl.js
475 ms
reset.css
287 ms
skeleton.css
287 ms
superfish.css
289 ms
touchTouch.css
290 ms
camera.css
291 ms
form.css
372 ms
subscribe-form.css
377 ms
owl.carousel.css
378 ms
css
24 ms
css
36 ms
picha.jpg
130 ms
logo.png
275 ms
indicator.png
114 ms
flags_sprites.png
116 ms
bg_pattern_1.png
116 ms
icons_bg.png
282 ms
plus_sign.png
174 ms
page1_icon1.png
184 ms
equal_sign.png
194 ms
page1_icon2.png
194 ms
page1_icon3.png
257 ms
letter_sign.png
275 ms
cell_sign.png
287 ms
jj.jpg
660 ms
price_bg.png
348 ms
2.jpg
730 ms
3.jpg
643 ms
11.jpg
556 ms
8.jpg
660 ms
12.jpg
803 ms
1.jpg
831 ms
10.jpg
825 ms
bg_pattern_2.png
753 ms
quote_bg.png
754 ms
sign3.png
819 ms
bpg_algeti_compact.otf
1277 ms
bpg_square_banner_caps_2013.otf
901 ms
bpg_supersquare_2013.otf
947 ms
gugeshashvili_rachveli_2-webfont.woff
873 ms
fKnfV28XkldRW297cFLeqfesZW2xOQ-xsNqO47m55DA.ttf
64 ms
bg_transparent.png
879 ms
fb.png
885 ms
logo_footer.png
969 ms
analytics.js
60 ms
pagination.png
912 ms
prev.png
996 ms
next.png
998 ms
camera-loader.gif
1003 ms
tafli.png
2030 ms
fND5XPYKrF2tQDwwfWZJI4nF5uFdDttMLvmWuJdhhgs.ttf
38 ms
qLBu5CQmSMt1H43OiWJ77aCWcynf_cDxXwCLxiixG1c.ttf
38 ms
collect
14 ms
902302_1431817450365068_1474714571_o.jpg
749 ms
lile.ge 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
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
Image elements do not have [alt] attributes
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.
lile.ge 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
Browser errors were logged to the console
Page has valid source maps
lile.ge SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
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
KA
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lile.ge can be misinterpreted by Google and other search engines. Our service has detected that Georgian is used on the page, and it does not match the claimed English language. Our system also found out that Lile.ge 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.
lile.ge
Open Graph data is detected on the main page of Lile. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: