5.6 sec in total
454 ms
4.7 sec
464 ms
Welcome to prology.ru homepage info - get ready to check PROLOGY best content for Russia right away, or after learning these important things about prology.ru
PROLOGY производитель систем навигации, устройств мобильного видео, автомагнитол, головных устройств.
Visit prology.ruWe analyzed Prology.ru page load time and found that the first response time was 454 ms and then it took 5.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
prology.ru performance score
name
value
score
weighting
Value6.0 s
4/100
10%
Value22.0 s
0/100
25%
Value13.0 s
2/100
10%
Value3,110 ms
2/100
30%
Value0.126
83/100
15%
Value19.4 s
2/100
10%
454 ms
676 ms
236 ms
468 ms
353 ms
Our browser made a total of 152 requests to load all elements on the main page. We found that 87% of them (132 requests) were addressed to the original Prology.ru, 5% (7 requests) were made to Top-fwz1.mail.ru and 2% (3 requests) were made to Vk.com. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Prology.ru.
Page size can be reduced by 269.5 kB (12%)
2.2 MB
2.0 MB
In fact, the total size of Prology.ru main page is 2.2 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. 65% of websites need less resources to load. Images take 1.2 MB which makes up the majority of the site volume.
Potential reduce by 219.0 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 160.3 kB, which is 68% 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 219.0 kB or 93% of the original size.
Potential reduce by 27.2 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. PROLOGY images are well optimized though.
Potential reduce by 12.2 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. This website has mostly compressed JavaScripts.
Potential reduce by 11.0 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. Prology.ru has all CSS files already compressed.
Number of requests can be reduced by 90 (68%)
132
42
The browser has sent 132 CSS, Javascripts, AJAX and image requests in order to completely render the main page of PROLOGY. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 59 to 1 for JavaScripts and from 21 to 1 for CSS and as a result speed up the page load time.
prology.ru
454 ms
prology.ru
676 ms
index.min.js
236 ms
01-bootstrap.min.css
468 ms
02-slick.css
353 ms
03-swiper.min.css
356 ms
04-nouislider.css
382 ms
05-darktooltip.css
400 ms
06-animate.css
405 ms
07-style.css
717 ms
08-megamenu.css
475 ms
09-icons.css
511 ms
10-oswald.css
535 ms
11-raleway.css
541 ms
12-bmi.css
585 ms
13-bmi-custom.css
597 ms
14-hint.css
642 ms
15-view360.css
671 ms
16-prology.css
678 ms
17-roboto.css
703 ms
18-online-mess.css
735 ms
wow_book.css
899 ms
kraken-team.css
807 ms
snow.min.css
816 ms
jquery.min.js
938 ms
jquery.cookie.js
835 ms
jquery-ui.min.js
965 ms
View360.js
949 ms
pdf.combined.min.js
1629 ms
wow_book.min.js
979 ms
load_more.user.js
1028 ms
lazyload.user.js
1056 ms
catalogSearch.user.js
1079 ms
catalog.user.js
1085 ms
goup.user.js
1085 ms
mylocation.user.js
1157 ms
core.user.js
1175 ms
cookieagreement.user.js
1102 ms
mobile_check.user.js
972 ms
seourls.user.js
859 ms
categoryimagesloader.user.js
937 ms
firebase-messaging-config.user.js
915 ms
add-to-cart.user.js
930 ms
pushMessages.user.js
926 ms
noui-slider.user.js
884 ms
cart_lang.user.js
947 ms
buy-oneclick.user.js
903 ms
navmenu.user.js
914 ms
products.user.js
910 ms
utils.user.js
904 ms
callbackform.user.js
937 ms
extended_delivery_fields.user.js
911 ms
comparison.user.js
895 ms
fields_restore.user.js
892 ms
siteMailing.user.js
923 ms
wow.min.js
953 ms
swiper.min.js
974 ms
bootstrap.min.js
902 ms
bmi.min.js
891 ms
jquery.pulsate.min.js
959 ms
jquery.blockui.min.js
890 ms
slick.min.js
847 ms
parallax.min.js
907 ms
isotope.pkgd.min.js
875 ms
jquery.countdown.min.js
876 ms
jquery.nouislider.min.js
868 ms
hidemaxlistitem.min.js
850 ms
jquery.ezplus.js
810 ms
tocca.min.js
846 ms
tabcollapse.js
848 ms
scrollLock.min.js
798 ms
jquery.darktooltip.js
831 ms
imagesloaded.pkgd.min.js
826 ms
megamenu.min.js
837 ms
app.js
842 ms
rtrg
558 ms
prology_250.svg
369 ms
Prology_2Gift_Action_v2_1813x708_4site.jpg
659 ms
WHM_700_Kraken_Prology_ru_main_1813x708_v2.jpg
671 ms
kraken_01.jpg
1007 ms
kraken_slide_center.png
553 ms
kraken_slide_left.png
551 ms
kraken_slide_right.png
552 ms
subs_ps_rx_prology_ru_1813x708.jpg
849 ms
t_prology-cmx-235_id1469_1.jpg
615 ms
t_ruchka-stilus-brendirovannaya-kraken_id1524_1.jpg
638 ms
t_tolstovka-brendirovannaya-prology-na-krilyah-zvuka_id1527_1.jpg
735 ms
t_futbolka-brendirovannaya-prology-na-krilyah-zvuka_id1533_1.jpg
776 ms
t_tolstovka-brendirovannaya-kraken-by-prology-chernaya-razmer-l_id1539_2.jpg
787 ms
t_prology-ps-165_id1562_9.jpg
787 ms
t_prology-rx-8-kraken_id1567_4.jpg
854 ms
t_prology-rx-12-kraken_id1569_3.jpg
913 ms
code.js
677 ms
tag.js
855 ms
t_prology-ps-10-poseidon_id1571_4.jpg
901 ms
t_prology-ra-121_id1575_3.jpg
888 ms
t_prology-rvc-110_id1320_9.jpg
950 ms
t_prology-vx-m300_id1422_5.jpg
907 ms
Roboto-Light.woff
937 ms
Roboto-Thin.woff
1013 ms
Roboto-Regular.woff
996 ms
Roboto-Medium.woff
952 ms
Roboto-Bold.woff
1047 ms
Roboto-Black.woff
998 ms
icomoon-reg.ttf
967 ms
ralewaybold.woff
1048 ms
ralewayextrabold.woff
1037 ms
ralewayblack.woff
1012 ms
ralewaysemibold.woff
1052 ms
ralewaymedium.woff
1030 ms
ralewayregular.woff
1016 ms
ralewaylight.woff
1032 ms
ralewaythin.woff
1021 ms
Oswaldregular.woff
1025 ms
analytics.js
21 ms
Oswaldlight.woff
1054 ms
collect
13 ms
collect
30 ms
js
67 ms
ga-audiences
32 ms
Oswaldbold.woff
885 ms
ajax.php
920 ms
openapi.a2ed73393cad04481c1dfb3f7794921f.js
260 ms
t_prology-rfc-200_id1442_2.jpg
882 ms
t_prology-rvc-180_id1445_1.jpg
888 ms
t_prology-whm-700_id1456_9.jpg
864 ms
prology_white.svg
897 ms
sync-loader.js
881 ms
counter
126 ms
763 ms
dyn-goal-config.js
251 ms
tracker
398 ms
counter
399 ms
telegram.svg
848 ms
vk_blue.svg
833 ms
ok_orange.svg
838 ms
youtube_red.svg
851 ms
rtrg
141 ms
rutube.svg
816 ms
dzen.svg
847 ms
advert.gif
628 ms
free-shiping.png
801 ms
mms_53x13.png
815 ms
on_logo.jpg
838 ms
on_askline_on.jpg
788 ms
on_close.png
826 ms
on_mess.gif
836 ms
loader.gif
775 ms
block-bg-4.jpg
748 ms
1
144 ms
tracker
127 ms
tracker
139 ms
prology.ru accessibility score
ARIA
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.
Impact
Issue
[aria-*] attributes do not match their roles
[aria-hidden="true"] elements contain focusable descendents
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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.
prology.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
Missing source maps for large first-party JavaScript
prology.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 uses legible font sizes
Tap targets are not sized appropriately
RU
RU
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Prology.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 Prology.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.
prology.ru
Open Graph data is detected on the main page of PROLOGY. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: