Tools & Wizards About Us
pflegerfuneralhome.com screenshot

Report Summary

  • 8

    Performance

    Renders faster than
    22% of other websites

  • 99

    Accessibility

    Visual factors better than
    that of 96% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

pflegerfuneralhome.com

Middletown's Funeral Arrangements & Cremation Services

Page Load Speed

1.1 sec in total

First Response

37 ms

Resources Loaded

703 ms

Page Rendered

342 ms

pflegerfuneralhome.com screenshot

About Website

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

John F. Pfleger Funeral Home provides affordable personalized funeral, memorial, aftercare, pre-planning, and cremation services in Middletown, NJ. Call us now.

Visit pflegerfuneralhome.com

Key Findings

We analyzed Pflegerfuneralhome.com page load time and found that the first response time was 37 ms and then it took 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

pflegerfuneralhome.com performance score

8

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.3 s

18/100

10%

LCP (Largest Contentful Paint)

Value8.6 s

1/100

25%

SI (Speed Index)

Value6.4 s

41/100

10%

TBT (Total Blocking Time)

Value3,110 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0.815

4/100

15%

TTI (Time to Interactive)

Value17.9 s

4/100

10%

Network Requests Diagram

pflegerfuneralhome.com

37 ms

www.pflegerfuneralhome.com

10 ms

www.pflegerfuneralhome.com

292 ms

gtm.js

48 ms

gtm.js

129 ms

Our browser made a total of 44 requests to load all elements on the main page. We found that 25% of them (11 requests) were addressed to the original Pflegerfuneralhome.com, 30% (13 requests) were made to D2zeeo94hsmapq.cloudfront.net and 11% (5 requests) were made to Tributecenteronline.s3-accelerate.amazonaws.com. The less responsive or slowest element that took the longest time to load (292 ms) belongs to the original domain Pflegerfuneralhome.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 202.4 kB (16%)

Content Size

1.2 MB

After Optimization

1.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-72%

Potential reduce by 151.9 kB

  • Original 209.6 kB
  • After minification 199.2 kB
  • After compression 57.7 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 151.9 kB or 72% of the original size.

Image Optimization

-6%

Potential reduce by 47.2 kB

  • Original 750.0 kB
  • After minification 702.8 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. Pfleger Funeral Home images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 296 B

  • Original 200.4 kB
  • After minification 200.4 kB
  • After compression 200.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

-4%

Potential reduce by 3.1 kB

  • Original 85.6 kB
  • After minification 85.4 kB
  • After compression 82.5 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. Pflegerfuneralhome.com has all CSS files already compressed.

Requests Breakdown

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

Requests Now

36

After Optimization

14

  • Images
  • JavaScript
  • CSS

The browser has sent 36 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Pfleger 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 9 to 1 for JavaScripts and from 15 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

pflegerfuneralhome.com

pflegerfuneralhome.com

37 ms

www.pflegerfuneralhome.com

www.pflegerfuneralhome.com

10 ms

www.pflegerfuneralhome.com

www.pflegerfuneralhome.com

292 ms

gtm.js

gtm.js

48 ms

gtm.js

gtm.js

129 ms

js

js

147 ms

common.css

common.css

24 ms

tribute-pay-panel.css

tribute-pay-panel.css

34 ms

lightbox.css

lightbox.css

40 ms

2ea18e93d7b4278a63e09a302acc095a.513.css

2ea18e93d7b4278a63e09a302acc095a.513.css

13 ms

rotating-banner.css

rotating-banner.css

42 ms

8577586dc142bd1cbb54c69235ec0888.513.css

8577586dc142bd1cbb54c69235ec0888.513.css

25 ms

obituaries-homepage.css

obituaries-homepage.css

43 ms

feeefa511254c061e8ad7d0fbd7de833.513.css

feeefa511254c061e8ad7d0fbd7de833.513.css

28 ms

shared.css

shared.css

43 ms

fonts.css

fonts.css

58 ms

0c28e5df75513ba69612ad23749e7fe0.513.css

0c28e5df75513ba69612ad23749e7fe0.513.css

26 ms

DynamicForms.css

DynamicForms.css

57 ms

679da333f9a713965154d43db16f6c39.513.css

679da333f9a713965154d43db16f6c39.513.css

25 ms

aos.css

aos.css

56 ms

client.js

client.js

23 ms

0a599583b6638b129fac13f6a740f24b.513.js

0a599583b6638b129fac13f6a740f24b.513.js

39 ms

aos.js

aos.js

73 ms

site.css

site.css

76 ms

js

js

141 ms

logo516f6fae549f423eb653cd80ddc3eccd_62683386da234cb0bad0d865c391b63b.png

logo516f6fae549f423eb653cd80ddc3eccd_62683386da234cb0bad0d865c391b63b.png

49 ms

25da0e43-051d-4dca-89e1-262e6b332709.webp

25da0e43-051d-4dca-89e1-262e6b332709.webp

171 ms

funeral-home.jpg

funeral-home.jpg

113 ms

burial-services.jpg

burial-services.jpg

113 ms

widget.js

widget.js

178 ms

funeral-preplanning-services.jpg

funeral-preplanning-services.jpg

222 ms

green-burial-management.jpg

green-burial-management.jpg

147 ms

9f71d734-5f2f-434b-b8cc-86db480fb6fd.jpg

9f71d734-5f2f-434b-b8cc-86db480fb6fd.jpg

147 ms

8145f164-d2dd-401e-9d09-003c1c4641a2.jpg

8145f164-d2dd-401e-9d09-003c1c4641a2.jpg

177 ms

fec1edb7-70ae-46c3-9757-3530ec298f34.jpg

fec1edb7-70ae-46c3-9757-3530ec298f34.jpg

177 ms

0cefbc6d-00bc-4a10-b8a8-37d8ab5224f1.jpg

0cefbc6d-00bc-4a10-b8a8-37d8ab5224f1.jpg

222 ms

intro.jpg

intro.jpg

110 ms

flowers14.jpg

flowers14.jpg

65 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aX8.ttf

30 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf

39 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aX8.ttf

57 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf

75 ms

9oRPNYsQpS4zjuA_iwgT.ttf

9oRPNYsQpS4zjuA_iwgT.ttf

76 ms

widget_app_base_1729845524407.js

widget_app_base_1729845524407.js

33 ms

Accessibility Review

pflegerfuneralhome.com accessibility score

99

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

pflegerfuneralhome.com best practices score

83

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

Missing source maps for large first-party JavaScript

SEO Factors

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

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

    N/A

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pflegerfuneralhome.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Pflegerfuneralhome.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

pflegerfuneralhome.com

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