9 sec in total
946 ms
7.4 sec
630 ms
Visit 89.ru now to see the best up-to-date 89 content for Russia and also check out these interesting facts you probably never knew about 89.ru
Последние свежие новости Салехарда и Ямало-Ненецкого автономного округа за сегодня - онлайн на сайте 89.ру
Visit 89.ruWe analyzed 89.ru page load time and found that the first response time was 946 ms and then it took 8 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
89.ru performance score
name
value
score
weighting
Value5.1 s
9/100
10%
Value8.0 s
2/100
25%
Value14.7 s
1/100
10%
Value3,460 ms
2/100
30%
Value0.003
100/100
15%
Value27.7 s
0/100
10%
946 ms
993 ms
1015 ms
1029 ms
545 ms
Our browser made a total of 143 requests to load all elements on the main page. We found that 1% of them (2 requests) were addressed to the original 89.ru, 43% (62 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 (1.9 sec) relates to the external source I.sdska.ru.
Page size can be reduced by 688.8 kB (51%)
1.3 MB
648.9 kB
In fact, the total size of 89.ru main page is 1.3 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 814.6 kB which makes up the majority of the site volume.
Potential reduce by 131.3 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 131.3 kB or 80% of the original size.
Potential reduce by 15.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. 89 images are well optimized though.
Potential reduce by 440.9 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 440.9 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. 89.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 86 (62%)
138
52
The browser has sent 138 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 89. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 52 to 1 for JavaScripts and from 17 to 1 for CSS and as a result speed up the page load time.
89.ru
946 ms
jquery-1.9.1.min.js
993 ms
jquery-1.8.3.min.js
1015 ms
jquery.js
1029 ms
jquery.xdomainrequest.min.js
545 ms
png.css
546 ms
popup_passport.css
547 ms
styles.css
699 ms
d_common.css
701 ms
d.css
709 ms
jquery.smartbanner.css
854 ms
styles.css
856 ms
announce.css
870 ms
widgets_common.css
1009 ms
widgets.css
1023 ms
news_d.css
1046 ms
news_common.css
1139 ms
styles.css
1163 ms
styles.css
1165 ms
styles.css
1166 ms
pt_serif.css
1179 ms
common.js
1352 ms
sdb.js
1289 ms
jquery.cookie.js
1317 ms
api.js
1475 ms
jquery.waypoints.js
1321 ms
fotorama-4.4.2.js
1887 ms
fotorama.waypoints.js
1439 ms
dohcohT2.js
561 ms
ngs-place.js
1469 ms
startpage.js
1478 ms
browser_detect.js
1510 ms
google_charts.js
1586 ms
jquery.smartbanner.js
1623 ms
jquery.multi-ddm.js
1627 ms
scroll.js
1629 ms
dropdown.js
1753 ms
update_browser.js
1277 ms
paginate.js
1275 ms
poll.js
1275 ms
analytics.js
37 ms
boomerang-0.9.1401865982.js
333 ms
top100.cnt
323 ms
hit;72
326 ms
hit;rugion
319 ms
89
319 ms
watch.js
0 ms
2-z7-633e14a5-8e15-48f5-a439-b033c105ece1.jpg
719 ms
2-z3-01b9f3d2-0fc0-49a1-980b-26bf2d6a817f.jpg
564 ms
2-z23-ac3daa69-dfc4-401a-a868-6e3dd43b73de.jpg
562 ms
banner-88x31-rambler-gray2.gif
314 ms
18plus.png
173 ms
logo.89.ru.png
183 ms
6.png
215 ms
6.png
183 ms
b3.gif
173 ms
gorod-online.png
323 ms
x.gif
328 ms
rugion_job.png
337 ms
auto.89.png
345 ms
dom.89.png
383 ms
fin.89.png
500 ms
afisha.89.png
490 ms
rugion-logo-color.png
488 ms
rn-logo-color.png
492 ms
18plus_bottom.png
502 ms
logo
314 ms
tcounter.js
275 ms
215 ms
collect
40 ms
188 ms
hit;rugion
135 ms
89
135 ms
hit;72
137 ms
f3edabddb100e6c053c5f3720703978c_145.jpg
751 ms
tpx
376 ms
382 ms
p_common.css
158 ms
569709573
275 ms
194 ms
192 ms
195 ms
6b55a5b4370677f6a80ac9c40fc74edb_1384.html
425 ms
service_icons_simple.gif
161 ms
tpx
190 ms
195 ms
clicktrack.js
228 ms
runtime.js
53 ms
419 ms
input-back.png
162 ms
select-back.png
159 ms
button-back.png
159 ms
line.png
165 ms
200 ms
198 ms
191 ms
193 ms
219 ms
189 ms
192 ms
adsbygoogle.js
14 ms
tpx
192 ms
198 ms
ca-pub-6074599255075755.js
56 ms
zrt_lookup.html
109 ms
show_ads_impl.js
51 ms
ads
258 ms
osd.js
11 ms
2-z24-a1a287b2-4068-43a5-9f9f-c8d53913d3c4.jpg
591 ms
2-z22-78efb6cd-9fb9-48ac-a8b5-645eb5a80534.jpg
640 ms
2-z5-06cfbab1-907d-4c2c-85d9-a14f2973624c.jpg
507 ms
2-z34-c70d5120-5a1a-4a09-b1e7-27b95e95caa5.jpg
479 ms
button.png
160 ms
2-z10-34509cc5-694d-4c9d-a97c-fefacd8554d4.jpg
714 ms
2-z35-86b96af5-8ea1-42cb-b324-1759e5bb65d5.jpg
558 ms
2-z4-e6f358bb-887a-4f90-b71e-2dd1199528be.jpg
548 ms
2-z3-846dcf29-f0b2-4f96-b8cd-63ba08fcbf5d.jpg
181 ms
2-z1-96574735-0448-4e08-a08b-eb4623a196e8.jpg
593 ms
2-z16-2ea0a4a4-3c02-42eb-abfa-e956b93fc00d.jpg
532 ms
2-z13-62bc096e-c7ab-4434-a2b2-c91ab88d8372.jpg
600 ms
2-z8-70256a57-4482-4214-b74e-5b2da5f8e599.jpg
548 ms
2-z25-8e0ce4f9-eb2b-45bb-9d9c-03ab2aa1ef6e.jpg
477 ms
2-z12-f3035b0b-9b68-461d-9ea7-612433f649d1.jpg
508 ms
2-z18-cfc57aff-2443-4a45-9788-1b447dd28fae.jpg
605 ms
2-z9-35f33a74-baef-4005-b3a0-71b2e4f62338.jpg
512 ms
2-z22-293f307b-76dd-445c-924d-e89d638ffe3b.jpg
595 ms
2-z22-2e82eaa5-b44f-42fa-b41b-ff21da065711.jpg
606 ms
2-z35-23f1a67c-3a72-4984-95b4-630bbe3cf30a.jpg
530 ms
2-z35-47d5734d-71bc-412b-ad8e-2217c58f0abe.jpg
563 ms
2-z4-24b9a057-a8b6-4b30-8b8b-38876f0f1611.jpg
517 ms
2-z10-6b397c2b-bf9b-4b33-99d2-502e5902d25e.jpg
519 ms
2-z24-d2fcc592-1d7d-44b9-ab73-781b649457ce.jpg
545 ms
2-z5-ad4ea5d2-675b-4580-8f3c-97795b9da39b.jpg
503 ms
service_icons.png
302 ms
Widget_Login
204 ms
9992165196292414217
47 ms
abg.js
47 ms
m_js_controller.js
59 ms
googlelogo_color_112x36dp.png
14 ms
s
24 ms
x_button_blue2.png
24 ms
j6SDDiQit5YY48GNgPpnCluJgoNCzbKlh5o6eVjReZI.js
4 ms
checkauth.php
857 ms
89.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
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.
89.ru best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
89.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 89.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 89.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.
89.ru
Open Graph description is not detected on the main page of 89. 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: