Tools & Wizards About Us
patchboyz.ca screenshot

Report Summary

  • 49

    Performance

    Renders faster than
    67% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 51% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 98

    SEO

    Google-friendlier than
    92% of websites

patchboyz.ca

PatchBoyz | Ottawa Drywall Repair & Stipple Removal Contractor

Page Load Speed

1.7 sec in total

First Response

168 ms

Resources Loaded

728 ms

Page Rendered

765 ms

patchboyz.ca screenshot

About Website

Visit patchboyz.ca now to see the best up-to-date Patch Boyz content for Canada and also check out these interesting facts you probably never knew about patchboyz.ca

Ottawa Drywall Repairs and Stipple Ceiling Repairs - Patch and Paint at a moments notice - 100% reliability -Family Business- Stipple Removal & Asbestos Removal

Visit patchboyz.ca

Key Findings

We analyzed Patchboyz.ca page load time and found that the first response time was 168 ms and then it took 1.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.

Performance Metrics

patchboyz.ca performance score

49

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

45/100

10%

LCP (Largest Contentful Paint)

Value3.5 s

63/100

25%

SI (Speed Index)

Value4.0 s

81/100

10%

TBT (Total Blocking Time)

Value1,670 ms

11/100

30%

CLS (Cumulative Layout Shift)

Value0.007

100/100

15%

TTI (Time to Interactive)

Value10.6 s

23/100

10%

Network Requests Diagram

www.patchboyz.ca

168 ms

jquery-latest.min.js

43 ms

pagecloud.runtime.js

65 ms

pagecloud.reset.css

75 ms

pagecloud.common.css

74 ms

Our browser made a total of 49 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Patchboyz.ca, 41% (20 requests) were made to Img.pagecloud.com and 22% (11 requests) were made to App-assets.pagecloud.com. The less responsive or slowest element that took the longest time to load (386 ms) relates to the external source Img.pagecloud.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 422.5 kB (55%)

Content Size

769.1 kB

After Optimization

346.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Patchboyz.ca main page is 769.1 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 50% of websites need less resources to load. HTML takes 460.8 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 384.1 kB

  • Original 460.8 kB
  • After minification 456.6 kB
  • After compression 76.7 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 384.1 kB or 83% of the original size.

Image Optimization

-1%

Potential reduce by 2.7 kB

  • Original 183.5 kB
  • After minification 180.9 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. Patch Boyz images are well optimized though.

JavaScript Optimization

-29%

Potential reduce by 35.7 kB

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

CSS Optimization

-2%

Potential reduce by 41 B

  • Original 2.3 kB
  • After minification 2.3 kB
  • After compression 2.3 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. Patchboyz.ca has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 23 (48%)

Requests Now

48

After Optimization

25

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 48 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Patch Boyz. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 19 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.patchboyz.ca

www.patchboyz.ca

168 ms

jquery-latest.min.js

jquery-latest.min.js

43 ms

pagecloud.runtime.js

pagecloud.runtime.js

65 ms

pagecloud.reset.css

pagecloud.reset.css

75 ms

pagecloud.common.css

pagecloud.common.css

74 ms

css

css

64 ms

css

css

94 ms

css

css

101 ms

js

js

64 ms

css

css

145 ms

pagecloud.events.js

pagecloud.events.js

91 ms

pagecloud.pageconfig.js

pagecloud.pageconfig.js

71 ms

pagecloud.form.js

pagecloud.form.js

84 ms

pagecloud.navigation.js

pagecloud.navigation.js

70 ms

pagecloud.sections.js

pagecloud.sections.js

77 ms

pagecloud.fullbleed.js

pagecloud.fullbleed.js

75 ms

pagecloud.analytics.js

pagecloud.analytics.js

77 ms

gtm.js

gtm.js

96 ms

PBlogo-fe920.png

PBlogo-fe920.png

216 ms

PBlogo-fe920.png

PBlogo-fe920.png

210 ms

bmo-a96f9.png

bmo-a96f9.png

212 ms

GNI-c111c.png

GNI-c111c.png

373 ms

made-oe461.png

made-oe461.png

300 ms

Mrr-h3760.png

Mrr-h3760.png

371 ms

reliance-k9373.png

reliance-k9373.png

211 ms

image-qa1ed.jpeg

image-qa1ed.jpeg

295 ms

Ottawa1.png

Ottawa1.png

373 ms

51962235-0-111-v00f3.png

51962235-0-111-v00f3.png

250 ms

tribefore-u9b3f-f829f.jpg

tribefore-u9b3f-f829f.jpg

296 ms

triafter-ufab6-vea69.jpg

triafter-ufab6-vea69.jpg

373 ms

image-c666c-u03da.jpeg

image-c666c-u03da.jpeg

298 ms

image-lc636-qf935.jpeg

image-lc636-qf935.jpeg

299 ms

image-1c5e2.png

image-1c5e2.png

386 ms

fbevents.js

fbevents.js

179 ms

image-dd9cc.jpeg

image-dd9cc.jpeg

326 ms

image-kb08b.png

image-kb08b.png

327 ms

image-j9351.png

image-j9351.png

360 ms

image-93bf2-i9107.jpeg

image-93bf2-i9107.jpeg

328 ms

image-gcdeb-94470.jpeg

image-gcdeb-94470.jpeg

330 ms

js

js

201 ms

analytics.js

analytics.js

231 ms

api.js

api.js

229 ms

js

js

157 ms

collect

collect

65 ms

collect

collect

70 ms

39 ms

loader.js

loader.js

22 ms

call-tracking_7.js

call-tracking_7.js

4 ms

14 ms

Accessibility Review

patchboyz.ca accessibility score

81

Accessibility Issues

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

Buttons do not have an accessible name

High

Links do not have a discernible name

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

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

Best Practices

patchboyz.ca best practices score

75

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

SEO Factors

patchboyz.ca SEO score

98

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

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 Patchboyz.ca 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 Patchboyz.ca 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

patchboyz.ca

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