9.2 sec in total
983 ms
7.6 sec
598 ms
Welcome to 116.ru homepage info - get ready to check 116 best content for Russia right away, or after learning these important things about 116.ru
Последние свежие новости Казани и Республики Татарстан за сегодня - онлайн на сайте 116.ру
Visit 116.ruWe analyzed 116.ru page load time and found that the first response time was 983 ms and then it took 8.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.
116.ru performance score
name
value
score
weighting
Value3.4 s
37/100
10%
Value23.9 s
0/100
25%
Value12.0 s
4/100
10%
Value2,000 ms
7/100
30%
Value0.004
100/100
15%
Value22.4 s
1/100
10%
983 ms
921 ms
937 ms
936 ms
455 ms
Our browser made a total of 154 requests to load all elements on the main page. We found that 1% of them (2 requests) were addressed to the original 116.ru, 44% (67 requests) were made to I.sdska.ru and 14% (22 requests) were made to Reklama.ngs.ru. The less responsive or slowest element that took the longest time to load (1.7 sec) relates to the external source I.sdska.ru.
Page size can be reduced by 1.1 MB (49%)
2.3 MB
1.2 MB
In fact, the total size of 116.ru main page is 2.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. 50% of websites need less resources to load. Javascripts take 1.2 MB which makes up the majority of the site volume.
Potential reduce by 143.5 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 143.5 kB or 81% of the original size.
Potential reduce by 67.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. 116 images are well optimized though.
Potential reduce by 829.6 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 829.6 kB or 67% 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. 116.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 91 (61%)
148
57
The browser has sent 148 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 116. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 55 to 1 for JavaScripts and from 17 to 1 for CSS and as a result speed up the page load time.
116.ru
983 ms
jquery-1.9.1.min.js
921 ms
jquery-1.8.3.min.js
937 ms
jquery.js
936 ms
jquery.xdomainrequest.min.js
455 ms
png.css
456 ms
popup_passport.css
456 ms
styles.css
615 ms
d_common.css
614 ms
d.css
617 ms
jquery.smartbanner.css
768 ms
styles.css
767 ms
announce.css
771 ms
widgets_common.css
932 ms
widgets.css
968 ms
news_d.css
969 ms
news_common.css
1069 ms
styles.css
1071 ms
styles.css
1072 ms
styles.css
1073 ms
pt_serif.css
1073 ms
common.js
1230 ms
sdb.js
1222 ms
jquery.cookie.js
1227 ms
api.js
1700 ms
jquery.waypoints.js
1228 ms
fotorama-4.4.2.js
1545 ms
fotorama.waypoints.js
1390 ms
dohcohT2.js
524 ms
popup.js
1392 ms
ngs-place.js
1392 ms
startpage.js
1393 ms
browser_detect.js
1542 ms
google_charts.js
1543 ms
jquery.smartbanner.js
1545 ms
jquery.multi-ddm.js
1550 ms
scroll.js
1693 ms
dropdown.js
1267 ms
update_browser.js
1276 ms
paginate.js
1276 ms
poll.js
1247 ms
analytics.js
16 ms
boomerang-0.9.1401865982.js
155 ms
top100.cnt
271 ms
gcount.pl
345 ms
2-z32-484a3abb-882f-491d-93e0-27788ef39468.jpg
708 ms
2-z3-01b9f3d2-0fc0-49a1-980b-26bf2d6a817f.jpg
474 ms
2-z7-d8e8b91a-786a-47c8-aacc-383c923a20c9.jpg
450 ms
2-z25-e4056571-d1da-49df-8dc9-598ccb360554.jpg
574 ms
2-z6-ea82e5be-c563-4f82-824d-5cf4a8f2b02a.jpg
318 ms
2-z23-ac3daa69-dfc4-401a-a868-6e3dd43b73de.jpg
451 ms
2-z28-e92d6ddc-0b7a-4031-8d5f-8200d91960fc.jpg
318 ms
banner-88x31-rambler-gray2.gif
265 ms
logo;16
264 ms
mobile.gif
159 ms
12x12.png
160 ms
12x12.png
160 ms
12x12.png
159 ms
18plus.png
159 ms
logo.116.ru.png
299 ms
1.png
318 ms
1.png
318 ms
b3.gif
317 ms
gorod-online.png
317 ms
x.gif
316 ms
rugion_job.png
465 ms
auto.16.png
471 ms
dom.16.png
468 ms
fin.16.png
472 ms
afisha.16.png
468 ms
rugion-logo-color.png
469 ms
rn-logo-color.png
616 ms
18plus_bottom.png
623 ms
collect
23 ms
hit;16
269 ms
hit;rugion
268 ms
16
267 ms
watch.js
1 ms
watch.js
0 ms
tcounter.js
275 ms
185 ms
183 ms
16
134 ms
hit;rugion
134 ms
hit;16
134 ms
191 ms
555636287
274 ms
180 ms
p_common.css
156 ms
180 ms
180 ms
service_icons_simple.gif
161 ms
182 ms
180 ms
input-back.png
162 ms
select-back.png
184 ms
button-back.png
160 ms
line.png
156 ms
191 ms
181 ms
194 ms
180 ms
180 ms
179 ms
193 ms
adsbygoogle.js
21 ms
tpx
192 ms
359 ms
ca-pub-6074599255075755.js
53 ms
zrt_lookup.html
59 ms
show_ads_impl.js
108 ms
ads
274 ms
osd.js
25 ms
201 ms
1519155825012727531
39 ms
abg.js
41 ms
m_js_controller.js
51 ms
googlelogo_color_112x36dp.png
34 ms
s
21 ms
x_button_blue2.png
22 ms
j6SDDiQit5YY48GNgPpnCluJgoNCzbKlh5o6eVjReZI.js
3 ms
178 ms
179 ms
2-z32-b4d6f2fc-4e9c-4171-a789-a3c51b2ca714.png
308 ms
button.png
154 ms
2-z24-a1a287b2-4068-43a5-9f9f-c8d53913d3c4.jpg
619 ms
2-z16-0e666fa9-ad57-47f8-a3b3-a3dd56f2c9ea.jpg
466 ms
2-z27-f24dee02-9f2f-4341-82bb-2c258066eac1.jpg
498 ms
2-z22-293f307b-76dd-445c-924d-e89d638ffe3b.jpg
442 ms
2-z5-06cfbab1-907d-4c2c-85d9-a14f2973624c.jpg
492 ms
2-z34-c70d5120-5a1a-4a09-b1e7-27b95e95caa5.jpg
441 ms
2-z10-34509cc5-694d-4c9d-a97c-fefacd8554d4.jpg
645 ms
2-z35-86b96af5-8ea1-42cb-b324-1759e5bb65d5.jpg
318 ms
2-z4-e6f358bb-887a-4f90-b71e-2dd1199528be.jpg
506 ms
2-z3-846dcf29-f0b2-4f96-b8cd-63ba08fcbf5d.jpg
157 ms
2-z7-46e2c23b-254b-4d17-9c24-40de0d5798c8.jpg
157 ms
2-z13-62bc096e-c7ab-4434-a2b2-c91ab88d8372.jpg
460 ms
2-z8-70256a57-4482-4214-b74e-5b2da5f8e599.jpg
436 ms
2-z25-8e0ce4f9-eb2b-45bb-9d9c-03ab2aa1ef6e.jpg
164 ms
2-z12-f3035b0b-9b68-461d-9ea7-612433f649d1.jpg
466 ms
2-z18-cfc57aff-2443-4a45-9788-1b447dd28fae.jpg
485 ms
2-z9-35f33a74-baef-4005-b3a0-71b2e4f62338.jpg
465 ms
2-z22-2e82eaa5-b44f-42fa-b41b-ff21da065711.jpg
395 ms
2-z35-23f1a67c-3a72-4984-95b4-630bbe3cf30a.jpg
319 ms
2-z35-47d5734d-71bc-412b-ad8e-2217c58f0abe.jpg
320 ms
2-z4-67db540a-ffba-41fd-8881-86db3face60b.jpg
468 ms
2-z4-24b9a057-a8b6-4b30-8b8b-38876f0f1611.jpg
469 ms
2-z10-6b397c2b-bf9b-4b33-99d2-502e5902d25e.jpg
452 ms
2-z24-d2fcc592-1d7d-44b9-ab73-781b649457ce.jpg
570 ms
2-z5-ad4ea5d2-675b-4580-8f3c-97795b9da39b.jpg
452 ms
service_icons.png
308 ms
178 ms
Widget_Login
172 ms
checkauth.php
939 ms
116.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.
116.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
116.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 116.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 116.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.
116.ru
Open Graph description is not detected on the main page of 116. 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: