Tools & Wizards About Us
fluresh.com screenshot

Report Summary

  • 4

    Performance

    Renders faster than
    20% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 68% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

fluresh.com

Fluresh Cannabis Retail

Page Load Speed

13.6 sec in total

First Response

283 ms

Resources Loaded

3.4 sec

Page Rendered

9.8 sec

fluresh.com screenshot

About Website

Click here to check amazing Fluresh content for United States. Otherwise, check out these important facts you probably never knew about fluresh.com

Visit fluresh.com

Key Findings

We analyzed Fluresh.com page load time and found that the first response time was 283 ms and then it took 13.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

fluresh.com performance score

4

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.8 s

28/100

10%

LCP (Largest Contentful Paint)

Value7.4 s

4/100

25%

SI (Speed Index)

Value23.6 s

0/100

10%

TBT (Total Blocking Time)

Value24,920 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value1.103

1/100

15%

TTI (Time to Interactive)

Value38.3 s

0/100

10%

Network Requests Diagram

fluresh.com

283 ms

frontend.css

144 ms

style.min.css

278 ms

theme.min.css

272 ms

header-footer.min.css

272 ms

Our browser made a total of 60 requests to load all elements on the main page. We found that 75% of them (45 requests) were addressed to the original Fluresh.com, 15% (9 requests) were made to Fonts.gstatic.com and 2% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1 sec) belongs to the original domain Fluresh.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 112.1 kB (13%)

Content Size

857.5 kB

After Optimization

745.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Fluresh.com main page is 857.5 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 70% of websites need less resources to load. Javascripts take 376.3 kB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 95.7 kB

  • Original 113.0 kB
  • After minification 109.8 kB
  • After compression 17.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. 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 95.7 kB or 85% of the original size.

Image Optimization

-2%

Potential reduce by 6.4 kB

  • Original 307.2 kB
  • After minification 300.8 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. Fluresh images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 3.8 kB

  • Original 376.3 kB
  • After minification 376.3 kB
  • After compression 372.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. This website has mostly compressed JavaScripts.

CSS Optimization

-10%

Potential reduce by 6.2 kB

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

Requests Breakdown

Number of requests can be reduced by 41 (85%)

Requests Now

48

After Optimization

7

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

fluresh.com

fluresh.com

283 ms

frontend.css

frontend.css

144 ms

style.min.css

style.min.css

278 ms

theme.min.css

theme.min.css

272 ms

header-footer.min.css

header-footer.min.css

272 ms

frontend.min.css

frontend.min.css

272 ms

post-5.css

post-5.css

271 ms

elementor-icons.min.css

elementor-icons.min.css

276 ms

swiper.min.css

swiper.min.css

313 ms

e-swiper.min.css

e-swiper.min.css

324 ms

frontend.min.css

frontend.min.css

322 ms

post-6665.css

post-6665.css

308 ms

post-6674.css

post-6674.css

336 ms

post-5592.css

post-5592.css

317 ms

post-6252.css

post-6252.css

355 ms

css

css

261 ms

fontawesome.min.css

fontawesome.min.css

354 ms

solid.min.css

solid.min.css

396 ms

jquery.min.js

jquery.min.js

507 ms

jquery-migrate.min.js

jquery-migrate.min.js

497 ms

js

js

934 ms

platform.js

platform.js

877 ms

widget-image.min.css

widget-image.min.css

427 ms

widget-nav-menu.min.css

widget-nav-menu.min.css

862 ms

widget-heading.min.css

widget-heading.min.css

863 ms

widget-text-editor.min.css

widget-text-editor.min.css

896 ms

widget-forms.min.css

widget-forms.min.css

894 ms

fadeIn.min.css

fadeIn.min.css

895 ms

hello-frontend.min.js

hello-frontend.min.js

896 ms

api.js

api.js

264 ms

smush-lazy-load.min.js

smush-lazy-load.min.js

1018 ms

jquery.smartmenus.min.js

jquery.smartmenus.min.js

1018 ms

webpack-pro.runtime.min.js

webpack-pro.runtime.min.js

1015 ms

webpack.runtime.min.js

webpack.runtime.min.js

991 ms

frontend-modules.min.js

frontend-modules.min.js

988 ms

hooks.min.js

hooks.min.js

1000 ms

i18n.min.js

i18n.min.js

1003 ms

frontend.min.js

frontend.min.js

995 ms

core.min.js

core.min.js

1001 ms

frontend.min.js

frontend.min.js

1003 ms

elements-handlers.min.js

elements-handlers.min.js

1001 ms

waypoints.js

waypoints.js

980 ms

jet-elements.min.js

jet-elements.min.js

873 ms

IMG_0852-scaled-e1689273007560.jpg

IMG_0852-scaled-e1689273007560.jpg

286 ms

2020-06_Fluresh_0109-scaled-e1689261122865-1024x1024.jpg

2020-06_Fluresh_0109-scaled-e1689261122865-1024x1024.jpg

249 ms

footer-pattern2.png

footer-pattern2.png

234 ms

secondary-brand-pattern-1-grey-tile.jpeg

secondary-brand-pattern-1-grey-tile.jpeg

243 ms

platform.js

platform.js

543 ms

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K0nXBi8JoA.woff

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K0nXBi8JoA.woff

830 ms

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K3vXBi8JoA.woff

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K3vXBi8JoA.woff

752 ms

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32KxfXBi8JoA.woff

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32KxfXBi8JoA.woff

835 ms

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K8nXBi8JoA.woff

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K8nXBi8JoA.woff

828 ms

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K0nWBi8JoA.woff

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K0nWBi8JoA.woff

820 ms

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K5fQBi8JoA.woff

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K5fQBi8JoA.woff

825 ms

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K67QBi8JoA.woff

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K67QBi8JoA.woff

838 ms

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K8nQBi8JoA.woff

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K8nQBi8JoA.woff

837 ms

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K-DQBi8JoA.woff

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K-DQBi8JoA.woff

832 ms

eicons.woff

eicons.woff

502 ms

recaptcha__en.js

recaptcha__en.js

676 ms

Color-logo.svg

Color-logo.svg

344 ms

Accessibility Review

fluresh.com accessibility score

88

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.

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

ARIA IDs are not unique

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

Low

No form fields have multiple labels

High

Links do not have a discernible name

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

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

Missing source maps for large first-party JavaScript

SEO Factors

fluresh.com SEO score

93

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

fluresh.com

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