Report Summary

  • 11

    Performance

    Renders faster than
    24% of other websites

  • 61

    Accessibility

    Visual factors better than
    that of 27% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 79

    SEO

    Google-friendlier than
    40% of websites

ashtonwalden.com

Residential & Commercial Lawn Care in Texas | Ashton Walden

Page Load Speed

3.3 sec in total

First Response

102 ms

Resources Loaded

2.2 sec

Page Rendered

1 sec

About Website

Click here to check amazing Ashton Walden content. Otherwise, check out these important facts you probably never knew about ashtonwalden.com

For over 20 years, Ashton Walden Turf Services has provided lawn care services for residential and commercial customers throughout Lubbock, Texas, and the surrounding areas.

Visit ashtonwalden.com

Key Findings

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

Performance Metrics

ashtonwalden.com performance score

11

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.3 s

73/100

10%

LCP (Largest Contentful Paint)

Value19.3 s

0/100

25%

SI (Speed Index)

Value18.2 s

0/100

10%

TBT (Total Blocking Time)

Value1,940 ms

8/100

30%

CLS (Cumulative Layout Shift)

Value0.648

9/100

15%

TTI (Time to Interactive)

Value27.7 s

0/100

10%

Network Requests Diagram

ashtonwalden.com

102 ms

ashtonwalden.com

1388 ms

gtm.js

85 ms

widget.js

97 ms

fbevents.js

46 ms

Our browser made a total of 62 requests to load all elements on the main page. We found that 65% of them (40 requests) were addressed to the original Ashtonwalden.com, 6% (4 requests) were made to Dkg63mm7284y1.cloudfront.net and 5% (3 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Ashtonwalden.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 130.3 kB (2%)

Content Size

6.3 MB

After Optimization

6.2 MB

In fact, the total size of Ashtonwalden.com main page is 6.3 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 5.6 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 84.1 kB

  • Original 99.4 kB
  • After minification 78.5 kB
  • After compression 15.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. This page needs HTML code to be minified as it can gain 20.9 kB, which is 21% 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 84.1 kB or 85% of the original size.

Image Optimization

-0%

Potential reduce by 351 B

  • Original 5.6 MB
  • After minification 5.6 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. Ashton Walden images are well optimized though.

JavaScript Optimization

-6%

Potential reduce by 29.1 kB

  • Original 517.9 kB
  • After minification 517.9 kB
  • After compression 488.8 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.

CSS Optimization

-18%

Potential reduce by 16.7 kB

  • Original 95.4 kB
  • After minification 95.4 kB
  • After compression 78.7 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. Ashtonwalden.com needs all CSS files to be minified and compressed as it can save up to 16.7 kB or 18% of the original size.

Requests Breakdown

Number of requests can be reduced by 35 (61%)

Requests Now

57

After Optimization

22

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

Accessibility Review

ashtonwalden.com accessibility score

61

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-*] attributes do not match their roles

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

High

[role]s are not contained by their required parent element

High

ARIA IDs are not unique

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

[id] attributes on active, focusable elements are not unique

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

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

Missing source maps for large first-party JavaScript

SEO Factors

ashtonwalden.com SEO score

79

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

High

Image elements do not have [alt] attributes

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

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