Tools & Wizards About Us
doodycalls.com screenshot

Report Summary

  • 72

    Performance

    Renders faster than
    82% of other websites

  • 79

    Accessibility

    Visual factors better than
    that of 47% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

doodycalls.com

Pooper Scooper Service - Pet Waste Removal | DoodyCalls

Page Load Speed

1.1 sec in total

First Response

82 ms

Resources Loaded

679 ms

Page Rendered

294 ms

doodycalls.com screenshot

About Website

Visit doodycalls.com now to see the best up-to-date Doody Calls content for United States and also check out these interesting facts you probably never knew about doodycalls.com

DoodyCalls offers a variety of residential and commercial pet waste removal services backed by a 100% Satisfaction Guarantee. Request a free quote today and have one less thing to worry about!

Visit doodycalls.com

Key Findings

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

Performance Metrics

doodycalls.com performance score

72

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.9 s

86/100

10%

LCP (Largest Contentful Paint)

Value1.9 s

97/100

25%

SI (Speed Index)

Value2.3 s

99/100

10%

TBT (Total Blocking Time)

Value470 ms

61/100

30%

CLS (Cumulative Layout Shift)

Value0.222

56/100

15%

TTI (Time to Interactive)

Value10.0 s

26/100

10%

Network Requests Diagram

www.doodycalls.com

82 ms

4391496594.js

32 ms

style.css

6 ms

clforms.css

12 ms

jquery-ui.css

12 ms

Our browser made a total of 77 requests to load all elements on the main page. We found that 60% of them (46 requests) were addressed to the original Doodycalls.com, 6% (5 requests) were made to Fonts.gstatic.com and 3% (2 requests) were made to Calls.netsearchdirect.com. The less responsive or slowest element that took the longest time to load (271 ms) belongs to the original domain Doodycalls.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 775.3 kB (34%)

Content Size

2.3 MB

After Optimization

1.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Doodycalls.com main page is 2.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. 70% of websites need less resources to load. Images take 1.3 MB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 89.0 kB

  • Original 112.5 kB
  • After minification 107.2 kB
  • After compression 23.5 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 89.0 kB or 79% of the original size.

Image Optimization

-8%

Potential reduce by 99.1 kB

  • Original 1.3 MB
  • After minification 1.2 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. Doody Calls images are well optimized though.

JavaScript Optimization

-64%

Potential reduce by 472.5 kB

  • Original 736.7 kB
  • After minification 722.0 kB
  • After compression 264.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 472.5 kB or 64% of the original size.

CSS Optimization

-80%

Potential reduce by 114.7 kB

  • Original 143.4 kB
  • After minification 142.8 kB
  • After compression 28.8 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. Doodycalls.com needs all CSS files to be minified and compressed as it can save up to 114.7 kB or 80% of the original size.

Requests Breakdown

Number of requests can be reduced by 22 (32%)

Requests Now

68

After Optimization

46

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.doodycalls.com

www.doodycalls.com

82 ms

4391496594.js

4391496594.js

32 ms

style.css

style.css

6 ms

clforms.css

clforms.css

12 ms

jquery-ui.css

jquery-ui.css

12 ms

jquery.min.js

jquery.min.js

12 ms

jquery-ui.min.js

jquery-ui.min.js

30 ms

html5shiv.min.js

html5shiv.min.js

11 ms

modernizr.custom.js

modernizr.custom.js

10 ms

polyfiller.js

polyfiller.js

25 ms

api.js

api.js

182 ms

pinit.js

pinit.js

97 ms

css

css

98 ms

script.js

script.js

23 ms

number-changer.js

number-changer.js

98 ms

conversion.js

conversion.js

97 ms

event

event

34 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

13 ms

css

css

25 ms

analytics.js

analytics.js

27 ms

shim-ext.css

shim-ext.css

12 ms

geolocation.js

geolocation.js

57 ms

8.js

8.js

100 ms

form-shim-extend.js

form-shim-extend.js

57 ms

17.js

17.js

125 ms

mediaelement-jaris.js

mediaelement-jaris.js

116 ms

track.js

track.js

119 ms

canvas-blob.js

canvas-blob.js

121 ms

recaptcha__en.js

recaptcha__en.js

162 ms

sdk.js

sdk.js

129 ms

gtm.js

gtm.js

154 ms

seal_1221728.js

seal_1221728.js

212 ms

getnumdata.js

getnumdata.js

143 ms

252 ms

mobile-header-menu.png

mobile-header-menu.png

116 ms

pinterestLogoSmall.png

pinterestLogoSmall.png

116 ms

sprite.png

sprite.png

185 ms

home-bg4.png

home-bg4.png

271 ms

slogan-new.png

slogan-new.png

115 ms

dogownerbox2.png

dogownerbox2.png

115 ms

dog-body.png

dog-body.png

118 ms

dog-paws.png

dog-paws.png

119 ms

tablet-dog-body.png

tablet-dog-body.png

118 ms

tablet-dog-paws.png

tablet-dog-paws.png

117 ms

mobile-dog-body.png

mobile-dog-body.png

122 ms

mobile-dog-paws.png

mobile-dog-paws.png

121 ms

catownerbox2.png

catownerbox2.png

122 ms

cat-body2.png

cat-body2.png

119 ms

cat-paws.png

cat-paws.png

177 ms

tablet-cat-body.png

tablet-cat-body.png

183 ms

tablet-cat-paws.png

tablet-cat-paws.png

182 ms

mobile-cat-body.png

mobile-cat-body.png

182 ms

mobile-cat-paws.png

mobile-cat-paws.png

212 ms

commbox2.png

commbox2.png

211 ms

kid-dog.png

kid-dog.png

211 ms

goodHousekeepingLogo.png

goodHousekeepingLogo.png

212 ms

peoplePetsLogo.png

peoplePetsLogo.png

211 ms

redBookLogo.png

redBookLogo.png

218 ms

usaTodayLogo.png

usaTodayLogo.png

218 ms

wallStreetJournalLogo.png

wallStreetJournalLogo.png

217 ms

topShadow.png

topShadow.png

217 ms

Daneillos01.jpg

Daneillos01.jpg

246 ms

shade-background-find-a-scooper.png

shade-background-find-a-scooper.png

227 ms

collect

collect

76 ms

v0SdcGFAl2aezM9Vq_aFTQ.ttf

v0SdcGFAl2aezM9Vq_aFTQ.ttf

34 ms

DvlFBScY1r-FMtZSYIYoYw.ttf

DvlFBScY1r-FMtZSYIYoYw.ttf

92 ms

FUDHvzEKSJww3kCxuiAo2A.ttf

FUDHvzEKSJww3kCxuiAo2A.ttf

126 ms

0XxGQsSc1g4rdRdjJKZrNC3USBnSvpkopQaUR-2r7iU.ttf

0XxGQsSc1g4rdRdjJKZrNC3USBnSvpkopQaUR-2r7iU.ttf

109 ms

Qx6FPcitRwTC_k88tLPc-SbsRidxnYrfzLNRqJkHfFo.ttf

Qx6FPcitRwTC_k88tLPc-SbsRidxnYrfzLNRqJkHfFo.ttf

109 ms

pinit_main.js

pinit_main.js

95 ms

collect

collect

155 ms

207 ms

pixel.gif

pixel.gif

113 ms

pixel.gif

pixel.gif

89 ms

xd_arbiter.php

xd_arbiter.php

46 ms

xd_arbiter.php

xd_arbiter.php

71 ms

37 ms

Accessibility Review

doodycalls.com accessibility score

79

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 have valid values

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.

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

Links do not have a discernible name

Best Practices

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

doodycalls.com SEO score

91

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Doodycalls.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 Doodycalls.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

doodycalls.com

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