8.6 sec in total
862 ms
7.2 sec
562 ms
Welcome to 70.ru homepage info - get ready to check 70 best content for Russia right away, or after learning these important things about 70.ru
Последние свежие новости Томска за сегодня - онлайн на сайте ngs70.ru
Visit 70.ruWe analyzed 70.ru page load time and found that the first response time was 862 ms and then it took 7.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.
70.ru performance score
name
value
score
weighting
Value3.5 s
34/100
10%
Value5.7 s
17/100
25%
Value10.4 s
8/100
10%
Value2,130 ms
6/100
30%
Value0.005
100/100
15%
Value20.8 s
2/100
10%
862 ms
784 ms
806 ms
804 ms
336 ms
Our browser made a total of 140 requests to load all elements on the main page. We found that 1% of them (2 requests) were addressed to the original 70.ru, 44% (61 requests) were made to I.sdska.ru and 15% (21 requests) were made to Reklama.ngs.ru. The less responsive or slowest element that took the longest time to load (1.5 sec) relates to the external source I.sdska.ru.
Page size can be reduced by 705.8 kB (51%)
1.4 MB
666.5 kB
In fact, the total size of 70.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. 55% of websites need less resources to load. Javascripts take 689.8 kB which makes up the majority of the site volume.
Potential reduce by 127.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 127.4 kB or 80% of the original size.
Potential reduce by 37.2 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. 70 images are well optimized though.
Potential reduce by 440.3 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.3 kB or 64% 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. 70.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 84 (62%)
135
51
The browser has sent 135 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 70. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 53 to 1 for JavaScripts and from 17 to 1 for CSS and as a result speed up the page load time.
70.ru
862 ms
jquery-1.9.1.min.js
784 ms
jquery-1.8.3.min.js
806 ms
jquery.js
804 ms
jquery.xdomainrequest.min.js
336 ms
png.css
313 ms
popup_passport.css
314 ms
styles.css
463 ms
d_common.css
467 ms
d.css
491 ms
jquery.smartbanner.css
617 ms
styles.css
632 ms
announce.css
648 ms
widgets_common.css
771 ms
widgets.css
800 ms
news_d.css
848 ms
news_common.css
931 ms
styles.css
940 ms
styles.css
942 ms
styles.css
943 ms
pt_serif.css
951 ms
common.js
1134 ms
sdb.js
1236 ms
jquery.cookie.js
1098 ms
api.js
1255 ms
jquery.waypoints.js
1104 ms
fotorama-4.4.2.js
1135 ms
fotorama.waypoints.js
1253 ms
dohcohT2.js
525 ms
ngs-place.js
1263 ms
startpage.js
1295 ms
browser_detect.js
1294 ms
google_charts.js
1541 ms
jquery.smartbanner.js
1405 ms
jquery.multi-ddm.js
1404 ms
scroll.js
1405 ms
dropdown.js
1456 ms
update_browser.js
1259 ms
paginate.js
1261 ms
poll.js
1237 ms
analytics.js
20 ms
boomerang-0.9.1401865982.js
156 ms
top100.cnt
264 ms
2-z32-484a3abb-882f-491d-93e0-27788ef39468.jpg
483 ms
2-z3-01b9f3d2-0fc0-49a1-980b-26bf2d6a817f.jpg
468 ms
2-z23-ac3daa69-dfc4-401a-a868-6e3dd43b73de.jpg
507 ms
banner-88x31-rambler-gray2.gif
279 ms
logo;r70
266 ms
18plus.png
165 ms
logo.70.ru.png
164 ms
13.png
160 ms
13.png
159 ms
gorod-online.png
161 ms
x.gif
306 ms
rugion_job.png
321 ms
auto.70.png
319 ms
dom.70.png
317 ms
fin.70.png
318 ms
afisha.70.png
320 ms
rugion-logo-color.png
456 ms
rn-logo-color.png
468 ms
18plus_bottom.png
468 ms
hit;r70
265 ms
collect
15 ms
hit;rugion
275 ms
rugion
275 ms
watch.js
1 ms
tcounter.js
292 ms
183 ms
194 ms
hit;r70
159 ms
hit;rugion
133 ms
rugion
128 ms
181 ms
p_common.css
154 ms
190 ms
51651316
291 ms
180 ms
197 ms
service_icons_simple.gif
161 ms
195 ms
192 ms
input-back.png
194 ms
select-back.png
195 ms
button-back.png
196 ms
line.png
211 ms
207 ms
186 ms
241 ms
181 ms
184 ms
181 ms
180 ms
adsbygoogle.js
12 ms
tpx
184 ms
351 ms
ca-pub-6074599255075755.js
50 ms
zrt_lookup.html
50 ms
show_ads_impl.js
63 ms
ads
264 ms
osd.js
5 ms
207 ms
9992165196292414217
63 ms
abg.js
68 ms
m_js_controller.js
78 ms
googlelogo_color_112x36dp.png
43 ms
s
29 ms
x_button_blue2.png
28 ms
j6SDDiQit5YY48GNgPpnCluJgoNCzbKlh5o6eVjReZI.js
11 ms
191 ms
181 ms
2-z3-5e14ca44-95b9-4cac-9db5-69e19dd37bc1.jpg
155 ms
2-z24-a1a287b2-4068-43a5-9f9f-c8d53913d3c4.jpg
469 ms
2-z22-293f307b-76dd-445c-924d-e89d638ffe3b.jpg
450 ms
2-z5-06cfbab1-907d-4c2c-85d9-a14f2973624c.jpg
464 ms
2-z34-c70d5120-5a1a-4a09-b1e7-27b95e95caa5.jpg
318 ms
button.png
158 ms
2-z10-34509cc5-694d-4c9d-a97c-fefacd8554d4.jpg
450 ms
2-z35-86b96af5-8ea1-42cb-b324-1759e5bb65d5.jpg
448 ms
2-z4-e6f358bb-887a-4f90-b71e-2dd1199528be.jpg
469 ms
2-z8-e9e7c265-79ca-4e01-9eb2-b97c070d8edf.jpg
314 ms
2-z13-62bc096e-c7ab-4434-a2b2-c91ab88d8372.jpg
438 ms
2-z25-8e0ce4f9-eb2b-45bb-9d9c-03ab2aa1ef6e.jpg
448 ms
2-z12-f3035b0b-9b68-461d-9ea7-612433f649d1.jpg
464 ms
2-z18-cfc57aff-2443-4a45-9788-1b447dd28fae.jpg
478 ms
2-z9-35f33a74-baef-4005-b3a0-71b2e4f62338.jpg
483 ms
2-z22-2e82eaa5-b44f-42fa-b41b-ff21da065711.jpg
438 ms
2-z3-846dcf29-f0b2-4f96-b8cd-63ba08fcbf5d.jpg
270 ms
2-z35-23f1a67c-3a72-4984-95b4-630bbe3cf30a.jpg
420 ms
2-z35-47d5734d-71bc-412b-ad8e-2217c58f0abe.jpg
423 ms
2-z4-67db540a-ffba-41fd-8881-86db3face60b.jpg
442 ms
2-z4-24b9a057-a8b6-4b30-8b8b-38876f0f1611.jpg
442 ms
2-z10-6b397c2b-bf9b-4b33-99d2-502e5902d25e.jpg
315 ms
2-z24-d2fcc592-1d7d-44b9-ab73-781b649457ce.jpg
430 ms
2-z8-70256a57-4482-4214-b74e-5b2da5f8e599.jpg
322 ms
2-z5-ad4ea5d2-675b-4580-8f3c-97795b9da39b.jpg
430 ms
service_icons.png
312 ms
Widget_Login
173 ms
checkauth.php
840 ms
activeview
14 ms
70.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.
70.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
70.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 70.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 70.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.
70.ru
Open Graph description is not detected on the main page of 70. 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: