Tools & Wizards About Us
caryestateplanning.com screenshot

Report Summary

  • 14

    Performance

    Renders faster than
    26% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 68% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

caryestateplanning.com

Cary Trust and Estates Lawyer | North Carolina Trusts Attorney

Page Load Speed

6.4 sec in total

First Response

85 ms

Resources Loaded

1.2 sec

Page Rendered

5.1 sec

caryestateplanning.com screenshot

About Website

Click here to check amazing Cary Estateplanning content. Otherwise, check out these important facts you probably never knew about caryestateplanning.com

For help protecting assets or to ensure that your family is taken care in event of an emergency, seek the help of a Cary trust and estates lawyer today.

Visit caryestateplanning.com

Key Findings

We analyzed Caryestateplanning.com page load time and found that the first response time was 85 ms and then it took 6.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

caryestateplanning.com performance score

14

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.2 s

8/100

10%

LCP (Largest Contentful Paint)

Value13.3 s

0/100

25%

SI (Speed Index)

Value9.3 s

13/100

10%

TBT (Total Blocking Time)

Value1,480 ms

14/100

30%

CLS (Cumulative Layout Shift)

Value0.246

50/100

15%

TTI (Time to Interactive)

Value19.2 s

2/100

10%

Network Requests Diagram

caryestateplanning.com

85 ms

caryestateplanning.com

87 ms

css2

87 ms

dashicons.min.css

34 ms

admin-bar.min.css

66 ms

