10.3 sec in total
867 ms
8.7 sec
694 ms
Click here to check amazing 93 content for Russia. Otherwise, check out these important facts you probably never knew about 93.ru
Последние свежие новости Краснодара и Краснодарского края за сегодня - онлайн на сайте 93.ру
Visit 93.ruWe analyzed 93.ru page load time and found that the first response time was 867 ms and then it took 9.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
93.ru performance score
name
value
score
weighting
Value4.1 s
21/100
10%
Value20.9 s
0/100
25%
Value11.9 s
4/100
10%
Value3,950 ms
1/100
30%
Value0.005
100/100
15%
Value24.1 s
0/100
10%
867 ms
923 ms
960 ms
953 ms
473 ms
Our browser made a total of 134 requests to load all elements on the main page. We found that 1% of them (2 requests) were addressed to the original 93.ru, 49% (66 requests) were made to I.sdska.ru and 18% (24 requests) were made to Reklama.ngs.ru. The less responsive or slowest element that took the longest time to load (2.1 sec) relates to the external source I.sdska.ru.
Page size can be reduced by 607.5 kB (48%)
1.3 MB
648.2 kB
In fact, the total size of 93.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. 45% of websites need less resources to load. Javascripts take 627.7 kB which makes up the majority of the site volume.
Potential reduce by 133.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 133.4 kB or 80% of the original size.
Potential reduce by 33.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. 93 images are well optimized though.
Potential reduce by 440.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 440.2 kB or 70% of the original size.
Number of requests can be reduced by 81 (63%)
129
48
The browser has sent 129 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 93. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 47 to 1 for JavaScripts and from 17 to 1 for CSS and as a result speed up the page load time.
93.ru
867 ms
jquery-1.9.1.min.js
923 ms
jquery-1.8.3.min.js
960 ms
jquery.js
953 ms
jquery.xdomainrequest.min.js
473 ms
png.css
464 ms
popup_passport.css
474 ms
styles.css
636 ms
d_common.css
641 ms
d.css
643 ms
jquery.smartbanner.css
1213 ms
styles.css
1210 ms
announce.css
1214 ms
widgets_common.css
1212 ms
widgets.css
1215 ms
news_d.css
1216 ms
news_common.css
1371 ms
styles.css
1367 ms
styles.css
1372 ms
styles.css
1377 ms
pt_serif.css
1373 ms
common.js
1375 ms
sdb.js
1561 ms
jquery.cookie.js
1565 ms
api.js
2056 ms
jquery.waypoints.js
1566 ms
fotorama-4.4.2.js
1566 ms
fotorama.waypoints.js
1566 ms
dohcohT2.js
580 ms
popup.js
1715 ms
ngs-place.js
1723 ms
startpage.js
1724 ms
browser_detect.js
1724 ms
google_charts.js
1902 ms
jquery.smartbanner.js
1869 ms
jquery.multi-ddm.js
1883 ms
scroll.js
1902 ms
dropdown.js
1575 ms
update_browser.js
1592 ms
paginate.js
1626 ms
poll.js
1488 ms
analytics.js
83 ms
boomerang-0.9.1401865982.js
237 ms
top100.cnt
370 ms
2-z32-484a3abb-882f-491d-93e0-27788ef39468.jpg
707 ms
2-z3-01b9f3d2-0fc0-49a1-980b-26bf2d6a817f.jpg
565 ms
2-z23-ac3daa69-dfc4-401a-a868-6e3dd43b73de.jpg
585 ms
banner-88x31-rambler-gray2.gif
378 ms
logo;r93
371 ms
12x12.png
249 ms
12x12.png
236 ms
12x12.png
241 ms
18plus.png
240 ms
logo.93.ru.png
247 ms
1.png
411 ms
1.png
411 ms
b3.gif
420 ms
gorod-online.png
420 ms
x.gif
423 ms
rugion_job.png
418 ms
auto.93.png
575 ms
dom.93.png
572 ms
fin.93.png
587 ms
afisha.93.png
583 ms
rugion-logo-color.png
581 ms
rn-logo-color.png
616 ms
18plus_bottom.png
730 ms
hit;r93
361 ms
hit;rugion
371 ms
rugion
371 ms
watch.js
1 ms
tcounter.js
374 ms
938 ms
collect
23 ms
hit;r93
128 ms
rugion
133 ms
hit;rugion
132 ms
356976846
256 ms
p_common.css
162 ms
180 ms
179 ms
181 ms
181 ms
182 ms
service_icons_simple.gif
163 ms
21ee7646e83dd841e1b3e6801a6d6bfd_452.jpg
394 ms
tpx
350 ms
377 ms
208 ms
input-back.png
162 ms
select-back.png
165 ms
button-back.png
158 ms
line.png
163 ms
188 ms
214 ms
180 ms
180 ms
179 ms
179 ms
204 ms
a1303d0c9dfc5febdb1a2f88b24315fe_347.gif
1058 ms
tpx
176 ms
182 ms
180 ms
193 ms
258 ms
2-z7-084b2a52-167b-41f0-a043-4571c163a020.jpg
752 ms
2-z33-40164b8b-d293-4bfa-b8c6-4f8aac1762d7.jpg
613 ms
2-z22-293f307b-76dd-445c-924d-e89d638ffe3b.jpg
466 ms
2-z5-06cfbab1-907d-4c2c-85d9-a14f2973624c.jpg
353 ms
2-z34-c70d5120-5a1a-4a09-b1e7-27b95e95caa5.jpg
532 ms
button.png
221 ms
2-z10-34509cc5-694d-4c9d-a97c-fefacd8554d4.jpg
692 ms
2-z35-86b96af5-8ea1-42cb-b324-1759e5bb65d5.jpg
348 ms
2-z4-e6f358bb-887a-4f90-b71e-2dd1199528be.jpg
461 ms
2-z3-846dcf29-f0b2-4f96-b8cd-63ba08fcbf5d.jpg
207 ms
2-z24-d2fcc592-1d7d-44b9-ab73-781b649457ce.jpg
576 ms
2-z13-62bc096e-c7ab-4434-a2b2-c91ab88d8372.jpg
572 ms
2-z8-70256a57-4482-4214-b74e-5b2da5f8e599.jpg
502 ms
2-z25-8e0ce4f9-eb2b-45bb-9d9c-03ab2aa1ef6e.jpg
499 ms
2-z12-f3035b0b-9b68-461d-9ea7-612433f649d1.jpg
558 ms
2-z18-cfc57aff-2443-4a45-9788-1b447dd28fae.jpg
497 ms
2-z9-35f33a74-baef-4005-b3a0-71b2e4f62338.jpg
463 ms
2-z22-2e82eaa5-b44f-42fa-b41b-ff21da065711.jpg
414 ms
2-z35-23f1a67c-3a72-4984-95b4-630bbe3cf30a.jpg
330 ms
2-z35-47d5734d-71bc-412b-ad8e-2217c58f0abe.jpg
331 ms
2-z34-ab797190-4a15-4d62-853e-8781682a6948.jpg
489 ms
2-z4-67db540a-ffba-41fd-8881-86db3face60b.jpg
417 ms
2-z4-24b9a057-a8b6-4b30-8b8b-38876f0f1611.jpg
415 ms
2-z10-6b397c2b-bf9b-4b33-99d2-502e5902d25e.jpg
525 ms
2-z5-ad4ea5d2-675b-4580-8f3c-97795b9da39b.jpg
365 ms
service_icons.png
335 ms
Widget_Login
174 ms
checkauth.php
915 ms
93.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.
93.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
93.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 93.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 93.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.
93.ru
Open Graph description is not detected on the main page of 93. 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: