9.8 sec in total
396 ms
8.1 sec
1.3 sec
Click here to check amazing Leibstandart content for Russia. Otherwise, check out these important facts you probably never knew about leibstandart.com
Leibstandart — Reenactment gear
Visit leibstandart.comWe analyzed Leibstandart.com page load time and found that the first response time was 396 ms and then it took 9.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
leibstandart.com performance score
name
value
score
weighting
Value10.4 s
0/100
10%
Value20.9 s
0/100
25%
Value19.3 s
0/100
10%
Value1,230 ms
20/100
30%
Value0.069
96/100
15%
Value24.3 s
0/100
10%
396 ms
2484 ms
234 ms
343 ms
352 ms
Our browser made a total of 121 requests to load all elements on the main page. We found that 87% of them (105 requests) were addressed to the original Leibstandart.com, 4% (5 requests) were made to Yastatic.net and 2% (2 requests) were made to Seal.globalsign.com. The less responsive or slowest element that took the longest time to load (2.5 sec) belongs to the original domain Leibstandart.com.
Page size can be reduced by 209.0 kB (10%)
2.1 MB
1.8 MB
In fact, the total size of Leibstandart.com main page is 2.1 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. 60% of websites need less resources to load. Images take 1.4 MB which makes up the majority of the site volume.
Potential reduce by 141.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. This page needs HTML code to be minified as it can gain 44.5 kB, which is 27% 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 141.8 kB or 86% of the original size.
Potential reduce by 27.0 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. Leibstandart images are well optimized though.
Potential reduce by 35.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. This website has mostly compressed JavaScripts.
Potential reduce by 4.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. Leibstandart.com has all CSS files already compressed.
Number of requests can be reduced by 68 (59%)
115
47
The browser has sent 115 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Leibstandart. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 42 to 1 for JavaScripts and from 28 to 1 for CSS and as a result speed up the page load time.
leibstandart.com
396 ms
leibstandart.com
2484 ms
style.css
234 ms
ui.font.opensans.css
343 ms
main.popup.bundle.css
352 ms
style.css
353 ms
style.css
353 ms
style.css
355 ms
style.css
354 ms
style.css
455 ms
style.css
468 ms
style.css
469 ms
style.css
467 ms
style.css
469 ms
fotorama.css
469 ms
slick.css
568 ms
owl.carousel.min.css
583 ms
swiper-bundle.min.css
584 ms
jquery.fancybox.min.css
586 ms
style.css
588 ms
style.css
587 ms
style.css
681 ms
style.css
700 ms
style.css
701 ms
style.css
702 ms
style.css
703 ms
styles.css
703 ms
template_styles.css
909 ms
core.js
1176 ms
main.polyfill.customevent.js
817 ms
dexie.bitrix.bundle.js
1058 ms
core_ls.js
817 ms
core_fx.js
818 ms
core_frame_cache.js
934 ms
protobuf.js
1230 ms
model.js
937 ms
rest.client.js
1024 ms
jquery-migrate-1.2.1.js
15 ms
gmogs_image_90-35_en_black.js
29 ms
style-up.css
939 ms
pull.client.js
830 ms
jquery-1.8.3.min.js
920 ms
main.popup.bundle.js
825 ms
currency-core.bundle.js
881 ms
core_currency.js
881 ms
script-up.js
940 ms
jq_color.js
943 ms
function.js
843 ms
fotorama.js
832 ms
slick.min.js
832 ms
owl.carousel.min.js
909 ms
swiper-bundle.min.js
952 ms
jquery.fancybox.min.js
948 ms
smooth-scrollbar.js
849 ms
jquery.maskedinput.js
833 ms
main.js
834 ms
cartAdd.js
903 ms
script.js
946 ms
script.js
945 ms
script.js
851 ms
script.js
835 ms
script.js
833 ms
script.js
902 ms
script.js
946 ms
script.js
945 ms
ba.js
284 ms
spread.php
882 ms
gs_noscript_90-35_en.gif
31 ms
logo-leib-1.jpg
120 ms
select_str.png
118 ms
icon_search.svg
115 ms
icon_basket.svg
119 ms
icon_auth.svg
122 ms
001.png
353 ms
img_6807_150488_16258345583663952.png
682 ms
komplekt_paradnoy_formy_sobstvennogo_ego_imperatorskogo_velichestva_konvoya_seredina_xix_veka_rossiya.JPG
236 ms
komplekt_uniformy_ryadovogo_gusara_leyb_gvardii_gusarskogo_ego_imperatorskogo_velichestva_polka_1812.jpg
236 ms
doloman_ofitsera_leyb_gvardii_gusarskogo_ego_imperatorskogo_velichestva_polka_obr_1807_goda_rossiya_.JPG
237 ms
doloman_ofitsera_leyb_gvardii_gusarskogo_ego_imperatorskogo_velichestva_polka_obr_1809_goda_1812_god.jpg
354 ms
mentik_ofitsera_leyb_gvardii_gusarskogo_ego_imperatorskogo_velichestva_polka_1812_god_rossiya_kopiya.jpg
355 ms
valtrap_cheprak_ofitserskiy_aleksandriyskogo_gusarskogo_polka_rossiya_kopiya.JPG
355 ms
valtrap_ofitserskiy_gvardeyskikh_gusar_perioda_pravleniya_aleksandra_i_rossiya_kopiya.jpg
355 ms
tashka_ofitserskaya_leyb_gvardii_gusarskogo_polka_obr_1816_goda_rossiya_kopiya.jpg
484 ms
katalog_vystavki_chasovye_otechestva_iz_istorii_rossiyskogo_kazachestva.jpg
480 ms
avtomobilnaya_shina_ya_13_yelochka_gaz_67b_gaz_64_gaz_69_polnoprivodnaya_pobeda_sssr_kopiya.jpg
480 ms
otboynik_vizira_voditelya_nemetskikh_tankov_i_bronevikov.jpg
477 ms
prokladka_tormoznoy_pruzhiny_demag_d_7_demag_d7p_sdkfz_250.jpg
479 ms
otboynik_podveski_tanka_t_2_.jpg
593 ms
oranzhevyy_revolvernyy_shnur_nizhnikh_chinov_ryadovogo_zvaniya_ria_pvv_1873g_348.jpg
597 ms
unter_ofitserskiy_oranzhevyy_revolvernyy_shnur_ria_pvv_1873g_348.jpg
595 ms
galun_shirokiy_na_obshivku_pod_gazyryami_ofitserskoy_cherkeski_sobstvennogo_ego_imperatorskogo_velich.jpg
597 ms
galun_uzkiy_dlya_rasshivki_gazyrey_i_vokrug_gazyrey_na_ofitserskoy_cherkeski_sobstvennogo_ego_impera.jpg
601 ms
routing-1.svg
709 ms
routing-2.svg
711 ms
routing-3.svg
714 ms
routing-4.svg
713 ms
routing-8.svg
716 ms
Vkhod-v-zdanie.png
795 ms
vkhod-v-zdanie-3.png
943 ms
Vkhod-v-zdanie-2.png
945 ms
logo_visa.png
829 ms
logo_mastercard.png
829 ms
logo_paypal.png
832 ms
watsapp.antic.svg
883 ms
751 ms
siteSeal.do
1592 ms
PTSansCaptionRegular.woff
1068 ms
PTSansCaptionBold.woff
951 ms
ajax_counter.php
1224 ms
ajax.php
1080 ms
fix-logo.svg
942 ms
icon_subscribe.png
832 ms
bx_stat
193 ms
0e6a1a8fd97dfd41ed2d.css
544 ms
797 ms
a4f86aa409286eff290c.yandex.en.js
811 ms
0e6a1a8fd97dfd41ed2d.yandex.en.js
870 ms
watch.js
2 ms
logo-web-en-80x40.svg
407 ms
full-2383587e566073d105d35dad05bb01d1698b04bf.js
2037 ms
siteSealImage.do
535 ms
leibstandart.com 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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
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.
leibstandart.com 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
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
leibstandart.com 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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Leibstandart.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Leibstandart.com 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.
leibstandart.com
Open Graph data is detected on the main page of Leibstandart. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: