Tools & Wizards About Us
communityfamilyfh.com screenshot

Report Summary

  • 32

    Performance

    Renders faster than
    52% of other websites

  • 97

    Accessibility

    Visual factors better than
    that of 92% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

communityfamilyfh.com

Community Family Funeral Home : Richmond, Indiana (IN)

Page Load Speed

2.3 sec in total

First Response

111 ms

Resources Loaded

1.9 sec

Page Rendered

266 ms

communityfamilyfh.com screenshot

About Website

Click here to check amazing Community Family Fh content. Otherwise, check out these important facts you probably never knew about communityfamilyfh.com

Community Family Funeral Home provides complete funeral and cremation services to Richmond, Indiana; Wayne County and the surrounding areas.

Visit communityfamilyfh.com

Key Findings

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

Performance Metrics

communityfamilyfh.com performance score

32

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.8 s

28/100

10%

LCP (Largest Contentful Paint)

Value8.8 s

1/100

25%

SI (Speed Index)

Value5.1 s

61/100

10%

TBT (Total Blocking Time)

Value930 ms

30/100

30%

CLS (Cumulative Layout Shift)

Value0.163

72/100

15%

TTI (Time to Interactive)

Value9.5 s

30/100

10%

Network Requests Diagram

www.communityfamilyfh.com

111 ms

www.communityfamilyfh.com

276 ms

icons.css

148 ms

legacyStylesheet.css

166 ms

aos.css

58 ms

Our browser made a total of 78 requests to load all elements on the main page. We found that 77% of them (60 requests) were addressed to the original Communityfamilyfh.com, 5% (4 requests) were made to Unpkg.com and 4% (3 requests) were made to Cdnjs.cloudflare.com. The less responsive or slowest element that took the longest time to load (892 ms) belongs to the original domain Communityfamilyfh.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 50.1 kB (6%)

Content Size

832.4 kB

After Optimization

782.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Communityfamilyfh.com main page is 832.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. 40% of websites need less resources to load. Images take 748.6 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 24.6 kB

  • Original 32.1 kB
  • After minification 30.5 kB
  • After compression 7.5 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 24.6 kB or 77% of the original size.

Image Optimization

-3%

Potential reduce by 21.3 kB

  • Original 748.6 kB
  • After minification 727.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. Community Family Fh images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 206 B

  • Original 27.3 kB
  • After minification 27.3 kB
  • After compression 27.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.

CSS Optimization

-16%

Potential reduce by 4.0 kB

  • Original 24.4 kB
  • After minification 24.4 kB
  • After compression 20.4 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. Communityfamilyfh.com needs all CSS files to be minified and compressed as it can save up to 4.0 kB or 16% of the original size.

Requests Breakdown

Number of requests can be reduced by 22 (31%)

Requests Now

72

After Optimization

50

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.communityfamilyfh.com

www.communityfamilyfh.com

111 ms

www.communityfamilyfh.com

www.communityfamilyfh.com

276 ms

icons.css

icons.css

148 ms

legacyStylesheet.css

legacyStylesheet.css

166 ms

aos.css

aos.css

58 ms

bootstrap.min.css

bootstrap.min.css

49 ms

font-awesome.min.css

font-awesome.min.css

47 ms

hero-carousel.css

hero-carousel.css

187 ms

layout.css

layout.css

173 ms

comp2.css

comp2.css

159 ms

theme-merlot.css

theme-merlot.css

178 ms

series_a.css

series_a.css

276 ms

_page_sections.css

_page_sections.css

293 ms

jquery-3.5.1.min.js

jquery-3.5.1.min.js

46 ms

bootstrap.min.js

bootstrap.min.js

58 ms

fb_utilities.js

fb_utilities.js

319 ms

enterprise.js

enterprise.js

64 ms

email-decode.min.js

email-decode.min.js

143 ms

jquery.transit.min.js

jquery.transit.min.js

25 ms

aos.js

aos.js

24 ms

global.js

global.js

66 ms

aos.js

aos.js

31 ms

aos.css

aos.css

11 ms

css2

css2

29 ms

css2

css2

41 ms

css2

css2

45 ms

matomo.js

matomo.js

107 ms

hatch-bg.jpg

hatch-bg.jpg

251 ms

logo_solo.png

logo_solo.png

221 ms

pattern-crosshatch-merlot.jpg

pattern-crosshatch-merlot.jpg

197 ms

hero-bg-rose-01.jpg

hero-bg-rose-01.jpg

197 ms

hero-people-blank.png

hero-people-blank.png

179 ms

main-shadow.png

main-shadow.png

179 ms

obit_placeholder_26.jpg

obit_placeholder_26.jpg

305 ms

obit-shadow.png

obit-shadow.png

304 ms

obit_placeholder_15.jpg

obit_placeholder_15.jpg

340 ms

8854191_fbs.jpg

8854191_fbs.jpg

346 ms

8853248_fbs.jpg

8853248_fbs.jpg

343 ms

8853259_fbs.jpeg

8853259_fbs.jpeg

373 ms

8853265_fbs.jpg

8853265_fbs.jpg

422 ms

8852882_fbs.jpg

8852882_fbs.jpg

427 ms

8851501_fbs.jpeg

8851501_fbs.jpeg

468 ms

obit_placeholder_03.jpg

obit_placeholder_03.jpg

477 ms

8845163_fbs.jpg

8845163_fbs.jpg

472 ms

obit_placeholder_12.jpg

obit_placeholder_12.jpg

541 ms

8846032_fbs.jpg

8846032_fbs.jpg

473 ms

8843278_fbs.jpg

8843278_fbs.jpg

559 ms

8843867_fbs.jpeg

8843867_fbs.jpeg

592 ms

8842741_fbs.jpg

8842741_fbs.jpg

608 ms

8841476_fbs.jpg

8841476_fbs.jpg

594 ms

obit_placeholder_18.jpg

obit_placeholder_18.jpg

594 ms

8835746_fbs.jpg

8835746_fbs.jpg

695 ms

8835618_fbs.jpg

8835618_fbs.jpg

687 ms

8833525_fbs.jpg

8833525_fbs.jpg

712 ms

8830960_fbs.jpg

8830960_fbs.jpg

717 ms

8831666_fbs.jpg

8831666_fbs.jpg

720 ms

8830232_fbs.jpg

8830232_fbs.jpg

740 ms

8830952_fbs.jpg

8830952_fbs.jpg

818 ms

8826512_fbs.png

8826512_fbs.png

881 ms

8829675_fbs.jpg

8829675_fbs.jpg

763 ms

8822162_fbs.jpg

8822162_fbs.jpg

836 ms

8819960_fbs.jpg

8819960_fbs.jpg

892 ms

obit_placeholder_07.jpg

obit_placeholder_07.jpg

819 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

19 ms

matomo.php

matomo.php

207 ms

matomo.php

matomo.php

217 ms

45_608.jpg

45_608.jpg

654 ms

Community.jpg

Community.jpg

101 ms

have_the_talk_of_a_lifetime.png

have_the_talk_of_a_lifetime.png

752 ms

flag_1.jpg

flag_1.jpg

742 ms

plan-ahead-1b.jpg

plan-ahead-1b.jpg

716 ms

plan-service-1.jpg

plan-service-1.jpg

630 ms

homesteaders-assoc_mono.png

homesteaders-assoc_mono.png

711 ms

NFDA%20(3).png

NFDA%20(3).png

716 ms

download%20(4).png

download%20(4).png

710 ms

IN16.gif

IN16.gif

658 ms

ifda-logo-new%20(7).png

ifda-logo-new%20(7).png

776 ms

main.js

main.js

199 ms

Accessibility Review

communityfamilyfh.com accessibility score

97

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.

Best Practices

communityfamilyfh.com best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

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

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

communityfamilyfh.com SEO score

92

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Page is blocked from indexing

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

    UTF-8

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

communityfamilyfh.com

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