Tools & Wizards About Us
elliottsangster.com screenshot

Report Summary

  • 6

    Performance

    Renders faster than
    21% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 54% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

elliottsangster.com

Elliott & Sangster, Local accountants in Cheboygan!

Page Load Speed

10.2 sec in total

First Response

2.4 sec

Resources Loaded

7.3 sec

Page Rendered

533 ms

elliottsangster.com screenshot

About Website

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

Visit elliottsangster.com

Key Findings

We analyzed Elliottsangster.com page load time and found that the first response time was 2.4 sec and then it took 7.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

elliottsangster.com performance score

6

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.0 s

1/100

10%

LCP (Largest Contentful Paint)

Value93.5 s

0/100

25%

SI (Speed Index)

Value16.2 s

0/100

10%

TBT (Total Blocking Time)

Value1,810 ms

9/100

30%

CLS (Cumulative Layout Shift)

Value0.633

9/100

15%

TTI (Time to Interactive)

Value12.5 s

14/100

10%

Network Requests Diagram

elliottsangster.com

2415 ms

js

98 ms

wp-emoji-release.min.js

36 ms

style.min.css

68 ms

mediaelementplayer-legacy.min.css

94 ms

Our browser made a total of 74 requests to load all elements on the main page. We found that 85% of them (63 requests) were addressed to the original Elliottsangster.com, 5% (4 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 (2.4 sec) belongs to the original domain Elliottsangster.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 348.7 kB (1%)

Content Size

30.9 MB

After Optimization

30.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Elliottsangster.com main page is 30.9 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 30.2 MB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 150.8 kB

  • Original 175.9 kB
  • After minification 173.5 kB
  • After compression 25.2 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 150.8 kB or 86% of the original size.

Image Optimization

-0%

Potential reduce by 48.5 kB

  • Original 30.2 MB
  • After minification 30.1 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. Elliott Sangster images are well optimized though.

JavaScript Optimization

-10%

Potential reduce by 18.5 kB

  • Original 193.8 kB
  • After minification 193.8 kB
  • After compression 175.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. This website has mostly compressed JavaScripts.

CSS Optimization

-39%

Potential reduce by 131.0 kB

  • Original 339.0 kB
  • After minification 322.0 kB
  • After compression 208.0 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. Elliottsangster.com needs all CSS files to be minified and compressed as it can save up to 131.0 kB or 39% of the original size.

Requests Breakdown

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

Requests Now

68

After Optimization

14

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

elliottsangster.com

elliottsangster.com

2415 ms

js

js

98 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

36 ms

style.min.css

style.min.css

68 ms

mediaelementplayer-legacy.min.css

mediaelementplayer-legacy.min.css

94 ms

wp-mediaelement.min.css

wp-mediaelement.min.css

95 ms

wc-blocks-vendors-style.css

wc-blocks-vendors-style.css

96 ms

wc-blocks-style.css

wc-blocks-style.css

128 ms

classic-themes.min.css

classic-themes.min.css

111 ms

woocommerce-layout.css

woocommerce-layout.css

108 ms

woocommerce.css

woocommerce.css

109 ms

frontend.min.css

frontend.min.css

147 ms

flatpickr.min.css

flatpickr.min.css

113 ms

select2.min.css

select2.min.css

122 ms

js_composer.min.css

js_composer.min.css

163 ms

bootstrap.min.css

bootstrap.min.css

150 ms

font-awesome.min.css

font-awesome.min.css

156 ms

ind-woocommerce.css

ind-woocommerce.css

159 ms

vc.css

vc.css

159 ms

css

css

40 ms

owl.carousel.css

owl.carousel.css

179 ms

owl.theme.css

owl.theme.css

180 ms

magnific-popup.css

magnific-popup.css

182 ms

dashicons.min.css

dashicons.min.css

215 ms

style.css

style.css

207 ms

jetpack.css

jetpack.css

209 ms

frontend-gtag.min.js

frontend-gtag.min.js

209 ms

jquery.min.js

jquery.min.js

213 ms

jquery-migrate.min.js

jquery-migrate.min.js

212 ms

jquery.blockUI.min.js

jquery.blockUI.min.js

235 ms

add-to-cart.min.js

add-to-cart.min.js

237 ms

flatpickr.min.js

flatpickr.min.js

238 ms

select2.min.js

select2.min.js

253 ms

woocommerce-add-to-cart.js

woocommerce-add-to-cart.js

237 ms

s-202409.js

s-202409.js

26 ms

js_composer_tta.min.css

js_composer_tta.min.css

242 ms

js.cookie.min.js

js.cookie.min.js

243 ms

woocommerce.min.js

woocommerce.min.js

243 ms

cart-fragments.min.js

cart-fragments.min.js

249 ms

e-202409.js

e-202409.js

25 ms

frontend.min.js

frontend.min.js

330 ms

bootstrap.min.js

bootstrap.min.js

307 ms

owl.carousel.min.js

owl.carousel.min.js

272 ms

jquery.magnific-popup.min.js

jquery.magnific-popup.min.js

248 ms

imagesloaded.min.js

imagesloaded.min.js

249 ms

js

js

83 ms

analytics.js

analytics.js

24 ms

isotope.pkgd.min.js

isotope.pkgd.min.js

233 ms

packery.min.js

packery.min.js

232 ms

jquery.counterup.min.js

jquery.counterup.min.js

231 ms

waypoints.min.js

waypoints.min.js

229 ms

custom.js

custom.js

227 ms

js_composer_front.min.js

js_composer_front.min.js

219 ms

vc-accordion.min.js

vc-accordion.min.js

211 ms

collect

collect

38 ms

vc-tta-autoplay.min.js

vc-tta-autoplay.min.js

186 ms

vc-tabs.min.js

vc-tabs.min.js

185 ms

service-5-360x203-1.jpg

service-5-360x203-1.jpg

86 ms

service-6-360x203-1.jpg

service-6-360x203-1.jpg

87 ms

service-2-360x203-1.jpg

service-2-360x203-1.jpg

86 ms

service-3-300x300-100x100.jpg

service-3-300x300-100x100.jpg

87 ms

service-1-150x150-1-100x100.jpg

service-1-150x150-1-100x100.jpg

88 ms

service-3-300x300.jpg

service-3-300x300.jpg

127 ms

service-1-150x150-1.jpg

service-1-150x150-1.jpg

128 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVQ.woff

63 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVQ.woff

64 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVQ.woff

142 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVQ.woff

143 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

143 ms

elliottsangster.com

elliottsangster.com

446 ms

woocommerce-smallscreen.css

woocommerce-smallscreen.css

34 ms

FullSizeRender-2.jpg

FullSizeRender-2.jpg

302 ms

IMG_1800.png

IMG_1800.png

657 ms

IMG_1798-1.png

IMG_1798-1.png

636 ms

Accessibility Review

elliottsangster.com accessibility score

83

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.

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

Low

No form fields have multiple labels

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

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

elliottsangster.com SEO score

86

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

elliottsangster.com

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