Tools & Wizards About Us
lawnsavers.com screenshot

Report Summary

  • 4

    Performance

    Renders faster than
    20% of other websites

  • 65

    Accessibility

    Visual factors better than
    that of 30% of websites

  • 77

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 78

    SEO

    Google-friendlier than
    39% of websites

lawnsavers.com

Toronto Lawn Care & Weed Control | 1000+ Positive Reviews | LawnSavers | GTA Lawn Care Near You!

Page Load Speed

3.8 sec in total

First Response

175 ms

Resources Loaded

3.1 sec

Page Rendered

551 ms

lawnsavers.com screenshot

About Website

Visit lawnsavers.com now to see the best up-to-date Lawn Savers content for Canada and also check out these interesting facts you probably never knew about lawnsavers.com

Effective lawn care & weed control service since 1989 in the Greater Toronto Area. Voted Consumer Choice Best Lawn Care Company past 10 years | No Risk Guarantee.

Visit lawnsavers.com

Key Findings

We analyzed Lawnsavers.com page load time and found that the first response time was 175 ms and then it took 3.6 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

lawnsavers.com performance score

4

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.5 s

6/100

10%

LCP (Largest Contentful Paint)

Value18.0 s

0/100

25%

SI (Speed Index)

Value20.1 s

0/100

10%

TBT (Total Blocking Time)

Value3,460 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0.492

17/100

15%

TTI (Time to Interactive)

Value28.9 s

0/100

10%

Network Requests Diagram

lawnsavers.com

175 ms

lawnsavers.com

287 ms

wp-emoji-release.min.js

51 ms

style.min.css

130 ms

go_pricing_styles.css

177 ms

Our browser made a total of 155 requests to load all elements on the main page. We found that 59% of them (91 requests) were addressed to the original Lawnsavers.com, 9% (14 requests) were made to Fonts.gstatic.com and 7% (11 requests) were made to Use.typekit.net. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source M.addthis.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 778.2 kB (39%)

Content Size

2.0 MB

After Optimization

1.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Lawnsavers.com main page is 2.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. 80% 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 912.0 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 176.4 kB

  • Original 221.7 kB
  • After minification 214.6 kB
  • After compression 45.4 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 176.4 kB or 80% of the original size.

Image Optimization

-2%

Potential reduce by 15.5 kB

  • Original 912.0 kB
  • After minification 896.5 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. Lawn Savers images are well optimized though.

JavaScript Optimization

-58%

Potential reduce by 243.2 kB

  • Original 421.6 kB
  • After minification 414.6 kB
  • After compression 178.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 243.2 kB or 58% of the original size.

CSS Optimization

-74%

Potential reduce by 343.1 kB

  • Original 464.5 kB
  • After minification 461.7 kB
  • After compression 121.4 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. Lawnsavers.com needs all CSS files to be minified and compressed as it can save up to 343.1 kB or 74% of the original size.

Requests Breakdown

Number of requests can be reduced by 68 (57%)

Requests Now

119

After Optimization

51

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

lawnsavers.com

lawnsavers.com

175 ms

lawnsavers.com

lawnsavers.com

287 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

51 ms

style.min.css

style.min.css

130 ms

go_pricing_styles.css

go_pricing_styles.css

177 ms

video-container.min.css

video-container.min.css

161 ms

wpfront-scroll-top.min.css

wpfront-scroll-top.min.css

181 ms

yet_styles.css

yet_styles.css

174 ms

addthis_wordpress_public.min.css

addthis_wordpress_public.min.css

180 ms

ubermenu.min.css

ubermenu.min.css

189 ms

simplegreen.css

simplegreen.css

197 ms

font-awesome.min.css

font-awesome.min.css

215 ms

jquery.bxslider.css

jquery.bxslider.css

218 ms

TweenMax.min.js

TweenMax.min.js

124 ms

jquery.min.js

jquery.min.js

250 ms

jquery-migrate.min.js

jquery-migrate.min.js

242 ms

wpgmza_data.js

wpgmza_data.js

205 ms

jquery.bxslider.min.js

jquery.bxslider.min.js

234 ms

t.js

t.js

164 ms

addthis_widget.js

addthis_widget.js

211 ms

style.css

style.css

217 ms

oqr8sag.js

oqr8sag.js

158 ms

formreset.min.css

formreset.min.css

212 ms

formsmain.min.css

formsmain.min.css

355 ms

readyclass.min.css

readyclass.min.css

212 ms

browsers.min.css

browsers.min.css

352 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

353 ms

wp-polyfill.min.js

wp-polyfill.min.js

353 ms

dom-ready.min.js

