Access orgpage.by. Справочник организаций Беларуси

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

40/100

10%

LCP (Largest Contentful Paint)

Value5.7 s

16/100

25%

SI (Speed Index)

Value15.3 s

1/100

10%

TBT (Total Blocking Time)

Value6,750 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value35.7 s

0/100

10%

orgpage.by

1064 ms

orgpage.by

524 ms

orgpage-ghost.js

104 ms

bootstrap.min.css

228 ms

css

43 ms

Our browser made a total of 66 requests to load all elements on the main page. We found that 35% of them (23 requests) were addressed to the original Orgpage.by, 15% (10 requests) were made to Static.orgpage.ru and 14% (9 requests) were made to Api-maps.yandex.ru. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Static.orgpage.ru.

Content Size

1.7 MB

After Optimization

1.1 MB

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

HTML Optimization

-88%

Potential reduce by 393.2 kB

Original 445.5 kB
After minification 391.1 kB
After compression 52.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. This page needs HTML code to be minified as it can gain 54.3 kB, which is 12% 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 393.2 kB or 88% of the original size.

Image Optimization

-15%

Potential reduce by 34.4 kB

Original 221.9 kB
After minification 187.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. Obviously, Orgpage needs image optimization as it can save up to 34.4 kB or 15% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-24%

Potential reduce by 153.0 kB

Original 628.9 kB
After minification 628.9 kB
After compression 476.0 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 153.0 kB or 24% of the original size.

CSS Optimization

-6%

Potential reduce by 25.6 kB

Original 418.1 kB
After minification 418.1 kB
After compression 392.5 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. Orgpage.by has all CSS files already compressed.

Requests Now

After Optimization

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

Accessibility Issues

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

High

ARIA input fields do not have accessible names

These are opportunities to improve the legibility of your content.

High

Background and foreground colors do not have a sufficient contrast ratio.

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.

High

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

High

Links do not have a discernible name

These are opportunities to improve keyboard navigation in your application.

High

Heading elements are not in a sequentially-descending order

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

These items highlight common accessibility best practices.

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Areas of Improvement

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

Search Engine Optimization Advices

To appear in search results, crawlers need access to your app.

High

Links are not crawlable

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/).

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

orgpage.by

Open Graph data is detected on the main page of Orgpage. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook:

Report Summary

Performance

Accessibility

Best Practices

SEO

Справочник организаций Беларуси

Page Load Speed

First Response

Resources Loaded

Page Rendered

About Website

Key Findings

Performance Metrics

Measured Metrics

FCP (First Contentful Paint)

LCP (Largest Contentful Paint)

SI (Speed Index)

TBT (Total Blocking Time)

CLS (Cumulative Layout Shift)

TTI (Time to Interactive)

Network Requests Diagram

orgpage.by

orgpage.by

orgpage-ghost.js

bootstrap.min.css

css

Page Optimization Overview & Recommendations

Content Size

After Optimization

HTML Optimization

Image Optimization

JavaScript Optimization

CSS Optimization

Requests Breakdown

Requests Now

After Optimization

Network Requests Diagram

orgpage.by

orgpage.by

orgpage-ghost.js

bootstrap.min.css

css

bundleStyle2.min.css

adsbygoogle.js

jquery.min.js

bootstrap.min.js

angular.min.js

bundleScript1.min.js

bundleScript2.min.js

bundleScript3.min.js

bundleHomePage.min.js

bundleScript4.min.js

gtm.js

map_5190818.png

ico01.png

ico-nophoto.png

ico05.png

59912186.jpg

6b5e732bd7f44e3eaa426c365c44bc5d.png

map_5385505.png

map_5316972.png

1317289255_5.jpg

map_5190797.png

map_5385753.png

2687595.jpg

2672568.jpg

openapi.c340c125c61ec5745ebb2a98626e46ab.js

logos.svg

ico03.png

ico04.png

sprite.png

line-decor-white.png

line-decor-transparent.png

bg01.jpg

font

upload.gif

widget_community.php

hit

watch.js

ui-bg_flat_75_ffffff_40x100.png