5.8 sec in total
553 ms
5 sec
246 ms
Visit potomy.ru now to see the best up-to-date Potomy content for Russia and also check out these interesting facts you probably never knew about potomy.ru
Купить домен, регистрация домена, домен истек
Visit potomy.ruWe analyzed Potomy.ru page load time and found that the first response time was 553 ms and then it took 5.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
potomy.ru performance score
name
value
score
weighting
Value3.0 s
49/100
10%
Value3.6 s
61/100
25%
Value7.4 s
27/100
10%
Value3,160 ms
2/100
30%
Value0.006
100/100
15%
Value30.2 s
0/100
10%
553 ms
601 ms
144 ms
37 ms
37 ms
Our browser made a total of 92 requests to load all elements on the main page. We found that 21% of them (19 requests) were addressed to the original Potomy.ru, 47% (43 requests) were made to St6-21.vk.com and 7% (6 requests) were made to Vk.com. The less responsive or slowest element that took the longest time to load (1.8 sec) relates to the external source St6-21.vk.com.
Page size can be reduced by 433.5 kB (13%)
3.4 MB
2.9 MB
In fact, the total size of Potomy.ru main page is 3.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. 55% of websites need less resources to load. Javascripts take 2.2 MB which makes up the majority of the site volume.
Potential reduce by 32.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. This page needs HTML code to be minified as it can gain 4.6 kB, which is 11% 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 32.1 kB or 76% of the original size.
Potential reduce by 13.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. Potomy images are well optimized though.
Potential reduce by 316.4 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 316.4 kB or 14% of the original size.
Potential reduce by 71.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. Potomy.ru needs all CSS files to be minified and compressed as it can save up to 71.7 kB or 13% of the original size.
Number of requests can be reduced by 62 (73%)
85
23
The browser has sent 85 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Potomy. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 45 to 1 for JavaScripts and from 19 to 1 for CSS and as a result speed up the page load time.
potomy.ru
553 ms
potomy.ru
601 ms
style.min-26fbe14846252c08f9d98aa25d1b7442.css
144 ms
adsplacer.adblock.css
37 ms
css
37 ms
style.min-2.3.2.css
433 ms
main-5d6da7e762ff3571375b4d9907178d49.css
417 ms
jquery-1.12.4.js
563 ms
jquery-migrate.min-1.4.1.js
420 ms
jquery.iframetracker.js
47 ms
jquery.adsplacer.frontend.js
59 ms
jquery.adsplacer.ab-testing.js
51 ms
11ak5.min.js
531 ms
cache-adsreplace-shortcodes.js
51 ms
scripts.min-2.3.2.js
422 ms
main-d1e7469f68e034c9baaef2b8339b35d8.js
422 ms
wp-embed.min-26fbe14846252c08f9d98aa25d1b7442.js
552 ms
openapi.a2ed73393cad04481c1dfb3f7794921f.js
255 ms
tag.js
853 ms
phon.jpg
569 ms
Arrow.cur
153 ms
Hand.cur
153 ms
KFOmCnqEu92Fr1Mu5mxP.ttf
18 ms
KFOlCnqEu92Fr1MmWUlfABc9.ttf
26 ms
fontawesome-webfont.woff
413 ms
11ak5.json
235 ms
upload.gif
127 ms
lazyload-8.15.2.min.js
140 ms
admin-ajax.php
426 ms
widget_community.php
314 ms
1132.jpg
140 ms
616.jpg
283 ms
643643.jpeg
550 ms
11ak5.json
192 ms
loader_nav21007247412_3.js
298 ms
fonts_cnt.c7a76efe.css
988 ms
lite.ca486089.css
691 ms
lang3_2.js
643 ms
polyfills.560a594b.js
630 ms
vkui.43318ab6.css
710 ms
xdm.js
534 ms
ui_common.5f35f406.css
621 ms
react.759f82b6.js
806 ms
vkui.847cc706.js
1023 ms
vkcom-kit.7a5ea5e9.css
844 ms
vkcom-kit.aac2b77c.js
1054 ms
vkcom-kit-icons.7c2762f5.js
906 ms
state-management.148fcc7d.js
918 ms
architecture-mobx.511780b3.js
956 ms
audioplayer-lib.93b52d88.css
1021 ms
audioplayer-lib.9d47f848.js
1117 ms
common.dccb9af0.js
1752 ms
ui_common.b1037836.css
1070 ms
ui_common.96d7cbf1.js
1092 ms
audioplayer.7787a5d3.css
1084 ms
audioplayer.31c80ab2.js
1141 ms
widget_community.4978d481.css
1155 ms
5441c5ed.c6a2c19e.js
1181 ms
aa3c5e05.0d43f81d.js
1186 ms
likes.33883160.css
1204 ms
likes.7fa999ed.js
1236 ms
react.7abe3f06.js
1267 ms
vkcom-kit.4d5aaa48.css
1277 ms
vkcom-kit.8cfd1737.js
1293 ms
vkui.3a455cb9.js
1465 ms
vkcom-kit-icons.90941907.js
1331 ms
audioplayer-lib.85b39ca5.css
1353 ms
audioplayer-lib.cea41f24.js
1455 ms
architecture-mobx.357513b5.js
1396 ms
state-management.5b1df85b.js
1426 ms
c3d11fba.2ecb05ac.js
1442 ms
0fc69f32.52f19f82.js
1498 ms
context.js
966 ms
lite.bcf10ece3464fec8b554bde483fa2494.js
323 ms
advert.gif
697 ms
community.be2fc20a.css
985 ms
base.76878bfc.css
919 ms
e7eaa3a9.778eaa3f.js
923 ms
57703e15.882f7e68.js
866 ms
edb6ffde.a437d5be.js
1346 ms
community.a031ecdb.js
802 ms
sync_cookie_image_decide
152 ms
1
148 ms
zIVbKRt0sKEGC0JusnVIklCFp9dfjeYbZgc8n5Sl_FqLzXYFFU-9huMyRFGLpunLa6SElOpv.jpg
482 ms
QulWsGFAn5k.png
661 ms
dpu07cGW6DLJ5M9kI4bcszsSYSqZpXlR45yvR9q6l5oOhcc06MUpyDszViD18mLC7lqyplVdtMZZDN8IJPI5alwf.jpg
366 ms
mLiaiOWzUmgCCAdqHoFe_cyp39KbvCA_z27OuOny9VrIpvH_qSdSZa55EqadFuOIiC1lW130bU-rXAy9vPGLlWPa.jpg
488 ms
5Ru_8b_e8DHaDpn0xlkfL8nen1qpcock8NX0myF8A_85IrRTBm-5zu1F1MWJjkyzcxBCoiX5.jpg
485 ms
Xi222v3wFeUf4hMfJari_l9YTW76i82eZ6cswrpOhW6aAShvFm2X4arSGrxY9rnZ40DLM4MSDWbjnkK0oaROIv2A.jpg
490 ms
x7RWhKyFUowNvvd9Qa1WjN0KhfZFocG_XgzyoLCfeMEyEI89v3-UAW0LTTvliYqgJgsBWCG6PLDZkkNmjQb-5UGF.jpg
371 ms
tCTdsP9oxvQVPy6x4QNmMP7OvG_jfJQcVujFpj9WikI9yDlvj7U7mwR2V9270B941vutaI7lz5OQn17kLuWIJ_Me.jpg
371 ms
upload.gif
89 ms
potomy.ru 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
Form elements do not have associated labels
potomy.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
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
potomy.ru SEO score
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
![]()
RU
![]()
RU
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Potomy.ru 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 Potomy.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.
potomy.ru
Open Graph data is detected on the main page of Potomy. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: