Tools & Wizards About Us
flowerone.com screenshot

Report Summary

  • 46

    Performance

    Renders faster than
    64% of other websites

  • 77

    Accessibility

    Visual factors better than
    that of 44% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 84

    SEO

    Google-friendlier than
    52% of websites

flowerone.com

Leading Cannabis Grower, Supplier & Innovator | Flower One

Page Load Speed

1.7 sec in total

First Response

87 ms

Resources Loaded

1.1 sec

Page Rendered

513 ms

flowerone.com screenshot

About Website

Click here to check amazing Flower One content. Otherwise, check out these important facts you probably never knew about flowerone.com

Experienced cannabis cultivator, producer, and innovator with the largest cannabis manufacturing facility in Nevada. Work with us today.

Visit flowerone.com

Key Findings

We analyzed Flowerone.com page load time and found that the first response time was 87 ms and then it took 1.6 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

flowerone.com performance score

46

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

45/100

10%

LCP (Largest Contentful Paint)

Value22.2 s

0/100

25%

SI (Speed Index)

Value8.0 s

22/100

10%

TBT (Total Blocking Time)

Value310 ms

78/100

30%

CLS (Cumulative Layout Shift)

Value0.018

100/100

15%

TTI (Time to Interactive)

Value14.7 s

8/100

10%

Network Requests Diagram

flowerone.com

87 ms

flowerone.com

131 ms

js

67 ms

style.min.css

23 ms

styles.css

43 ms

Our browser made a total of 41 requests to load all elements on the main page. We found that 59% of them (24 requests) were addressed to the original Flowerone.com, 10% (4 requests) were made to Use.typekit.net and 7% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (475 ms) relates to the external source I.vimeocdn.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 333.0 kB (11%)

Content Size

3.0 MB

After Optimization

2.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Flowerone.com main page is 3.0 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. 40% of websites need less resources to load. Images take 2.6 MB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 42.0 kB

  • Original 53.3 kB
  • After minification 47.0 kB
  • After compression 11.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. This page needs HTML code to be minified as it can gain 6.4 kB, which is 12% 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 42.0 kB or 79% of the original size.

Image Optimization

-7%

Potential reduce by 188.6 kB

  • Original 2.6 MB
  • After minification 2.5 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. Flower One images are well optimized though.

JavaScript Optimization

-43%

Potential reduce by 97.5 kB

  • Original 226.6 kB
  • After minification 222.1 kB
  • After compression 129.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 97.5 kB or 43% of the original size.

CSS Optimization

-8%

Potential reduce by 4.9 kB

  • Original 63.9 kB
  • After minification 62.6 kB
  • After compression 59.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. Flowerone.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 21 (58%)

Requests Now

36

After Optimization

15

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

flowerone.com

flowerone.com

87 ms

flowerone.com

flowerone.com

131 ms

js

js

67 ms

style.min.css

style.min.css

23 ms

styles.css

styles.css

43 ms

style.css

style.css

42 ms

bootstrap-reboot.min.css

bootstrap-reboot.min.css

35 ms

bootstrap.min.css

bootstrap.min.css

36 ms

style.css

style.css

48 ms

page-style.css

page-style.css

49 ms

northern-styles.css

northern-styles.css

55 ms

all.css

all.css

172 ms

pow5cgc.css

pow5cgc.css

207 ms

frontend-gtag.min.js

frontend-gtag.min.js

52 ms

jquery.min.js

jquery.min.js

52 ms

jquery-migrate.min.js

jquery-migrate.min.js

50 ms

player.js

player.js

82 ms

classic-10_7.css

classic-10_7.css

50 ms

mc-validate.js

mc-validate.js

82 ms

index.js

index.js

57 ms

index.js

index.js

59 ms

bootstrap.min.js

bootstrap.min.js

60 ms

scripts.js

scripts.js

58 ms

analytics.js

analytics.js

20 ms

collect

collect

12 ms

collect

collect

25 ms

p.css

p.css

24 ms

collect

collect

49 ms

logo.svg

logo.svg

49 ms

341440505

341440505

112 ms

hero_image@2x.jpg

hero_image@2x.jpg

385 ms

pin-white.png

pin-white.png

51 ms

flowerone-logo.png

flowerone-logo.png

49 ms

linkedin.png

linkedin.png

225 ms

twitter.png

twitter.png

50 ms

close.svg

close.svg

51 ms

790053369-1b77fca33adcb859d920dd62479b932444c649229b7c6d4f4f22f7657ae95664-d

790053369-1b77fca33adcb859d920dd62479b932444c649229b7c6d4f4f22f7657ae95664-d

475 ms

d

d

64 ms

d

d

76 ms

d

d

90 ms

FONE.json

FONE.json

165 ms

Accessibility Review

flowerone.com accessibility score

77

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

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

Best Practices

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

High

Page has valid source maps

SEO Factors

flowerone.com SEO score

84

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

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

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Flowerone.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 Flowerone.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

flowerone.com

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