Tools & Wizards About Us
frankfuneralhome.net screenshot

Report Summary

  • 24

    Performance

    Renders faster than
    43% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

frankfuneralhome.net

Frank Funeral Home : Wellington, Kansas (KS)

Page Load Speed

2.1 sec in total

First Response

513 ms

Resources Loaded

1.3 sec

Page Rendered

303 ms

frankfuneralhome.net screenshot

About Website

Visit frankfuneralhome.net now to see the best up-to-date Frank Funeral Home content and also check out these interesting facts you probably never knew about frankfuneralhome.net

Frank Funeral Home | provides complete funeral services to the local community.

Visit frankfuneralhome.net

Key Findings

We analyzed Frankfuneralhome.net page load time and found that the first response time was 513 ms and then it took 1.6 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

frankfuneralhome.net performance score

24

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.1 s

21/100

10%

LCP (Largest Contentful Paint)

Value11.0 s

0/100

25%

SI (Speed Index)

Value5.9 s

47/100

10%

TBT (Total Blocking Time)

Value2,690 ms

4/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value13.4 s

11/100

10%

Network Requests Diagram

www.frankfuneralhome.net

513 ms

icons.css

43 ms

legacyStylesheet.css

73 ms

aos.css

78 ms

font-awesome.min.css

110 ms

Our browser made a total of 70 requests to load all elements on the main page. We found that 43% of them (30 requests) were addressed to the original Frankfuneralhome.net, 13% (9 requests) were made to Cdnjs.cloudflare.com and 11% (8 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (513 ms) belongs to the original domain Frankfuneralhome.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 182.8 kB (12%)

Content Size

1.5 MB

After Optimization

1.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Frankfuneralhome.net main page is 1.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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 1.2 MB which makes up the majority of the site volume.

HTML Optimization

-73%

Potential reduce by 19.0 kB

  • Original 25.9 kB
  • After minification 24.9 kB
  • After compression 6.9 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 19.0 kB or 73% of the original size.

Image Optimization

-13%

Potential reduce by 156.9 kB

  • Original 1.2 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. Obviously, Frank Funeral Home needs image optimization as it can save up to 156.9 kB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-1%

Potential reduce by 1.6 kB

  • Original 256.8 kB
  • After minification 256.8 kB
  • After compression 255.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

-7%

Potential reduce by 5.2 kB

  • Original 76.0 kB
  • After minification 76.0 kB
  • After compression 70.8 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. Frankfuneralhome.net has all CSS files already compressed.

Requests Breakdown

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

Requests Now

53

After Optimization

24

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.frankfuneralhome.net

www.frankfuneralhome.net

513 ms

icons.css

icons.css

43 ms

legacyStylesheet.css

legacyStylesheet.css

73 ms

aos.css

aos.css

78 ms

font-awesome.min.css

font-awesome.min.css

110 ms

main.css

main.css

78 ms

bootstrap.min.css

bootstrap.min.css

66 ms

all.min.css

all.min.css

49 ms

font-awesome.min.css

font-awesome.min.css

60 ms

theme-blackswan.css

theme-blackswan.css

63 ms

hero-carousel.css

hero-carousel.css

79 ms

jquery.js

jquery.js

55 ms

bootstrap.min.js

bootstrap.min.js

81 ms

fb_utilities.js

fb_utilities.js

75 ms

_page_sections.css

_page_sections.css

91 ms

enterprise.js

enterprise.js

55 ms

email-decode.min.js

email-decode.min.js

76 ms

jquery.transit.min.js

jquery.transit.min.js

51 ms

aos.js

aos.js

86 ms

global.js

global.js

78 ms

css2

css2

35 ms

css2

css2

37 ms

css2

css2

35 ms

aos.css

aos.css

37 ms

css

css

33 ms

aos.js

aos.js

17 ms

matomo.js

matomo.js

127 ms

recaptcha__en.js

recaptcha__en.js

67 ms

siteBG.png

siteBG.png

60 ms

logo_w_standard_white.png

logo_w_standard_white.png

106 ms

hero-bg-field-04.jpg

hero-bg-field-04.jpg

127 ms

8969731_fbs.jpeg

8969731_fbs.jpeg

107 ms

8917985_fbs.jpg

8917985_fbs.jpg

105 ms

8907555_fbs.jpg

8907555_fbs.jpg

106 ms

8906231_fbs.jpeg

8906231_fbs.jpeg

106 ms

8860954_fbs.jpg

8860954_fbs.jpg

164 ms

obit_placeholder_26.jpg

obit_placeholder_26.jpg

144 ms

8817381_fbs.jpg

8817381_fbs.jpg

152 ms

8803530_fbs.jpg

8803530_fbs.jpg

164 ms

8788114_fbs.jpg

8788114_fbs.jpg

230 ms

8790136_fbs.jpg

8790136_fbs.jpg

163 ms

planAhead.jpg

planAhead.jpg

261 ms

griefSupport.jpg

griefSupport.jpg

229 ms

flowers.jpg

flowers.jpg

261 ms

NFDA%20(3).png

NFDA%20(3).png

247 ms

KFDA-Logo-Mono.png

KFDA-Logo-Mono.png

247 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

96 ms

BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjojISmb2Rm.ttf

BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjojISmb2Rm.ttf

113 ms

BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjojISWaA.ttf

BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjojISWaA.ttf

132 ms

BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjoa4OWaA.ttf

BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjoa4OWaA.ttf

133 ms

55xoey1sJNPjPiv1ZZZrxK170bg.ttf

55xoey1sJNPjPiv1ZZZrxK170bg.ttf

126 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

94 ms

fa-v4compatibility.ttf

fa-v4compatibility.ttf

75 ms

fa-regular-400.ttf

fa-regular-400.ttf

74 ms

fa-brands-400.ttf

fa-brands-400.ttf

94 ms

fa-solid-900.ttf

fa-solid-900.ttf

94 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

382 ms

anchor

anchor

59 ms

main.js

main.js

148 ms

matomo.php

matomo.php

141 ms

matomo.php

matomo.php

271 ms

styles__ltr.css

styles__ltr.css

10 ms

recaptcha__en.js

recaptcha__en.js

24 ms

9J_OlxnAizjMJN_fZ8JRYj0PV4Me2EAx1CVcnywh2Sk.js

9J_OlxnAizjMJN_fZ8JRYj0PV4Me2EAx1CVcnywh2Sk.js

52 ms

webworker.js

webworker.js

48 ms

logo_48.png

logo_48.png

35 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

29 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

28 ms

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

29 ms

recaptcha__en.js

recaptcha__en.js

30 ms

Accessibility Review

frankfuneralhome.net accessibility score

100

Accessibility Issues

Best Practices

frankfuneralhome.net best practices score

83

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

SEO Factors

frankfuneralhome.net SEO score

83

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

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

High

Tap targets are not sized appropriately

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 Frankfuneralhome.net 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 Frankfuneralhome.net 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

frankfuneralhome.net

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