dom-ready.min.js

355 ms

hooks.min.js

hooks.min.js

356 ms

i18n.min.js

i18n.min.js

355 ms

a11y.min.js

a11y.min.js

356 ms

jquery.json.min.js

jquery.json.min.js

356 ms

gravityforms.min.js

gravityforms.min.js

359 ms

api.js

api.js

204 ms

moxie.min.js

moxie.min.js

360 ms

plupload.min.js

plupload.min.js

356 ms

jquery.maskedinput.min.js

jquery.maskedinput.min.js

356 ms

placeholders.jquery.min.js

placeholders.jquery.min.js

357 ms

comment-reply.min.js

comment-reply.min.js

357 ms

comment_count.js

comment_count.js

358 ms

comment_embed.js

comment_embed.js

359 ms

widget.js

widget.js

202 ms

go_pricing_scripts.js

go_pricing_scripts.js

359 ms

wpfront-scroll-top.min.js

wpfront-scroll-top.min.js

328 ms

ubermenu.min.js

ubermenu.min.js

268 ms

lazyload.min.js

lazyload.min.js

248 ms

style.css

style.css

116 ms

moatframe.js

moatframe.js

250 ms

gtm.js

gtm.js

422 ms

analytics.js

analytics.js

343 ms

bat.js

bat.js

417 ms

family2.jpg

family2.jpg

207 ms

twitter.png

twitter.png

206 ms

facebook.png

facebook.png

206 ms

youtube.png

youtube.png

204 ms

instagram.png

instagram.png

204 ms

home_26.png

home_26.png

180 ms

home_28.png

home_28.png

183 ms

d

d

179 ms

d

d

219 ms

d

d

221 ms

d

d

219 ms

d

d

219 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

293 ms

zSbdkzym0OY

zSbdkzym0OY

223 ms

home_30.png

home_30.png

141 ms

pinterest.png

pinterest.png

142 ms

count.js

count.js

203 ms

collect

collect

87 ms

B3BDFx3L0W4

B3BDFx3L0W4

94 ms

style-tablet.css

style-tablet.css

81 ms

5661390.js

5661390.js

116 ms

www-player.css

www-player.css

42 ms

www-embed-player.js

www-embed-player.js

83 ms

base.js

base.js

293 ms

fetch-polyfill.js

fetch-polyfill.js

130 ms

collect

collect

286 ms

style-mobile.css

style-mobile.css

117 ms

5661390

5661390

589 ms

recaptcha__en.js

recaptcha__en.js

719 ms

zoid.frame.min.js

zoid.frame.min.js

573 ms

captivated.css

captivated.css

715 ms

300lo.json

300lo.json

1087 ms

ga-audiences

ga-audiences

433 ms

logo.png

logo.png

250 ms

sh.f48a1a04fe8dbf021b4cda1d.html

sh.f48a1a04fe8dbf021b4cda1d.html

303 ms

d

d

315 ms

d

d

300 ms

d

d

306 ms

d

d

300 ms

d

d

305 ms

consumer-choice-award.jpg

consumer-choice-award.jpg

304 ms

homestars-best-of-award-winner.jpg

homestars-best-of-award-winner.jpg

315 ms

homestars-best-of-the-best-winner.jpg

homestars-best-of-the-best-winner.jpg

304 ms

top-choice-award.jpg

top-choice-award.jpg

305 ms

RC_TorStar-Diamond.gif

RC_TorStar-Diamond.gif

303 ms

Screen-Shot-2016-05-12-at-2.14.50-PM-150x150.png

Screen-Shot-2016-05-12-at-2.14.50-PM-150x150.png

304 ms

Screen-Shot-2016-05-12-at-2.12.02-PM-150x150.png

Screen-Shot-2016-05-12-at-2.12.02-PM-150x150.png

381 ms

Screen-Shot-2016-05-12-at-2.08.17-PM-150x150.png

Screen-Shot-2016-05-12-at-2.08.17-PM-150x150.png

382 ms

Screen-Shot-2016-05-12-at-2.03.28-PM-150x150.png

Screen-Shot-2016-05-12-at-2.03.28-PM-150x150.png

382 ms

Screen-Shot-2016-05-12-at-1.34.37-PM-150x150.png

Screen-Shot-2016-05-12-at-1.34.37-PM-150x150.png

381 ms

homestars.png

homestars.png

303 ms

google.png

google.png

380 ms

facebook.png

facebook.png

381 ms

sticky1.png

sticky1.png

381 ms

sticky2.png

sticky2.png

381 ms

sticky3.png

sticky3.png

380 ms

home_13.png

home_13.png

380 ms

home_15.png

home_15.png

380 ms

home_17.png

home_17.png

525 ms

home_19.png

home_19.png

523 ms

newsletter-cta.png

newsletter-cta.png

520 ms

jenny.jpg

jenny.jpg

699 ms

expertise.png

expertise.png

700 ms

members.png

members.png

699 ms

threebestrated.png

threebestrated.png

698 ms

115.png

115.png

698 ms

bx_loader.gif

bx_loader.gif

698 ms

p.gif

p.gif

621 ms

layers.fa6cd1947ce26e890d3d.js

layers.fa6cd1947ce26e890d3d.js

368 ms

ad_status.js

ad_status.js

685 ms

0Q0sPaTf27KkVV0qBrYI7cmJeSJkpG4CF1zVddAZEjs.js

0Q0sPaTf27KkVV0qBrYI7cmJeSJkpG4CF1zVddAZEjs.js

211 ms

embed.js

embed.js

161 ms

clarity.js

clarity.js

240 ms

components.js

components.js

238 ms

KFOmCnqEu92Fr1Mu4mxMKTU1Kg.woff

KFOmCnqEu92Fr1Mu4mxMKTU1Kg.woff

492 ms

KFOmCnqEu92Fr1Mu7GxMKTU1Kvnz.woff

KFOmCnqEu92Fr1Mu7GxMKTU1Kvnz.woff

558 ms

KFOmCnqEu92Fr1Mu7WxMKTU1Kvnz.woff

KFOmCnqEu92Fr1Mu7WxMKTU1Kvnz.woff

560 ms

KFOmCnqEu92Fr1Mu4WxMKTU1Kvnz.woff

KFOmCnqEu92Fr1Mu4WxMKTU1Kvnz.woff

569 ms

KFOmCnqEu92Fr1Mu7mxMKTU1Kvnz.woff

KFOmCnqEu92Fr1Mu7mxMKTU1Kvnz.woff

569 ms

KFOmCnqEu92Fr1Mu5mxMKTU1Kvnz.woff

KFOmCnqEu92Fr1Mu5mxMKTU1Kvnz.woff

569 ms

KFOmCnqEu92Fr1Mu72xMKTU1Kvnz.woff

KFOmCnqEu92Fr1Mu72xMKTU1Kvnz.woff

568 ms

KFOlCnqEu92Fr1MmEU9fBBc-AMP6lQ.woff

KFOlCnqEu92Fr1MmEU9fBBc-AMP6lQ.woff

568 ms

KFOlCnqEu92Fr1MmEU9fChc-AMP6lbBP.woff

KFOlCnqEu92Fr1MmEU9fChc-AMP6lbBP.woff

569 ms

KFOlCnqEu92Fr1MmEU9fCxc-AMP6lbBP.woff

KFOlCnqEu92Fr1MmEU9fCxc-AMP6lbBP.woff

570 ms

KFOlCnqEu92Fr1MmEU9fBxc-AMP6lbBP.woff

KFOlCnqEu92Fr1MmEU9fBxc-AMP6lbBP.woff

571 ms

KFOlCnqEu92Fr1MmEU9fCBc-AMP6lbBP.woff

KFOlCnqEu92Fr1MmEU9fCBc-AMP6lbBP.woff

569 ms

KFOlCnqEu92Fr1MmEU9fABc-AMP6lbBP.woff

KFOlCnqEu92Fr1MmEU9fABc-AMP6lbBP.woff

570 ms

KFOlCnqEu92Fr1MmEU9fCRc-AMP6lbBP.woff

KFOlCnqEu92Fr1MmEU9fCRc-AMP6lbBP.woff

570 ms

homestars.png

homestars.png

485 ms

google.png

google.png

407 ms

sticky1.png

sticky1.png

474 ms

sticky3.png

sticky3.png

474 ms

home_13.png

home_13.png

404 ms

home_15.png

home_15.png

406 ms

sticky2.png

sticky2.png

482 ms

home_19.png

home_19.png

327 ms

home_17.png

home_17.png

327 ms

id

id

253 ms

render.js

render.js

79 ms

Create

Create

126 ms

Create

Create

128 ms

c.gif

c.gif

45 ms

GenerateIT

GenerateIT

13 ms

Accessibility Review

lawnsavers.com accessibility score

65

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

[role] values are not valid

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

Some elements have a [tabindex] value greater than 0

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

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

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

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

lawnsavers.com best practices score

77

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

High

Registers an unload listener

Low

Detected JavaScript libraries

SEO Factors

lawnsavers.com SEO score

78

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lawnsavers.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Lawnsavers.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

lawnsavers.com

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