9.9 sec in total
1.1 sec
8.3 sec
560 ms
Click here to check amazing 164 content for Russia. Otherwise, check out these important facts you probably never knew about 164.ru
Последние свежие новости Саратова и Саратовской области за сегодня - онлайн на сайте 164.ru
Visit 164.ruWe analyzed 164.ru page load time and found that the first response time was 1.1 sec and then it took 8.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.
164.ru performance score
name
value
score
weighting
Value3.3 s
39/100
10%
Value5.8 s
15/100
25%
Value9.3 s
12/100
10%
Value2,320 ms
5/100
30%
Value0.005
100/100
15%
Value22.1 s
1/100
10%
1078 ms
965 ms
979 ms
993 ms
470 ms
Our browser made a total of 133 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original 164.ru, 47% (62 requests) were made to I.sdska.ru and 17% (23 requests) were made to Reklama.ngs.ru. The less responsive or slowest element that took the longest time to load (1.8 sec) relates to the external source I.sdska.ru.
Page size can be reduced by 737.9 kB (55%)
1.4 MB
614.7 kB
In fact, the total size of 164.ru main page is 1.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. 45% of websites need less resources to load. Javascripts take 694.2 kB which makes up the majority of the site volume.
Potential reduce by 130.4 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 130.4 kB or 81% of the original size.
Potential reduce by 34.0 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. 164 images are well optimized though.
Potential reduce by 483.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 483.1 kB or 70% of the original size.
Potential reduce by 90.3 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. 164.ru needs all CSS files to be minified and compressed as it can save up to 90.3 kB or 82% of the original size.
Number of requests can be reduced by 81 (63%)
128
47
The browser has sent 128 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 164. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 49 to 1 for JavaScripts and from 17 to 1 for CSS and as a result speed up the page load time.
164.ru
1078 ms
jquery-1.9.1.min.js
965 ms
jquery-1.8.3.min.js
979 ms
jquery.js
993 ms
jquery.xdomainrequest.min.js
470 ms
png.css
470 ms
popup_passport.css
472 ms
styles.css
635 ms
d_common.css
637 ms
d.css
638 ms
jquery.smartbanner.css
797 ms
styles.css
800 ms
announce.css
802 ms
widgets_common.css
1005 ms
widgets.css
1005 ms
news_d.css
1005 ms
news_common.css
1123 ms
styles.css
1123 ms
styles.css
1124 ms
styles.css
1125 ms
pt_serif.css
1130 ms
common.js
1300 ms
sdb.js
1285 ms
jquery.cookie.js
1287 ms
api.js
1450 ms
jquery.waypoints.js
1288 ms
fotorama-4.4.2.js
1624 ms
fotorama.waypoints.js
1449 ms
dohcohT2.js
595 ms
ngs-place.js
1454 ms
startpage.js
1455 ms
browser_detect.js
1462 ms
google_charts.js
1613 ms
jquery.smartbanner.js
1614 ms
jquery.multi-ddm.js
1616 ms
scroll.js
1617 ms
dropdown.js
1777 ms
update_browser.js
1330 ms
paginate.js
1330 ms
poll.js
1330 ms
analytics.js
20 ms
boomerang-0.9.1401865982.js
166 ms
top100.cnt
253 ms
2-z11-9ea618ed-f8e7-4fa6-baa8-d586f054ca95.jpg
750 ms
2-z31-1daebb06-f9fa-4a06-993e-ae4e23be2f07.jpg
802 ms
2-z36-d0a6228f-755f-4a20-9433-6292b70d7e9e.jpg
582 ms
2-z34-73eaa262-1593-42bc-9165-f4e28cef06c3.jpg
557 ms
2-z22-45e5f20b-4554-4edd-8eef-f99fc1a1eb0a.jpg
466 ms
banner-88x31-rambler-gray2.gif
254 ms
logo;r64
259 ms
18plus.png
166 ms
logo.164.ru.png
167 ms
2.png
168 ms
2.png
169 ms
b3.gif
168 ms
gorod-online.png
320 ms
x.gif
325 ms
rugion_job.png
325 ms
auto.64.png
327 ms
dom.64.png
326 ms
fin.64.png
328 ms
afisha.64.png
481 ms
rugion-logo-color.png
486 ms
rn-logo-color.png
487 ms
18plus_bottom.png
488 ms
2-z11-163c0ad8-97cc-4450-9b54-13d8eacf1385.jpg
581 ms
hit;r64
252 ms
hit;rugion
256 ms
64
256 ms
watch.js
226 ms
tcounter.js
256 ms
200 ms
collect
12 ms
201 ms
watch.js
577 ms
hit;r64
128 ms
hit;rugion
132 ms
64
130 ms
201 ms
p_common.css
166 ms
625469436
256 ms
222 ms
advert.gif
112 ms
202 ms
201 ms
1
113 ms
202 ms
service_icons_simple.gif
169 ms
1ab7cdba2537ee0deb11c0a389ed2a2a_145.jpg
635 ms
tpx
390 ms
394 ms
202 ms
input-back.png
168 ms
select-back.png
167 ms
button-back.png
168 ms
200 ms
201 ms
202 ms
205 ms
201 ms
202 ms
211 ms
202 ms
201 ms
201 ms
205 ms
2-z20-d595ea8a-d489-4bba-8bc4-e74c8dbbd47f.jpg
481 ms
2-z27-ad818b8a-3b4f-4e7e-ba76-36c2cf366308.jpg
608 ms
2-z22-293f307b-76dd-445c-924d-e89d638ffe3b.jpg
148 ms
2-z10-edc97dee-cc43-4cd6-873d-99ef359bdbef.jpg
457 ms
button.png
172 ms
2-z23-e84a624a-fb74-4ce5-9f59-dded2daf6176.jpg
490 ms
2-z30-c51f36f2-65a1-48d2-8415-550881b6f47d.jpg
437 ms
2-z17-0354c4c5-c966-45db-903a-3d5ec6b4b322.jpg
562 ms
2-z35-f0db4915-7542-4083-8c84-d23627f348b3.jpg
438 ms
2-z34-1add2218-bc2c-47e1-9a81-028f649436bd.jpg
161 ms
2-z36-0963c37e-05be-4c97-a5f7-69b172f57ed8.jpg
161 ms
2-z5-3bac2bbc-2631-43a8-89da-441fea0963d3.jpg
526 ms
2-z6-1ede6f18-63be-4266-bcf6-b692e4069ad5.jpg
484 ms
2-z31-e7a3d089-fd65-4cef-b5ff-185c2994bcf0.jpg
167 ms
line.png
167 ms
2-z23-b1785d16-143b-43ca-b14e-9ba6d7d6f76f.jpg
462 ms
2-z20-29313ffb-d503-45a2-b5cd-26d2fe59a3c0.jpg
437 ms
2-z22-d432d681-eed9-4ad4-acdd-5def75fef9ef.jpg
254 ms
2-z36-0f41d6c1-451c-4478-a094-0f6acbab6f8b.jpg
296 ms
2-z30-e01667d9-446e-4b2b-852e-a2fb08af484a.jpg
426 ms
2-z30-0f903aed-f3db-4324-a17d-5db6deb39d57.jpg
428 ms
2-z34-9c78eda5-cb60-4919-831d-463b4eaa818d.jpg
296 ms
2-z35-d678afe3-915f-4f6c-ad8b-fa47675106fa.jpg
434 ms
2-z35-535b5053-6cc7-404d-b045-533672c53c24.jpg
435 ms
service_icons.png
328 ms
Widget_Login
169 ms
checkauth.php
848 ms
164.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.
164.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
164.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 164.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 164.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.
164.ru
Open Graph description is not detected on the main page of 164. 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: