Tools & Wizards About Us
flowerbowl.com screenshot

Report Summary

  • 25

    Performance

    Renders faster than
    44% of other websites

  • 93

    Accessibility

    Visual factors better than
    that of 80% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

flowerbowl.com

The Flower Bowl | Recreational & Medical Cannabis Dispensaries | Michigan

Page Load Speed

21.6 sec in total

First Response

74 ms

Resources Loaded

21.4 sec

Page Rendered

57 ms

flowerbowl.com screenshot

About Website

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

Start Healing with The Flower Bowl. The Flower Bowl offers Recreational & Medical Cannabis Dispensaries in Michigan. Visit our dispensaries today and order online.

Visit flowerbowl.com

Key Findings

We analyzed Flowerbowl.com page load time and found that the first response time was 74 ms and then it took 21.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster. Unfortunately, there was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

flowerbowl.com performance score

25

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.1 s

81/100

10%

LCP (Largest Contentful Paint)

Value12.8 s

0/100

25%

SI (Speed Index)

Value9.5 s

12/100

10%

TBT (Total Blocking Time)

Value4,080 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value18.7 s

3/100

10%

Network Requests Diagram

www.flowerbowl.com

74 ms

originTrials.41d7301a.bundle.min.js

43 ms

minified.js

51 ms

focus-within-polyfill.js

43 ms

polyfill.min.js

20440 ms

Our browser made a total of 57 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Flowerbowl.com, 37% (21 requests) were made to Static.parastorage.com and 37% (21 requests) were made to Static.wixstatic.com. The less responsive or slowest element that took the longest time to load (20.4 sec) relates to the external source Polyfill.io.

Page Optimization Overview & Recommendations

Page size can be reduced by 598.2 kB (54%)

Content Size

1.1 MB

After Optimization

501.8 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Flowerbowl.com main page is 1.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. 50% of websites need less resources to load. HTML takes 696.3 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 586.3 kB

  • Original 696.3 kB
  • After minification 694.7 kB
  • After compression 110.0 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 586.3 kB or 84% of the original size.

Image Optimization

-6%

Potential reduce by 11.0 kB

  • Original 194.2 kB
  • After minification 183.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. Flower Bowl images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 807 B

  • Original 209.5 kB
  • After minification 209.4 kB
  • After compression 208.7 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.

Requests Breakdown

Number of requests can be reduced by 10 (30%)

Requests Now

33

After Optimization

23

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.flowerbowl.com

www.flowerbowl.com

74 ms

originTrials.41d7301a.bundle.min.js

originTrials.41d7301a.bundle.min.js

43 ms

minified.js

minified.js

51 ms

focus-within-polyfill.js

focus-within-polyfill.js

43 ms

polyfill.min.js

polyfill.min.js

20440 ms

thunderbolt-commons.7c91a755.bundle.min.js

thunderbolt-commons.7c91a755.bundle.min.js

31 ms

main.8534eeb3.bundle.min.js

main.8534eeb3.bundle.min.js

27 ms

lodash.min.js

lodash.min.js

28 ms

react.production.min.js

react.production.min.js

25 ms

react-dom.production.min.js

react-dom.production.min.js

30 ms

siteTags.bundle.min.js

siteTags.bundle.min.js

29 ms

wix-perf-measure.umd.min.js

wix-perf-measure.umd.min.js

30 ms

061324_ff1344fd5b9644d5a8f89c560f7c0fc3~mv2.png

061324_ff1344fd5b9644d5a8f89c560f7c0fc3~mv2.png

206 ms

6956e6_fb439cadc0594b229c5bba49fe4cb832~mv2.png

6956e6_fb439cadc0594b229c5bba49fe4cb832~mv2.png

342 ms

6956e6_4dccf1b2338a45f5827964243df821b2~mv2.png

6956e6_4dccf1b2338a45f5827964243df821b2~mv2.png

393 ms

6956e6_288685be594f42ee9058c48f82582849~mv2.png

6956e6_288685be594f42ee9058c48f82582849~mv2.png

437 ms

6956e6_a081635fe6844cceaaf7b037807d3c4d~mv2.png

6956e6_a081635fe6844cceaaf7b037807d3c4d~mv2.png

402 ms

6956e6_9caed48b6fd049538a28a321242e7d6e~mv2.png

6956e6_9caed48b6fd049538a28a321242e7d6e~mv2.png

408 ms

6956e6_b7f6073327bd409a8ccf825188c5816d~mv2.png

6956e6_b7f6073327bd409a8ccf825188c5816d~mv2.png

396 ms

6956e6_f98be9ec7a5e4fe4ab092a9a2d244615~mv2.png

6956e6_f98be9ec7a5e4fe4ab092a9a2d244615~mv2.png

472 ms

1C1A9945.jpg

1C1A9945.jpg

541 ms

store.jpg

store.jpg

545 ms

store.jpg

store.jpg

485 ms

store.jpg

store.jpg

590 ms

store.jpg

store.jpg

630 ms

store.jpg

store.jpg

602 ms

1C1A9945.jpg

1C1A9945.jpg

730 ms

mockup-of-a-young-man-holding-an-iphone-11-pro-2130-el1%20(5).png

mockup-of-a-young-man-holding-an-iphone-11-pro-2130-el1%20(5).png

772 ms

Mountains.jpg

Mountains.jpg

828 ms

tfblogo.png

tfblogo.png

730 ms

bundle.min.js

bundle.min.js

206 ms

file.woff

file.woff

499 ms

03805817-4611-4dbc-8c65-0f73031c3973.woff

03805817-4611-4dbc-8c65-0f73031c3973.woff

61 ms

80c34ad2-27c2-4d99-90fa-985fd64ab81a.woff

80c34ad2-27c2-4d99-90fa-985fd64ab81a.woff

61 ms

4021a3b9-f782-438b-aeb4-c008109a8b64.woff

4021a3b9-f782-438b-aeb4-c008109a8b64.woff

29 ms

c5749443-93da-4592-b794-42f28d62ef72.woff

c5749443-93da-4592-b794-42f28d62ef72.woff

60 ms

192dac76-a6d9-413d-bb74-22308f2e0cc5.woff

192dac76-a6d9-413d-bb74-22308f2e0cc5.woff

60 ms

0a3939d0-3833-4db3-8b85-f64c2b3350d2.woff

0a3939d0-3833-4db3-8b85-f64c2b3350d2.woff

60 ms

file.woff

file.woff

402 ms

STBOO2waD2LpX45SXYjQBRsxEYwM7FgeyaSgU71cLG0.woff

STBOO2waD2LpX45SXYjQBRsxEYwM7FgeyaSgU71cLG0.woff

62 ms

WmVKXVcOuffP_qmCpFuyzRsxEYwM7FgeyaSgU71cLG0.woff

WmVKXVcOuffP_qmCpFuyzRsxEYwM7FgeyaSgU71cLG0.woff

61 ms

file.woff

file.woff

443 ms

46 ms

8 ms

9 ms

11 ms

9 ms

11 ms

50 ms

50 ms

49 ms

57 ms

52 ms

deprecation-en.v5.html

deprecation-en.v5.html

10 ms

bolt-performance

bolt-performance

20 ms

deprecation-style.v5.css

deprecation-style.v5.css

7 ms

right-arrow.svg

right-arrow.svg

4 ms

Accessibility Review

flowerbowl.com accessibility score

93

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

button, link, and menuitem elements do not have accessible names.

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.

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

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

High

Page has valid source maps

SEO Factors

flowerbowl.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 Flowerbowl.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 Flowerbowl.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

flowerbowl.com

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