13.7 sec in total
1.2 sec
9.5 sec
2.9 sec
Visit site12.ru now to see the best up-to-date Site 12 content for Russia and also check out these interesting facts you probably never knew about site12.ru
Сделай первый шаг к собственному успеху в инфо-бизнесе - создай сайт прямо сейчас и получи поддержку веб-мастера Василия Сенченко до полного освоения управления сайтом
Visit site12.ruWe analyzed Site12.ru page load time and found that the first response time was 1.2 sec and then it took 12.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
site12.ru performance score
name
value
score
weighting
Value4.1 s
21/100
10%
Value4.1 s
46/100
25%
Value7.7 s
24/100
10%
Value140 ms
95/100
30%
Value0.045
99/100
15%
Value8.3 s
40/100
10%
1192 ms
272 ms
341 ms
342 ms
342 ms
Our browser made a total of 147 requests to load all elements on the main page. We found that 37% of them (54 requests) were addressed to the original Site12.ru, 6% (9 requests) were made to Static.xx.fbcdn.net and 6% (9 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (2.7 sec) relates to the external source Smartinfomarketing.ru.
Page size can be reduced by 654.6 kB (56%)
1.2 MB
516.3 kB
In fact, the total size of Site12.ru main page is 1.2 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 565.7 kB which makes up the majority of the site volume.
Potential reduce by 70.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. This page needs HTML code to be minified as it can gain 12.5 kB, which is 14% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 70.5 kB or 77% of the original size.
Potential reduce by 59.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. Obviously, Site 12 needs image optimization as it can save up to 59.8 kB or 16% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 407.8 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 407.8 kB or 72% of the original size.
Potential reduce by 116.5 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. Site12.ru needs all CSS files to be minified and compressed as it can save up to 116.5 kB or 85% of the original size.
Number of requests can be reduced by 78 (57%)
137
59
The browser has sent 137 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Site 12. 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 14 to 1 for CSS and as a result speed up the page load time.
site12.ru
1192 ms
style.css
272 ms
widget.css
341 ms
pagenavi-css.css
342 ms
share-buttons-user.css
342 ms
odkl_share.css
415 ms
share-buttons.js
351 ms
plusone.js
149 ms
share.js
380 ms
openapi.js
522 ms
odkl_share.js
412 ms
odkl_init.js
349 ms
share.js
697 ms
widgets.js
176 ms
button.js
89 ms
wide_form.css
462 ms
cforms.js
472 ms
plusone.js
193 ms
loader.js
678 ms
watch.js
1 ms
wp-embed.min.js
363 ms
top100.jcn
497 ms
heightMatch.js
363 ms
topmenudynamic.js
364 ms
dropdown.js
475 ms
niftycube.js
485 ms
niftylayout.js
485 ms
audio-player.js
559 ms
aa73ec5156
2000 ms
wp-emoji-release.min.js
287 ms
odkl_share.js
362 ms
loader.js
505 ms
cb=gapi.loaded_0
162 ms
connect.js
787 ms
new_share_buttons_sprite.gif
1128 ms
calendar.css
136 ms
webinar_zakaz_1.png
793 ms
ArrowDownGreenGloss.gif
2696 ms
novosti
188 ms
110523-radio-pixel-88x31.gif
326 ms
yamoney_logo88x31.gif
851 ms
attestated1.gif
596 ms
blue_rus.gif
593 ms
girlanda.gif
235 ms
newyeargif1.png
699 ms
12_header_fig.png
233 ms
ico_posts.png
234 ms
order19.png
233 ms
ico_comments.png
229 ms
ico_tags.png
369 ms
bullet.gif
297 ms
guar_05.gif
368 ms
blockquote.gif
367 ms
IMG_3982-Edit-web.jpg
531 ms
facebook.png
531 ms
googlebuzz.png
556 ms
googleplus.png
556 ms
livejournal.png
556 ms
mailru.png
598 ms
odnoklassniki.png
622 ms
twitter.png
626 ms
yandex.png
625 ms
shop-100x100.gif
715 ms
IMG_3944-Edit-web.jpg
808 ms
button-faq-blue.png
689 ms
rss_32.png
713 ms
email_32.png
713 ms
facebook_32.png
806 ms
twitter_32.png
822 ms
planeta-web.jpg
861 ms
pro128_2013.png
1012 ms
planeta-2013.png
861 ms
rss.png
957 ms
logo_qiwi_88-31.png
956 ms
paypal_logo1.gif
967 ms
blue_rus.gif
1012 ms
imp.php
349 ms
vkontakte.png
849 ms
all.js
80 ms
grstat
683 ms
api_min.js
864 ms
h.gif
843 ms
widgets.js
65 ms
hit
315 ms
128 ms
top100.scn
169 ms
xd_arbiter.php
110 ms
xd_arbiter.php
209 ms
n.js
489 ms
hit
175 ms
aa73ec5156
329 ms
share_button
1550 ms
jadqs.php
119 ms
fixed2.png
1347 ms
q.png
1346 ms
chat
1703 ms
timeline.0eae788bc4fdbe9cd3e72dca3bc26358.js
492 ms
cb=gapi.loaded_1
122 ms
fastbutton
301 ms
jquery.js
1709 ms
uber-share.js
982 ms
20.css
964 ms
postmessageRelay
354 ms
cb=gapi.loaded_0
252 ms
cb=gapi.loaded_1
231 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
707 ms
like.php
339 ms
syndication
880 ms
295532270058606592
1450 ms
main.css
443 ms
fileuploader.css
555 ms
jquery.min.js
1000 ms
common.js
648 ms
members.js
678 ms
fileuploader.js
677 ms
1077434459-postmessagerelay.js
753 ms
rpc:shindig_random.js
437 ms
GpH30OGHRCO.css
725 ms
6E5a9811sQJ.css
1074 ms
AdP_CKHZFBh.css
1269 ms
SRSW8M763HA.js
1371 ms
mRhXF6EZrXA.js
1369 ms
-7sxH8Epaiq.js
1534 ms
LqnpVxuPHMV.js
1526 ms
cb=gapi.loaded_0
578 ms
mm-oval.png
666 ms
preloader.gif
649 ms
proxy.jpg
680 ms
proxy.jpg
943 ms
proxy.jpg
915 ms
proxy.jpg
831 ms
proxy.jpg
914 ms
proxy.jpg
914 ms
proxy.jpg
908 ms
timeline.f7130f11be9c2719286897ede16853b9.light.ltr.css
229 ms
grstat
811 ms
d525461.gif
1161 ms
code.js
808 ms
iPqzqrk7Z2P.js
122 ms
dB3ZYGvze89.js
327 ms
timeline.f7130f11be9c2719286897ede16853b9.light.ltr.css
303 ms
IMG_3944-Edit_normal.jpg
978 ms
euqA4xQc_normal.jpg
1014 ms
counter
195 ms
niftyCorners.css
938 ms
tracker
200 ms
jot
70 ms
site12.ru accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
Image elements do not have [alt] attributes
<input type="image"> elements do not have [alt] text
Form elements do not have associated labels
Links do not have a discernible name
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
site12.ru best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
site12.ru SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
RU
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Site12.ru can be misinterpreted by Google and other search engines. Our service has detected that Russian is used on the page, and it matches the claimed language. Our system also found out that Site12.ru main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.
site12.ru
Open Graph data is detected on the main page of Site 12. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: