24.9 sec in total
325 ms
24.1 sec
454 ms
Visit faberlic.ru now to see the best up-to-date Faberlic content for Russia and also check out these interesting facts you probably never knew about faberlic.ru
Информацию о продукции, выборе консультанта, новости, помощь при выборе продукции вы можете найти на официальном сайте Faberlic (Фаберлик).
Visit faberlic.ruWe analyzed Faberlic.ru page load time and found that the first response time was 325 ms and then it took 24.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster. Unfortunately, there was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
faberlic.ru performance score
325 ms
3679 ms
165 ms
332 ms
668 ms
Our browser made a total of 94 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Faberlic.ru, 66% (62 requests) were made to Faberlic.com and 5% (5 requests) were made to Ssp.adriver.ru. The less responsive or slowest element that took the longest time to load (20.1 sec) relates to the external source C.imrk.net.
Page size can be reduced by 266.1 kB (11%)
2.5 MB
2.3 MB
In fact, the total size of Faberlic.ru main page is 2.5 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. Images take 2.2 MB which makes up the majority of the site volume.
Potential reduce by 36.7 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 36.7 kB or 79% of the original size.
Potential reduce by 7.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. Faberlic images are well optimized though.
Potential reduce by 9.6 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 9.6 kB or 28% of the original size.
Potential reduce by 212.6 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. Faberlic.ru needs all CSS files to be minified and compressed as it can save up to 212.6 kB or 81% of the original size.
Number of requests can be reduced by 51 (66%)
77
26
The browser has sent 77 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Faberlic. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and from 17 to 1 for CSS and as a result speed up the page load time.
faberlic.ru
325 ms
index.php
3679 ms
jcemediabox.css
165 ms
style.css
332 ms
bootstrap.min.css
668 ms
bootstrap-theme.min.css
642 ms
font-awesome.min.css
645 ms
style.css
649 ms
style.css
649 ms
template.css
646 ms
typography.css
801 ms
jquery-ui.css
812 ms
jquery-ui.css
813 ms
fl_default.css
816 ms
fl_mainbanners.css
812 ms
mod_flvideos.css
825 ms
style.css
959 ms
mod_uparrow.css
970 ms
mootools.js
1462 ms
fix.js
976 ms
caption.js
975 ms
jcemediabox.js
1143 ms
jquery.js
1601 ms
jquery-migrate-1.2.1.min.js
1127 ms
bootstrap.min.js
1294 ms
bootstrap.fix.js
1130 ms
jquery-ui.min.js
3066 ms
script.js
1292 ms
mt_slider_noconflict.js
1302 ms
mod_flregionselection.js
1457 ms
flbootstrap.js
1486 ms
mod_uparrow.js
1486 ms
css
56 ms
conv.js
20116 ms
watch.js
107 ms
gtm.js
142 ms
rtrg
557 ms
ui-icons_ffffff_256x240.png
171 ms
popup.html
174 ms
tooltip.html
174 ms
RUv2.png
607 ms
1-SkyLine-3-2016-gl.jpg
4648 ms
2-Dom-3-2016-gl.jpg
4499 ms
4-Blur-2-2016-gl.jpg
1857 ms
7-%D0%A1hildrens-clothing-2-2016-gl.jpg
829 ms
2-Posadi-les-2-2016-nov.jpg
1146 ms
int-magazin-5-2016.jpg
1245 ms
small-1-5-2016.jpg
992 ms
small-2-5-2016.jpg
1327 ms
small-3-5-2016.jpg
1630 ms
Home-office-2.jpg
4841 ms
Manicure_copy_copy.jpg
2627 ms
Minimal-style-1.jpg
3091 ms
272.jpg
5805 ms
play68.png
2794 ms
270.jpg
3299 ms
260.jpg
3959 ms
vk.png
3483 ms
ok.png
3643 ms
youtube.png
3804 ms
facebook.png
3973 ms
twitter.png
4120 ms
instagram.png
4134 ms
google.png
4282 ms
i.js
60 ms
936cea6df534ad55010914b6d9c25171e56cba76.2.js
169 ms
K88pR3goAWT7BTt32Z01m6CWcynf_cDxXwCLxiixG1c.ttf
71 ms
DXI1ORHCpsQm3Vp6mXoaTWeP1y_Bkidl4ESyB_O2G_c.ttf
103 ms
MTP_ySUJH_bn48VBG8sNSmeP1y_Bkidl4ESyB_O2G_c.ttf
118 ms
k3k702ZOKiLJc3WVjuplzGeP1y_Bkidl4ESyB_O2G_c.ttf
127 ms
EInbV5DfGHOiMmvb1Xr-hmeP1y_Bkidl4ESyB_O2G_c.ttf
126 ms
fl-menu.ttf
4300 ms
faberlic.ttf
4462 ms
fontawesome-webfont.woff
4654 ms
glyphicons-halflings-regular.woff
4641 ms
analytics.js
40 ms
collect
19 ms
collect
82 ms
e
47 ms
ga-audiences
55 ms
image
99 ms
erle.cgi
311 ms
1.html
553 ms
1.js
409 ms
pixel
45 ms
A-J-rSexI4kuQ56SoEH7Uvw
340 ms
adriver-sync
563 ms
A-J-rSexI4kuQ56SoEH7Uvw
584 ms
pixel
19 ms
sync.cgi
552 ms
sync.cgi
275 ms
sync.cgi
388 ms
sync.cgi
262 ms
sync.cgi
131 ms
faberlic.ru SEO score
RU
RU
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Faberlic.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 Faberlic.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.
faberlic.ru
Open Graph description is not detected on the main page of Faberlic. 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: