Tools & Wizards About Us
604goodguy.com screenshot

Report Summary

  • 36

    Performance

    Renders faster than
    55% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 71% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

604goodguy.com

Good Guys Heating, Cooling & Plumbing: Serving Greater Vancouver - 604goodguy - 604goodguy

Page Load Speed

2.3 sec in total

First Response

361 ms

Resources Loaded

1.5 sec

Page Rendered

380 ms

604goodguy.com screenshot

About Website

Click here to check amazing 604 Good Guy content. Otherwise, check out these important facts you probably never knew about 604goodguy.com

Good Guys Heating, Cooling & Plumbing. Providing the Greater Vancouver area with quality plumbing, heating, and air conditioning services.

Visit 604goodguy.com

Key Findings

We analyzed 604goodguy.com page load time and found that the first response time was 361 ms and then it took 1.9 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.

Performance Metrics

604goodguy.com performance score

36

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.2 s

44/100

10%

LCP (Largest Contentful Paint)

Value7.3 s

5/100

25%

SI (Speed Index)

Value4.0 s

81/100

10%

TBT (Total Blocking Time)

Value740 ms

40/100

30%

CLS (Cumulative Layout Shift)

Value0.331

34/100

15%

TTI (Time to Interactive)

Value7.6 s

47/100

10%

Network Requests Diagram

604goodguy.com

361 ms

frontend.min.css

127 ms

menu-animation.min.css

188 ms

main.css

189 ms

bootstrap.min.css

189 ms

Our browser made a total of 74 requests to load all elements on the main page. We found that 68% of them (50 requests) were addressed to the original 604goodguy.com, 28% (21 requests) were made to Fonts.gstatic.com and 3% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (584 ms) belongs to the original domain 604goodguy.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 181.9 kB (12%)

Content Size

1.5 MB

After Optimization

1.3 MB

  • HTML
  • Images

In fact, the total size of 604goodguy.com main page is 1.5 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

-86%

Potential reduce by 171.5 kB

  • Original 200.3 kB
  • After minification 194.6 kB
  • After compression 28.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 171.5 kB or 86% of the original size.

Image Optimization

-1%

Potential reduce by 10.4 kB

  • Original 1.3 MB
  • After minification 1.3 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. 604 Good Guy images are well optimized though.

Requests Breakdown

Number of requests can be reduced by 27 (54%)

Requests Now

50

After Optimization

23

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

604goodguy.com

604goodguy.com

361 ms

frontend.min.css

frontend.min.css

127 ms

menu-animation.min.css

menu-animation.min.css

188 ms

main.css

main.css

189 ms

bootstrap.min.css

bootstrap.min.css

189 ms

style.min.css

style.min.css

249 ms

styles.css

styles.css

137 ms

contact-form-7.min.css

contact-form-7.min.css

138 ms

header-footer-elementor.css

header-footer-elementor.css

197 ms

elementor-icons.min.css

elementor-icons.min.css

197 ms

animations.min.css

animations.min.css

201 ms

frontend.min.css

frontend.min.css

262 ms

post-11.css

post-11.css

199 ms

global.css

global.css

259 ms

post-7.css

post-7.css

266 ms

frontend.css

frontend.css

268 ms

all.min.css

all.min.css

271 ms

v4-shims.min.css

v4-shims.min.css

270 ms

post-9.css

post-9.css

324 ms

post-30.css

post-30.css

325 ms

style.css

style.css

327 ms

css

css

43 ms

fontawesome.min.css

fontawesome.min.css

327 ms

regular.min.css

regular.min.css

332 ms

solid.min.css

solid.min.css

332 ms

jquery.min.js

jquery.min.js

584 ms

js

js

79 ms

js

js

127 ms

lazyload.min.js

lazyload.min.js

579 ms

344f0f516a979458cfae7cba06a8bb6e.js

344f0f516a979458cfae7cba06a8bb6e.js

581 ms

banner-2.jpg

banner-2.jpg

408 ms

banner-2.jpg

banner-2.jpg

264 ms

bg-1.jpg

bg-1.jpg

267 ms

KFOmCnqEu92Fr1Mu4mxM.woff

KFOmCnqEu92Fr1Mu4mxM.woff

52 ms

KFOlCnqEu92Fr1MmEU9fBBc-.woff

KFOlCnqEu92Fr1MmEU9fBBc-.woff

34 ms

KFOlCnqEu92Fr1MmSU5fBBc-.woff

KFOlCnqEu92Fr1MmSU5fBBc-.woff

33 ms

KFOkCnqEu92Fr1MmgVxIIzQ.woff

KFOkCnqEu92Fr1MmgVxIIzQ.woff

52 ms

KFOlCnqEu92Fr1MmWUlfBBc-.woff

KFOlCnqEu92Fr1MmWUlfBBc-.woff

51 ms

KFOlCnqEu92Fr1MmYUtfBBc-.woff

KFOlCnqEu92Fr1MmYUtfBBc-.woff

52 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVQ.woff

52 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVQ.woff

52 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVQ.woff

53 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjr0B4gaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjr0B4gaVQ.woff

52 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVQ.woff

54 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVQ.woff

55 ms

pxiByp8kv8JHgFVrLEj6Z1xlEw.woff

pxiByp8kv8JHgFVrLEj6Z1xlEw.woff

54 ms

pxiByp8kv8JHgFVrLCz7Z1xlEw.woff

pxiByp8kv8JHgFVrLCz7Z1xlEw.woff

54 ms

pxiByp8kv8JHgFVrLDD4Z1xlEw.woff

pxiByp8kv8JHgFVrLDD4Z1xlEw.woff

55 ms

pxiByp8kv8JHgFVrLBT5Z1xlEw.woff

pxiByp8kv8JHgFVrLBT5Z1xlEw.woff

56 ms

pxiByp8kv8JHgFVrLGT9Z1xlEw.woff

pxiByp8kv8JHgFVrLGT9Z1xlEw.woff

57 ms

pxiEyp8kv8JHgFVrJJfedA.woff

pxiEyp8kv8JHgFVrJJfedA.woff

56 ms

pxiByp8kv8JHgFVrLDz8Z1xlEw.woff

pxiByp8kv8JHgFVrLDz8Z1xlEw.woff

57 ms

pxiByp8kv8JHgFVrLFj_Z1xlEw.woff

pxiByp8kv8JHgFVrLFj_Z1xlEw.woff

57 ms

pxiGyp8kv8JHgFVrLPTucHtG.woff

pxiGyp8kv8JHgFVrLPTucHtG.woff

57 ms

fa-solid-900.woff

fa-solid-900.woff

252 ms

fa-regular-400.woff

fa-regular-400.woff

116 ms

logo5.png

logo5.png

96 ms

banner-1.jpg

banner-1.jpg

191 ms

Mobile_Banner-1.jpg

Mobile_Banner-1.jpg

188 ms

img-1.jpg

img-1.jpg

97 ms

img-2.jpg

img-2.jpg

130 ms

img-3.jpg

img-3.jpg

135 ms

img-4.jpg

img-4.jpg

151 ms

img-5.jpg

img-5.jpg

187 ms

img-1.png

img-1.png

199 ms

img-2.png

img-2.png

216 ms

img-5.png

img-5.png

260 ms

img-6.png

img-6.png

312 ms

hot-water.png

hot-water.png

261 ms

air-quality.png

air-quality.png

263 ms

img-8.jpg

img-8.jpg

281 ms

img-7.jpg

img-7.jpg

297 ms

banner3.jpg

banner3.jpg

316 ms

img-2-2.png

img-2-2.png

323 ms

Accessibility Review

604goodguy.com accessibility score

89

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-hidden="true"] elements contain focusable descendents

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

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

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

604goodguy.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

SEO Factors

604goodguy.com SEO score

93

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

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 604goodguy.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 604goodguy.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

604goodguy.com

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