Tools & Wizards About Us
185.by screenshot

Report Summary

  • 44

    Performance

    Renders faster than
    63% of other websites

  • 68

    Accessibility

    Visual factors better than
    that of 33% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 69

    SEO

    Google-friendlier than
    28% of websites

185.by

185.by Найти адреса, телефоны в Беларуси, справочная информация. Справочник контактов, товаров и услуг, Минск.

Page Load Speed

44.3 sec in total

First Response

406 ms

Resources Loaded

43.8 sec

Page Rendered

92 ms

185.by screenshot

About Website

Welcome to 185.by homepage info - get ready to check 185 best content for Belarus right away, or after learning these important things about 185.by

Справочная информация, адреса, телефоны, реквизиты предприятий, организаций и учреждений г. Минска и Республики Беларусь

Visit 185.by

Key Findings

We analyzed 185.by page load time and found that the first response time was 406 ms and then it took 43.9 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster. Unfortunately, there were 2 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

185.by performance score

44

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value13.6 s

0/100

10%

LCP (Largest Contentful Paint)

Value24.3 s

0/100

25%

SI (Speed Index)

Value23.2 s

0/100

10%

TBT (Total Blocking Time)

Value140 ms

95/100

30%

CLS (Cumulative Layout Shift)

Value0.008

100/100

15%

TTI (Time to Interactive)

Value14.2 s

9/100

10%

Network Requests Diagram

185.by

406 ms

www.185.by

1633 ms

combine.php

1313 ms

combine.php

848 ms

rexdot.gif

20484 ms

Our browser made a total of 45 requests to load all elements on the main page. We found that 71% of them (32 requests) were addressed to the original 185.by, 4% (2 requests) were made to S7.addthis.com and 4% (2 requests) were made to Adlik.akavita.com. The less responsive or slowest element that took the longest time to load (20.5 sec) relates to the external source Gaby1.hit.gemius.pl.

Page Optimization Overview & Recommendations

Page size can be reduced by 44.4 kB (23%)

Content Size

190.7 kB

After Optimization

146.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of 185.by main page is 190.7 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. 25% of websites need less resources to load. Javascripts take 83.1 kB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 31.6 kB

  • Original 42.7 kB
  • After minification 37.9 kB
  • After compression 11.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.8 kB, which is 11% 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 31.6 kB or 74% of the original size.

Image Optimization

-14%

Potential reduce by 8.2 kB

  • Original 57.9 kB
  • After minification 49.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, 185 needs image optimization as it can save up to 8.2 kB or 14% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-4%

Potential reduce by 3.6 kB

  • Original 83.1 kB
  • After minification 83.1 kB
  • After compression 79.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. This website has mostly compressed JavaScripts.

CSS Optimization

-15%

Potential reduce by 1.0 kB

  • Original 6.9 kB
  • After minification 6.9 kB
  • After compression 5.9 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. 185.by needs all CSS files to be minified and compressed as it can save up to 1.0 kB or 15% of the original size.

Requests Breakdown

Number of requests can be reduced by 15 (44%)

Requests Now

34

After Optimization

19

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

185.by

185.by

406 ms

www.185.by

www.185.by

1633 ms

combine.php

combine.php

1313 ms

combine.php

combine.php

848 ms

rexdot.gif

rexdot.gif

20484 ms

widget49.css

widget49.css

20287 ms

ajax.gif

ajax.gif

410 ms

0.gif

0.gif

408 ms

banner_loading.gif

banner_loading.gif

413 ms

rating.cgi

rating.cgi

385 ms

thumb.php

thumb.php

436 ms

thumb.php

thumb.php

425 ms

185.gif

185.gif

408 ms

btn1.gif

btn1.gif

427 ms

thumb.php

thumb.php

427 ms

btn_search.gif

btn_search.gif

416 ms

00455418.png

00455418.png

708 ms

00455416.png

00455416.png

428 ms

00455563.png

00455563.png

844 ms

sm-plus.gif

sm-plus.gif

716 ms

ico6.gif

ico6.gif

727 ms

ico4.gif

ico4.gif

722 ms

ico3.gif

ico3.gif

836 ms

qmark.png

qmark.png

1105 ms

ico5.gif

ico5.gif

1120 ms

ico7.gif

ico7.gif

1137 ms

ico1.gif

ico1.gif

1024 ms

10.gif

10.gif

1130 ms

ico2.gif

ico2.gif

1244 ms

t_mini-a.png

t_mini-a.png

1325 ms

catalog-tut2.gif

catalog-tut2.gif

1408 ms

favorites.png

favorites.png

1115 ms

odnk.png

odnk.png

1519 ms

btn.gif

btn.gif

1529 ms

square.gif

square.gif

1414 ms

lik

lik

298 ms

hit

hit

494 ms

watch.js

watch.js

13 ms

ga.js

ga.js

13 ms

__utm.gif

__utm.gif

13 ms

collect

collect

25 ms

ga-audiences

ga-audiences

100 ms

lik

lik

193 ms

hit

hit

502 ms

sh29.html

sh29.html

19650 ms

Accessibility Review

185.by accessibility score

68

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.

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

Form elements do not have associated labels

High

Links do not have a discernible name

Best Practices

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

185.by SEO score

69

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 185.by 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 185.by 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

185.by

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