12.6 sec in total
3 sec
8.8 sec
732 ms
Click here to check amazing Gpk content for Belarus. Otherwise, check out these important facts you probably never knew about gpk.gov.by
Официальный интернет портал Государственного пограничного комитета Республики Беларусь
Visit gpk.gov.byWe analyzed Gpk.gov.by page load time and found that the first response time was 3 sec and then it took 9.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
gpk.gov.by performance score
name
value
score
weighting
Value4.8 s
11/100
10%
Value16.4 s
0/100
25%
Value12.8 s
2/100
10%
Value1,280 ms
18/100
30%
Value0.225
55/100
15%
Value15.7 s
6/100
10%
3037 ms
293 ms
295 ms
294 ms
1506 ms
Our browser made a total of 129 requests to load all elements on the main page. We found that 71% of them (92 requests) were addressed to the original Gpk.gov.by, 8% (10 requests) were made to Cam.gpk.gov.by and 2% (3 requests) were made to Avatars-fast.yandex.net. The less responsive or slowest element that took the longest time to load (4.3 sec) relates to the external source Vitebsk.customs.gov.by.
Page size can be reduced by 1.2 MB (46%)
2.5 MB
1.4 MB
In fact, the total size of Gpk.gov.by main page is 2.5 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. 55% of websites need less resources to load. Images take 1.2 MB which makes up the majority of the site volume.
Potential reduce by 68.7 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 13.0 kB, which is 16% 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 68.7 kB or 83% of the original size.
Potential reduce by 91.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. Gpk images are well optimized though.
Potential reduce by 552.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 552.0 kB or 71% of the original size.
Potential reduce by 454.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. Gpk.gov.by needs all CSS files to be minified and compressed as it can save up to 454.5 kB or 88% of the original size.
Number of requests can be reduced by 29 (24%)
123
94
The browser has sent 123 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Gpk. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 24 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
gpk.gov.by
3037 ms
kernel_main.css
293 ms
kernel_socialservices.css
295 ms
kernel_altasib.errorsend.css
294 ms
template_017001ac58d937d149d7bb7666580a5f.css
1506 ms
popup.min.css
429 ms
kernel_main.js
1216 ms
kernel_socialservices.js
432 ms
error.js
433 ms
template_3203e138722c3ef4605c2c6766039bcc.js
433 ms
global.css
576 ms
css
31 ms
js
32 ms
jquery.min.js
38 ms
jquery-1.11.3.min.js
890 ms
bootstrap.js
746 ms
jquery.liquidcarousel.js
435 ms
jquery.flexslider.js
755 ms
jquery.jcarousel.min.js
744 ms
jcarousel.responsive.js
892 ms
scrollup.js
891 ms
jquery.bxslider.min.js
898 ms
urchin.js
8 ms
ba.js
261 ms
logo.png
241 ms
menu.png
239 ms
twitter.png
238 ms
facebook.png
239 ms
youtube.png
235 ms
rss.png
242 ms
vk.jpg
357 ms
twitter.png
390 ms
facebook.png
384 ms
youtube.png
393 ms
rss.png
388 ms
gerb_rb.png
391 ms
flag_rb_color.png
503 ms
pop_up_opros.jpg
666 ms
ocheredi.png
575 ms
maps.png
530 ms
banner_kak_stat.png
532 ms
pogran_zona.png
526 ms
pravila_peresechenia.png
659 ms
childrens.png
668 ms
icon_priem_grazhdan.png
670 ms
el_obrascheniya.png
675 ms
square.png
726 ms
podvig.png
798 ms
vneocherednoi_viezd.png
803 ms
crossing-rules.png
808 ms
platnye_uslugi.png
810 ms
beltoll.png
819 ms
prigranichnoe_peredvizhenie.png
859 ms
banner_opros.jpg
1098 ms
e804db8a2325e469547a888c17a84f7c.jpg
986 ms
1c06e3ab6beac055875db95001b75339.jpg
1099 ms
0f1ec3c736e72225d4f1e9d713506551.jpg
983 ms
ba09df4ab652348cd10dff7c5e39a8a5.JPG
986 ms
d365825b6e2cf16a2a8f514654ec348a.jpg
999 ms
k-log-gtk.jpg
859 ms
2cd9a80021f6e3d75592de415c42a803.jpg
1245 ms
iZNC3ZEYwe3je6H-28d5Ug.ttf
174 ms
beniakoni1.jpg
1151 ms
privalka-gtk.jpg
954 ms
bruzgi-gtk.jpg
852 ms
kotlovka-gtk.jpg
851 ms
berestovica-gtk.jpg
952 ms
brest-gtk.jpg
1142 ms
domachevo-gtk.jpg
1148 ms
mokrany-gtk.jpg
1000 ms
n-guta-gtk.jpg
1150 ms
snap_c1.jpg
4294 ms
snap_c1.jpg
4028 ms
context.js
305 ms
acode.js
298 ms
xgemius.js
498 ms
watch.js
61 ms
__utm.gif
96 ms
SegoeUIRegular.woff
1492 ms
fontawesome-webfont.woff
1042 ms
ed0f62c0f6d261110f871fbb7431b123.jpg
917 ms
688efaeda8177ebdedb0f7bf8c96a1c8.jpg
1012 ms
948a1e7a5bf8943b76aa44e81ba37768.jpg
1173 ms
8496bcddb809c89edcb81e89527e1a67.jpg
1073 ms
bx_stat
228 ms
559fd5dfe95581ddb9ff0e9f97869147.jpg
1037 ms
context_static_r1084.js
340 ms
7533400c56a75b0d428ea44c12749a30.jpg
1192 ms
23f368e0c8fcf221b31b3972c8c99202.jpg
1042 ms
kontrakt.jpg
1049 ms
otdyh.jpg
1142 ms
wm
196 ms
s_detmi.jpg
1166 ms
pasport.jpg
1100 ms
pravila_peresechenia.jpg
1094 ms
zavtra_voina.jpg
1160 ms
pust_mechty.jpg
1170 ms
pogranichnye-sutki.jpg
1143 ms
fpdata.js
126 ms
lsget.html
238 ms
Vodnye_rybezhi.jpg
1119 ms
aeoport.jpg
1115 ms
pylayuschaya-granica.jpg
1170 ms
1-voennyi-gospital-OPS-RB.jpg
1175 ms
OSAM-granica-specialnogo-naznacheniya.jpg
1186 ms
160156
160 ms
watch.js
1 ms
kinologicheski-centr-OPS.jpg
1141 ms
adlik
220 ms
voina-ot-pervogo-lica.jpg
1103 ms
back-to-top.png
1105 ms
arrow_news_all.png
1178 ms
larrow.png
1179 ms
rarrow.png
1200 ms
left.png
1152 ms
x90
183 ms
zonp.ru
287 ms
y80
209 ms
x90
388 ms
needguide.ru
386 ms
right.png
1090 ms
map_locator.png
1087 ms
phone.png
1184 ms
altasib.errorsend.ok.gif
1179 ms
rexdot.js
131 ms
altasib.errorsend.png
1107 ms
bx_loader.gif
1114 ms
controls-l.png
1117 ms
controls-r.png
1022 ms
gpk.gov.by accessibility score
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
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
gpk.gov.by best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
gpk.gov.by SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
Document uses legible font sizes
Tap targets are not sized appropriately
RU
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Gpk.gov.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 Gpk.gov.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.
gpk.gov.by
Open Graph description is not detected on the main page of Gpk. 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: