5.5 sec in total
475 ms
4.8 sec
262 ms
Welcome to feliche.ru homepage info - get ready to check Feliche best content for Russia right away, or after learning these important things about feliche.ru
Интернет магазин одежда, нижнее белье, купальники и пляжная одежда, женские колготки и чулки, женские сумки, мужские портфели, портмоне, кошельки, домашняя одежда, детская одежда, маскарадные костюмы ...
Visit feliche.ruWe analyzed Feliche.ru page load time and found that the first response time was 475 ms and then it took 5.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
feliche.ru performance score
name
value
score
weighting
Value4.2 s
19/100
10%
Value8.8 s
1/100
25%
Value12.1 s
4/100
10%
Value12,100 ms
0/100
30%
Value0.021
100/100
15%
Value26.5 s
0/100
10%
475 ms
1141 ms
338 ms
221 ms
328 ms
Our browser made a total of 106 requests to load all elements on the main page. We found that 42% of them (45 requests) were addressed to the original Feliche.ru, 9% (10 requests) were made to Tpc.googlesyndication.com and 8% (9 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source Status.icq.com.
Page size can be reduced by 231.9 kB (39%)
596.0 kB
364.0 kB
In fact, the total size of Feliche.ru main page is 596.0 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. 65% of websites need less resources to load. Javascripts take 298.1 kB which makes up the majority of the site volume.
Potential reduce by 85.8 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 85.8 kB or 81% of the original size.
Potential reduce by 29.5 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, Feliche needs image optimization as it can save up to 29.5 kB or 19% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 88.9 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 88.9 kB or 30% of the original size.
Potential reduce by 27.7 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. Feliche.ru needs all CSS files to be minified and compressed as it can save up to 27.7 kB or 83% of the original size.
Number of requests can be reduced by 60 (67%)
89
29
The browser has sent 89 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Feliche. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 28 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
feliche.ru
475 ms
www.feliche.ru
1141 ms
style.css
338 ms
highslide.css
221 ms
sc.js
328 ms
swfobject.js
231 ms
ajax.js
232 ms
popup.js
314 ms
jquery-1.4.4.min.js
551 ms
leobox.js
342 ms
jcarousellite.js
452 ms
11792.js
537 ms
adsbygoogle.js
40 ms
adsbygoogle.js
27 ms
watch.js
1 ms
top100.jcn
251 ms
top100.jcn
863 ms
spinner.gif
172 ms
close.png
175 ms
mbutik-index_47.gif
174 ms
mbutik-index_53.gif
170 ms
mbutik-index_55.gif
171 ms
mbutik-index_01.gif
172 ms
mbutik-index_04.gif
266 ms
mbutik-index_07.gif
266 ms
logo-feliche.gif
266 ms
mbutik-index_03.gif
266 ms
viewImg.php
271 ms
mbutik-index_03-08.gif
265 ms
mbutik-index_30.gif
382 ms
bags.gif
521 ms
sergio.jpg
492 ms
titan.gif
385 ms
mbutikvnutr1_17.gif
384 ms
hit.png
499 ms
new.png
510 ms
arr.gif
516 ms
mbutik-index_70.gif
601 ms
twitter_icon_31.gif
606 ms
facebook_icon_31.gif
619 ms
vkontakte_icon_31.jpg
626 ms
v_blue_on_white_ru.png
628 ms
aci.js
544 ms
show_ads_impl.js
53 ms
zrt_lookup.html
29 ms
feliche.msk
16 ms
online.dll
644 ms
misc.gif
581 ms
mbutik-index_25.gif
640 ms
mbutik-index_33.gif
644 ms
mbutik-index_81.gif
669 ms
mbutik-index_39.gif
677 ms
search.png
718 ms
left_arr.png
722 ms
sale2.png
745 ms
right_arr.png
677 ms
cookie.js
85 ms
integrator.js
79 ms
ads
703 ms
ads
466 ms
online.gif
1258 ms
ga.js
52 ms
1
537 ms
watch.js
5 ms
__utm.gif
17 ms
reactive_library.js
63 ms
integrator.js
45 ms
ads
670 ms
zrt_lookup.html
108 ms
css2
158 ms
14763004658117789537
175 ms
load_preloaded_resource.js
173 ms
abg_lite.js
189 ms
window_focus.js
226 ms
qs_click_protection.js
233 ms
rx_lidar.js
226 ms
042791247ab671b2831aa311d6583330.js
166 ms
interstitial_ad_frame.js
219 ms
one_click_handler_one_afma.js
489 ms
feedback_grey600_24dp.png
140 ms
settings_grey600_24dp.png
195 ms
icon.png
75 ms
4025169608974103745
487 ms
s
322 ms
css
69 ms
activeview
70 ms
KFOlCnqEu92Fr1MmWUlvAw.ttf
179 ms
KFOmCnqEu92Fr1Me5Q.ttf
179 ms
85254efcadaacab5fed344cbf203b7e7.js
54 ms
c471d9b7113df21a6cf58632ab968748.js
52 ms
4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrw2IJllpyw.ttf
100 ms
4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrwEIJllpyw.ttf
101 ms
cookie_push_onload.html
72 ms
b4aq_x9zMiku-4ayY0gQrcEuJNMSghrM2Nuaea2nyAg.js
33 ms
dpixel
225 ms
googleredir
864 ms
activeview
102 ms
sodar
139 ms
pixel
53 ms
pixel
60 ms
sodar2.js
19 ms
pixel
23 ms
pixel
17 ms
pixel
15 ms
runner.html
7 ms
aframe
74 ms
feliche.ru accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
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
<frame> or <iframe> elements do not have a title
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
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
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>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
feliche.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
Browser errors were logged to the console
Page has valid source maps
feliche.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
RU
RU
WINDOWS-1251
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Feliche.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 Feliche.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.
feliche.ru
Open Graph description is not detected on the main page of Feliche. 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: