7.6 sec in total
1.2 sec
6.1 sec
327 ms
Visit pbrf.ru now to see the best up-to-date Pbrf content for Russia and also check out these interesting facts you probably never knew about pbrf.ru
Почтовый бланк заполнить онлайн
Visit pbrf.ruWe analyzed Pbrf.ru page load time and found that the first response time was 1.2 sec and then it took 6.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
pbrf.ru performance score
name
value
score
weighting
Value4.7 s
13/100
10%
Value5.8 s
15/100
25%
Value8.1 s
21/100
10%
Value170 ms
92/100
30%
Value1.367
0/100
15%
Value6.9 s
54/100
10%
1202 ms
186 ms
338 ms
349 ms
493 ms
Our browser made a total of 102 requests to load all elements on the main page. We found that 78% of them (80 requests) were addressed to the original Pbrf.ru, 4% (4 requests) were made to Fonts.gstatic.com and 3% (3 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (3 sec) belongs to the original domain Pbrf.ru.
Page size can be reduced by 878.6 kB (46%)
1.9 MB
1.0 MB
In fact, the total size of Pbrf.ru main page is 1.9 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. 70% of websites need less resources to load. Images take 792.2 kB which makes up the majority of the site volume.
Potential reduce by 41.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. 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 41.1 kB or 81% of the original size.
Potential reduce by 0 B
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. Pbrf images are well optimized though.
Potential reduce by 545.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 545.8 kB or 73% of the original size.
Potential reduce by 291.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. Pbrf.ru needs all CSS files to be minified and compressed as it can save up to 291.7 kB or 87% of the original size.
Number of requests can be reduced by 52 (55%)
94
42
The browser has sent 94 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Pbrf. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 30 to 1 for JavaScripts and from 15 to 1 for CSS and as a result speed up the page load time.
pbrf.ru
1202 ms
source.js
186 ms
default.css
338 ms
app.css
349 ms
foundation.css
493 ms
jquery-ui.css
352 ms
social-likes_classic.css
350 ms
hover-min.css
361 ms
validationEngine.jquery.css
485 ms
animate.css
495 ms
zoom.css
495 ms
shCore.css
496 ms
shThemeDefault.css
508 ms
default.css
829 ms
jquery.min.js
838 ms
jquery.vticker.min.js
832 ms
jquery.plainoverlay.min.js
830 ms
foundation.min.js
828 ms
app.min.js
828 ms
freewall.js
828 ms
jquery-ui.min.js
1219 ms
css3-mediaqueries.js
896 ms
social-likes.min.js
898 ms
jquery.cookie.js
912 ms
jquery.mask.min.js
921 ms
source.min.js
939 ms
TemplatesView.min.js
941 ms
blanks.min.js
945 ms
api.min.js
967 ms
user.min.js
1054 ms
jquery.validationEngine-ru.js
1074 ms
jquery.validationEngine.js
1383 ms
zoom.js
1085 ms
shCore.js
1109 ms
shBrushPhp.js
1186 ms
chartPie.js
1209 ms
css
138 ms
214 ms
ui+en.css
17 ms
format+en,default+en,ui+en,corechart+en.I.js
145 ms
widget-1.4.gz.js
963 ms
ga.js
412 ms
pbrf_logo.png
357 ms
menu_active_1.gif
353 ms
menu_active_2.gif
360 ms
second_slide_API.gif
366 ms
first_slide_ems.gif
366 ms
third_slide_f112.gif
360 ms
bg_blanks_index.jpg
346 ms
borders.png
350 ms
blank_f7_f7a_f7b_f7p_pochta_rossii.jpg
352 ms
blank_f116_posilka_soprovoditelnii_address_pochta_rossii.jpg
474 ms
blank_f112ep_nalozhennii_platezh_pochtovii_perevod.jpg
490 ms
blank_f107_opis_vlozheniya_pochta_rossii.jpg
491 ms
blank_f103_partionnoe_otpravlenie_pochta_rossii.jpg
493 ms
blank_f7_f7a_f7b_f7p_adresniy_yarlik_na_posilky_pochta_rossii_2015.jpg
491 ms
blank_ems_e1_vnutrirossiiskiy_po_strane_rf_pochta_rossii.jpg
493 ms
blank_f112ek_federalniy_klient_nalozhennii_platezh_perevod_pochta_rossii.jpg
564 ms
blank_pechati_adresov_na_konverti.jpg
572 ms
blank_cp71_soprovoditelniy_address_k_posilke_pochta_rossii.jpg
578 ms
blank_cn23_tamozhennaya_deklaratsiya_pochta_rossii.jpg
614 ms
zayavlenie_na_rozisk_vnutrennego_pochtovogo_otpravleniya.jpg
614 ms
zayavlenie_na_rozisk_mezdunarodnogo_pochtovogo_otpravleniya.jpg
606 ms
blank_f113_f116_posilka_s_nalozhennim_platezhom_pochta_rossii.jpg
846 ms
blank_f113en_nalozhenii_platezh_perevod_pochta_rossii.jpg
846 ms
pbrf.ru
973 ms
button.png
856 ms
vk.png
840 ms
fb.png
854 ms
gp.png
857 ms
yt.png
957 ms
spark.png
955 ms
large_8_part1.png
1147 ms
large_5_part1.png
1035 ms
large_4_thumb_4_part1.png
3041 ms
large_3_d107.jpg
1255 ms
large_1_f116.jpg
1256 ms
large_2_cp71.jpg
1205 ms
large_37_front.jpg
1200 ms
large_38_address-label-1-klass.jpg
1155 ms
large_39_ZAYaVLENIE_mezhdunarodnoe_pochtovoe_otpravlenie.png
1249 ms
large_40_internal_mail.jpg
1385 ms
large_42_print_adress.png
1276 ms
large_43_f112ek.jpg
1820 ms
pkYDSlCHbDnBWPT5PPFFTA.ttf
146 ms
g46X4VH_KHOWAAa-HpnGPi3USBnSvpkopQaUR-2r7iU.ttf
207 ms
7dSh6BcuqDLzS2qAASIeuqCWcynf_cDxXwCLxiixG1c.ttf
211 ms
lILlYDvubYemzYzN7GbLkPOEPOIfcPv-fZ-WyMUtx48.ttf
210 ms
__utm.gif
117 ms
watch.js
223 ms
__utm.gif
233 ms
getCountForBlank
1591 ms
fql
280 ms
share_count
1636 ms
share.php
592 ms
dk
411 ms
gpp.xml
406 ms
0KfQsNGC
139 ms
322 ms
0JfQsNC00LDRgtGMINCy0L7Qv9GA0L7RgQ%3D%3D
210 ms
tooltip.css
162 ms
zoom-shadow.png
209 ms
pbrf.ru accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<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
Image elements do not have [alt] attributes
pbrf.ru 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
pbrf.ru 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
RU
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pbrf.ru 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 Pbrf.ru 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.
pbrf.ru
Open Graph description is not detected on the main page of Pbrf. 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: