12.9 sec in total
1.8 sec
10.1 sec
1 sec
Visit lgpol.ru now to see the best up-to-date Lgpol content for Russia and also check out these interesting facts you probably never knew about lgpol.ru
Интернет-магазин напольных покрытий в Москве и других регионах от ведущих мировых брендов по оптовым ценам. Мы исполняем каждый заказ с учётом малейших деталей, которые для Вас так важны!
Visit lgpol.ruWe analyzed Lgpol.ru page load time and found that the first response time was 1.8 sec and then it took 11.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
lgpol.ru performance score
name
value
score
weighting
Value4.4 s
17/100
10%
Value16.5 s
0/100
25%
Value9.7 s
11/100
10%
Value2,190 ms
6/100
30%
Value0.164
72/100
15%
Value17.8 s
4/100
10%
1802 ms
61 ms
325 ms
358 ms
355 ms
Our browser made a total of 103 requests to load all elements on the main page. We found that 91% of them (94 requests) were addressed to the original Lgpol.ru, 3% (3 requests) were made to App.comagic.ru and 2% (2 requests) were made to Bitrix.info. The less responsive or slowest element that took the longest time to load (4.5 sec) belongs to the original domain Lgpol.ru.
Page size can be reduced by 1.1 MB (67%)
1.7 MB
546.0 kB
In fact, the total size of Lgpol.ru main page is 1.7 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. 70% of websites need less resources to load. Javascripts take 663.6 kB which makes up the majority of the site volume.
Potential reduce by 285.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 104.6 kB, which is 34% 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 285.9 kB or 92% of the original size.
Potential reduce by 82.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, Lgpol needs image optimization as it can save up to 82.5 kB or 20% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 502.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 502.9 kB or 76% of the original size.
Potential reduce by 259.1 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. Lgpol.ru needs all CSS files to be minified and compressed as it can save up to 259.1 kB or 89% of the original size.
Number of requests can be reduced by 16 (17%)
96
80
The browser has sent 96 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Lgpol. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 13 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
lgpol.ru
1802 ms
watch.js
61 ms
core.css
325 ms
core_popup.css
358 ms
ss_admin.css
355 ms
style.css
514 ms
popup.css
365 ms
core.js
575 ms
core_popup.js
488 ms
core_ajax.js
573 ms
core_window.js
720 ms
ss_admin.js
570 ms
jquery-1.11.3.min.js
659 ms
script.js
702 ms
logo_10let.png
701 ms
b7b7436b30a959e6141e86f9c7eb1fbf.png
1836 ms
59be4dd0acd4a7244661ce7e7bcfe332.jpg
1981 ms
177accd1c8ed356548159710212ffa72.jpeg
1854 ms
5dead284d2c8fc089f5350174873c209.jpeg
929 ms
fbd6623a507f4f39ad80c9b33f02ef05.jpeg
929 ms
8a8e8ac4195dd2090ae46cfc8b8ae987.jpeg
947 ms
1de07a8260eee06c9f0cda24e618cd95.jpeg
1096 ms
812747116f5ffc2ec7e26f6255ac22e4.jpeg
1096 ms
9189eb6395b72f39b77a1776ab99e732.jpeg
1096 ms
0be7c91451e4e98cdb39ba505eb31835.jpeg
1217 ms
ac103803044e306ffee7b787610f9f7c.jpeg
1250 ms
a2e2da2ebfd1994c5b32a8e30c928968.jpeg
1317 ms
59f09b2aee5cc01d2c9aa0004797bce0.jpeg
1402 ms
fecc167b601ce0387f1d1a48f4745ec3.jpeg
1448 ms
145cb16ebe0a1664521d8dab457209a2.jpeg
4521 ms
42e6d9ea513c82225f898cda5bacc718.jpeg
1558 ms
3b4871d8d49f751aa567b070f78f1acc.jpeg
1624 ms
30ca87f2524222b16ced417f085c9ce2.jpeg
1742 ms
dd5f31ab0afdba87ca56f7c8eec994a9.jpg
1782 ms
ccbcc1cb6187e7c8adf758dffe0595e1.jpg
1895 ms
30293fa3c73eff7fd1b5524e23c75214.jpg
1951 ms
82d035eeb9dc82833d2ae76697443653.jpg
1986 ms
cs.min.js
1192 ms
script.js
1890 ms
609c1633c0c752677713e1de01cd826c.jpg
4220 ms
bc7cafa61a16cc564c83113bf9cd5c3e.jpg
4187 ms
503e03e51b2cfd0be264a13f2b605f0e.jpg
4185 ms
71e3072340e14dfe83556dc2aa627c16.jpg
4248 ms
0d2951867d196337831eee94ecae27ff.jpg
4067 ms
659830e2026997ca6678cf3cf7adf13a.jpg
3991 ms
4c6a1e79e5d0ac7dcf282f65d5995484.jpg
4058 ms
ffffd8de7573696160d94a05f6b965a6.jpg
4059 ms
opensans-regular-webfont.woff
4076 ms
77ef7ac6f1f827e2967ce945f08846ee.jpg
3900 ms
282e83155247493f94639ce884cec73a.jpg
3870 ms
49c2bc2d889400beefd4035bfa3d1813.jpg
3867 ms
9a6704819e3396640e1fbf0785d2de81.jpg
3866 ms
ba.js
348 ms
analytics.js
199 ms
626e889c2652d33dc28c6db30439fba5.jpg
3637 ms
64db60a154522bfc57d63e91f01eb83c.jpg
3626 ms
bf6d41642fd5a3a911a992a4df77e92e.jpg
4490 ms
52a7c40524eaf3ea2a7f93047e3f9fb6.jpg
3483 ms
eb10deadb95b0d19eb96f6b4435e5c13.jpg
3486 ms
opensans-extrabold-webfont.woff
3510 ms
collect
62 ms
collect
292 ms
ou92jmyj-webfont.woff
3385 ms
ProximaNovaBold.woff
3383 ms
a5204d5982577aceab5e586e786a3b03.jpg
3303 ms
db7ef8b95f7f67dd1edd967f55364f36.jpg
3221 ms
b6f9941afac7dbca392b04e7217d4e62.jpg
3176 ms
e8972b985170a875899a53aa1f25b2ac.jpg
3102 ms
3419cfd6366de202c898e541b822c5d5.jpg
3036 ms
8956810c7dd50ec2e6b217f4da37fbc4.jpg
2919 ms
01fc666118aa2f131e32fef9fe6f367c.jpg
3614 ms
cafe36fa364b3fa532907f71ac8c154e.jpg
3602 ms
66de04556a693c93777aea99ec3be86a.jpg
2830 ms
b28a25545836b4a19ba6e3e963c893c9.jpg
2768 ms
04f3f0b727bd661af5918b4824b7e9ef.jpg
2714 ms
9dbf355e1faf067cba03e76cb222b5f1.jpg
2706 ms
5b345d566876de3a2be890294e869f45.jpg
2681 ms
ajax_counter.php
3442 ms
bx_stat
972 ms
json.php
324 ms
639c51703b14a98e9732e39f52225fc6.jpg
302 ms
eb89adc9f2a5212a97a4da18639cf02a.jpg
919 ms
f8640909a27c464f80953d7f03915f71.jpg
904 ms
fd74328d230cfd43e2dd8e9c730d7f9b.jpg
1488 ms
58f6e607e3bf3bd8b71e7340d7a6b782.jpg
1497 ms
0d6016cda2029e1ec611b7b9bfda474d.jpg
895 ms
d94bcb82d17de3e8fa4124c602ec3478.jpg
1332 ms
7f8c91072291a15b5d95c01703ed91c0.jpg
950 ms
83dff3e9fad8668265da2e49336e93ad.jpg
2024 ms
360279d1e69f5a3059b70542507eb894.jpg
1175 ms
ff87b9871ec242bbafc42c8a72eca9a7.png
2269 ms
3f21882a1be01b527c6573898e8e1338.png
1322 ms
e71cd7d79218c489088eada068285fc3.png
1455 ms
263f4d6dbd4c1302b170c9fffae10510.png
1452 ms
fb7de0e157a45ed134dd4850eefd6171.png
1588 ms
93a064073af18393592326e48266d9a4.png
1561 ms
bbdb9c731cbc3f6286c2de6d52bfb80b.png
1564 ms
b8f0a38d66de345af84390485df75ef4.png
1576 ms
7b61f9a8a7124b36943a185e89eacf72.png
1690 ms
9bcebd3ee4cecb24c87b522234a31690.png
1703 ms
spritesheet.png
1870 ms
655 ms
2672 ms
lgpol.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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
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
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
lgpol.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
Missing source maps for large first-party JavaScript
lgpol.ru SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lgpol.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 Lgpol.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.
lgpol.ru
Open Graph description is not detected on the main page of Lgpol. 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: