Tools & Wizards About Us
lile.ge screenshot

Report Summary

  • 42

    Performance

    Renders faster than
    61% of other websites

  • 59

    Accessibility

    Visual factors better than
    that of 26% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

lile.ge

თაფლი ლილე

Page Load Speed

7.8 sec in total

First Response

471 ms

Resources Loaded

7 sec

Page Rendered

292 ms

lile.ge screenshot

About Website

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.ge

Key Findings

We analyzed Lile.ge page load time and found that the first response time was 471 ms and then it took 7.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

lile.ge performance score

42

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.2 s

19/100

10%

LCP (Largest Contentful Paint)

Value6.4 s

9/100

25%

SI (Speed Index)

Value7.5 s

27/100

10%

TBT (Total Blocking Time)

Value640 ms

47/100

30%

CLS (Cumulative Layout Shift)

Value0.057

98/100

15%

TTI (Time to Interactive)

Value6.4 s

59/100

10%

Network Requests Diagram

lile.ge

471 ms

lile.ge

744 ms

style.css

179 ms

font-awesome.min.css

336 ms

font.css

458 ms

Our browser made a total of 74 requests to load all elements on the main page. We found that 86% 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 Counter.top.ge. The less responsive or slowest element that took the longest time to load (3.2 sec) belongs to the original domain Lile.ge.

Page Optimization Overview & Recommendations

Page size can be reduced by 113.3 kB (7%)

Content Size

1.6 MB

After Optimization

1.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Lile.ge main page is 1.6 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. 35% of websites need less resources to load. Images take 1.4 MB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 18.7 kB

  • Original 25.0 kB
  • After minification 24.1 kB
  • After compression 6.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. 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 18.7 kB or 75% of the original size.

Image Optimization

-4%

Potential reduce by 51.1 kB

  • Original 1.4 MB
  • After minification 1.4 MB

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.

JavaScript Optimization

-29%

Potential reduce by 40.2 kB

  • Original 140.2 kB
  • After minification 140.2 kB
  • After compression 99.9 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 40.2 kB or 29% of the original size.

CSS Optimization

-17%

Potential reduce by 3.2 kB

  • Original 18.4 kB
  • After minification 18.4 kB
  • After compression 15.2 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 3.2 kB or 17% of the original size.

Requests Breakdown

Number of requests can be reduced by 27 (43%)

Requests Now

63

After Optimization

36

  • AJAX
  • Images
  • JavaScript
  • CSS

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 16 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

lile.ge

lile.ge

471 ms

lile.ge

lile.ge

744 ms

style.css

style.css

179 ms

font-awesome.min.css

font-awesome.min.css

336 ms

font.css

font.css

458 ms

ga.js

ga.js

615 ms

jquery_004.js

jquery_004.js

722 ms

jquery-migrate-1.js

jquery-migrate-1.js

459 ms

jquery.js

jquery.js

464 ms

scroll_to_top.js

scroll_to_top.js

491 ms

script.js

script.js

612 ms

sForm.js

sForm.js

611 ms

jquery_005.js

jquery_005.js

618 ms

superfish.js

superfish.js

636 ms

jquery_002.js

jquery_002.js

761 ms

touchTouch.js

touchTouch.js

760 ms

camera.js

camera.js

773 ms

jquery_003.js

jquery_003.js

771 ms

owl.js

owl.js

3179 ms

counter.js

counter.js

703 ms

reset.css

reset.css

694 ms

skeleton.css

skeleton.css

732 ms

superfish.css

superfish.css

733 ms

touchTouch.css

touchTouch.css

747 ms

camera.css

camera.css

746 ms

form.css

form.css

845 ms

subscribe-form.css

subscribe-form.css

883 ms

owl.carousel.css

owl.carousel.css

881 ms

css

css

26 ms

css

css

43 ms

picha.jpg

picha.jpg

2920 ms

logo.png

logo.png

1104 ms

indicator.png

indicator.png

813 ms

flags_sprites.png

flags_sprites.png

818 ms

bg_pattern_1.png

bg_pattern_1.png

159 ms

icons_bg.png

icons_bg.png

462 ms

plus_sign.png

plus_sign.png

815 ms

page1_icon1.png

page1_icon1.png

815 ms

equal_sign.png

equal_sign.png

968 ms

page1_icon2.png

page1_icon2.png

1164 ms

page1_icon3.png

page1_icon3.png

974 ms

letter_sign.png

letter_sign.png

974 ms

cell_sign.png

cell_sign.png

982 ms

jj.jpg

jj.jpg

1730 ms

price_bg.png

price_bg.png

1130 ms

2.jpg

2.jpg

1568 ms

3.jpg

3.jpg

1458 ms

11.jpg

11.jpg

1401 ms

8.jpg

8.jpg

1581 ms

12.jpg

12.jpg

1643 ms

5.jpg

5.jpg

1702 ms

bg_pattern_2.png

bg_pattern_2.png

1630 ms

quote_bg.png

quote_bg.png

1725 ms

sign3.png

sign3.png

1749 ms

fb.png

fb.png

1792 ms

logo_footer.png

logo_footer.png

1807 ms

bg_transparent.png

bg_transparent.png

1827 ms

bpg_algeti_compact.otf

bpg_algeti_compact.otf

2443 ms

bpg_square_banner_caps_2013.otf

bpg_square_banner_caps_2013.otf

1854 ms

bpg_supersquare_2013.otf

bpg_supersquare_2013.otf

1871 ms

gugeshashvili_rachveli_2-webfont.woff

gugeshashvili_rachveli_2-webfont.woff

1911 ms

FwZY7-Qmy14u9lezJ-6H6Mw.ttf

FwZY7-Qmy14u9lezJ-6H6Mw.ttf

49 ms

analytics.js

analytics.js

52 ms

init.js

init.js

86 ms

1Pt_g8LJRfWJmhDAuUsSQamb1W0lwk4S4Y_LDrMfJQ.ttf

1Pt_g8LJRfWJmhDAuUsSQamb1W0lwk4S4Y_LDrMfJQ.ttf

15 ms

1Pt_g8LJRfWJmhDAuUsSQamb1W0lwk4S4WjMDrMfJQ.ttf

1Pt_g8LJRfWJmhDAuUsSQamb1W0lwk4S4WjMDrMfJQ.ttf

38 ms

pagination.png

pagination.png

1886 ms

prev.png

prev.png

1940 ms

next.png

next.png

1966 ms

camera-loader.gif

camera-loader.gif

2004 ms

baneri-lile.png

baneri-lile.png

2349 ms

count222

count222

165 ms

collect

collect

14 ms

tafli.jpg

tafli.jpg

169 ms

Accessibility Review

lile.ge accessibility score

59

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

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

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

lile.ge best practices score

58

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

lile.ge SEO score

86

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    KA

  • Language Claimed

    EN

  • Encoding

    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.

Social Sharing Optimization

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: