Tools & Wizards About Us
charlottetrees.com screenshot

Report Summary

  • 80

    Performance

    Renders faster than
    86% of other websites

  • 87

    Accessibility

    Visual factors better than
    that of 67% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

charlottetrees.com

Page Load Speed

5.6 sec in total

First Response

1.7 sec

Resources Loaded

3.5 sec

Page Rendered

420 ms

charlottetrees.com screenshot

About Website

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

We specialize in Tree Removal, Trimming & Pruning, and Stump Grinding in the Charlotte, North Carolina area. Call us today for your free consultation.

Visit charlottetrees.com

Key Findings

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

Performance Metrics

charlottetrees.com performance score

80

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.9 s

52/100

10%

LCP (Largest Contentful Paint)

Value3.7 s

57/100

25%

SI (Speed Index)

Value2.9 s

95/100

10%

TBT (Total Blocking Time)

Value160 ms

94/100

30%

CLS (Cumulative Layout Shift)

Value0.095

91/100

15%

TTI (Time to Interactive)

Value3.2 s

95/100

10%

Network Requests Diagram

charlottetrees.com

1741 ms

wp-emoji-release.min.js

106 ms

style.css

148 ms

jquery.js

336 ms

jquery-migrate.min.js

222 ms

Our browser made a total of 54 requests to load all elements on the main page. We found that 19% of them (10 requests) were addressed to the original Charlottetrees.com, 22% (12 requests) were made to Maps.googleapis.com and 17% (9 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Charlottetrees.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 961.6 kB (55%)

Content Size

1.7 MB

After Optimization

773.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Charlottetrees.com main page is 1.7 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. 50% of websites need less resources to load. Javascripts take 1.0 MB which makes up the majority of the site volume.

HTML Optimization

-67%

Potential reduce by 12.5 kB

  • Original 18.8 kB
  • After minification 18.2 kB
  • After compression 6.3 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 12.5 kB or 67% of the original size.

Image Optimization

-9%

Potential reduce by 39.8 kB

  • Original 440.0 kB
  • After minification 400.2 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. Charlottetrees images are well optimized though.

JavaScript Optimization

-68%

Potential reduce by 689.4 kB

  • Original 1.0 MB
  • After minification 1.0 MB
  • After compression 321.2 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 689.4 kB or 68% of the original size.

CSS Optimization

-83%

Potential reduce by 219.9 kB

  • Original 265.1 kB
  • After minification 257.6 kB
  • After compression 45.3 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. Charlottetrees.com needs all CSS files to be minified and compressed as it can save up to 219.9 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 24 (46%)

Requests Now

52

After Optimization

28

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

charlottetrees.com

charlottetrees.com

1741 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

106 ms

style.css

style.css

148 ms

jquery.js

jquery.js

336 ms

jquery-migrate.min.js

jquery-migrate.min.js

222 ms

tinynav.js

tinynav.js

159 ms

css

css

23 ms

css

css

35 ms

maps

maps

146 ms

bg.png

bg.png

225 ms

charlotte-logo1.png

charlotte-logo1.png

201 ms

cropped-tree-service-charlotte-nc-header.jpg

cropped-tree-service-charlotte-nc-header.jpg

472 ms

tree-service-charlotte-nc2-251x300.jpg

tree-service-charlotte-nc2-251x300.jpg

224 ms

yz8CbUNtnJA

yz8CbUNtnJA

140 ms

9nxddRDoJb4

9nxddRDoJb4

234 ms

js

js

59 ms

embed

embed

510 ms

www-embed-player-vflfNyN_r.css

www-embed-player-vflfNyN_r.css

64 ms

www-embed-player.js

www-embed-player.js

98 ms

in.php

in.php

282 ms

Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js

Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js

32 ms

ad_status.js

ad_status.js

190 ms

js

js

80 ms

init_embed.js

init_embed.js

44 ms

common.js

common.js

99 ms

map.js

map.js

98 ms

google4.png

google4.png

33 ms

overlay.js

overlay.js

32 ms

util.js

util.js

186 ms

onion.js

onion.js

27 ms

search_impl.js

search_impl.js

184 ms

StaticMapService.GetMapImage

StaticMapService.GetMapImage

231 ms

stats.js

stats.js

156 ms

openhand_8_8.cur

openhand_8_8.cur

139 ms

kh

kh

228 ms

ViewportInfoService.GetViewportInfo

ViewportInfoService.GetViewportInfo

68 ms

transparent.png

transparent.png

87 ms

ViewportInfoService.GetViewportInfo

ViewportInfoService.GetViewportInfo

66 ms

kh

kh

201 ms

controls.js

controls.js

46 ms

kh

kh

201 ms

kh

kh

161 ms

kh

kh

182 ms

vt

vt

132 ms

vt

vt

137 ms

vt

vt

121 ms

css

css

110 ms

entity11.png

entity11.png

60 ms

vt

vt

107 ms

vt

vt

121 ms

vt

vt

109 ms

vt

vt

80 ms

mapcnt6.png

mapcnt6.png

45 ms

tmapctrl.png

tmapctrl.png

38 ms

Accessibility Review

charlottetrees.com accessibility score

87

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.

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

Document doesn't have a <title> element

Best Practices

charlottetrees.com best practices score

92

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

Page has valid source maps

SEO Factors

charlottetrees.com SEO score

75

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

Document doesn't have a <title> element

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

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

charlottetrees.com

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