Tools & Wizards About Us
jmackie.com screenshot

Report Summary

  • 35

    Performance

    Renders faster than
    55% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 61% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 84

    SEO

    Google-friendlier than
    52% of websites

jmackie.com

Western Financial Group | Pembroke Nelson Street Insurance Broker

Page Load Speed

1.5 sec in total

First Response

75 ms

Resources Loaded

1 sec

Page Rendered

344 ms

jmackie.com screenshot

About Website

Welcome to jmackie.com homepage info - get ready to check Jmackie best content right away, or after learning these important things about jmackie.com

Whether you’re looking for car and truck insurance, home insurance, business insurance, farm insurance or seasonal property insurance, we’re licensed experts in Pembroke, Ontario Nelson Street.

Visit jmackie.com

Key Findings

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

jmackie.com performance score

35

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.2 s

43/100

10%

LCP (Largest Contentful Paint)

Value4.7 s

33/100

25%

SI (Speed Index)

Value6.7 s

36/100

10%

TBT (Total Blocking Time)

Value1,700 ms

11/100

30%

CLS (Cumulative Layout Shift)

Value0.006

100/100

15%

TTI (Time to Interactive)

Value16.3 s

5/100

10%

Network Requests Diagram

Johnston-and-Mackie-Insurance-Pembroke2

75 ms

Pembroke-Nelson-Street

222 ms

be8c78e6029cb74a263ce68d52dccfa8.min.css

42 ms

font-awesome.min.css

40 ms

yvl3ckf.css

271 ms

Our browser made a total of 52 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Jmackie.com, 19% (10 requests) were made to Use.typekit.net and 6% (3 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (271 ms) relates to the external source Use.typekit.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 87.0 kB (28%)

Content Size

306.1 kB

After Optimization

219.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Jmackie.com main page is 306.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. 40% of websites need less resources to load. Images take 187.1 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 69.0 kB

  • Original 85.7 kB
  • After minification 71.5 kB
  • After compression 16.6 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 14.1 kB, which is 17% 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 69.0 kB or 81% of the original size.

Image Optimization

-7%

Potential reduce by 13.4 kB

  • Original 187.1 kB
  • After minification 173.7 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. Jmackie images are well optimized though.

JavaScript Optimization

-14%

Potential reduce by 4.5 kB

  • Original 33.4 kB
  • After minification 33.4 kB
  • After compression 28.9 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 4.5 kB or 14% of the original size.

CSS Optimization

-0%

Potential reduce by 0 B

  • Original 5 B

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.

Requests Breakdown

Number of requests can be reduced by 18 (46%)

Requests Now

39

After Optimization

21

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Johnston-and-Mackie-Insurance-Pembroke2

Johnston-and-Mackie-Insurance-Pembroke2

75 ms

Pembroke-Nelson-Street

Pembroke-Nelson-Street

222 ms

be8c78e6029cb74a263ce68d52dccfa8.min.css

be8c78e6029cb74a263ce68d52dccfa8.min.css

42 ms

font-awesome.min.css

font-awesome.min.css

40 ms

yvl3ckf.css

yvl3ckf.css

271 ms

owlcarousel.css

owlcarousel.css

57 ms

e9a401cfe052c28e47ecce90abd1bf81.min.css

e9a401cfe052c28e47ecce90abd1bf81.min.css

92 ms

user.svg

user.svg

60 ms

western-desktop-logo-2024.svg

western-desktop-logo-2024.svg

57 ms

logo_mobile.svg

logo_mobile.svg

61 ms

90e196dff822052fe72e36daf2b578c5.jpg

90e196dff822052fe72e36daf2b578c5.jpg

73 ms

find-broker-icon.svg

find-broker-icon.svg

70 ms

Why-Western-Blue-2024_v2.jpg

Why-Western-Blue-2024_v2.jpg

102 ms

945855cfc027eedb73b0ffab981de952.min.js

945855cfc027eedb73b0ffab981de952.min.js

99 ms

js

js

98 ms

9303.js

9303.js

45 ms

launch-4914025d5743.min.js

launch-4914025d5743.min.js

35 ms

jquery.waypoints.min.js

jquery.waypoints.min.js

44 ms

1.js

1.js

35 ms

5124a8f515e262690d735902d75b98ce.min.js

5124a8f515e262690d735902d75b98ce.min.js

64 ms

footer-logo.svg

footer-logo.svg

75 ms

css

css

39 ms

p.css

p.css

35 ms

bundle-icon.svg

bundle-icon.svg

69 ms

homeIconNew.svg

homeIconNew.svg

58 ms

carIconNew.svg

carIconNew.svg

59 ms

farmIconNew.svg

farmIconNew.svg

60 ms

businessIconNew.svg

businessIconNew.svg

57 ms

camperIconNew.svg

camperIconNew.svg

62 ms

motorcycleIconNew.svg

motorcycleIconNew.svg

60 ms

boatIconNew.svg

boatIconNew.svg

63 ms

lifeIconNew.svg

lifeIconNew.svg

64 ms

travelIconNew.svg

travelIconNew.svg

62 ms

gtm.js

gtm.js

57 ms

w.js

w.js

72 ms

fbevents.js

fbevents.js

71 ms

seal.min.js

seal.min.js

117 ms

app.js

app.js

117 ms

d

d

97 ms

d

d

128 ms

d

d

128 ms

d

d

125 ms

d

d

125 ms

d

d

129 ms

d

d

141 ms

d

d

150 ms

d

d

154 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

54 ms

js

js

69 ms

19e4dc39-e61f-4f46-a551-6cbdcb0d506a.js

19e4dc39-e61f-4f46-a551-6cbdcb0d506a.js

82 ms

settings.luckyorange.net

settings.luckyorange.net

23 ms

12 ms

Accessibility Review

jmackie.com accessibility score

86

Accessibility Issues

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

jmackie.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

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

jmackie.com SEO score

84

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

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

jmackie.com

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