Tools & Wizards About Us
declarantbel.by screenshot

Report Summary

  • 28

    Performance

    Renders faster than
    48% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

declarantbel.by

Таможенное оформление деклараций и услуги брокера - ДекларантБел

Page Load Speed

3.3 sec in total

First Response

463 ms

Resources Loaded

2.8 sec

Page Rendered

65 ms

declarantbel.by screenshot

About Website

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

❶ Таможенное оформление ❷ Таможенные услуги, сопровождение и декларирование ❸ Статистика и сертификация

Visit declarantbel.by

Key Findings

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

Performance Metrics

declarantbel.by performance score

28

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.9 s

53/100

10%

LCP (Largest Contentful Paint)

Value3.5 s

65/100

25%

SI (Speed Index)

Value10.4 s

8/100

10%

TBT (Total Blocking Time)

Value2,460 ms

5/100

30%

CLS (Cumulative Layout Shift)

Value0.472

18/100

15%

TTI (Time to Interactive)

Value13.9 s

10/100

10%

Network Requests Diagram

declarantbel.by

463 ms

declarantbel.by

556 ms

analytics.js

21 ms

css

79 ms

vendor.min.css

122 ms

Our browser made a total of 30 requests to load all elements on the main page. We found that 67% of them (20 requests) were addressed to the original Declarantbel.by, 7% (2 requests) were made to Google-analytics.com and 7% (2 requests) were made to Code-ya.jivosite.com. The less responsive or slowest element that took the longest time to load (968 ms) relates to the external source Yastatic.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 60.6 kB (36%)

Content Size

166.1 kB

After Optimization

105.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-75%

Potential reduce by 27.1 kB

  • Original 36.3 kB
  • After minification 36.2 kB
  • After compression 9.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 27.1 kB or 75% of the original size.

Image Optimization

-7%

Potential reduce by 220 B

  • Original 3.0 kB
  • After minification 2.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. Declarantbel images are well optimized though.

JavaScript Optimization

-27%

Potential reduce by 33.1 kB

  • Original 120.9 kB
  • After minification 120.9 kB
  • After compression 87.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 33.1 kB or 27% of the original size.

CSS Optimization

-1%

Potential reduce by 60 B

  • Original 5.8 kB
  • After minification 5.8 kB
  • After compression 5.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. Declarantbel.by has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 10 (48%)

Requests Now

21

After Optimization

11

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

declarantbel.by

declarantbel.by

463 ms

declarantbel.by

declarantbel.by

556 ms

analytics.js

analytics.js

21 ms

css

css

79 ms

vendor.min.css

vendor.min.css

122 ms

common.min.css

common.min.css

243 ms

debug.css

debug.css

351 ms

709 ms

vendor.min.js

vendor.min.js

598 ms

client.min.js

client.min.js

382 ms

scripts.js

scripts.js

383 ms

M9lfH73Xir

M9lfH73Xir

274 ms

sprite.svg

sprite.svg

412 ms

device-img.svg

device-img.svg

382 ms

sprite.svg

sprite.svg

468 ms

whatsapp.svg

whatsapp.svg

471 ms

phone.svg

phone.svg

475 ms

swd.png

swd.png

479 ms

collect

collect

15 ms

sprite.png

sprite.png

459 ms

MuseoSansCyrl-300.woff

MuseoSansCyrl-300.woff

745 ms

MuseoSansCyrl-500.woff

MuseoSansCyrl-500.woff

748 ms

MuseoSansCyrl-700.woff

MuseoSansCyrl-700.woff

756 ms

MuseoSansCyrl-900.woff

MuseoSansCyrl-900.woff

764 ms

sprite.png

sprite.png

300 ms

jizYRExUiTo99u79D0e0x8mNAjcQ-w.ttf

jizYRExUiTo99u79D0e0x8mNAjcQ-w.ttf

139 ms

full-f7aad75f4136fd546efbbe29908f2112821adcbc.js

full-f7aad75f4136fd546efbbe29908f2112821adcbc.js

968 ms

watch.js

watch.js

6 ms

M9lfH73Xir

M9lfH73Xir

188 ms

M9lfH73Xir

M9lfH73Xir

523 ms

Accessibility Review

declarantbel.by accessibility score

100

Accessibility Issues

Best Practices

declarantbel.by best practices score

75

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

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

declarantbel.by SEO score

83

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

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

    RU

  • Language Claimed

    RU

  • Encoding

    UTF-8

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

declarantbel.by

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