6.7 sec in total
530 ms
5.9 sec
240 ms
Click here to check amazing 161 Bank content. Otherwise, check out these important facts you probably never knew about 161bank.ru
Срок регистрации домена истек. Требуется продление, чтобы возобновить работу домена и его сервисов
Visit 161bank.ruWe analyzed 161bank.ru page load time and found that the first response time was 530 ms and then it took 6.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
161bank.ru performance score
name
value
score
weighting
Value14.9 s
0/100
10%
Value21.1 s
0/100
25%
Value16.9 s
0/100
10%
Value4,630 ms
0/100
30%
Value0.285
42/100
15%
Value28.0 s
0/100
10%
530 ms
695 ms
918 ms
764 ms
765 ms
Our browser made a total of 141 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original 161bank.ru, 38% (53 requests) were made to I.sdska.ru and 9% (13 requests) were made to Vk.com. The less responsive or slowest element that took the longest time to load (1.7 sec) relates to the external source I.sdska.ru.
Page size can be reduced by 896.0 kB (64%)
1.4 MB
508.3 kB
In fact, the total size of 161bank.ru main page is 1.4 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. 50% of websites need less resources to load. Javascripts take 912.8 kB which makes up the majority of the site volume.
Potential reduce by 72.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 72.2 kB or 77% of the original size.
Potential reduce by 38.3 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, 161 Bank needs image optimization as it can save up to 38.3 kB or 16% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 653.3 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 653.3 kB or 72% of the original size.
Potential reduce by 132.3 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. 161bank.ru needs all CSS files to be minified and compressed as it can save up to 132.3 kB or 81% of the original size.
Number of requests can be reduced by 83 (61%)
135
52
The browser has sent 135 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 161 Bank. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 47 to 1 for JavaScripts and from 19 to 1 for CSS and as a result speed up the page load time.
161bank.ru
530 ms
dengi.161.ru
695 ms
jquery-1.9.1.min.js
918 ms
jquery-1.8.3.min.js
764 ms
jquery.js
765 ms
jquery.xdomainrequest.min.js
309 ms
png.css
309 ms
popup_passport.css
310 ms
styles.css
460 ms
d_common.css
614 ms
d.css
462 ms
jquery.smartbanner.css
802 ms
news_d.css
615 ms
news_common.css
766 ms
styles.css
768 ms
styles.css
973 ms
widgets_common.css
974 ms
widgets.css
974 ms
pt_serif.css
975 ms
common.js
1141 ms
sdb.js
1067 ms
jquery.cookie.js
1067 ms
api.js
1374 ms
jquery.waypoints.js
1070 ms
fotorama-4.4.2.js
1224 ms
fotorama.waypoints.js
1218 ms
dohcohT2.js
402 ms
popup.js
1218 ms
ngs-place.js
1221 ms
startpage.js
1292 ms
browser_detect.js
1371 ms
google_charts.js
1371 ms
jquery.smartbanner.js
1391 ms
jquery.multi-ddm.js
1392 ms
scroll.js
1443 ms
dropdown.js
1673 ms
update_browser.js
1522 ms
x.gif
155 ms
analytics.js
8 ms
boomerang-0.9.1401865982.js
154 ms
205 ms
2-z1-083ec010-8e20-4ee1-8f36-189867857814.jpg
632 ms
2-z3-19226492-7c26-468f-8673-2de7e80a7456.jpg
311 ms
2-z9-ec577786-5983-458c-a252-f9228d565ef5.jpg
298 ms
2-z14-8011f936-edf8-464e-90cd-49577264a9c4.jpg
490 ms
2-z17-ca4be074-344b-4bfe-90c2-7b616e98d4a2.jpg
558 ms
2-z16-de3616a3-10f4-48aa-b287-67c9b3faafba.jpg
331 ms
2-z8-f70f2abf-ccb8-40c1-9f2d-63dfdff96301.jpg
599 ms
logo
257 ms
logo.61.png
156 ms
2.png
157 ms
fin.61.png
308 ms
rugion-logo-white.png
158 ms
rn-logo-white.png
294 ms
18plus_bottom.png
295 ms
collect
14 ms
213 ms
p_common.css
154 ms
hit;61
254 ms
watch.js
170 ms
tcounter.js
273 ms
service_icons_simple.gif
155 ms
hit;rugion
270 ms
61
269 ms
205 ms
watch.js
446 ms
205 ms
hit;61
145 ms
hit;rugion
129 ms
61
134 ms
bg_finance.gif
158 ms
bg_search.gif
157 ms
title-bull.gif
159 ms
sprite_social_tab.png
157 ms
openapi.js
453 ms
bg_button.gif
161 ms
line.png
161 ms
bull_hits.png
265 ms
227 ms
224569399
356 ms
likebox.php
236 ms
advert.gif
85 ms
connect.js
531 ms
bg_firms.gif
176 ms
service_icons.png
306 ms
Widget_Login
179 ms
410ucuAGgaJ.css
31 ms
tSbl8xBI27R.css
39 ms
q68gy-v_YMF.js
37 ms
FJmpeSpHpjS.js
62 ms
0wM5s1Khldu.js
36 ms
1bNoFZUdlYZ.js
32 ms
1
105 ms
10352028_712393915474097_110407984144609135_n.jpg
55 ms
10406918_710129449033877_5869820888630685819_n.jpg
23 ms
10354686_10150004552801856_220367501106153455_n.jpg
20 ms
26564_100231486684431_3016536_n.jpg
24 ms
12717285_1076294952428537_8357021317002432265_n.jpg
23 ms
12814542_759574550841159_6005162398121898051_n.jpg
20 ms
wL6VQj7Ab77.png
14 ms
s7jcwEQH7Sx.png
17 ms
I6-MnjEovm5.js
9 ms
pQrUxxo5oQp.js
5 ms
checkauth.php
679 ms
widget_community.php
179 ms
loader_nav19181_3.js
132 ms
lite.css
239 ms
lite.js
407 ms
lang3_0.js
250 ms
widget_community.css
251 ms
xdm.js
257 ms
al_community.js
258 ms
dk
143 ms
widget.a86e7c8a.css
528 ms
image
597 ms
image
586 ms
image
583 ms
image
589 ms
image
611 ms
image
620 ms
image
625 ms
image
626 ms
image
626 ms
image
597 ms
mzm3ioxIcZU.jpg
254 ms
e_676e7c1f.jpg
364 ms
RnaxrKoHwTs.jpg
382 ms
MoBbGJeg4Dg.jpg
380 ms
-xecO1bouXk.jpg
368 ms
svKlscmgP_0.jpg
389 ms
KuPfRsPKlME.jpg
371 ms
P8Vumslisa4.jpg
384 ms
yyynk6vHVhc.jpg
382 ms
camera_50.png
130 ms
deactivated_50.png
124 ms
upload.gif
137 ms
check
1069 ms
w_logo.png
130 ms
ic_odkl_m.png
127 ms
add-or.png
251 ms
ic_odkl.png
377 ms
161bank.ru accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
161bank.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
161bank.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
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 doesn't use legible font sizes
Tap targets are not sized appropriately
RU
N/A
WINDOWS-1251
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 161bank.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 161bank.ru main page’s claimed encoding is windows-1251. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
161bank.ru
Open Graph description is not detected on the main page of 161 Bank. 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: