Tools & Wizards About Us
log.by screenshot

Report Summary

  • 40

    Performance

    Renders faster than
    59% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 54% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 67

    SEO

    Google-friendlier than
    26% of websites

log.by

Логойск / LOG.BY

Page Load Speed

5.7 sec in total

First Response

1.1 sec

Resources Loaded

4.3 sec

Page Rendered

275 ms

log.by screenshot

About Website

Visit log.by now to see the best up-to-date LOG content for Belarus and also check out these interesting facts you probably never knew about log.by

LOG.BY Логойск

Visit log.by

Key Findings

We analyzed Log.by page load time and found that the first response time was 1.1 sec and then it took 4.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

log.by performance score

40

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

39/100

10%

LCP (Largest Contentful Paint)

Value3.3 s

69/100

25%

SI (Speed Index)

Value8.0 s

22/100

10%

TBT (Total Blocking Time)

Value2,970 ms

3/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value14.0 s

10/100

10%

Network Requests Diagram

log.by

1130 ms

style.css

315 ms

openapi.js

474 ms

form.js

27 ms

site.js

57 ms

Our browser made a total of 77 requests to load all elements on the main page. We found that 12% of them (9 requests) were addressed to the original Log.by, 21% (16 requests) were made to Vk.com and 8% (6 requests) were made to Site.yandex.net. The less responsive or slowest element that took the longest time to load (1.7 sec) relates to the external source Vk.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 287.2 kB (62%)

Content Size

464.1 kB

After Optimization

176.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Log.by main page is 464.1 kB. 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. Javascripts take 308.9 kB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 48.5 kB

  • Original 63.9 kB
  • After minification 63.2 kB
  • After compression 15.4 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 48.5 kB or 76% of the original size.

Image Optimization

-4%

Potential reduce by 1.4 kB

  • Original 32.0 kB
  • After minification 30.6 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. LOG images are well optimized though.

JavaScript Optimization

-61%

Potential reduce by 189.8 kB

  • Original 308.9 kB
  • After minification 246.1 kB
  • After compression 119.1 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 189.8 kB or 61% of the original size.

CSS Optimization

-80%

Potential reduce by 47.5 kB

  • Original 59.3 kB
  • After minification 48.4 kB
  • After compression 11.8 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. Log.by needs all CSS files to be minified and compressed as it can save up to 47.5 kB or 80% of the original size.

Requests Breakdown

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

Requests Now

71

After Optimization

28

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

log.by

log.by

1130 ms

style.css

style.css

315 ms

openapi.js

openapi.js

474 ms

form.js

form.js

27 ms

site.js

site.js

57 ms

share.js

share.js

43 ms

jquery.min.js

jquery.min.js

93 ms

jquery.mousewheel-3.0.4.pack.js

jquery.mousewheel-3.0.4.pack.js

219 ms

jquery.fancybox-1.3.4.pack.js

jquery.fancybox-1.3.4.pack.js

335 ms

jquery.fancybox-1.3.4.css

jquery.fancybox-1.3.4.css

334 ms

all.js

all.js

390 ms

plusone.js

plusone.js

194 ms

ga.js

ga.js

89 ms

log.by

log.by

917 ms

__utm.gif

__utm.gif

19 ms

log.by

log.by

666 ms

log.by

log.by

875 ms

top-back.png

top-back.png

131 ms

hit

hit

321 ms

acode.js

acode.js

1145 ms

jquery.min.js

jquery.min.js

33 ms

_site.js

_site.js

13 ms

upload.gif

upload.gif

333 ms

widget_like.php

widget_like.php

536 ms

log.php

log.php

95 ms

loader__progress.gif

loader__progress.gif

21 ms

widgets.js

widgets.js

111 ms

_form.js

_form.js

22 ms

widget_community.php

widget_community.php

629 ms

yandex-hint.png

yandex-hint.png

10 ms

hit

hit

150 ms

loader_nav19239_3.js

loader_nav19239_3.js

155 ms

lite.css

lite.css

362 ms

lite.js

lite.js

1131 ms

lang3_0.js

lang3_0.js

367 ms

widgets.css

widgets.css

374 ms

xdm.js

xdm.js

375 ms

al_like.js

al_like.js

372 ms

widget_community.css

widget_community.css

280 ms

al_community.js

al_community.js

324 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

137 ms

ya-share-cnt.html

ya-share-cnt.html

87 ms

watch.js

watch.js

55 ms

button.71000885400e222c3c0eec823f8f93f0.js

button.71000885400e222c3c0eec823f8f93f0.js

310 ms

timeline.0eae788bc4fdbe9cd3e72dca3bc26358.js

timeline.0eae788bc4fdbe9cd3e72dca3bc26358.js

372 ms

b-share-icon.png

b-share-icon.png

95 ms

b-share_counter_large.png

b-share_counter_large.png

95 ms

315 ms

xd_arbiter.php

xd_arbiter.php

1333 ms

xd_arbiter.php

xd_arbiter.php

812 ms

1360 ms

dk

dk

1514 ms

fql.query

fql.query

1128 ms

share.php

share.php

1700 ms

wm

wm

1617 ms

syndication

syndication

617 ms

254182892723380224

254182892723380224

1196 ms

follow_button.fd774b599f565016d763dd860cb31c79.ru.html

follow_button.fd774b599f565016d763dd860cb31c79.ru.html

118 ms

info.json

info.json

515 ms

e_259f3017.jpg

e_259f3017.jpg

1028 ms

VhJspwk0siw.jpg

VhJspwk0siw.jpg

497 ms

lqKRT6P5wOA.jpg

lqKRT6P5wOA.jpg

947 ms

e_f86d42c7.jpg

e_f86d42c7.jpg

1030 ms

ttLgW3wHx8E.jpg

ttLgW3wHx8E.jpg

493 ms

TQLDRrQjUxY.jpg

TQLDRrQjUxY.jpg

313 ms

Qv-TZLIIXwM.jpg

Qv-TZLIIXwM.jpg

1024 ms

D88nXBHY6Rw.jpg

D88nXBHY6Rw.jpg

491 ms

xaKwpmcUFaA.jpg

xaKwpmcUFaA.jpg

945 ms

w_logo.png

w_logo.png

173 ms

camera_50.png

camera_50.png

163 ms

like_widget.png

like_widget.png

166 ms

adlik

adlik

236 ms

1f5fc.png

1f5fc.png

188 ms

2b50.png

2b50.png

175 ms

1f60b.png

1f60b.png

246 ms

timeline.f7130f11be9c2719286897ede16853b9.light.ltr.css

timeline.f7130f11be9c2719286897ede16853b9.light.ltr.css

55 ms

timeline.f7130f11be9c2719286897ede16853b9.light.ltr.css

timeline.f7130f11be9c2719286897ede16853b9.light.ltr.css

158 ms

Accessibility Review

log.by accessibility score

83

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.

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

<frame> or <iframe> elements do not have a title

High

Links do not have a discernible name

Best Practices

log.by 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

SEO Factors

log.by SEO score

67

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

Language and Encoding

  • Language Detected

    RU

  • Language Claimed

    RU

  • Encoding

    N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Log.by can be misinterpreted by Google and other search engines. Our service has detected that Russian is used on the page, and it matches the claimed language. Our system also found out that Log.by main page’s claimed encoding is . 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

log.by

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