26.4 sec in total
783 ms
25.2 sec
428 ms
Click here to check amazing Edem content for Belarus. Otherwise, check out these important facts you probably never knew about edem.by
Заказать цветы - Минск с доставкой ⭐ в цветочном магазине Эдем. У нас большой выбор свежих цветов
Visit edem.byWe analyzed Edem.by page load time and found that the first response time was 783 ms and then it took 25.6 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster. Unfortunately, there was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
edem.by performance score
name
value
score
weighting
Value3.5 s
36/100
10%
Value21.2 s
0/100
25%
Value5.1 s
62/100
10%
Value450 ms
62/100
30%
Value0.093
91/100
15%
Value9.8 s
28/100
10%
783 ms
332 ms
19860 ms
90 ms
128 ms
Our browser made a total of 58 requests to load all elements on the main page. We found that 55% of them (32 requests) were addressed to the original Edem.by, 14% (8 requests) were made to Apis.google.com and 7% (4 requests) were made to Openstat.net. The less responsive or slowest element that took the longest time to load (19.9 sec) belongs to the original domain Edem.by.
Page size can be reduced by 157.6 kB (31%)
508.4 kB
350.8 kB
In fact, the total size of Edem.by main page is 508.4 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. 30% of websites need less resources to load. Images take 286.9 kB which makes up the majority of the site volume.
Potential reduce by 28.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 7.5 kB, which is 20% 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 28.8 kB or 76% of the original size.
Potential reduce by 11.9 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. Edem images are well optimized though.
Potential reduce by 56.7 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 56.7 kB or 54% of the original size.
Potential reduce by 60.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. Edem.by needs all CSS files to be minified and compressed as it can save up to 60.1 kB or 76% of the original size.
Number of requests can be reduced by 34 (68%)
50
16
The browser has sent 50 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Edem. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
edem.by
783 ms
start_bootstrap.css
332 ms
style.css
19860 ms
jquery-ui.css
90 ms
jquery-1.9.1.min.js
128 ms
jquery-ui.min.js
180 ms
jquery.mousewheel-3.0.6.pack.js
333 ms
jquery.fancybox.css
340 ms
jquery.fancybox.pack.js
3892 ms
jquery.fancybox-buttons.css
3313 ms
jquery.fancybox-buttons.js
1185 ms
jquery.fancybox-media.js
2437 ms
jquery.fancybox-thumbs.css
1104 ms
jquery.fancybox-thumbs.js
1298 ms
jquery.jgrowl.css
1351 ms
jquery.jgrowl.js
3323 ms
font-awesome.css
87 ms
xajax.js
2506 ms
logo_site.png
710 ms
sity_1.png
714 ms
sity_2.png
1650 ms
sity_3.png
1941 ms
sity_4.png
710 ms
mers.png
715 ms
micro.png
1114 ms
limuzin.png
1992 ms
autobus.png
1977 ms
kareta.png
2912 ms
bike.png
1636 ms
rss16.gif
1814 ms
plusone.js
592 ms
blr.gif
1793 ms
ukr.gif
1915 ms
rus.gif
1918 ms
kz.gif
2067 ms
profile_top.gif
2088 ms
profille_bottom.jpg
2075 ms
hit
393 ms
cnt.js
397 ms
ga.js
292 ms
watch.js
1 ms
__utm.gif
30 ms
2029225.js
413 ms
cb=gapi.loaded_0
730 ms
cb=gapi.loaded_1
758 ms
fastbutton
522 ms
digits
191 ms
cnt
367 ms
cb=gapi.loaded_0
504 ms
cb=gapi.loaded_1
501 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
400 ms
f.gif
158 ms
postmessageRelay
231 ms
1077434459-postmessagerelay.js
153 ms
rpc:shindig_random.js
71 ms
cb=gapi.loaded_0
127 ms
pixel
150 ms
pixel
56 ms
edem.by 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
Image elements do not have [alt] attributes
Form elements do not have associated labels
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.
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
edem.by 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
edem.by 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 Edem.by 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 Edem.by 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.
edem.by
Open Graph description is not detected on the main page of Edem. 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: