Tools & Wizards About Us
phone.1k.by screenshot

Report Summary

  • 63

    Performance

    Renders faster than
    77% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 94

    SEO

    Google-friendlier than
    90% of websites

phone.1k.by

Первый Каталог :: Телефония и связь - Каталог товаров и цены

Page Load Speed

5.1 sec in total

First Response

460 ms

Resources Loaded

4 sec

Page Rendered

581 ms

phone.1k.by screenshot

About Website

Visit phone.1k.by now to see the best up-to-date Phone 1 K content for Belarus and also check out these interesting facts you probably never knew about phone.1k.by

Телефония и связь - каталог описаний товаров с фотографиями и цены в Минске. Телефония и связь - покупка в интернет-магазине, продажа:мобильные телефоны, радиотелефоны, рации, voip-оборудование, чехлы...

Visit phone.1k.by

Key Findings

We analyzed Phone.1k.by page load time and found that the first response time was 460 ms 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

phone.1k.by performance score

63

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

41/100

10%

LCP (Largest Contentful Paint)

Value3.9 s

53/100

25%

SI (Speed Index)

Value5.7 s

51/100

10%

TBT (Total Blocking Time)

Value430 ms

65/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value6.7 s

56/100

10%

Network Requests Diagram

phone.1k.by

460 ms

phone.1k.by

561 ms

app.css

1287 ms

common.css

1067 ms

searchautocomplete.css

1072 ms

Our browser made a total of 73 requests to load all elements on the main page. We found that 4% of them (3 requests) were addressed to the original Phone.1k.by, 71% (52 requests) were made to 1k.by and 19% (14 requests) were made to Static.1k.by. The less responsive or slowest element that took the longest time to load (1.8 sec) relates to the external source 1k.by.

Page Optimization Overview & Recommendations

Page size can be reduced by 125.6 kB (21%)

Content Size

596.7 kB

After Optimization

471.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Phone.1k.by main page is 596.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. 40% of websites need less resources to load. Images take 260.9 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 54.5 kB

  • Original 70.8 kB
  • After minification 66.9 kB
  • After compression 16.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 54.5 kB or 77% of the original size.

Image Optimization

-3%

Potential reduce by 8.6 kB

  • Original 260.9 kB
  • After minification 252.4 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. Phone 1 K images are well optimized though.

JavaScript Optimization

-23%

Potential reduce by 41.3 kB

  • Original 177.1 kB
  • After minification 177.1 kB
  • After compression 135.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 41.3 kB or 23% of the original size.

CSS Optimization

-24%

Potential reduce by 21.1 kB

  • Original 87.8 kB
  • After minification 87.8 kB
  • After compression 66.7 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. Phone.1k.by needs all CSS files to be minified and compressed as it can save up to 21.1 kB or 24% of the original size.

Requests Breakdown

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

Requests Now

70

After Optimization

40

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 70 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Phone 1 K. 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 5 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

phone.1k.by

phone.1k.by

460 ms

phone.1k.by

phone.1k.by

561 ms

app.css

app.css

1287 ms

common.css

common.css

1067 ms

searchautocomplete.css

searchautocomplete.css

1072 ms

colorbox.css

colorbox.css

1075 ms

svgSymbolsLoader.js

svgSymbolsLoader.js

1083 ms

jquery-ui.min.css

jquery-ui.min.css

1091 ms

js-inline.php

js-inline.php

641 ms

js

js

48 ms

jquery-3.3.1.min.js

jquery-3.3.1.min.js

1349 ms

jquery-ui-1.12.1.min.js

jquery-ui-1.12.1.min.js

1531 ms

jquery.cookie.js

jquery.cookie.js

1188 ms

jquery-migrate-1.2.1.min.js

jquery-migrate-1.2.1.min.js

1197 ms

searchautocomplete-js-inline.php

searchautocomplete-js-inline.php

1239 ms

contactinfogoal-js-inline.php

contactinfogoal-js-inline.php

1350 ms

JBoxToggle.js

JBoxToggle.js

1350 ms

JDropMenu.js

JDropMenu.js

1359 ms

JDropModule.js

JDropModule.js

1403 ms

JFilterSelect.js

JFilterSelect.js

1403 ms

JFilterChecker.js

JFilterChecker.js

1453 ms

JOverlay.js

JOverlay.js

1454 ms

JProductView.js

JProductView.js

1477 ms

JMarketsPhones.js

JMarketsPhones.js

1507 ms

JTinySlider.js

JTinySlider.js

1515 ms

JVideos.js

JVideos.js

1546 ms

JOffersFilter.js

JOffersFilter.js

1552 ms

JTabs.js

JTabs.js

1594 ms

JWeekSchedule.js

JWeekSchedule.js

1619 ms

JCompare.js

JCompare.js

1627 ms

JSearch.js

JSearch.js

1642 ms

common.js

common.js

1659 ms

main.js

main.js

1666 ms

HTML_AJAX.js

HTML_AJAX.js

1832 ms

functions.js

functions.js

1730 ms

symbols.svg

symbols.svg

157 ms

i0121ab724.jpg

i0121ab724.jpg

1432 ms

by-logo.svg

by-logo.svg

424 ms

catalog.png

catalog.png

443 ms

catae38305ad.jpg

catae38305ad.jpg

461 ms

cat7f27e2169.jpeg

cat7f27e2169.jpeg

466 ms

cat7239f34e7.jpg

cat7239f34e7.jpg

540 ms

cat0675f9ac4.jpg

cat0675f9ac4.jpg

540 ms

cat02a0c281e.png

cat02a0c281e.png

557 ms

cat810110a21.jpg

cat810110a21.jpg

577 ms

cat478cd85c3.jpg

cat478cd85c3.jpg

581 ms

catb14d961f2.jpeg

catb14d961f2.jpeg

635 ms

cat56ccceedd.jpg

cat56ccceedd.jpg

639 ms

cat8f42358fe.png

cat8f42358fe.png

648 ms

cate4943f6e4.jpg

cate4943f6e4.jpg

671 ms

i04643239e.jpg

i04643239e.jpg

1444 ms

i15cbb2c0f.jpg

i15cbb2c0f.jpg

1447 ms

ifaf477a2c.jpg

ifaf477a2c.jpg

1446 ms

ia3112cb63.jpg

ia3112cb63.jpg

1449 ms

i60e1a91fb.jpg

i60e1a91fb.jpg

1463 ms

if903f2ca3.jpg

if903f2ca3.jpg

1540 ms

i84c4d86b2.jpg

i84c4d86b2.jpg

1558 ms

i640c820d7.jpg

i640c820d7.jpg

1559 ms

id1046f0e8.jpg

id1046f0e8.jpg

1561 ms

i733dec222.jpg

i733dec222.jpg

1563 ms

ib2a5e2d39.jpg

ib2a5e2d39.jpg

1581 ms

i8d2198d50.jpg

i8d2198d50.jpg

1651 ms

i249ab5e5b.jpg

i249ab5e5b.jpg

1672 ms

catf2443aaf9.png

catf2443aaf9.png

665 ms

cat67cd3423e.jpg

cat67cd3423e.jpg

667 ms

cat5422fcca0.jpg

cat5422fcca0.jpg

721 ms

cat83a4c5818.jpeg

cat83a4c5818.jpeg

721 ms

hit

hit

512 ms

watch.js

watch.js

1 ms

cat3cc12580b.jpg

cat3cc12580b.jpg

719 ms

catcbad4d6f7.jpg

catcbad4d6f7.jpg

701 ms

catd3ca08fcb.jpg

catd3ca08fcb.jpg

675 ms

b22f770b3dd.png

b22f770b3dd.png

906 ms

Accessibility Review

phone.1k.by accessibility score

84

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.

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

phone.1k.by best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

phone.1k.by SEO score

94

Search Engine Optimization Advices

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    RU

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Phone.1k.by can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is Russian. Our system also found out that Phone.1k.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

phone.1k.by

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