Tools & Wizards About Us
obrienfamilytreeservice.com screenshot

Report Summary

  • 47

    Performance

    Renders faster than
    65% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 68% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 84

    SEO

    Google-friendlier than
    52% of websites

obrienfamilytreeservice.com

O'Brien Family Tree Service - Serving Bucks County Since 1979

Page Load Speed

2.2 sec in total

First Response

66 ms

Resources Loaded

1.6 sec

Page Rendered

551 ms

obrienfamilytreeservice.com screenshot

About Website

Welcome to obrienfamilytreeservice.com homepage info - get ready to check O Brien Family Tree Service best content right away, or after learning these important things about obrienfamilytreeservice.com

O'Brien Family Tree Service. Providing tree grooming, tree removal, stump grinding, and other tree services in Newtown, Richboro, Bensalem, Langhorne, Trevose, Southampton, Churchville, Ivyland, Doyle...

Visit obrienfamilytreeservice.com

Key Findings

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

Performance Metrics

obrienfamilytreeservice.com performance score

47

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.2 s

79/100

10%

LCP (Largest Contentful Paint)

Value6.0 s

13/100

25%

SI (Speed Index)

Value3.2 s

92/100

10%

TBT (Total Blocking Time)

Value280 ms

81/100

30%

CLS (Cumulative Layout Shift)

Value1.784

0/100

15%

TTI (Time to Interactive)

Value9.9 s

27/100

10%

Network Requests Diagram

obrienfamilytreeservice.com

66 ms

obrienfamilytreeservice.com

236 ms

rocket-loader.min.js

15 ms

owl.carousel.min.css

113 ms

owl.theme.default.min.css

108 ms

Our browser made a total of 78 requests to load all elements on the main page. We found that 86% of them (67 requests) were addressed to the original Obrienfamilytreeservice.com, 12% (9 requests) were made to Fonts.gstatic.com and 1% (1 request) were made to Static.cloudflareinsights.com. The less responsive or slowest element that took the longest time to load (388 ms) belongs to the original domain Obrienfamilytreeservice.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 49.2 kB (67%)

Content Size

74.0 kB

After Optimization

24.7 kB

  • HTML
  • Images
  • JavaScript

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

HTML Optimization

-84%

Potential reduce by 46.7 kB

  • Original 55.4 kB
  • After minification 31.7 kB
  • After compression 8.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. This page needs HTML code to be minified as it can gain 23.7 kB, which is 43% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 46.7 kB or 84% of the original size.

Image Optimization

-18%

Potential reduce by 2.5 kB

  • Original 14.0 kB
  • After minification 11.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, O Brien Family Tree Service needs image optimization as it can save up to 2.5 kB or 18% 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 17 B

  • Original 4.5 kB
  • After minification 4.5 kB
  • After compression 4.5 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 40 (62%)

Requests Now

65

After Optimization

25

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

obrienfamilytreeservice.com

obrienfamilytreeservice.com

66 ms

obrienfamilytreeservice.com

obrienfamilytreeservice.com

236 ms

rocket-loader.min.js

rocket-loader.min.js

15 ms

owl.carousel.min.css

owl.carousel.min.css

113 ms

owl.theme.default.min.css

owl.theme.default.min.css

108 ms

core.css

core.css

105 ms

shortcodes.css

shortcodes.css

103 ms

responsive.css

responsive.css

106 ms

custom.css

custom.css

108 ms

modernizr-3.11.2.min.js

modernizr-3.11.2.min.js

203 ms

email-decode.min.js

email-decode.min.js

107 ms

jquery-3.6.0.min.js

jquery-3.6.0.min.js

196 ms

jquery-migrate-3.3.2.min.js

jquery-migrate-3.3.2.min.js

251 ms

bootstrap.bundle.min.js

bootstrap.bundle.min.js

204 ms

plugins.js

plugins.js

202 ms

slick.min.js

slick.min.js

215 ms

owl.carousel.min.js

owl.carousel.min.js

262 ms

waypoints.min.js

waypoints.min.js

298 ms

main.js

main.js

288 ms

vcd15cbe7772f49c399c6a5babf22c1241717689176015

vcd15cbe7772f49c399c6a5babf22c1241717689176015

41 ms

header.css

header.css

196 ms

slider.css

slider.css

207 ms

footer.css

footer.css

239 ms

material-design-iconic-font.min.css

material-design-iconic-font.min.css

250 ms

icofont.css

icofont.css

291 ms

bicon.min.css

bicon.min.css

290 ms

animate.css

animate.css

296 ms

animate-slider.css

animate-slider.css

294 ms

default.css

default.css

328 ms

jquery-ui.css

jquery-ui.css

336 ms

slick.css

slick.css

385 ms

slick-theme.css

slick-theme.css

372 ms

lightbox.css

lightbox.css

353 ms

meanmenu.css

meanmenu.css

388 ms

odometer.min.css

odometer.min.css

388 ms

css

css

32 ms

close.png

close.png

94 ms

loading.gif

loading.gif

87 ms

prev.png

prev.png

94 ms

next.png

next.png

97 ms

4.webp

4.webp

93 ms

obrien-logo-small.webp

obrien-logo-small.webp

87 ms

line.png

line.png

176 ms

menu.png

menu.png

174 ms

truck-large-bg.webp

truck-large-bg.webp

177 ms

obrien-logo-large.webp

obrien-logo-large.webp

180 ms

crew-bg.webp

crew-bg.webp

156 ms

services-tree-removal.webp

services-tree-removal.webp

187 ms

services-cranes.webp

services-cranes.webp

245 ms

services-grinding.webp

services-grinding.webp

267 ms

services-pruning.webp

services-pruning.webp

262 ms

services-firewood.webp

services-firewood.webp

262 ms

services-hedging.webp

services-hedging.webp

267 ms

tom-grinder.webp

tom-grinder.webp

281 ms

crew-2.webp

crew-2.webp

339 ms

jen-tree.webp

jen-tree.webp

349 ms

crew-1.webp

crew-1.webp

375 ms

faq.webp

faq.webp

370 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

23 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf

30 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf

38 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

40 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVc.ttf

49 ms

bicon.ttf

bicon.ttf

300 ms

icofont.ttf

icofont.ttf

374 ms

BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjojISmb2Rm.ttf

BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjojISmb2Rm.ttf

50 ms

BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjo0oSmb2Rm.ttf

BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjo0oSmb2Rm.ttf

48 ms

BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjoa4Omb2Rm.ttf

BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjoa4Omb2Rm.ttf

48 ms

bootstrap.min.css

bootstrap.min.css

97 ms

style.css

style.css

94 ms

modernizr-3.11.2.min.js

modernizr-3.11.2.min.js

17 ms

title-tree.png

title-tree.png

90 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk8ZkWVAexQ.ttf

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk8ZkWVAexQ.ttf

5 ms

jquery-3.6.0.min.js

jquery-3.6.0.min.js

12 ms

jquery-migrate-3.3.2.min.js

jquery-migrate-3.3.2.min.js

12 ms

bootstrap.bundle.min.js

bootstrap.bundle.min.js

26 ms

plugins.js

plugins.js

13 ms

slick.min.js

slick.min.js

27 ms

Accessibility Review

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

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

ARIA IDs are not unique

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Links do not have a discernible name

Best Practices

obrienfamilytreeservice.com best practices score

75

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

obrienfamilytreeservice.com SEO score

84

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

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

obrienfamilytreeservice.com

Open Graph description is not detected on the main page of O Brien Family Tree Service. 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: