Tools & Wizards About Us
chapelhillmemorial.com screenshot

Report Summary

  • 76

    Performance

    Renders faster than
    84% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 68% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

chapelhillmemorial.com

Funeral - Cemetery - Cremation | Chapel Hill Memorial Funeral Home

Page Load Speed

1.1 sec in total

First Response

42 ms

Resources Loaded

612 ms

Page Rendered

443 ms

chapelhillmemorial.com screenshot

About Website

Click here to check amazing Chapel Hill Memorial content. Otherwise, check out these important facts you probably never knew about chapelhillmemorial.com

Chapel Hill Memorial Gardens & Funeral Home has proudly served Osceola, South Bend, Mishawaka, Elkhart, and Granger area families since 1949.

Visit chapelhillmemorial.com

Key Findings

We analyzed Chapelhillmemorial.com page load time and found that the first response time was 42 ms and then it took 1.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.

Performance Metrics

chapelhillmemorial.com performance score

76

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.1 s

80/100

10%

LCP (Largest Contentful Paint)

Value3.4 s

65/100

25%

SI (Speed Index)

Value2.4 s

98/100

10%

TBT (Total Blocking Time)

Value370 ms

71/100

30%

CLS (Cumulative Layout Shift)

Value0.007

100/100

15%

TTI (Time to Interactive)

Value6.6 s

57/100

10%

Network Requests Diagram

chapelhillmemorial.com

42 ms

www.chapelhillmemorial.com

141 ms

gtm.js

57 ms

stonemortemplatecom_583422952.png

99 ms

icon-phone-solid.svg

67 ms

Our browser made a total of 25 requests to load all elements on the main page. We found that 8% of them (2 requests) were addressed to the original Chapelhillmemorial.com, 60% (15 requests) were made to Octanecdn.com and 24% (6 requests) were made to Transform.octanecdn.com. The less responsive or slowest element that took the longest time to load (349 ms) relates to the external source Transform.octanecdn.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 271.2 kB (73%)

Content Size

371.6 kB

After Optimization

100.4 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Chapelhillmemorial.com main page is 371.6 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. 15% of websites need less resources to load. HTML takes 292.2 kB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 256.3 kB

  • Original 292.2 kB
  • After minification 284.1 kB
  • After compression 35.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. 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.3 kB or 88% of the original size.

Image Optimization

-42%

Potential reduce by 14.8 kB

  • Original 35.3 kB
  • After minification 20.5 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. Obviously, Chapel Hill Memorial needs image optimization as it can save up to 14.8 kB or 42% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-0%

Potential reduce by 42 B

  • Original 44.2 kB
  • After minification 44.2 kB
  • After compression 44.1 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.

Requests Breakdown

Number of requests can be reduced by 16 (70%)

Requests Now

23

After Optimization

7

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

chapelhillmemorial.com

chapelhillmemorial.com

42 ms

www.chapelhillmemorial.com

www.chapelhillmemorial.com

141 ms

gtm.js

gtm.js

57 ms

stonemortemplatecom_583422952.png

stonemortemplatecom_583422952.png

99 ms

icon-phone-solid.svg

icon-phone-solid.svg

67 ms

plugins.min.js

plugins.min.js

60 ms

layouts.min.js

layouts.min.js

70 ms

main.min.js

main.min.js

68 ms

analytics.min.js

analytics.min.js

78 ms

extra.min.js

extra.min.js

73 ms

icon-chevron.svg

icon-chevron.svg

84 ms

icon-quote.svg

icon-quote.svg

76 ms

angle-left.svg

angle-left.svg

82 ms

angle-right.svg

angle-right.svg

129 ms

logo-facebook.svg

logo-facebook.svg

84 ms

dynamix-logo.svg

dynamix-logo.svg

88 ms

stonemortemplatecom_946765675.jpeg

stonemortemplatecom_946765675.jpeg

102 ms

stonemortemplatecom_251886651.jpg

stonemortemplatecom_251886651.jpg

349 ms

stonemortemplatecom_597564318.jpeg

stonemortemplatecom_597564318.jpeg

106 ms

stonemortemplatecom_572448733.jpeg

stonemortemplatecom_572448733.jpeg

111 ms

stonemortemplatecom_664139513.png

stonemortemplatecom_664139513.png

132 ms

css

css

33 ms

stonemortemplatecom_486915702.svg

stonemortemplatecom_486915702.svg

28 ms

stonemortemplatecom_633762767.svg

stonemortemplatecom_633762767.svg

32 ms

stonemortesttwo_788605499.svg

stonemortesttwo_788605499.svg

39 ms

Accessibility Review

chapelhillmemorial.com accessibility score

88

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.

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

Best Practices

chapelhillmemorial.com best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

chapelhillmemorial.com SEO score

86

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

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

    EN

  • Encoding

    N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Chapelhillmemorial.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 Chapelhillmemorial.com main page’s claimed encoding is . Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

chapelhillmemorial.com

Open Graph data is detected on the main page of Chapel Hill Memorial. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: