Tools & Wizards About Us
honeygrow.com screenshot

Report Summary

  • 63

    Performance

    Renders faster than
    77% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

honeygrow.com

honeygrow | Honest Eating + Growing Local

Page Load Speed

1.1 sec in total

First Response

40 ms

Resources Loaded

896 ms

Page Rendered

156 ms

honeygrow.com screenshot

About Website

Welcome to honeygrow.com homepage info - get ready to check Honeygrow best content for United States right away, or after learning these important things about honeygrow.com

Healthy, nourishing and delicious stir-frys, salads, and honeybars since 2012.

Visit honeygrow.com

Key Findings

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

Performance Metrics

honeygrow.com performance score

63

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.2 s

20/100

10%

LCP (Largest Contentful Paint)

Value19.6 s

0/100

25%

SI (Speed Index)

Value4.6 s

71/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value4.2 s

86/100

10%

Network Requests Diagram

www.honeygrow.com

40 ms

bootstrap.js

93 ms

head.min.js

48 ms

main.128d9cb9360dd450e451cb5b0cb0bc84.scss

106 ms

api.js

118 ms

Our browser made a total of 56 requests to load all elements on the main page. We found that 4% of them (2 requests) were addressed to the original Honeygrow.com, 18% (10 requests) were made to Fonts.gstatic.com and 16% (9 requests) were made to Images.getbento.com. The less responsive or slowest element that took the longest time to load (495 ms) relates to the external source Images.getbento.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 92.4 kB (6%)

Content Size

1.7 MB

After Optimization

1.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Honeygrow.com main page is 1.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. 65% of websites need less resources to load. Javascripts take 847.6 kB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 89.6 kB

  • Original 104.0 kB
  • After minification 99.7 kB
  • After compression 14.4 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 89.6 kB or 86% of the original size.

Image Optimization

-0%

Potential reduce by 805 B

  • Original 640.0 kB
  • After minification 639.2 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. Honeygrow images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 1.2 kB

  • Original 847.6 kB
  • After minification 847.6 kB
  • After compression 846.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

-1%

Potential reduce by 729 B

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

Requests Breakdown

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

Requests Now

35

After Optimization

18

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.honeygrow.com

www.honeygrow.com

40 ms

bootstrap.js

bootstrap.js

93 ms

head.min.js

head.min.js

48 ms

main.128d9cb9360dd450e451cb5b0cb0bc84.scss

main.128d9cb9360dd450e451cb5b0cb0bc84.scss

106 ms

api.js

api.js

118 ms

player.js

player.js

135 ms

foot.libs.min.js

foot.libs.min.js

101 ms

bentobox.min.js

bentobox.min.js

118 ms

main.js

main.js

115 ms

main.js.map

main.js.map

134 ms

bento-analytics.min.js

bento-analytics.min.js

116 ms

mfq6tlm.js

mfq6tlm.js

237 ms

css

css

76 ms

recaptcha__en.js

recaptcha__en.js

360 ms

fbevents.js

fbevents.js

444 ms

gtm.js

gtm.js

359 ms

images.getbento.com

images.getbento.com

306 ms

957805648

957805648

282 ms

www.honeygrow.com

www.honeygrow.com

266 ms

64cbe65e15366a343f0e841f_app_9038880

64cbe65e15366a343f0e841f_app_9038880

393 ms

45066honeygrow-wordmark_black_R.png

45066honeygrow-wordmark_black_R.png

343 ms

56638hg-down-default_150.png

56638hg-down-default_150.png

382 ms

9615hg_toms-river-wall2.png

9615hg_toms-river-wall2.png

388 ms

18421chesapeake-crab_app_detail.png

18421chesapeake-crab_app_detail.png

413 ms

3854flower.png

3854flower.png

380 ms

35152website-content-cartering-banner-2000_2023-Q2.jpg

35152website-content-cartering-banner-2000_2023-Q2.jpg

413 ms

41276Noodle-day-gif-invert.gif

41276Noodle-day-gif-invert.gif

479 ms

13681hosp-background.png

13681hosp-background.png

495 ms

3wIj9HXYQDOwoGZ87KrQ_ApfelGrotezk-Regular.woff

3wIj9HXYQDOwoGZ87KrQ_ApfelGrotezk-Regular.woff

332 ms

ZTgEEYfMSeSypeR9iqzY_ApfelGrotezk-Fett.woff

ZTgEEYfMSeSypeR9iqzY_ApfelGrotezk-Fett.woff

336 ms

font-bento-custom.woff

font-bento-custom.woff

200 ms

Qw3PZQNVED7rKGKxtqIqX5E-AVSJrOCfjY46_DjRbMZhKg.ttf

Qw3PZQNVED7rKGKxtqIqX5E-AVSJrOCfjY46_DjRbMZhKg.ttf

331 ms

Qw3PZQNVED7rKGKxtqIqX5E-AVSJrOCfjY46_LjQbMZhKg.ttf

Qw3PZQNVED7rKGKxtqIqX5E-AVSJrOCfjY46_LjQbMZhKg.ttf

336 ms

Qw3PZQNVED7rKGKxtqIqX5E-AVSJrOCfjY46_GbQbMZhKg.ttf

Qw3PZQNVED7rKGKxtqIqX5E-AVSJrOCfjY46_GbQbMZhKg.ttf

357 ms

Qw3PZQNVED7rKGKxtqIqX5E-AVSJrOCfjY46_DjQbMZhKg.ttf

Qw3PZQNVED7rKGKxtqIqX5E-AVSJrOCfjY46_DjQbMZhKg.ttf

365 ms

Qw3PZQNVED7rKGKxtqIqX5E-AVSJrOCfjY46_ArQbMZhKg.ttf

Qw3PZQNVED7rKGKxtqIqX5E-AVSJrOCfjY46_ArQbMZhKg.ttf

363 ms

Qw3PZQNVED7rKGKxtqIqX5E-AVSJrOCfjY46_ObXbMZhKg.ttf

Qw3PZQNVED7rKGKxtqIqX5E-AVSJrOCfjY46_ObXbMZhKg.ttf

362 ms

Qw3PZQNVED7rKGKxtqIqX5E-AVSJrOCfjY46_N_XbMZhKg.ttf

Qw3PZQNVED7rKGKxtqIqX5E-AVSJrOCfjY46_N_XbMZhKg.ttf

365 ms

d

d

29 ms

d

d

76 ms

d

d

84 ms

d

d

85 ms

d

d

207 ms

d

d

169 ms

p.gif

p.gif

188 ms

anchor

anchor

106 ms

331080637340741

331080637340741

149 ms

styles__ltr.css

styles__ltr.css

8 ms

recaptcha__en.js

recaptcha__en.js

26 ms

api.js

api.js

63 ms

tE6BD2dmJ4MsSW_XgLndBgqWpAgx-dXQ3y0tInp2GOI.js

tE6BD2dmJ4MsSW_XgLndBgqWpAgx-dXQ3y0tInp2GOI.js

39 ms

webworker.js

webworker.js

37 ms

logo_48.png

logo_48.png

27 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

7 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

7 ms

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

7 ms

Accessibility Review

honeygrow.com accessibility score

100

Accessibility Issues

Best Practices

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

High

Missing source maps for large first-party JavaScript

SEO Factors

honeygrow.com SEO score

100

Search Engine Optimization Advices

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

honeygrow.com

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