Our browser made a total of 198 requests to load all elements on the main page. We found that 86% of them (171 requests) were addressed to the original Caryestateplanning.com, 8% (16 requests) were made to Fonts.gstatic.com and 2% (3 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (490 ms) relates to the external source Fonts.gstatic.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 350.0 kB (14%)

Content Size

2.5 MB

After Optimization

2.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Caryestateplanning.com main page is 2.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. Only a small number of websites need less resources to load. Images take 1.5 MB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 225.6 kB

  • Original 298.5 kB
  • After minification 258.6 kB
  • After compression 72.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. This page needs HTML code to be minified as it can gain 39.9 kB, which is 13% 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 225.6 kB or 76% of the original size.

Image Optimization

-1%

Potential reduce by 15.5 kB

  • Original 1.5 MB
  • After minification 1.5 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. Cary Estateplanning images are well optimized though.

JavaScript Optimization

-11%

Potential reduce by 45.0 kB

  • Original 427.3 kB
  • After minification 427.3 kB
  • After compression 382.3 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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 45.0 kB or 11% of the original size.

CSS Optimization

-28%

Potential reduce by 64.0 kB

  • Original 232.1 kB
  • After minification 199.2 kB
  • After compression 168.1 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. Caryestateplanning.com needs all CSS files to be minified and compressed as it can save up to 64.0 kB or 28% of the original size.

Requests Breakdown

Number of requests can be reduced by 70 (39%)

Requests Now

179

After Optimization

109

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

caryestateplanning.com

caryestateplanning.com

85 ms

caryestateplanning.com

caryestateplanning.com

87 ms

css2

css2

87 ms

dashicons.min.css

dashicons.min.css

34 ms

admin-bar.min.css

admin-bar.min.css

66 ms

style.min.css

style.min.css

66 ms

cleantalk-public.min.css

cleantalk-public.min.css

64 ms

styles.css

styles.css

65 ms

events-manager.min.css

events-manager.min.css

69 ms

rmp-menu.css

rmp-menu.css

64 ms

fonts.css

fonts.css

145 ms

bootstrap.min.css

bootstrap.min.css

83 ms

slick.css

slick.css

124 ms

slick-theme.css

slick-theme.css

120 ms

scrollbar.css

scrollbar.css

122 ms

style.css

style.css

147 ms

responsive.css

responsive.css

126 ms

styles.min.css

styles.min.css

139 ms

intlTelInput.css

intlTelInput.css

137 ms

select2.min.css

select2.min.css

133 ms

ic_chat_public.css

ic_chat_public.css

160 ms

normalize.min.css

normalize.min.css

120 ms

ic_chat_bot.css

ic_chat_bot.css

157 ms

css2

css2

143 ms

jquery.min.js

jquery.min.js

171 ms

jquery-migrate.min.js

jquery-migrate.min.js

168 ms

apbct-public-bundle.min.js

apbct-public-bundle.min.js

168 ms

core.min.js

core.min.js

189 ms

mouse.min.js

mouse.min.js

190 ms

sortable.min.js

sortable.min.js

193 ms

datepicker.min.js

datepicker.min.js

194 ms

resizable.min.js

resizable.min.js

195 ms

draggable.min.js

draggable.min.js

197 ms

controlgroup.min.js

controlgroup.min.js

197 ms

checkboxradio.min.js

checkboxradio.min.js

196 ms

button.min.js

button.min.js

202 ms

dialog.min.js

dialog.min.js

195 ms

events-manager.js

events-manager.js

198 ms

rmp-menu.js

rmp-menu.js

193 ms

js

js

155 ms

hoverintent-js.min.js

hoverintent-js.min.js

191 ms

dayjs.min.js

dayjs.min.js

121 ms

hammer.min.js

hammer.min.js

120 ms

luxon.min.js

luxon.min.js

106 ms

admin-bar.min.js

admin-bar.min.js

185 ms

hooks.min.js

hooks.min.js

223 ms

i18n.min.js

i18n.min.js

188 ms

index.js

index.js

185 ms

index.js

index.js

190 ms

intlTelInput.min.js

intlTelInput.min.js

188 ms

select2.min.js

select2.min.js

185 ms

bootstrap.min.js

bootstrap.min.js

187 ms

gtm.js

gtm.js

163 ms

html5lightbox.js

html5lightbox.js

138 ms

doubletaptogo.js

doubletaptogo.js

226 ms

slick.js

slick.js

224 ms

jquery.scrollbar.js

jquery.scrollbar.js

222 ms

main.js

main.js

212 ms

scripts.min.js

scripts.min.js

210 ms

ic_chat_bot.js

ic_chat_bot.js

205 ms

css2

css2

119 ms

cary-estate-planing-logo-blue-1.png

cary-estate-planing-logo-blue-1.png

115 ms

search-icon.png

search-icon.png

111 ms

hero-bg.jpg

hero-bg.jpg

114 ms

hero-1.svg

hero-1.svg

116 ms

hero-2.svg

hero-2.svg

111 ms

hero-3.svg

hero-3.svg

116 ms

hero-4.svg

hero-4.svg

132 ms

logo-1.png

logo-1.png

134 ms

logo-2.png

logo-2.png

132 ms

logo-3.png

logo-3.png

131 ms

logo-4.png

logo-4.png

135 ms

logo-5.png

logo-5.png

134 ms

logo-6.png

logo-6.png

136 ms

logo-7.png

logo-7.png

139 ms

planing-bg.svg

planing-bg.svg

135 ms

planing-photo.jpg

planing-photo.jpg

137 ms

photo-el.svg

photo-el.svg

140 ms

help-1.svg

help-1.svg

146 ms

help-2.svg

help-2.svg

138 ms

help-3.svg

help-3.svg

142 ms

help-4.svg

help-4.svg

140 ms

help-5.svg

help-5.svg

141 ms

help-6.svg

help-6.svg

141 ms

services-bg-300x238-1.jpg

services-bg-300x238-1.jpg

142 ms

services-11.svg

services-11.svg

140 ms

services-10.svg

services-10.svg

146 ms

services-8.svg

services-8.svg

140 ms

services-2.svg

services-2.svg

141 ms

services-1.svg

services-1.svg

140 ms

services-3.svg

services-3.svg

109 ms

services-4.svg

services-4.svg

104 ms

services-6.svg

services-6.svg

104 ms

services-7.svg

services-7.svg

107 ms

services-9.svg

services-9.svg

104 ms

Financial-Planning.svg

Financial-Planning.svg

107 ms

reviews-bg.svg

reviews-bg.svg

108 ms

review-5.jpg

review-5.jpg

102 ms

review-4-1.jpg

review-4-1.jpg

103 ms

review-3-1.jpg

review-3-1.jpg

104 ms

review-2-2.jpg

review-2-2.jpg

101 ms

review-1-1.jpg

review-1-1.jpg

101 ms

process-bg.svg

process-bg.svg

91 ms

process-1.svg

process-1.svg

93 ms

process-2.svg

process-2.svg

86 ms

process-3.svg

process-3.svg

88 ms

process-4.svg

process-4.svg

89 ms

1-Paul.jpg

1-Paul.jpg

90 ms

2-Amanda-Honea.jpg

2-Amanda-Honea.jpg

90 ms

4-Marjorie-Thornton.jpg

4-Marjorie-Thornton.jpg

91 ms

5-Scott-Moesta.jpg

5-Scott-Moesta.jpg

96 ms

Jessica-Mantekas-1.jpg

Jessica-Mantekas-1.jpg

90 ms

Campbell.jpg

Campbell.jpg

92 ms

7-Maggie-Wells.jpg

7-Maggie-Wells.jpg

91 ms

8-rebecca.jpg

8-rebecca.jpg

87 ms

9-Maddie-Rogers.jpg

9-Maddie-Rogers.jpg

89 ms

10-Matt-Parker.jpg

10-Matt-Parker.jpg

90 ms

11-stepheni-johnson.jpg

11-stepheni-johnson.jpg

90 ms

sara-1.jpg

sara-1.jpg

89 ms

12-Claire-Werner.jpg

12-Claire-Werner.jpg

89 ms

14-Jessica-Singer.jpg

14-Jessica-Singer.jpg

85 ms

15-ashley.jpg

15-ashley.jpg

88 ms

16-sara-corman.jpg

16-sara-corman.jpg

87 ms

17-amanda-singletary.jpg

17-amanda-singletary.jpg

85 ms

18-Alix-Yokabitus.jpg

18-Alix-Yokabitus.jpg

86 ms

19-lenae-rastafar.jpg

19-lenae-rastafar.jpg

93 ms

Joy-1.jpg

Joy-1.jpg

94 ms

20-kendall-jackson.jpg

20-kendall-jackson.jpg

89 ms

21-alicia-decesare.jpg

21-alicia-decesare.jpg

91 ms

Madilyn.jpg

Madilyn.jpg

89 ms

24-kimberly-brown.jpg

24-kimberly-brown.jpg

90 ms

25-ali-moreci.jpg

25-ali-moreci.jpg

90 ms

26-Alissa-Wu.jpg

26-Alissa-Wu.jpg

89 ms

why-1.svg

why-1.svg

92 ms

why-2.svg

why-2.svg

88 ms

why-3.svg

why-3.svg

89 ms

why-4.svg

why-4.svg

92 ms

why-5.svg

why-5.svg

89 ms

why-6.svg

why-6.svg

92 ms

articles-bg-2.svg

articles-bg-2.svg

90 ms

How-often-should-I-update-my-estate-plan-300x180.jpg

How-often-should-I-update-my-estate-plan-300x180.jpg

87 ms

How-to-leave-a-legacy-for-future-generations-300x180.jpg

How-to-leave-a-legacy-for-future-generations-300x180.jpg

91 ms

how-is-a-will-executed-after-death-1-300x180.jpg

how-is-a-will-executed-after-death-1-300x180.jpg

88 ms

special-needs-trust-300x180.jpg

special-needs-trust-300x180.jpg

89 ms

legal-guardianship-for-adults-with-disabilities-300x225.jpg

legal-guardianship-for-adults-with-disabilities-300x225.jpg

88 ms

probate-without-a-will-300x225.jpg

probate-without-a-will-300x225.jpg

88 ms

guardianship-vs-power-of-attorney-300x180.jpg

guardianship-vs-power-of-attorney-300x180.jpg

88 ms

what-to-do-when-someone-dies-and-leaves-a-will-300x180.jpg

what-to-do-when-someone-dies-and-leaves-a-will-300x180.jpg

85 ms

mapbg.png

mapbg.png

320 ms

loc.svg

loc.svg

319 ms

footer-bg.svg

footer-bg.svg

319 ms

fb.svg

fb.svg

316 ms

ig.svg

ig.svg

317 ms

tw.svg

tw.svg

313 ms

in.svg

in.svg

322 ms

yt.svg

yt.svg

365 ms

group-2242.svg

group-2242.svg

316 ms

vector5.svg

vector5.svg

321 ms

logo-chat.png

logo-chat.png

318 ms

UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuI6fMZg.ttf

UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuI6fMZg.ttf

360 ms

UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuLyfMZg.ttf

UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuLyfMZg.ttf

412 ms

UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuOKfMZg.ttf

UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuOKfMZg.ttf

480 ms

UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuLyeMZg.ttf

UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuLyeMZg.ttf

479 ms

UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuGKYMZg.ttf

UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuGKYMZg.ttf

478 ms

UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuFuYMZg.ttf

UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuFuYMZg.ttf

476 ms

UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuDyYMZg.ttf

UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuDyYMZg.ttf

477 ms

UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuBWYMZg.ttf

UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuBWYMZg.ttf

467 ms

EJRSQgYoZZY2vCFuvAnt65qV.ttf

EJRSQgYoZZY2vCFuvAnt65qV.ttf

479 ms

EJRVQgYoZZY2vCFuvDFR.ttf

EJRVQgYoZZY2vCFuvDFR.ttf

490 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVuEooCP.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVuEooCP.ttf

490 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvoooCP.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvoooCP.ttf

490 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVsEpYCP.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVsEpYCP.ttf

489 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pYCP.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pYCP.ttf

489 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtapYCP.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtapYCP.ttf

490 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtzpYCP.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtzpYCP.ttf

490 ms

iframe_api

iframe_api

336 ms

help-1.svg

help-1.svg

271 ms

help-2.svg

help-2.svg

263 ms

help-3.svg

help-3.svg

267 ms

help-4.svg

help-4.svg

268 ms

help-5.svg

help-5.svg

265 ms

help-6.svg

help-6.svg

322 ms

why-1.svg

why-1.svg

318 ms

why-2.svg

why-2.svg

315 ms

why-3.svg

why-3.svg

320 ms

why-4.svg

why-4.svg

323 ms

why-5.svg

why-5.svg

322 ms

why-6.svg

why-6.svg

375 ms

fb.svg

fb.svg

377 ms

ig.svg

ig.svg

372 ms

tw.svg

tw.svg

376 ms

in.svg

in.svg

378 ms

yt.svg

yt.svg

379 ms

group-2242.svg

group-2242.svg

385 ms

vector5.svg

vector5.svg

391 ms

ajax-loader.gif

ajax-loader.gif

172 ms

slick.woff

slick.woff

145 ms

www-widgetapi.js

www-widgetapi.js

82 ms

Accessibility Review

caryestateplanning.com accessibility score

88

Accessibility Issues

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-hidden="true"] elements contain focusable descendents

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.

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

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

High

Page has valid source maps

SEO Factors

caryestateplanning.com SEO score

86

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

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

caryestateplanning.com

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