15.5 sec in total
732 ms
14.4 sec
428 ms
Visit uray.ru now to see the best up-to-date Uray content for Russia and also check out these interesting facts you probably never knew about uray.ru
Официальный сайт администрации города Урай Ханты-Мансийский автономный округ - Югра
Visit uray.ruWe analyzed Uray.ru page load time and found that the first response time was 732 ms and then it took 14.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
uray.ru performance score
name
value
score
weighting
Value4.7 s
13/100
10%
Value14.6 s
0/100
25%
Value21.6 s
0/100
10%
Value3,430 ms
2/100
30%
Value0.001
100/100
15%
Value56.3 s
0/100
10%
732 ms
5794 ms
629 ms
423 ms
643 ms
Our browser made a total of 122 requests to load all elements on the main page. We found that 96% of them (117 requests) were addressed to the original Uray.ru, 2% (2 requests) were made to Yandex.st and 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (5.8 sec) belongs to the original domain Uray.ru.
Page size can be reduced by 531.7 kB (21%)
2.6 MB
2.0 MB
In fact, the total size of Uray.ru main page is 2.6 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. 25% of websites need less resources to load. Images take 2.1 MB which makes up the majority of the site volume.
Potential reduce by 109.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. 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 109.0 kB or 80% of the original size.
Potential reduce by 232.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. Obviously, Uray needs image optimization as it can save up to 232.8 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 98.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 98.0 kB or 53% of the original size.
Potential reduce by 91.9 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. Uray.ru needs all CSS files to be minified and compressed as it can save up to 91.9 kB or 83% of the original size.
Number of requests can be reduced by 25 (21%)
118
93
The browser has sent 118 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Uray. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 8 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
uray.ru
732 ms
www.uray.ru
5794 ms
boot.css
629 ms
template.css
423 ms
general.css
643 ms
fancybox.css
430 ms
jquery.min.js
16 ms
jquery.mousewheel.min.js
32 ms
bootstrap.min.js
658 ms
core-1.0.js
632 ms
carousel.js
636 ms
fancybox.js
647 ms
general.js
839 ms
reset.css
418 ms
core.css
443 ms
emblem.png
219 ms
DSC_2091-1024x1024.jpg
1126 ms
flag.png
216 ms
gerb.png
210 ms
charter.png
214 ms
22_Glavniii_sait_111_I_TV_video_r.jpg
1610 ms
22_Glavniii_sait_113_1_r.jpg
886 ms
22_Glavniii_sait_116_dekl_r.jpg
1264 ms
22_Glavniii_sait_58_banner_v2_r.jpg
1143 ms
22_Glavniii_sait_96_2016_otdiih_detei_r.jpg
1873 ms
22_Glavniii_sait_4590_10186_DSC00608_r_i.jpg
444 ms
22_Glavniii_sait_4589_DSC_3666_i.jpg
688 ms
22_Glavniii_sait_4588_2384233_i.jpg
930 ms
22_Glavniii_sait_4587_image_07_04_16_14_55.jpeg_i.jpg
1126 ms
22_Glavniii_sait_4586_1434449835_d42d5b2fbad5d2608b49a386177537f0_kopiya.jpeg_i.jpg
1174 ms
video.png
1333 ms
transparent.png
1345 ms
22_Glavniii_sait_5285_K640_K1024_002_t.jpg
1855 ms
zoom-36.png
1476 ms
367px-Coat_of_Arms_of_the_Russian_Federation_2.svg.png
2027 ms
250px-Coat_of_Arms_of_Yugra.svg.png
1803 ms
COA_of_Central_Election_Commission_of_Russia.png
2394 ms
area.gif
1849 ms
population.gif
2028 ms
location.gif
2071 ms
google.gif
2069 ms
22_Glavniii_sait_17_Moiseeev_V._t.jpg
2097 ms
poll.png
2252 ms
22_Glavniii_sait_32_test_r.png
2255 ms
22_Glavniii_sait_25_gos_r.png
2282 ms
22_Glavniii_sait_31_torgi_r.png
2307 ms
22_Glavniii_sait_55_12122_r.jpg
2315 ms
22_Glavniii_sait_40_mon_r.jpg
2463 ms
22_Glavniii_sait_47_KMNS_r.jpg
2465 ms
22_Glavniii_sait_74_85_let_jugre_r.jpg
2726 ms
22_Glavniii_sait_75_Pensionniii_fond_r.jpg
2756 ms
22_Glavniii_sait_38_Rosstat_r.jpg
2575 ms
watch.js
1 ms
analytics.js
126 ms
datepicker.css
2432 ms
collect
15 ms
glyphicons-halflings-regular.woff
2491 ms
icomoon.ttf
2486 ms
admhmao.php
4379 ms
datepicker.js
2392 ms
22_Glavniii_sait_37_zapis4_r.jpg
2241 ms
22_Glavniii_sait_53_banner_TIS_Ugra_1_r.jpg
2023 ms
22_Glavniii_sait_58_Torgovo_prom_palata_r.jpg
2240 ms
22_Glavniii_sait_63_surdlempiiskie_igrii_r.jpg
2071 ms
22_Glavniii_sait_64_70_let_pobedii_r.jpg
1938 ms
include_news
2718 ms
include_gallery
2770 ms
include_products
3406 ms
include_links
3508 ms
include_history
2805 ms
22_Glavniii_sait_69_prom_r.jpg
2721 ms
22_Glavniii_sait_70_EDDS_r.jpg
2853 ms
22_Glavniii_sait_65_Rossiiskaya_initsiativa_r.jpg
3104 ms
22_Glavniii_sait_5_razv_r.png
2680 ms
22_Glavniii_sait_34_Ipotechnoe_agenstvo_r.png
2874 ms
22_Glavniii_sait_61_detstvoUgra_r.jpg
2779 ms
22_Glavniii_sait_43_logo_g_r.jpg
3038 ms
22_Glavniii_sait_60_infa__2__r.jpg
3133 ms
22_Glavniii_sait_14_child_r.png
2885 ms
22_Glavniii_sait_72_Rebenok_r.jpg
3346 ms
22_Glavniii_sait_71_Chelovek_r.jpg
3246 ms
22_Glavniii_sait_51_121_r.jpg
3175 ms
22_Glavniii_sait_59_fnb_r.jpg
3102 ms
22_Glavniii_sait_33_11_r.jpg
2969 ms
22_Glavniii_sait_76_Znamya_r.jpg
3327 ms
22_Glavniii_sait_50_muzei_r.jpg
3297 ms
22_Glavniii_sait_48_tsgb_banner_r.png
3138 ms
22_Glavniii_sait_52_kap_rem_r.jpg
3187 ms
22_Glavniii_sait_54_2_r.jpg
3518 ms
22_Glavniii_sait_68_Investitsionnaya_karta_YUgrii_r.jpg
3550 ms
22_Glavniii_sait_26_informatization_r.gif
3118 ms
22_Glavniii_sait_41_mfts6_r.jpg
3150 ms
22_Glavniii_sait_20_inf_r.png
3146 ms
22_Glavniii_sait_23_children_r.png
3143 ms
22_Glavniii_sait_57_pereselenie_r.jpg
3181 ms
22_Glavniii_sait_62_spice_r.jpg
3183 ms
22_Glavniii_sait_73_Rabota_v_rossii_r.jpg
3195 ms
22_Glavniii_sait_77_sro_r.jpg
3063 ms
footer.gif
3071 ms
leap.png
3107 ms
goldensite.gif
2377 ms
prev.png
2286 ms
next.png
2057 ms
22_Glavniii_sait_4585_DSC_3672_i.jpg
2051 ms
22_Glavniii_sait_4584_176_615964_W_i.jpg
1928 ms
22_Glavniii_sait_4583_102_1896__1__i.jpg
1923 ms
22_Glavniii_sait_4582_slide04_i.jpg
1872 ms
22_Glavniii_sait_4581_683bb87342d572898b524957c82f2042_i.jpg
1827 ms
22_Glavniii_sait_4580_487542113_i.jpg
1809 ms
22_Glavniii_sait_4579_1_html_m3c4455bc_i.jpg
1789 ms
22_Glavniii_sait_4578_silava_8_i.jpg
1812 ms
22_Glavniii_sait_4577_K640_SON_1391_i.jpg
1774 ms
22_Glavniii_sait_4576_K640_WP_20160401_00120160401120430_i.jpg
1783 ms
22_Glavniii_sait_5286_K640_K1024_013_t.jpg
1943 ms
22_Glavniii_sait_5287_K640_K1024_022_t.jpg
1610 ms
22_Glavniii_sait_5288_K640_K1024_027_t.jpg
1542 ms
22_Glavniii_sait_5289_K640_K1024_032_t.jpg
1512 ms
22_Glavniii_sait_5290_K640_K1024_034_t.jpg
1521 ms
22_Glavniii_sait_5291_K640_K1024_038_t.jpg
1756 ms
22_Glavniii_sait_5292_K640_K1024_041_t.jpg
1762 ms
22_Glavniii_sait_5293_K640_K1024_053_t.jpg
1475 ms
22_Glavniii_sait_5294_K640_K1024_054_t.jpg
1683 ms
uray.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 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.
ARIA toggle fields do not have accessible names
[aria-*] attributes are not valid or misspelled
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
List items (<li>) are not contained within <ul> or <ol> parent elements.
uray.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
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
uray.ru SEO score
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
WINDOWS-1251
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Uray.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 Uray.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.
uray.ru
Open Graph description is not detected on the main page of Uray. 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: