Tools & Wizards About Us
huckleberrypeople.com screenshot

Report Summary

  • 57

    Performance

    Renders faster than
    73% of other websites

  • 73

    Accessibility

    Visual factors better than
    that of 38% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

huckleberrypeople.com

Huckleberry Jams, Jellies, Syrups & Toppings | Huckleberry Candies & Chocolates | Keylime Gourmet Candies | Mustards, BBQ Sauces and Wine | Wild Choke...

Page Load Speed

2.2 sec in total

First Response

531 ms

Resources Loaded

1.5 sec

Page Rendered

156 ms

huckleberrypeople.com screenshot

About Website

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

The Huckleberry People Family Business was created in 1982 with one goal in mind: handmake jam and chocolate using Mother Nature's most distinctive and delectable wild berry: The Wild Huckleberry.

Visit huckleberrypeople.com

Key Findings

We analyzed Huckleberrypeople.com page load time and found that the first response time was 531 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

huckleberrypeople.com performance score

57

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.9 s

87/100

10%

LCP (Largest Contentful Paint)

Value7.2 s

5/100

25%

SI (Speed Index)

Value3.9 s

82/100

10%

TBT (Total Blocking Time)

Value260 ms

83/100

30%

CLS (Cumulative Layout Shift)

Value0.18

67/100

15%

TTI (Time to Interactive)

Value8.7 s

36/100

10%

Network Requests Diagram

huckleberrypeople.com

531 ms

css

20 ms

jquery1c59cc318f73f9da98e18cd20acd1e0f

154 ms

bundled1acf78c7fdff0ff92592a74b623c5954

269 ms

magicscroll.css

208 ms

Our browser made a total of 37 requests to load all elements on the main page. We found that 73% of them (27 requests) were addressed to the original Huckleberrypeople.com, 16% (6 requests) were made to Fonts.gstatic.com and 5% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (656 ms) belongs to the original domain Huckleberrypeople.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 109.5 kB (2%)

Content Size

7.1 MB

After Optimization

7.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Huckleberrypeople.com main page is 7.1 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. 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. Images take 7.0 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 26.6 kB

  • Original 32.2 kB
  • After minification 27.8 kB
  • After compression 5.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 4.3 kB, which is 13% 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 26.6 kB or 83% of the original size.

Image Optimization

-0%

Potential reduce by 32.1 kB

  • Original 7.0 MB
  • After minification 6.9 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. Huckleberry People images are well optimized though.

JavaScript Optimization

-41%

Potential reduce by 44.6 kB

  • Original 108.1 kB
  • After minification 108.1 kB
  • After compression 63.5 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 44.6 kB or 41% of the original size.

CSS Optimization

-34%

Potential reduce by 6.2 kB

  • Original 18.4 kB
  • After minification 18.4 kB
  • After compression 12.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. Huckleberrypeople.com needs all CSS files to be minified and compressed as it can save up to 6.2 kB or 34% of the original size.

Requests Breakdown

Number of requests can be reduced by 5 (17%)

Requests Now

29

After Optimization

24

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

huckleberrypeople.com

huckleberrypeople.com

531 ms

css

css

20 ms

jquery1c59cc318f73f9da98e18cd20acd1e0f

jquery1c59cc318f73f9da98e18cd20acd1e0f

154 ms

bundled1acf78c7fdff0ff92592a74b623c5954

bundled1acf78c7fdff0ff92592a74b623c5954

269 ms

magicscroll.css

magicscroll.css

208 ms

magicscroll.js

magicscroll.js

320 ms

minicart.js

minicart.js

142 ms

bundled9194e11828f06f763807c789d7093cf2

bundled9194e11828f06f763807c789d7093cf2

215 ms

logo.png

logo.png

82 ms

huckleberries.png

huckleberries.png

173 ms

seasalt.jpg

seasalt.jpg

421 ms

sourlicorice.jpg

sourlicorice.jpg

487 ms

lic-29.jpg

lic-29.jpg

449 ms

unicorn.jpg

unicorn.jpg

483 ms

candybars.jpg

candybars.jpg

496 ms

candybars1.jpg

candybars1.jpg

463 ms

maple.jpg

maple.jpg

558 ms

boogers.jpg

boogers.jpg

613 ms

brownies.jpg

brownies.jpg

615 ms

jellybeans.jpg

jellybeans.jpg

557 ms

jellybeans2.jpg

jellybeans2.jpg

560 ms

jellybeans1.jpg

jellybeans1.jpg

633 ms

storefront.jpg

storefront.jpg

622 ms

medium-newproducts1.jpg

medium-newproducts1.jpg

582 ms

amex.png

amex.png

593 ms

mastercard.png

mastercard.png

650 ms

visa.png

visa.png

656 ms

u-440qyriQwlOrhSvowK_l5-fCZK.woff

u-440qyriQwlOrhSvowK_l5-fCZK.woff

26 ms

u-4n0qyriQwlOrhSvowK_l521wRZWMf8.woff

u-4n0qyriQwlOrhSvowK_l521wRZWMf8.woff

183 ms

u-4n0qyriQwlOrhSvowK_l52xwNZWMf8.woff

u-4n0qyriQwlOrhSvowK_l52xwNZWMf8.woff

27 ms

glyphicons-halflings-regular.woff

glyphicons-halflings-regular.woff

650 ms

u-4m0qyriQwlOrhSvowK_l5-eRZOf-Q.woff

u-4m0qyriQwlOrhSvowK_l5-eRZOf-Q.woff

87 ms

u-4l0qyriQwlOrhSvowK_l5-eR7lXff4jvo.woff

u-4l0qyriQwlOrhSvowK_l5-eR7lXff4jvo.woff

57 ms

u-4l0qyriQwlOrhSvowK_l5-eR71Wvf4jvo.woff

u-4l0qyriQwlOrhSvowK_l5-eR71Wvf4jvo.woff

143 ms

analytics.js

analytics.js

8 ms

collect

collect

31 ms

js

js

58 ms

Accessibility Review

huckleberrypeople.com accessibility score

73

Accessibility Issues

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

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.

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best Practices

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

huckleberrypeople.com SEO score

83

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Huckleberrypeople.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Huckleberrypeople.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

huckleberrypeople.com

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