10.1 sec in total
929 ms
8.6 sec
602 ms
Welcome to 86.ru homepage info - get ready to check 86 best content for Russia right away, or after learning these important things about 86.ru
Последние свежие новости ХМАО — Югры и Ханты-Мансийска, Югры и Ханты-Мансийского автономного округа за сегодня - онлайн на сайте 86.ру
Visit 86.ruWe analyzed 86.ru page load time and found that the first response time was 929 ms and then it took 9.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
86.ru performance score
name
value
score
weighting
Value5.3 s
7/100
10%
Value12.7 s
0/100
25%
Value17.0 s
0/100
10%
Value18,410 ms
0/100
30%
Value0.001
100/100
15%
Value45.0 s
0/100
10%
929 ms
917 ms
934 ms
929 ms
468 ms
Our browser made a total of 148 requests to load all elements on the main page. We found that 1% of them (2 requests) were addressed to the original 86.ru, 43% (64 requests) were made to I.sdska.ru and 16% (23 requests) were made to Reklama.ngs.ru. The less responsive or slowest element that took the longest time to load (4.7 sec) relates to the external source Z23.d.sdska.ru.
Page size can be reduced by 712.4 kB (47%)
1.5 MB
797.2 kB
In fact, the total size of 86.ru main page is 1.5 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 815.0 kB which makes up the majority of the site volume.
Potential reduce by 132.8 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 132.8 kB or 80% of the original size.
Potential reduce by 37.6 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. 86 images are well optimized though.
Potential reduce by 441.1 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 441.1 kB or 54% of the original size.
Potential reduce by 101.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. 86.ru needs all CSS files to be minified and compressed as it can save up to 101.0 kB or 82% of the original size.
Number of requests can be reduced by 89 (62%)
143
54
The browser has sent 143 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 86. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 54 to 1 for JavaScripts and from 17 to 1 for CSS and as a result speed up the page load time.
86.ru
929 ms
jquery-1.9.1.min.js
917 ms
jquery-1.8.3.min.js
934 ms
jquery.js
929 ms
jquery.xdomainrequest.min.js
468 ms
png.css
470 ms
popup_passport.css
477 ms
styles.css
626 ms
d_common.css
630 ms
d.css
642 ms
jquery.smartbanner.css
781 ms
styles.css
791 ms
announce.css
803 ms
widgets_common.css
968 ms
widgets.css
969 ms
news_d.css
969 ms
news_common.css
1061 ms
styles.css
1114 ms
styles.css
1087 ms
styles.css
1094 ms
pt_serif.css
1115 ms
common.js
1306 ms
sdb.js
1211 ms
jquery.cookie.js
1245 ms
api.js
1735 ms
jquery.waypoints.js
1272 ms
fotorama-4.4.2.js
1594 ms
fotorama.waypoints.js
1361 ms
dohcohT2.js
561 ms
popup.js
1399 ms
ngs-place.js
1426 ms
startpage.js
1465 ms
browser_detect.js
1535 ms
google_charts.js
1574 ms
jquery.smartbanner.js
1587 ms
jquery.multi-ddm.js
1627 ms
scroll.js
1687 ms
dropdown.js
1293 ms
update_browser.js
1302 ms
paginate.js
1328 ms
poll.js
1226 ms
analytics.js
25 ms
boomerang-0.9.1401865982.js
166 ms
top100.cnt
293 ms
2-z32-484a3abb-882f-491d-93e0-27788ef39468.jpg
664 ms
2-z3-01b9f3d2-0fc0-49a1-980b-26bf2d6a817f.jpg
496 ms
2-z6-d661d7a7-a642-406f-9d70-d5c60696562d.jpg
502 ms
2-z23-ac3daa69-dfc4-401a-a868-6e3dd43b73de.jpg
4662 ms
banner-88x31-rambler-gray2.gif
283 ms
logo
286 ms
12x12.png
165 ms
18plus.png
168 ms
logo.86.ru.png
166 ms
1.png
153 ms
1.png
163 ms
b3.gif
315 ms
gorod-online.png
321 ms
x.gif
325 ms
rugion_job.png
317 ms
auto.86.png
321 ms
dom.86.png
330 ms
fin.86.png
497 ms
afisha.86.png
499 ms
rugion-logo-color.png
500 ms
rn-logo-color.png
500 ms
18plus_bottom.png
499 ms
hit;72
284 ms
hit;rugion
285 ms
86
286 ms
watch.js
0 ms
tcounter.js
281 ms
191 ms
collect
12 ms
179 ms
hit;72
161 ms
hit;rugion
155 ms
86
168 ms
199 ms
p_common.css
165 ms
210 ms
551754098
318 ms
194 ms
179 ms
304538c38807860700173442b6b72ce1_176.html
645 ms
service_icons_simple.gif
172 ms
tpx
357 ms
359 ms
clicktrack.js
347 ms
runtime.js
62 ms
275 ms
input-back.png
172 ms
select-back.png
170 ms
button-back.png
178 ms
line.png
172 ms
203 ms
186 ms
206 ms
369e25d1bd072cc88e284e67ddc0b599_106.jpg
361 ms
tpx
176 ms
216 ms
179 ms
182 ms
184 ms
adsbygoogle.js
13 ms
tpx
213 ms
214 ms
ca-pub-6074599255075755.js
34 ms
zrt_lookup.html
40 ms
show_ads_impl.js
51 ms
ads
235 ms
osd.js
173 ms
2-z24-a1a287b2-4068-43a5-9f9f-c8d53913d3c4.jpg
454 ms
2-z11-74db745a-f488-4663-80bc-d04598ddf0f2.jpg
477 ms
2-z22-293f307b-76dd-445c-924d-e89d638ffe3b.jpg
464 ms
2-z5-06cfbab1-907d-4c2c-85d9-a14f2973624c.jpg
454 ms
2-z34-c70d5120-5a1a-4a09-b1e7-27b95e95caa5.jpg
457 ms
button.png
164 ms
2-z10-34509cc5-694d-4c9d-a97c-fefacd8554d4.jpg
618 ms
2-z35-86b96af5-8ea1-42cb-b324-1759e5bb65d5.jpg
445 ms
2-z4-e6f358bb-887a-4f90-b71e-2dd1199528be.jpg
482 ms
2-z3-846dcf29-f0b2-4f96-b8cd-63ba08fcbf5d.jpg
158 ms
2-z28-2ed15d19-a0b7-487d-81c2-dbd1df1212d0.jpg
461 ms
2-z13-62bc096e-c7ab-4434-a2b2-c91ab88d8372.jpg
448 ms
2-z8-70256a57-4482-4214-b74e-5b2da5f8e599.jpg
310 ms
2-z25-8e0ce4f9-eb2b-45bb-9d9c-03ab2aa1ef6e.jpg
1471 ms
2-z12-f3035b0b-9b68-461d-9ea7-612433f649d1.jpg
476 ms
2-z18-cfc57aff-2443-4a45-9788-1b447dd28fae.jpg
470 ms
2-z9-35f33a74-baef-4005-b3a0-71b2e4f62338.jpg
1355 ms
2-z22-2e82eaa5-b44f-42fa-b41b-ff21da065711.jpg
431 ms
2-z35-23f1a67c-3a72-4984-95b4-630bbe3cf30a.jpg
444 ms
2-z35-47d5734d-71bc-412b-ad8e-2217c58f0abe.jpg
451 ms
2-z4-67db540a-ffba-41fd-8881-86db3face60b.jpg
451 ms
2-z4-24b9a057-a8b6-4b30-8b8b-38876f0f1611.jpg
463 ms
2-z10-6b397c2b-bf9b-4b33-99d2-502e5902d25e.jpg
431 ms
2-z24-d2fcc592-1d7d-44b9-ab73-781b649457ce.jpg
409 ms
2-z5-ad4ea5d2-675b-4580-8f3c-97795b9da39b.jpg
415 ms
service_icons.png
317 ms
Widget_Login
633 ms
1519155825012727531
36 ms
abg.js
38 ms
m_js_controller.js
51 ms
googlelogo_color_112x36dp.png
10 ms
s
32 ms
x_button_blue2.png
32 ms
Rf2QnA3orEL6Eez56HJgxRuQ77qJyxbefnbSCBE0iUQ.js
16 ms
checkauth.php
679 ms
activeview
20 ms
check
1146 ms
86.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
<frame> or <iframe> elements do not have a title
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.
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.
86.ru best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
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
Page has valid source maps
86.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
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 86.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 86.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.
86.ru
Open Graph description is not detected on the main page of 86. 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: