Tools & Wizards About Us
ecodar.by screenshot

Report Summary

  • 30

    Performance

    Renders faster than
    50% of other websites

  • 97

    Accessibility

    Visual factors better than
    that of 92% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 89

    SEO

    Google-friendlier than
    67% of websites

ecodar.by

Ритуальные услуги в Минске круглосуточно в похоронном бюро | Агентство Ecodar

Page Load Speed

11.2 sec in total

First Response

588 ms

Resources Loaded

9.4 sec

Page Rendered

1.2 sec

ecodar.by screenshot

About Website

Welcome to ecodar.by homepage info - get ready to check Ecodar best content for Belarus right away, or after learning these important things about ecodar.by

Ритуальные услуги в Минске круглосуточно. ✅ Наше бюро всегда готово помочь в организации погребения с соблюдением всех церемоний. Звоните по тел.: ☎️: +375 (44) 571-61-13.

Visit ecodar.by

Key Findings

We analyzed Ecodar.by page load time and found that the first response time was 588 ms and then it took 10.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

ecodar.by performance score

30

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.9 s

25/100

10%

LCP (Largest Contentful Paint)

Value4.2 s

44/100

25%

SI (Speed Index)

Value19.5 s

0/100

10%

TBT (Total Blocking Time)

Value2,360 ms

5/100

30%

CLS (Cumulative Layout Shift)

Value0.037

100/100

15%

TTI (Time to Interactive)

Value24.2 s

0/100

10%

Network Requests Diagram

ecodar.by

588 ms

bootstrap.css

2489 ms

jquery-ui-1.10.2.custom.css

2177 ms

jquery.fancybox-1.3.4.css

3687 ms

less.js

1572 ms

Our browser made a total of 40 requests to load all elements on the main page. We found that 65% of them (26 requests) were addressed to the original Ecodar.by, 10% (4 requests) were made to Api-maps.yandex.ru and 5% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (7.5 sec) belongs to the original domain Ecodar.by.

Page Optimization Overview & Recommendations

Page size can be reduced by 850.2 kB (40%)

Content Size

2.1 MB

After Optimization

1.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Ecodar.by 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. 35% of websites need less resources to load. Images take 1.0 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 256.2 kB

  • Original 315.4 kB
  • After minification 310.7 kB
  • After compression 59.2 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. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 256.2 kB or 81% of the original size.

Image Optimization

-2%

Potential reduce by 22.0 kB

  • Original 1.0 MB
  • After minification 1.0 MB

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. Ecodar images are well optimized though.

JavaScript Optimization

-72%

Potential reduce by 404.0 kB

  • Original 564.9 kB
  • After minification 532.0 kB
  • After compression 160.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 404.0 kB or 72% of the original size.

CSS Optimization

-86%

Potential reduce by 168.1 kB

  • Original 195.2 kB
  • After minification 155.5 kB
  • After compression 27.2 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. Ecodar.by needs all CSS files to be minified and compressed as it can save up to 168.1 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 10 (29%)

Requests Now

35

After Optimization

25

  • Images
  • JavaScript
  • CSS

The browser has sent 35 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ecodar. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

ecodar.by

ecodar.by

588 ms

bootstrap.css

bootstrap.css

2489 ms

jquery-ui-1.10.2.custom.css

jquery-ui-1.10.2.custom.css

2177 ms

jquery.fancybox-1.3.4.css

jquery.fancybox-1.3.4.css

3687 ms

less.js

less.js

1572 ms

jquery.js

jquery.js

2840 ms

jquery-ui-1.10.2.custom.min.js

jquery-ui-1.10.2.custom.min.js

2352 ms

jquery.fancybox-1.3.4.pack.js

jquery.fancybox-1.3.4.pack.js

1739 ms

bootstrap.js

bootstrap.js

1902 ms

app.js

app.js

2073 ms

1338 ms

logo.png

logo.png

2527 ms

products.png

products.png

5323 ms

pay_delivery.jpg

pay_delivery.jpg

2652 ms

salon.jpg

salon.jpg

6434 ms

map.jpg

map.jpg

2684 ms

slide-1.jpg

slide-1.jpg

3496 ms

slide-2.jpg

slide-2.jpg

5322 ms

slide-3.jpg

slide-3.jpg

5320 ms

slide-4.jpg

slide-4.jpg

7548 ms

770 ms

bg_content.jpg

bg_content.jpg

2246 ms

bg_top.jpg

bg_top.jpg

3272 ms

glyphicons-halflings-white.png

glyphicons-halflings-white.png

535 ms

glyphicons_169_phone_white.png

glyphicons_169_phone_white.png

171 ms

big-image.jpg

big-image.jpg

1447 ms

glyphicons-halflings.png

glyphicons-halflings.png

1227 ms

Annabelle.ttf

Annabelle.ttf

2677 ms

167 ms

analytics.js

analytics.js

103 ms

watch.js

watch.js

25 ms

119814

119814

283 ms

reformal.js

reformal.js

320 ms

collect

collect

52 ms

373 ms

tab.png

tab.png

307 ms

st.php

st.php

317 ms

778886%7CaHR0cDovL2Vjb2Rhci5ieS8=%7C%7C44279

778886%7CaHR0cDovL2Vjb2Rhci5ieS8=%7C%7C44279

310 ms

log.php

log.php

568 ms

gr.png

gr.png

174 ms

Accessibility Review

ecodar.by accessibility score

97

Accessibility Issues

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

ecodar.by best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

ecodar.by SEO score

89

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    RU

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ecodar.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 Ecodar.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.

Social Sharing Optimization

ecodar.by

Open Graph description is not detected on the main page of Ecodar. 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: