Report Summary

  • 68

    Performance

    Renders faster than
    80% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 89% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 100

    SEO

    Google-friendlier than
    95% of websites

indyarborist.com

IndyArborist.com - Tree Removal, Tree Service, Tree Trimming

Page Load Speed

777 ms in total

First Response

56 ms

Resources Loaded

492 ms

Page Rendered

229 ms

indyarborist.com screenshot

About Website

Welcome to indyarborist.com homepage info - get ready to check Indy Arborist best content right away, or after learning these important things about indyarborist.com

The best tree removal and pruning service in Indianapolis, IndyArborist.com tree service is a small company offering full service tree care at affordable rates.

Visit indyarborist.com

Key Findings

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

Performance Metrics

indyarborist.com performance score

68

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.3 s

98/100

10%

LCP (Largest Contentful Paint)

Value5.4 s

20/100

25%

SI (Speed Index)

Value2.7 s

97/100

10%

TBT (Total Blocking Time)

Value380 ms

70/100

30%

CLS (Cumulative Layout Shift)

Value0.027

100/100

15%

TTI (Time to Interactive)

Value5.3 s

73/100

10%

Network Requests Diagram

indyarborist.com

56 ms

rs=w:1920,m

336 ms

script.js

152 ms

UX.4.28.12.js

12 ms

script.js

195 ms

Our browser made a total of 10 requests to load all elements on the main page. We found that 10% of them (1 request) were addressed to the original Indyarborist.com, 90% (9 requests) were made to Img1.wsimg.com. The less responsive or slowest element that took the longest time to load (336 ms) relates to the external source Img1.wsimg.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 369.8 kB (36%)

Content Size

1.0 MB

After Optimization

652.4 kB

In fact, the total size of Indyarborist.com main page is 1.0 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 10% of websites need less resources to load. Images take 498.6 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 67.8 kB

  • Original 82.1 kB
  • After minification 82.1 kB
  • After compression 14.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 67.8 kB or 83% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 498.6 kB
  • After minification 498.6 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. Indy Arborist images are well optimized though.

JavaScript Optimization

-68%

Potential reduce by 302.0 kB

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

Requests Breakdown

Number of requests can be reduced by 3 (60%)

Requests Now

5

After Optimization

2

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

Accessibility Review

indyarborist.com accessibility score

96

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.

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

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

indyarborist.com SEO score

100

Search Engine Optimization Advices

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 Indyarborist.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 Indyarborist.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 Indy Arborist. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: