Report Summary

  • 44

    Performance

    Renders faster than
    63% of other websites

  • 94

    Accessibility

    Visual factors better than
    that of 83% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 89

    SEO

    Google-friendlier than
    66% of websites

aplustree.com

Leaders in Tree Care | A Plus Tree, Inc

Page Load Speed

4.1 sec in total

First Response

243 ms

Resources Loaded

2.3 sec

Page Rendered

1.5 sec

aplustree.com screenshot

About Website

Welcome to aplustree.com homepage info - get ready to check A Plus Tree best content for United States right away, or after learning these important things about aplustree.com

Expert tree care services for a greener tomorrow. Professional pruning, removal, and maintenance. Let us nurture nature at its best.

Visit aplustree.com

Key Findings

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

Performance Metrics

aplustree.com performance score

44

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.9 s

52/100

10%

LCP (Largest Contentful Paint)

Value8.9 s

1/100

25%

SI (Speed Index)

Value6.5 s

39/100

10%

TBT (Total Blocking Time)

Value440 ms

64/100

30%

CLS (Cumulative Layout Shift)

Value0.127

82/100

15%

TTI (Time to Interactive)

Value9.5 s

30/100

10%

Network Requests Diagram

aplustree.com

243 ms

aplustree.com

657 ms

jquery.min.js

21 ms

jquery-migrate.min.js

29 ms

rbtools.min.js

210 ms

Our browser made a total of 97 requests to load all elements on the main page. We found that 97% of them (94 requests) were addressed to the original Aplustree.com, 3% (3 requests) were made to Staging-aplustree.kinsta.cloud. The less responsive or slowest element that took the longest time to load (1 sec) relates to the external source Staging-aplustree.kinsta.cloud.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.5 MB (31%)

Content Size

4.8 MB

After Optimization

3.3 MB

In fact, the total size of Aplustree.com main page is 4.8 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 3.1 MB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 1.5 MB

  • Original 1.7 MB
  • After minification 1.7 MB
  • After compression 223.0 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 1.5 MB or 87% of the original size.

Image Optimization

-1%

Potential reduce by 27.7 kB

  • Original 3.1 MB
  • After minification 3.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. A Plus Tree images are well optimized though.

Requests Breakdown

Number of requests can be reduced by 45 (51%)

Requests Now

89

After Optimization

44

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

Accessibility Review

aplustree.com accessibility score

94

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.

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

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

SEO Factors

aplustree.com SEO score

89

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

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

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