4.7 sec in total
512 ms
3.8 sec
325 ms
Click here to check amazing S Builder content for Russia. Otherwise, check out these important facts you probably never knew about sbuilder.ru
CMS S.Builder: понятный интерфейс и легкость в обучении, расширение возможностей в любой момент, обширная документация
Visit sbuilder.ruWe analyzed Sbuilder.ru page load time and found that the first response time was 512 ms and then it took 4.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
sbuilder.ru performance score
name
value
score
weighting
Value3.4 s
37/100
10%
Value3.4 s
66/100
25%
Value4.4 s
73/100
10%
Value10 ms
100/100
30%
Value0
100/100
15%
Value3.8 s
89/100
10%
512 ms
1105 ms
406 ms
308 ms
440 ms
Our browser made a total of 65 requests to load all elements on the main page. We found that 97% of them (63 requests) were addressed to the original Sbuilder.ru, 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Sbuilder.ru.
Page size can be reduced by 183.6 kB (45%)
405.5 kB
221.9 kB
In fact, the total size of Sbuilder.ru main page is 405.5 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 20% of websites need less resources to load. Images take 211.6 kB which makes up the majority of the site volume.
Potential reduce by 33.9 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 7.9 kB, which is 19% 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 33.9 kB or 82% of the original size.
Potential reduce by 53.7 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, S Builder needs image optimization as it can save up to 53.7 kB or 25% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 78.0 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 78.0 kB or 60% of the original size.
Potential reduce by 18.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. Sbuilder.ru needs all CSS files to be minified and compressed as it can save up to 18.0 kB or 81% of the original size.
Number of requests can be reduced by 28 (44%)
63
35
The browser has sent 63 CSS, Javascripts, AJAX and image requests in order to completely render the main page of S Builder. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 6 to 1 for JavaScripts and as a result speed up the page load time.
sbuilder.ru
512 ms
www.sbuilder.ru
1105 ms
styles.css
406 ms
func.js
308 ms
fsmenu.js
440 ms
jquery-1.4.2.min.js
808 ms
jquery.mousewheel-3.0.2.pack.js
291 ms
jquery.fancybox-1.3.1.js
517 ms
jquery.fancybox-1.3.1.css
424 ms
style.css
439 ms
ga.js
50 ms
head_r.jpg
684 ms
head_l.gif
325 ms
logo.png
1362 ms
slogan.png
185 ms
ico_home.gif
183 ms
ico_mail.gif
183 ms
ico_map.gif
313 ms
srch_but.gif
313 ms
twitter.gif
314 ms
login_but.gif
441 ms
icon_part_disc.png
441 ms
icon_part_nored.png
444 ms
icon_part_pay.png
451 ms
icon_part_free.png
569 ms
cl_unesco.png
570 ms
cl_volvo.jpg
572 ms
cl_bsgv.jpg
580 ms
cl_lmaster.jpg
698 ms
cl_rbk.jpg
699 ms
cl_ercao.png
829 ms
cl_shape.jpg
708 ms
cl_zarulem.jpg
808 ms
cl_holod.jpg
827 ms
cl_gsk.jpg
828 ms
cl_rospas.jpg
836 ms
cl_cisa.jpg
937 ms
cl_vavz.jpg
959 ms
ban_word2.png
1084 ms
head_bot.gif
956 ms
head_bot_l.jpg
957 ms
head_bot_r.jpg
1059 ms
block_fon.gif
1077 ms
srch_block_fon.gif
1085 ms
cent_fon.jpg
1090 ms
block_r.gif
1188 ms
block_b.gif
1207 ms
__utm.gif
12 ms
block_r_t.gif
1046 ms
block_r_b.gif
1049 ms
h2_i_fon.jpg
1050 ms
l_menu_dot.gif
1020 ms
block_l.gif
1037 ms
block_l_t.gif
1044 ms
block_l_b.gif
1039 ms
h2_fon.jpg
921 ms
inact_fon.gif
1021 ms
r_menu_top.jpg
1037 ms
r_menu_fon.gif
1054 ms
r_menu_dot.gif
926 ms
footer.gif
932 ms
copyr_fon.jpg
924 ms
copyr_l.jpg
1012 ms
copyr_r.jpg
930 ms
act_fon.gif
926 ms
sbuilder.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.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
Form elements do not have associated labels
Links do not have a discernible name
sbuilder.ru best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
sbuilder.ru SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
RU
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Sbuilder.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 Sbuilder.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.
sbuilder.ru
Open Graph description is not detected on the main page of S Builder. 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: