Tools & Wizards About Us
highliner.com screenshot

Report Summary

  • 45

    Performance

    Renders faster than
    64% of other websites

  • 98

    Accessibility

    Visual factors better than
    that of 94% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

highliner.com

Highliner

Page Load Speed

1.7 sec in total

First Response

63 ms

Resources Loaded

1.2 sec

Page Rendered

452 ms

highliner.com screenshot

About Website

Welcome to highliner.com homepage info - get ready to check Highliner best content for Canada right away, or after learning these important things about highliner.com

Offering quality guarantee frozen fish and seafood for you and your family for over one hundred years.

Visit highliner.com

Key Findings

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

Performance Metrics

highliner.com performance score

45

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.6 s

32/100

10%

LCP (Largest Contentful Paint)

Value9.8 s

0/100

25%

SI (Speed Index)

Value9.5 s

12/100

10%

TBT (Total Blocking Time)

Value330 ms

76/100

30%

CLS (Cumulative Layout Shift)

Value0.041

99/100

15%

TTI (Time to Interactive)

Value9.8 s

28/100

10%

Network Requests Diagram

highliner.com

63 ms

highliner.com

96 ms

www.highliner.com

187 ms

gtm.js

103 ms

js

184 ms

Our browser made a total of 61 requests to load all elements on the main page. We found that 36% of them (22 requests) were addressed to the original Highliner.com, 23% (14 requests) were made to Images.contentstack.io and 16% (10 requests) were made to Cdn.cookielaw.org. The less responsive or slowest element that took the longest time to load (788 ms) relates to the external source Images.contentstack.io.

Page Optimization Overview & Recommendations

Page size can be reduced by 196.4 kB (5%)

Content Size

3.7 MB

After Optimization

3.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Highliner.com main page is 3.7 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. 80% 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. Images take 3.4 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 191.3 kB

  • Original 226.8 kB
  • After minification 226.6 kB
  • After compression 35.5 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 191.3 kB or 84% of the original size.

Image Optimization

-0%

Potential reduce by 2.4 kB

  • Original 3.4 MB
  • After minification 3.4 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. Highliner images are well optimized though.

JavaScript Optimization

-2%

Potential reduce by 2.6 kB

  • Original 137.1 kB
  • After minification 137.1 kB
  • After compression 134.4 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 15 B

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

Requests Breakdown

Number of requests can be reduced by 32 (60%)

Requests Now

53

After Optimization

21

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

highliner.com

highliner.com

63 ms

highliner.com

highliner.com

96 ms

www.highliner.com

www.highliner.com

187 ms

gtm.js

gtm.js

103 ms

js

js

184 ms

otSDKStub.js

otSDKStub.js

34 ms

5fa7f25b87b45e6e.css

5fa7f25b87b45e6e.css

78 ms

polyfills-c67a75d1b6f99dc8.js

polyfills-c67a75d1b6f99dc8.js

219 ms

145-21e42e71563a2145.js

145-21e42e71563a2145.js

183 ms

693.ac4cacfc2cd74d28.js

693.ac4cacfc2cd74d28.js

213 ms

webpack-22e11ff32e7236a9.js

webpack-22e11ff32e7236a9.js

197 ms

framework-0bff4c72fef67389.js

framework-0bff4c72fef67389.js

218 ms

main-a2fb11407b7331fb.js

main-a2fb11407b7331fb.js

146 ms

_app-4943af5506d1a5c4.js

_app-4943af5506d1a5c4.js

273 ms

518-3992a28203d4c5a1.js

518-3992a28203d4c5a1.js

218 ms

242-ab88325ca735d35c.js

242-ab88325ca735d35c.js

269 ms

714-c1a5f9cc6faf76cc.js

714-c1a5f9cc6faf76cc.js

329 ms

147-d5eb96369d9c1fab.js

147-d5eb96369d9c1fab.js

329 ms

index-92b9af11f6b9cb1b.js

index-92b9af11f6b9cb1b.js

329 ms

_buildManifest.js

_buildManifest.js

329 ms

_ssgManifest.js

_ssgManifest.js

329 ms

widget.js

widget.js

123 ms

4797c563-cd70-4741-aa40-abaa65287bdd.json

4797c563-cd70-4741-aa40-abaa65287bdd.json

40 ms

events.js

events.js

60 ms

core.js

core.js

64 ms

hl.png

hl.png

105 ms

HL_Homepage_Family_Favourites_sub_category_component2.png

HL_Homepage_Family_Favourites_sub_category_component2.png

139 ms

HL_Homepage_Signature_Cuts_sub_category_component2.png

HL_Homepage_Signature_Cuts_sub_category_component2.png

139 ms

HL_Homepage_Pan_Sear_Selects_sub_category_component2.png

HL_Homepage_Pan_Sear_Selects_sub_category_component2.png

139 ms

hl.png

hl.png

138 ms

Email.svg

Email.svg

100 ms

Facebook.svg

Facebook.svg

102 ms

Pinterest.svg

Pinterest.svg

135 ms

Instagram.svg

Instagram.svg

137 ms

search.svg

search.svg

291 ms

menu.svg

menu.svg

325 ms

location

location

140 ms

125th-Web-Banner-V2-Web.jpg

125th-Web-Banner-V2-Web.jpg

788 ms

125th-Web-Banner-V2-Web.jpg

125th-Web-Banner-V2-Web.jpg

129 ms

section0-hero@2x.png

section0-hero@2x.png

276 ms

Banner1.png

Banner1.png

564 ms

Banner1.png

Banner1.png

98 ms

cta.svg

cta.svg

318 ms

cta-light.svg

cta-light.svg

280 ms

saq_pxl

saq_pxl

24 ms

widget.css

widget.css

42 ms

i

i

98 ms

open_sans.css

open_sans.css

85 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1y4k.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1y4k.woff

137 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1y4k.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1y4k.woff

162 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1y4k.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1y4k.woff

170 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0C4k.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0C4k.woff

183 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0C4k.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0C4k.woff

175 ms

otBannerSdk.js

otBannerSdk.js

117 ms

en.json

en.json

29 ms

otFlat.json

otFlat.json

17 ms

otPcCenter.json

otPcCenter.json

23 ms

otCookieSettingsButton.json

otCookieSettingsButton.json

24 ms

otCommonStyles.css

otCommonStyles.css

33 ms

ot_close.svg

ot_close.svg

29 ms

2023-05-09_High_Liner_Foods_Logo_Horizontal_P_BLUE_RGB.png

2023-05-09_High_Liner_Foods_Logo_Horizontal_P_BLUE_RGB.png

26 ms

Accessibility Review

highliner.com accessibility score

98

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.

Best Practices

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

highliner.com SEO score

92

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

highliner.com

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