11.1 sec in total
3.2 sec
7.6 sec
328 ms
Visit lorelei.ru now to see the best up-to-date Lorelei content and also check out these interesting facts you probably never knew about lorelei.ru
Visit lorelei.ruWe analyzed Lorelei.ru page load time and found that the first response time was 3.2 sec and then it took 7.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
lorelei.ru performance score
name
value
score
weighting
Value2.6 s
63/100
10%
Value3.3 s
68/100
25%
Value5.0 s
64/100
10%
Value60 ms
100/100
30%
Value0.008
100/100
15%
Value4.6 s
81/100
10%
3169 ms
147 ms
357 ms
39 ms
355 ms
Our browser made a total of 74 requests to load all elements on the main page. We found that 88% of them (65 requests) were addressed to the original Lorelei.ru, 5% (4 requests) were made to Code.jquery.com and 3% (2 requests) were made to Cabinet.oliwa-pro.ru. The less responsive or slowest element that took the longest time to load (3.3 sec) belongs to the original domain Lorelei.ru.
Page size can be reduced by 151.2 kB (24%)
631.1 kB
479.9 kB
In fact, the total size of Lorelei.ru main page is 631.1 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. 35% of websites need less resources to load. Images take 480.6 kB which makes up the majority of the site volume.
Potential reduce by 54.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 7.7 kB, which is 12% 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 54.7 kB or 84% of the original size.
Potential reduce by 35.3 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. Lorelei images are well optimized though.
Potential reduce by 32.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 32.9 kB or 72% of the original size.
Potential reduce by 28.3 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. Lorelei.ru needs all CSS files to be minified and compressed as it can save up to 28.3 kB or 71% of the original size.
Number of requests can be reduced by 16 (22%)
72
56
The browser has sent 72 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Lorelei. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 8 to 1 for JavaScripts and as a result speed up the page load time.
lorelei.ru
3169 ms
index.css
147 ms
modernizr.custom.js
357 ms
jquery-2.0.2.min.js
39 ms
jquery.jcarousel.min.js
355 ms
index.js
426 ms
goods.js
427 ms
jquery.presentation.js
429 ms
jquery-ui.min.js
86 ms
jquery-ui.css
33 ms
service.php
668 ms
cycounter
415 ms
3_1_FFFFFFFF_EFEFEFFF_0_pageviews
367 ms
forma.png
213 ms
captcha.php
1420 ms
logo.png
212 ms
px_serch.png
209 ms
isq.png
209 ms
px_basket.png
210 ms
ico_basket.png
389 ms
menu1.png
392 ms
menu2.png
388 ms
menu3.png
389 ms
menu4.png
390 ms
demo1.png
856 ms
banner1.jpg
1897 ms
main_2.jpg
560 ms
banner2.jpg
803 ms
left.png
556 ms
right.png
704 ms
el_plash1.png
716 ms
smes22.png
995 ms
Lorelei_s.png
1153 ms
el_plash2.png
1263 ms
el_plash4.png
992 ms
el_plash5.png
1276 ms
ic1.png
1127 ms
ic2.png
1274 ms
ic3.png
1290 ms
visa.png
1396 ms
mk.png
1421 ms
ic4.png
1424 ms
ico5.png
1433 ms
gl_prev.png
1541 ms
good_id4061252.jpg
2937 ms
good_id4061251.jpg
2805 ms
good_id4061250.jpg
2761 ms
good_id4061249.jpg
2843 ms
good_id4061248.jpg
2861 ms
watch.js
1 ms
ui-bg_inset-hard_100_fcfdfd_1x100.png
105 ms
bridge.html
188 ms
good_id4061247.jpg
2008 ms
good_id4061246.jpg
2503 ms
good_id4061245.jpg
2768 ms
good_id4061244.jpg
2826 ms
good_id4061243.jpg
2853 ms
good_id4061242.jpg
2736 ms
good_id4061241.jpg
2948 ms
good_id4061240.jpg
2945 ms
good_id4061239.jpg
2949 ms
good_id4061238.jpg
2969 ms
good_id4061237.jpg
2814 ms
good_id4061236.jpg
2847 ms
good_id4061235.jpg
3268 ms
good_id4061234.jpg
3079 ms
good_id4061233.jpg
3169 ms
gl_next.png
2648 ms
foot_logo.png
2538 ms
card1.png
2591 ms
card2.png
2536 ms
card3.png
2530 ms
navia.png
1829 ms
navi.png
1916 ms
lorelei.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
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
lorelei.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
lorelei.ru SEO score
RU
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lorelei.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 Lorelei.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.
lorelei.ru
Open Graph description is not detected on the main page of Lorelei. 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: