Tools & Wizards About Us
philadelphiafuneralcare.com screenshot

Report Summary

  • 26

    Performance

    Renders faster than
    45% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 61% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

philadelphiafuneralcare.com

Oliver H. Bair Funeral Home : Upper Darby, Pennsylvania (PA)

Page Load Speed

1.9 sec in total

First Response

300 ms

Resources Loaded

1.2 sec

Page Rendered

416 ms

philadelphiafuneralcare.com screenshot

About Website

Click here to check amazing Philadelphia Funeral Care content. Otherwise, check out these important facts you probably never knew about philadelphiafuneralcare.com

Oliver H. Bair Funeral Home | provides complete funeral services to the local community.

Visit philadelphiafuneralcare.com

Key Findings

We analyzed Philadelphiafuneralcare.com page load time and found that the first response time was 300 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

philadelphiafuneralcare.com performance score

26

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.3 s

17/100

10%

LCP (Largest Contentful Paint)

Value12.0 s

0/100

25%

SI (Speed Index)

Value5.7 s

52/100

10%

TBT (Total Blocking Time)

Value1,820 ms

9/100

30%

CLS (Cumulative Layout Shift)

Value0.024

100/100

15%

TTI (Time to Interactive)

Value13.2 s

12/100

10%

Network Requests Diagram

www.philadelphiafuneralcare.com

300 ms

icons.css

49 ms

legacyStylesheet.css

79 ms

aos.css

74 ms

font-awesome.min.css

84 ms

Our browser made a total of 58 requests to load all elements on the main page. We found that 43% of them (25 requests) were addressed to the original Philadelphiafuneralcare.com, 16% (9 requests) were made to Cdnjs.cloudflare.com and 9% (5 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (702 ms) relates to the external source Cdn.rlets.com.

Page Optimization Overview & Recommendations

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

Content Size

1.6 MB

After Optimization

1.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-72%

Potential reduce by 20.0 kB

  • Original 27.6 kB
  • After minification 26.5 kB
  • After compression 7.6 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 20.0 kB or 72% of the original size.

Image Optimization

-13%

Potential reduce by 159.2 kB

  • Original 1.3 MB
  • After minification 1.1 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, Philadelphia Funeral Care needs image optimization as it can save up to 159.2 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.2 kB

  • Original 247.7 kB
  • After minification 247.7 kB
  • After compression 246.4 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 5.3 kB

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

Requests Breakdown

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

Requests Now

44

After Optimization

18

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 44 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Philadelphia Funeral Care. 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 16 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

www.philadelphiafuneralcare.com

www.philadelphiafuneralcare.com

300 ms

icons.css

icons.css

49 ms

legacyStylesheet.css

legacyStylesheet.css

79 ms

aos.css

aos.css

74 ms

font-awesome.min.css

font-awesome.min.css

84 ms

main.css

main.css

61 ms

bootstrap.min.css

bootstrap.min.css

95 ms

all.min.css

all.min.css

85 ms

font-awesome.min.css

font-awesome.min.css

105 ms

theme-fullmoon.css

theme-fullmoon.css

92 ms

hero-carousel.css

hero-carousel.css

110 ms

jquery.js

jquery.js

124 ms

bootstrap.min.js

bootstrap.min.js

105 ms

fb_utilities.js

fb_utilities.js

69 ms

_page_sections.css

_page_sections.css

96 ms

enterprise.js

enterprise.js

96 ms

e2b4987baff2feeb34f4304.js

e2b4987baff2feeb34f4304.js

702 ms

email-decode.min.js

email-decode.min.js

86 ms

jquery.transit.min.js

jquery.transit.min.js

171 ms

aos.js

aos.js

97 ms

global.js

global.js

95 ms

css

css

47 ms

aos.css

aos.css

28 ms

css2

css2

49 ms

css2

css2

49 ms

css2

css2

42 ms

aos.js

aos.js

12 ms

matomo.js

matomo.js

141 ms

recaptcha__en.js

recaptcha__en.js

98 ms

siteBG.png

siteBG.png

131 ms

page.php

page.php

162 ms

Main-Logo-Horizontal-2023.png

Main-Logo-Horizontal-2023.png

67 ms

hero-bg-leaves-01.jpg

hero-bg-leaves-01.jpg

159 ms

9108821_fbs.jpg

9108821_fbs.jpg

157 ms

obit-shadow.png

obit-shadow.png

216 ms

obit_placeholder_01.jpg

obit_placeholder_01.jpg

68 ms

9098090_fbs.jpg

9098090_fbs.jpg

186 ms

9092603_fbs.jpg

9092603_fbs.jpg

200 ms

9091352_fbs.jpg

9091352_fbs.jpg

230 ms

planAhead.jpg

planAhead.jpg

272 ms

griefSupport.jpg

griefSupport.jpg

306 ms

veterans.jpg

veterans.jpg

308 ms

fb-icon.png

fb-icon.png

240 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

145 ms

BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjojISmb2Rm.ttf

BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjojISmb2Rm.ttf

95 ms

BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjojISWaA.ttf

BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjojISWaA.ttf

101 ms

BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjoa4OWaA.ttf

BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjoa4OWaA.ttf

100 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

84 ms

fa-v4compatibility.ttf

fa-v4compatibility.ttf

60 ms

fa-regular-400.ttf

fa-regular-400.ttf

54 ms

fa-brands-400.ttf

fa-brands-400.ttf

97 ms

fa-solid-900.ttf

fa-solid-900.ttf

130 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

343 ms

55xoey1sJNPjPiv1ZZZrxK170bg.ttf

55xoey1sJNPjPiv1ZZZrxK170bg.ttf

97 ms

matomo.php

matomo.php

99 ms

matomo.php

matomo.php

147 ms

plkvQylRGqm.css

plkvQylRGqm.css

49 ms

main.js

main.js

14 ms

Accessibility Review

philadelphiafuneralcare.com accessibility score

86

Accessibility Issues

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

Buttons do not have an accessible name

High

<frame> or <iframe> elements do not have a title

High

Links do not have a discernible name

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

philadelphiafuneralcare.com 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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

philadelphiafuneralcare.com SEO score

82

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

philadelphiafuneralcare.com

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