10.6 sec in total
1.1 sec
9.2 sec
353 ms
Click here to check amazing Linife content for Russia. Otherwise, check out these important facts you probably never knew about linife.ru
✓ Интернет-магазин товаров изо льна ✓ Бесплатная доставка по России! ✓ Низкие цены! ✓ Широкий ассортимент льняных товаров! тел: ☎ +7 (499) 703-47-87
Visit linife.ruWe analyzed Linife.ru page load time and found that the first response time was 1.1 sec and then it took 9.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
linife.ru performance score
name
value
score
weighting
Value4.8 s
11/100
10%
Value7.8 s
3/100
25%
Value6.5 s
39/100
10%
Value150 ms
94/100
30%
Value0.5
16/100
15%
Value7.7 s
45/100
10%
1135 ms
405 ms
614 ms
439 ms
442 ms
Our browser made a total of 97 requests to load all elements on the main page. We found that 68% of them (66 requests) were addressed to the original Linife.ru, 9% (9 requests) were made to Analitycs.perezvoni.com and 5% (5 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (6.3 sec) relates to the external source Cleversite.ru.
Page size can be reduced by 291.0 kB (21%)
1.4 MB
1.1 MB
In fact, the total size of Linife.ru main page is 1.4 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 1.1 MB which makes up the majority of the site volume.
Potential reduce by 94.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. This page needs HTML code to be minified as it can gain 51.4 kB, which is 48% 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 94.7 kB or 88% of the original size.
Potential reduce by 70.1 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. Linife images are well optimized though.
Potential reduce by 37.3 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 37.3 kB or 47% of the original size.
Potential reduce by 88.9 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. Linife.ru needs all CSS files to be minified and compressed as it can save up to 88.9 kB or 82% of the original size.
Number of requests can be reduced by 41 (48%)
86
45
The browser has sent 86 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Linife. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 24 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
linife.ru
1135 ms
core.css
405 ms
styles.css
614 ms
added_styles.css
439 ms
jquery-ui-1.9.2.custom.css
442 ms
jquery.fancybox.css
436 ms
jquery.formstyler.css
443 ms
core.js
793 ms
core_ajax.js
611 ms
session.js
628 ms
jquery-1.7.2.min.js
814 ms
functions.js
629 ms
jquery.cookie.js
800 ms
jquery-ui-1.9.2.custom.min.js
802 ms
jquery.maskedinput-1.3.min.js
803 ms
jquery.fancybox.pack.js
815 ms
sly.min.js
1023 ms
jquery.formstyler.min.js
1025 ms
cloud-zoom.1.0.2.min.js
1027 ms
jquery.printPage.js
1026 ms
geolocation.js
1028 ms
openstatparser.js
1029 ms
4487-55-e2bece4c5c02f30-eb0fb7ab2-f30-c5c02f30-0274e2be.js
557 ms
css
279 ms
w.js
828 ms
know_size_1.png
361 ms
know_size_2.png
2098 ms
logo_new.png
353 ms
logo_small_new.png
750 ms
31f4d19b40b1fb3e482379d3edcce7a8.jpg
3565 ms
d87bf63011f34aae9af1a72fb7e01315.png
2181 ms
3b091b8c90f9756b46e97159fc7da926.jpg
542 ms
6e402f9136e86657987e58d7a471627d.jpg
1475 ms
64235f247b8f6d46c5d82ba2c71d7cbd.jpg
897 ms
92965f633c45fa0fea830edc8deda383.jpg
1073 ms
cf919d04a68a321c3e8075eb42ff57f6.jpg
1073 ms
bfe9cbffa8443e8e26cc015ea71ae0b3.jpg
5042 ms
017d7fbf541b4385a5b2ba59b13c47c2.jpg
2860 ms
c423c44cccd143a1887f4296e4dd6315.jpg
1633 ms
c90d2417063676059ebd35bf0c7b452b.jpg
1832 ms
88a4edfddc2eb8c9bb56b969e33d892e.jpg
2008 ms
a2becbbc20e55d458f63ba9de03ab732.jpg
2435 ms
d0d49951278942e65949898825115813.jpg
2657 ms
7a65024acba23932ae4637c4bd7d06b0.jpg
3349 ms
394a2e0622b762afa97e8506d5877bff.jpg
2645 ms
0c892f70ef304d2362813810879606cb.jpg
2837 ms
fed4914229f9b335a75570e0b673e195.jpg
3100 ms
pays.jpg
3089 ms
analytics.js
304 ms
bg.jpg
3082 ms
rtrg
376 ms
code.js
421 ms
black_56.png
3246 ms
colors_bg.png
3248 ms
slider_buttons.jpg
3454 ms
belye.jpg
3453 ms
rub.png
3451 ms
catalog.png
3613 ms
sumki.jpg
3608 ms
pledy.jpg
3610 ms
podushki.jpg
3607 ms
rub_min.png
3782 ms
normal_btn.png
3769 ms
linen_tag.png
3774 ms
watch.js
155 ms
widget_new.php
443 ms
rtrg
237 ms
ajax.php
3776 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
219 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
272 ms
kelson_sans_light_ru.woff
3691 ms
getTime.js
377 ms
frame_cookie.php
373 ms
collect
53 ms
collect
492 ms
counter
213 ms
kelson_sans_regular_ru.woff
3646 ms
widget.php
217 ms
kelson_sans_bold_ru.woff
3634 ms
firstInput.js
158 ms
notify
1849 ms
site.css
177 ms
widget.js
6279 ms
rub_big_new.png
3142 ms
bf6fd4a2d3e1f73493968444624196e81af95dece5e6f3e9d977f94b2b7ba4bb.js
179 ms
social_icons.png
3135 ms
ok.png
3134 ms
perezvoniWidget.css
181 ms
css
194 ms
perezvoniWidget_popup-underlay.png
184 ms
perezvoniWidget_button-moving-bg.png
362 ms
perezvoniWidget_button-moving-icon.png
1085 ms
perezvoniWidget_bg.png
368 ms
RjgO7rYTmqiVp7vzi-Q5UaCWcynf_cDxXwCLxiixG1c.ttf
81 ms
DXI1ORHCpsQm3Vp6mXoaTfOEPOIfcPv-fZ-WyMUtx48.ttf
131 ms
MTP_ySUJH_bn48VBG8sNSvOEPOIfcPv-fZ-WyMUtx48.ttf
217 ms
ajax.php
234 ms
linife.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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
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
linife.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
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
linife.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 Linife.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 Linife.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.
linife.ru
Open Graph description is not detected on the main page of Linife. 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: