Tools & Wizards About Us
ler.ru screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

ler.ru

«Фирма ЛИР» - решения для широкоформатной печати, сканирования и обработки информации

Page Load Speed

5.6 sec in total

First Response

450 ms

Resources Loaded

4.9 sec

Page Rendered

222 ms

ler.ru screenshot

About Website

Click here to check amazing Ler content for Russia. Otherwise, check out these important facts you probably never knew about ler.ru

«Фирма ЛИР» – поставка оборудования для широкоформатной печати. Cтруйные плоттеры Mutoh, УФ-принтеры JETRIX, режущие плоттеры Summa, ламинаторы/аппликаторы Rollover, а также материалы для печати Decop...

Visit ler.ru

Key Findings

We analyzed Ler.ru page load time and found that the first response time was 450 ms and then it took 5.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

ler.ru performance score

0

Network Requests Diagram

ler.ru

450 ms

www.ler.ru

1051 ms

kernel_main.css

114 ms

page_fc005c6fa1024b2aa69bd67330c98f44.css

225 ms

template_307ff3db625678d861a75837bd953d0e.css

335 ms

Our browser made a total of 111 requests to load all elements on the main page. We found that 53% of them (59 requests) were addressed to the original Ler.ru, 6% (7 requests) were made to St6-21.vk.com and 6% (7 requests) were made to Youtube.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Ler.ru.

Page Optimization Overview & Recommendations

Page size can be reduced by 278.0 kB (17%)

Content Size

1.6 MB

After Optimization

1.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Ler.ru 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. 55% of websites need less resources to load. Javascripts take 667.9 kB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 42.6 kB

  • Original 55.8 kB
  • After minification 51.1 kB
  • After compression 13.3 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 42.6 kB or 76% of the original size.

Image Optimization

-24%

Potential reduce by 131.8 kB

  • Original 560.5 kB
  • After minification 428.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. Obviously, Ler needs image optimization as it can save up to 131.8 kB or 24% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-12%

Potential reduce by 77.1 kB

  • Original 667.9 kB
  • After minification 667.9 kB
  • After compression 590.8 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 77.1 kB or 12% of the original size.

CSS Optimization

-7%

Potential reduce by 26.5 kB

  • Original 361.9 kB
  • After minification 361.6 kB
  • After compression 335.4 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. Ler.ru has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 73 (69%)

Requests Now

106

After Optimization

33

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 106 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ler. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 34 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

ler.ru

ler.ru

450 ms

www.ler.ru

www.ler.ru

1051 ms

kernel_main.css

kernel_main.css

114 ms

page_fc005c6fa1024b2aa69bd67330c98f44.css

page_fc005c6fa1024b2aa69bd67330c98f44.css

225 ms

template_307ff3db625678d861a75837bd953d0e.css

template_307ff3db625678d861a75837bd953d0e.css

335 ms

kernel_main.js

kernel_main.js

562 ms

core_db.min.js

core_db.min.js

359 ms

core_frame_cache.min.js

core_frame_cache.min.js

337 ms

template_9221c6b10fcb733ecaac5c5625d50c4b.js

template_9221c6b10fcb733ecaac5c5625d50c4b.js

445 ms

jquery.min.js

jquery.min.js

10 ms

main.js

main.js

447 ms

masket.js

masket.js

470 ms

spinners.js

spinners.js

556 ms

lightview.js

lightview.js

694 ms

lightview.css

lightview.css

668 ms

jquery.easing.1.3.js

jquery.easing.1.3.js

668 ms

tms-0.3.2.js

tms-0.3.2.js

671 ms

tms_presets.js

tms_presets.js

779 ms

platform.js

platform.js

20 ms

openapi.a2ed73393cad04481c1dfb3f7794921f.js

openapi.a2ed73393cad04481c1dfb3f7794921f.js

238 ms

ba.js

ba.js

319 ms

spread.php

spread.php

498 ms

logo_2.png

logo_2.png

112 ms

2022.jpg

2022.jpg

290 ms

3648.jpg

3648.jpg

290 ms

3614.jpg

3614.jpg

290 ms

3613.jpg

3613.jpg

374 ms

captcha.php

captcha.php

442 ms

signes2.gif

signes2.gif

397 ms

Mutoh%20XpertJet%20special%20price.png

Mutoh%20XpertJet%20special%20price.png

506 ms

footer_logo.png

footer_logo.png

485 ms

t0DluQShXw

t0DluQShXw

288 ms

analytics.js

analytics.js

46 ms

watch.js

watch.js

6 ms

hit

hit

651 ms

__overall_sub_wrap_bg.jpg

__overall_sub_wrap_bg.jpg

504 ms

top_menu_bg.gif

top_menu_bg.gif

547 ms

cart_bg.png

cart_bg.png

594 ms

user_area_bg.png

user_area_bg.png

611 ms

root_item_bg.gif

root_item_bg.gif

616 ms

left_menu_bg.gif

left_menu_bg.gif

658 ms

left_menu_divider.png

left_menu_divider.png

702 ms

left_menu_dots.gif

left_menu_dots.gif

721 ms

left_root_item_bg.png

left_root_item_bg.png

727 ms

more_bg.png

more_bg.png

770 ms

hr_bg.gif

hr_bg.gif

843 ms

s_field_bg.gif

s_field_bg.gif

789 ms

search.gif

search.gif

808 ms

s_btn_bg.png

s_btn_bg.png

815 ms

lang_bg.png

lang_bg.png

857 ms

flag_bg.gif

flag_bg.gif

900 ms

contacts_block_bg.gif

contacts_block_bg.gif

917 ms

block_shadow_bg.png

block_shadow_bg.png

926 ms

contacts_block_info_bg.gif

contacts_block_info_bg.gif

1527 ms

phone_email_bg.png

phone_email_bg.png

965 ms

service_bnr_2.jpg

service_bnr_2.jpg

1109 ms

collect

collect

43 ms

collect

collect

38 ms

likebox.php

likebox.php

89 ms

upload.gif

upload.gif

124 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

25 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

42 ms

subscribe_embed

subscribe_embed

92 ms

vendors_bg.gif

vendors_bg.gif

958 ms

vendors_arrow_bg.png

vendors_arrow_bg.png

966 ms

vendors_li_bg.png

vendors_li_bg.png

1007 ms

footer_bg.jpg

footer_bg.jpg

1076 ms

footer_sub_wrap_bg.jpg

footer_sub_wrap_bg.jpg

1077 ms

fb_name.gif

fb_name.gif

1117 ms

collect

collect

50 ms

js

js

95 ms

widget_community.php

widget_community.php

270 ms

bx_stat

bx_stat

231 ms

fb_mail.gif

fb_mail.gif

1156 ms

postmessageRelay

postmessageRelay

52 ms

1l56xVUMItd.css

1l56xVUMItd.css

23 ms

ga-audiences

ga-audiences

34 ms

www-subscribe-embed_split_v0.css

www-subscribe-embed_split_v0.css

3 ms

www-subscribe-embed_v0.js

www-subscribe-embed_v0.js

71 ms

AIdro_kaEOK-IVF4OcEeHKfzJcdEg4lRTwpbrA1_FIxX1pvOxA=s48-c-k-c0x00ffffff-no-rj

AIdro_kaEOK-IVF4OcEeHKfzJcdEg4lRTwpbrA1_FIxX1pvOxA=s48-c-k-c0x00ffffff-no-rj

345 ms

subscribe_button_branded_lozenge.png

subscribe_button_branded_lozenge.png

81 ms

3604799710-postmessagerelay.js

3604799710-postmessagerelay.js

93 ms

rpc:shindig_random.js

rpc:shindig_random.js

79 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

19 ms

fb_phone.gif

fb_phone.gif

1005 ms

t0DluQShXw

t0DluQShXw

466 ms

fb_message.gif

fb_message.gif

1041 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

24 ms

cb=gapi.loaded_2

cb=gapi.loaded_2

5 ms

border_3.gif

border_3.gif

4 ms

subscribe_embed

subscribe_embed

52 ms

spacer.gif

spacer.gif

3 ms

bubbleSprite_3.png

bubbleSprite_3.png

5 ms

bubbleDropR_3.png

bubbleDropR_3.png

8 ms

bubbleDropB_3.png

bubbleDropB_3.png

10 ms

sprite.png

sprite.png

1011 ms

loader_nav21015637446_3.js

loader_nav21015637446_3.js

269 ms

fonts_cnt.c7a76efe.css

fonts_cnt.c7a76efe.css

1109 ms

lite.ca486089.css

lite.ca486089.css

794 ms

lang3_2.js

lang3_2.js

428 ms

c3d11fba.296f7859.js

c3d11fba.296f7859.js

896 ms

xdm.js

xdm.js

991 ms

base.9b237a0c.css

base.9b237a0c.css

1450 ms

blank.gif

blank.gif

1005 ms

www-subscribe-embed-card_v0.css

www-subscribe-embed-card_v0.css

3 ms

www-subscribe-embed-card_v0.js

www-subscribe-embed-card_v0.js

7 ms

lite.bcf10ece3464fec8b554bde483fa2494.js

lite.bcf10ece3464fec8b554bde483fa2494.js

371 ms

t0DluQShXw

t0DluQShXw

511 ms

browsers.png

browsers.png

139 ms

upload.gif

upload.gif

158 ms

code.js

code.js

779 ms

SEO Factors

ler.ru SEO score

0

Language and Encoding

  • Language Detected

    RU

  • Language Claimed

    N/A

  • Encoding

    WINDOWS-1251

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ler.ru can be misinterpreted by Google and other search engines. Our service has detected that Russian is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Ler.ru main page’s claimed encoding is windows-1251. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

ler.ru

Open Graph description is not detected on the main page of Ler. 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: