Tools & Wizards About Us
highwatertackle.com screenshot

Report Summary

  • 45

    Performance

    Renders faster than
    64% of other websites

  • 87

    Accessibility

    Visual factors better than
    that of 66% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

highwatertackle.com

Highwater Fish and Tackle Shop North Vancouver BC

Page Load Speed

2.4 sec in total

First Response

184 ms

Resources Loaded

2 sec

Page Rendered

244 ms

highwatertackle.com screenshot

About Website

Visit highwatertackle.com now to see the best up-to-date Highwater Tackle content and also check out these interesting facts you probably never knew about highwatertackle.com

Highwater Fish and Tackle shop centrally located in North Vancouver BC. From gear to tackle and everything in between, servicing salt and fresh water angler needs for over 30 years

Visit highwatertackle.com

Key Findings

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

Performance Metrics

highwatertackle.com performance score

45

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.2 s

20/100

10%

LCP (Largest Contentful Paint)

Value11.1 s

0/100

25%

SI (Speed Index)

Value8.5 s

17/100

10%

TBT (Total Blocking Time)

Value290 ms

80/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value9.9 s

27/100

10%

Network Requests Diagram

highwatertackle.com

184 ms

www.highwatertackle.com

319 ms

style.min.css

16 ms

font-awesome-legacy.min.css

26 ms

grid-system.css

23 ms

Our browser made a total of 54 requests to load all elements on the main page. We found that 85% of them (46 requests) were addressed to the original Highwatertackle.com, 9% (5 requests) were made to Fonts.gstatic.com and 4% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (460 ms) belongs to the original domain Highwatertackle.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 77.1 kB (19%)

Content Size

408.7 kB

After Optimization

331.6 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Highwatertackle.com main page is 408.7 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 189.2 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 75.5 kB

  • Original 92.8 kB
  • After minification 90.9 kB
  • After compression 17.3 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 75.5 kB or 81% of the original size.

JavaScript Optimization

-1%

Potential reduce by 1.1 kB

  • Original 189.2 kB
  • After minification 189.2 kB
  • After compression 188.1 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

-0%

Potential reduce by 558 B

  • Original 126.8 kB
  • After minification 126.8 kB
  • After compression 126.2 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. Highwatertackle.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 34 (76%)

Requests Now

45

After Optimization

11

  • Images
  • JavaScript
  • CSS

The browser has sent 45 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Highwater Tackle. 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 18 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

highwatertackle.com

highwatertackle.com

184 ms

www.highwatertackle.com

www.highwatertackle.com

319 ms

style.min.css

style.min.css

16 ms

font-awesome-legacy.min.css

font-awesome-legacy.min.css

26 ms

grid-system.css

grid-system.css

23 ms

style.css

style.css

32 ms

element-fancy-box.css

element-fancy-box.css

31 ms

css

css

42 ms

responsive.css

responsive.css

29 ms

select2.css

select2.css

24 ms

skin-material.css

skin-material.css

39 ms

menu-dynamic.css

menu-dynamic.css

41 ms

widget-nectar-posts.css

widget-nectar-posts.css

44 ms

js_composer.min.css

js_composer.min.css

42 ms

salient-dynamic-styles.css

salient-dynamic-styles.css

51 ms

css

css

60 ms

jquery.min.js

jquery.min.js

43 ms

jquery-migrate.min.js

jquery-migrate.min.js

43 ms

js

js

159 ms

email-decode.min.js

email-decode.min.js

38 ms

style-non-critical.css

style-non-critical.css

46 ms

jquery.fancybox.css

jquery.fancybox.css

57 ms

core.css

core.css

57 ms

fullscreen-legacy.css

fullscreen-legacy.css

57 ms

jquery.easing.min.js

jquery.easing.min.js

151 ms

jquery.mousewheel.min.js

jquery.mousewheel.min.js

152 ms

priority.js

priority.js

152 ms

transit.min.js

transit.min.js

155 ms

waypoints.js

waypoints.js

154 ms

imagesLoaded.min.js

imagesLoaded.min.js

154 ms

hoverintent.min.js

hoverintent.min.js

157 ms

jquery.fancybox.js

jquery.fancybox.js

158 ms

anime.min.js

anime.min.js

157 ms

superfish.js

superfish.js

166 ms

init.js

init.js

169 ms

touchswipe.min.js

touchswipe.min.js

166 ms

select2.min.js

select2.min.js

168 ms

js_composer_front.min.js

js_composer_front.min.js

168 ms

Highwater_Tackle_LogoBlack.svg

Highwater_Tackle_LogoBlack.svg

117 ms

Highwater_Tackle_LogoWhite.svg

Highwater_Tackle_LogoWhite.svg

119 ms

outstore1-jpg.webp

outstore1-jpg.webp

121 ms

Summer_front_slash_2-scaled.webp

Summer_front_slash_2-scaled.webp

120 ms

1ae8be64-b552-4209-a10e-9b57028d757e1-jpg.webp

1ae8be64-b552-4209-a10e-9b57028d757e1-jpg.webp

122 ms

IMG_9716-jpg.webp

IMG_9716-jpg.webp

123 ms

IMG_0054-jpg.webp

IMG_0054-jpg.webp

124 ms

HighwaterTackle_890438-scaled.webp

HighwaterTackle_890438-scaled.webp

124 ms

KFOmCnqEu92Fr1Mu7GxPKTU1Kg.ttf

KFOmCnqEu92Fr1Mu7GxPKTU1Kg.ttf

21 ms

KFOlCnqEu92Fr1MmWUlfChc9AMP6lQ.ttf

KFOlCnqEu92Fr1MmWUlfChc9AMP6lQ.ttf

41 ms

pxiByp8kv8JHgFVrLCz7Z1JlEN2JQEk.ttf

pxiByp8kv8JHgFVrLCz7Z1JlEN2JQEk.ttf

53 ms

pxiByp8kv8JHgFVrLEj6Z1JlEN2JQEk.ttf

pxiByp8kv8JHgFVrLEj6Z1JlEN2JQEk.ttf

53 ms

pxiByp8kv8JHgFVrLGT9Z1JlEN2JQEk.ttf

pxiByp8kv8JHgFVrLGT9Z1JlEN2JQEk.ttf

54 ms

icomoon.woff

icomoon.woff

282 ms

fontawesome-webfont.svg

fontawesome-webfont.svg

460 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

441 ms

Accessibility Review

highwatertackle.com accessibility score

87

Accessibility Issues

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

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

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

highwatertackle.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 Highwatertackle.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 Highwatertackle.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

highwatertackle.com

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