Tools & Wizards About Us
econdolence.com screenshot

Report Summary

  • 15

    Performance

    Renders faster than
    27% of other websites

  • 39

    Accessibility

    Visual factors better than
    that of 19% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 79

    SEO

    Google-friendlier than
    40% of websites

econdolence.com

eCondolence.com | Learn about Funeral, Burial, and Mourning traditions, customs and more. Plan a funeral. Send appropriate sympathy gifts.

Page Load Speed

3 sec in total

First Response

148 ms

Resources Loaded

2.4 sec

Page Rendered

482 ms

econdolence.com screenshot

About Website

Visit econdolence.com now to see the best up-to-date ECondolence content for United States and also check out these interesting facts you probably never knew about econdolence.com

Find information, resources and tools to express condolences, grieve & cope with loss, and support family and friends.

Visit econdolence.com

Key Findings

We analyzed Econdolence.com page load time and found that the first response time was 148 ms and then it took 2.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

econdolence.com performance score

15

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.8 s

11/100

10%

LCP (Largest Contentful Paint)

Value10.9 s

0/100

25%

SI (Speed Index)

Value10.5 s

7/100

10%

TBT (Total Blocking Time)

Value760 ms

39/100

30%

CLS (Cumulative Layout Shift)

Value1.13

1/100

15%

TTI (Time to Interactive)

Value14.3 s

9/100

10%

Network Requests Diagram

econdolence.com

148 ms

www.econdolence.com

319 ms

jquery-3.5.1.min.js

23 ms

Telerik.Web.UI.WebResource.axd

240 ms

css

56 ms

Our browser made a total of 59 requests to load all elements on the main page. We found that 83% of them (49 requests) were addressed to the original Econdolence.com, 5% (3 requests) were made to Fonts.gstatic.com and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Econdolence.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 336.6 kB (13%)

Content Size

2.5 MB

After Optimization

2.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Econdolence.com main page is 2.5 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. 55% of websites need less resources to load. Images take 2.0 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 212.4 kB

  • Original 265.5 kB
  • After minification 224.4 kB
  • After compression 53.1 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 41.1 kB, which is 15% 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 212.4 kB or 80% of the original size.

Image Optimization

-5%

Potential reduce by 106.8 kB

  • Original 2.0 MB
  • After minification 1.9 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. ECondolence images are well optimized though.

JavaScript Optimization

-8%

Potential reduce by 17.3 kB

  • Original 228.6 kB
  • After minification 228.6 kB
  • After compression 211.3 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.

CSS Optimization

-2%

Potential reduce by 139 B

  • Original 8.1 kB
  • After minification 8.1 kB
  • After compression 7.9 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. Econdolence.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 14 (26%)

Requests Now

53

After Optimization

39

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

econdolence.com

econdolence.com

148 ms

www.econdolence.com

www.econdolence.com

319 ms

jquery-3.5.1.min.js

jquery-3.5.1.min.js

23 ms

Telerik.Web.UI.WebResource.axd

Telerik.Web.UI.WebResource.axd

240 ms

css

css

56 ms

skin.css

skin.css

598 ms

skin.css

skin.css

348 ms

skin.js

skin.js

507 ms

skin.js

skin.js

350 ms

WebResource.axd

WebResource.axd

81 ms

ScriptResource.axd

ScriptResource.axd

144 ms

Telerik.Web.UI.WebResource.axd

Telerik.Web.UI.WebResource.axd

259 ms

skin.js

skin.js

577 ms

vcd15cbe7772f49c399c6a5babf22c1241717689176015

vcd15cbe7772f49c399c6a5babf22c1241717689176015

78 ms

logo-eCondolence-notag.png

logo-eCondolence-notag.png

60 ms

logo-eCondolence.png

logo-eCondolence.png

95 ms

26788_1.jpg

26788_1.jpg

94 ms

26790_1.png

26790_1.png

410 ms

26792_1.png

26792_1.png

189 ms

26789_1.jpg

26789_1.jpg

474 ms

26787_1.jpg

26787_1.jpg

104 ms

26791_1.jpg

26791_1.jpg

165 ms

26794_1.png

26794_1.png

139 ms

26796_1.png

26796_1.png

166 ms

26798_1.png

26798_1.png

165 ms

26795_1.png

26795_1.png

187 ms

26793_1.png

26793_1.png

221 ms

26797_1.png

26797_1.png

186 ms

funeral-preparations.png

funeral-preparations.png

222 ms

expressing-condolences.png

expressing-condolences.png

232 ms

visiting-shiva-home.jpg

visiting-shiva-home.jpg

218 ms

10249_1_39_Thumb.png

10249_1_39_Thumb.png

680 ms

10246_1_39_Thumb.png

10246_1_39_Thumb.png

713 ms

10247_1_39_Thumb.png

10247_1_39_Thumb.png

776 ms

23642_1_39_Thumb.png

23642_1_39_Thumb.png

544 ms

Plan-Left-Small.png

Plan-Left-Small.png

544 ms

plan-icon.png

plan-icon.png

542 ms

31259_1_33_Thumb.png

31259_1_33_Thumb.png

648 ms

13817_1.jpg

13817_1.jpg

963 ms

24174_1.jpg

24174_1.jpg

558 ms

24173_1.jpg

24173_1.jpg

573 ms

26664_1.jpg

26664_1.jpg

588 ms

phoneIcon.jpg

phoneIcon.jpg

604 ms

13821_1.jpg

13821_1.jpg

636 ms

flUhRqu5zY00QEpyWJYWN59Yf_NeKBU.woff

flUhRqu5zY00QEpyWJYWN59Yf_NeKBU.woff

79 ms

flU8Rqu5zY00QEpyWJYWN5fzXeA.woff

flU8Rqu5zY00QEpyWJYWN5fzXeA.woff

131 ms

flUhRqu5zY00QEpyWJYWN58AfvNeKBU.woff

flUhRqu5zY00QEpyWJYWN58AfvNeKBU.woff

131 ms

sprite.png

sprite.png

1104 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

573 ms

pin-background.png

pin-background.png

880 ms

arrowLeft.png

arrowLeft.png

581 ms

arrowRight.png

arrowRight.png

687 ms

secondBG.png

secondBG.png

861 ms

gtm.js

gtm.js

98 ms

analytics.js

analytics.js

53 ms

bat.js

bat.js

52 ms

WebResource.axd

WebResource.axd

491 ms

5709171.js

5709171.js

25 ms

collect

collect

12 ms

Accessibility Review

econdolence.com accessibility score

39

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

High

Heading elements are not in a sequentially-descending order

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

High

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

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>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

econdolence.com best practices score

67

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

econdolence.com SEO score

79

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

High

Image elements do not have [alt] attributes

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

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Econdolence.com can be misinterpreted by Google and other search engines. Our service has detected that English 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 Econdolence.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.

Social Sharing Optimization

econdolence.com

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