8.9 sec in total
901 ms
7.5 sec
451 ms
Welcome to 26.ru homepage info - get ready to check 26 best content for Russia right away, or after learning these important things about 26.ru
Последние свежие новости Ставрополя и Ставропольского края за сегодня - онлайн на сайте 26.ru
Visit 26.ruWe analyzed 26.ru page load time and found that the first response time was 901 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.
26.ru performance score
name
value
score
weighting
Value3.3 s
41/100
10%
Value5.3 s
21/100
25%
Value11.2 s
5/100
10%
Value3,520 ms
1/100
30%
Value0.005
100/100
15%
Value21.5 s
1/100
10%
901 ms
926 ms
939 ms
948 ms
482 ms
Our browser made a total of 130 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original 26.ru, 48% (62 requests) were made to I.sdska.ru and 17% (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 756.3 kB (54%)
1.4 MB
641.6 kB
In fact, the total size of 26.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 132.2 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.2 kB or 80% of the original size.
Potential reduce by 39.9 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. 26 images are well optimized though.
Potential reduce by 483.2 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.2 kB or 70% 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. 26.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 76 (61%)
125
49
The browser has sent 125 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 26. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 48 to 1 for JavaScripts and from 17 to 1 for CSS and as a result speed up the page load time.
26.ru
901 ms
jquery-1.9.1.min.js
926 ms
jquery-1.8.3.min.js
939 ms
jquery.js
948 ms
jquery.xdomainrequest.min.js
482 ms
png.css
485 ms
popup_passport.css
484 ms
styles.css
645 ms
d_common.css
649 ms
d.css
649 ms
jquery.smartbanner.css
808 ms
styles.css
813 ms
announce.css
814 ms
widgets_common.css
970 ms
widgets.css
977 ms
news_d.css
978 ms
news_common.css
1076 ms
styles.css
1082 ms
styles.css
1098 ms
styles.css
1133 ms
pt_serif.css
1140 ms
common.js
1305 ms
sdb.js
1229 ms
jquery.cookie.js
1237 ms
api.js
1412 ms
jquery.waypoints.js
1295 ms
fotorama-4.4.2.js
1632 ms
fotorama.waypoints.js
1383 ms
dohcohT2.js
589 ms
ngs-place.js
1390 ms
startpage.js
1457 ms
browser_detect.js
1467 ms
google_charts.js
1535 ms
jquery.smartbanner.js
1545 ms
jquery.multi-ddm.js
1567 ms
scroll.js
1620 ms
dropdown.js
1688 ms
update_browser.js
1226 ms
paginate.js
1250 ms
poll.js
1307 ms
analytics.js
20 ms
boomerang-0.9.1401865982.js
156 ms
top100.cnt
253 ms
2-z36-f860f586-ca7c-4a8f-9079-9d885a0504cb.jpg
759 ms
2-z1-110c1306-c41b-4508-94ee-78dfac3e20cb.jpg
892 ms
2-z34-5304f3f1-aad7-400f-80e4-9da363f80df1.jpg
442 ms
2-z11-58d7fb1b-7803-4e27-9dd6-10ed762ed17b.jpg
433 ms
2-z23-9ec35fdc-4c0d-4ff9-a907-ddd19fefe6ae.jpg
610 ms
banner-88x31-rambler-gray2.gif
259 ms
logo;r26
254 ms
18plus.png
166 ms
logo.26.ru.png
156 ms
1.png
164 ms
1.png
159 ms
b3.gif
166 ms
gorod-online.png
304 ms
x.gif
308 ms
rugion_job.png
316 ms
auto.26.png
327 ms
dom.26.png
329 ms
fin.26.png
329 ms
afisha.26.png
460 ms
rugion-logo-color.png
461 ms
rn-logo-color.png
473 ms
18plus_bottom.png
489 ms
hit;r26
253 ms
hit;rugion
254 ms
26
258 ms
watch.js
181 ms
tcounter.js
274 ms
200 ms
collect
25 ms
watch.js
432 ms
201 ms
201 ms
p_common.css
156 ms
715962904
264 ms
200 ms
advert.gif
84 ms
1
85 ms
205 ms
201 ms
service_icons_simple.gif
156 ms
3c09c4007c97188455e44f8bc269576b_911.jpg
627 ms
tpx
384 ms
395 ms
198 ms
input-back.png
156 ms
select-back.png
165 ms
button-back.png
156 ms
line.png
164 ms
196 ms
200 ms
201 ms
200 ms
205 ms
201 ms
201 ms
200 ms
200 ms
201 ms
200 ms
2-z19-d3eb3579-0fd5-4e17-968c-7584645ddc2e.jpg
460 ms
2-z22-5543f2bb-50e9-4234-9ad8-0c3685edc90f.jpg
547 ms
2-z11-54890bad-4b7b-481e-b2ca-0adeff0046e9.jpg
150 ms
2-z3-84df9a8d-a45e-4865-a893-b580c7f12353.jpg
549 ms
2-z12-9582cd9b-143a-4f44-84c6-7df9d4349fde.jpg
592 ms
button.png
156 ms
2-z17-d1dd70b3-c57d-45e6-aa00-2eaea3931380.jpg
425 ms
2-z29-4e93d476-53a9-4c36-b12b-d3be9879753b.jpg
439 ms
2-z6-22b3a577-fa28-43dc-be0b-e37be79003ae.jpg
470 ms
2-z14-89b763a2-0be2-4708-983e-dfe4fe16bc45.jpg
473 ms
2-z25-55d31f4c-9cef-4ea2-94ea-9454e1110010.jpg
442 ms
2-z34-600abc67-1c9d-425d-8c69-2fdec0230d5c.jpg
154 ms
2-z15-db4e05a2-5683-4e21-8156-e7dcd2c1fb4f.jpg
446 ms
2-z16-429d3d39-8b47-4cef-9a44-bcd6fc188876.jpg
435 ms
2-z4-347940ee-69c1-49d5-a2ed-8336318c6d47.jpg
510 ms
2-z36-11d095e9-09ce-48ea-a31e-8bdfb45fd0b4.jpg
150 ms
2-z9-ec577786-5983-458c-a252-f9228d565ef5.jpg
472 ms
2-z21-efe7ad9e-f1c6-4015-bd35-6f993322737c.jpg
426 ms
2-z8-5114d7d4-ea32-43e3-82bc-c9784b1b0965.jpg
593 ms
2-z17-9b628303-6f41-4ca8-9d42-1f1241e822e7.jpg
404 ms
2-z12-ceaea620-2b4e-4e54-89c5-ae4a4f015365.jpg
577 ms
2-z22-293f307b-76dd-445c-924d-e89d638ffe3b.jpg
505 ms
2-z21-d6f6b0e2-bd88-4c55-9489-e64561910abf.jpg
446 ms
2-z6-7c511f1a-f84b-4957-9a2c-7dd52558db9a.jpg
446 ms
2-z14-8011f936-edf8-464e-90cd-49577264a9c4.jpg
449 ms
service_icons.png
330 ms
Widget_Login
170 ms
checkauth.php
801 ms
26.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.
26.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
26.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 26.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 26.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.
26.ru
Open Graph description is not detected on the main page of 26. 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: