Tools & Wizards About Us
floristware.com screenshot

Report Summary

  • 26

    Performance

    Renders faster than
    45% of other websites

  • 94

    Accessibility

    Visual factors better than
    that of 83% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

floristware.com

The Ideal POS/Shop Management System For Retail Florists

Page Load Speed

2.8 sec in total

First Response

98 ms

Resources Loaded

1.8 sec

Page Rendered

943 ms

floristware.com screenshot

About Website

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

A powerful, affordable & easy-to-use POS/Shop Management System that saves retail florists time & money while increasing sales & profits.

Visit floristware.com

Key Findings

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

Performance Metrics

floristware.com performance score

26

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.5 s

35/100

10%

LCP (Largest Contentful Paint)

Value6.7 s

7/100

25%

SI (Speed Index)

Value12.0 s

4/100

10%

TBT (Total Blocking Time)

Value600 ms

49/100

30%

CLS (Cumulative Layout Shift)

Value0.396

26/100

15%

TTI (Time to Interactive)

Value11.3 s

19/100

10%

Network Requests Diagram

floristware.com

98 ms

floristware.com

170 ms

www.floristware.com

622 ms

css2

40 ms

bootstrap.css

23 ms

Our browser made a total of 62 requests to load all elements on the main page. We found that 68% of them (42 requests) were addressed to the original Floristware.com, 19% (12 requests) were made to Fonts.gstatic.com and 3% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (622 ms) belongs to the original domain Floristware.com.

Page Optimization Overview & Recommendations

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

Content Size

979.2 kB

After Optimization

868.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Floristware.com main page is 979.2 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. 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 621.3 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 109.1 kB

  • Original 133.7 kB
  • After minification 133.7 kB
  • After compression 24.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. 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 109.1 kB or 82% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 621.3 kB
  • After minification 621.3 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. Floristware images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 41 B

  • Original 148.7 kB
  • After minification 148.7 kB
  • After compression 148.6 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

-3%

Potential reduce by 2.0 kB

  • Original 75.5 kB
  • After minification 73.5 kB
  • After compression 73.5 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. Floristware.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 20 (43%)

Requests Now

46

After Optimization

26

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

floristware.com

floristware.com

98 ms

floristware.com

floristware.com

170 ms

www.floristware.com

www.floristware.com

622 ms

css2

css2

40 ms

bootstrap.css

bootstrap.css

23 ms

style.css

style.css

49 ms

font-awesome.css

font-awesome.css

68 ms

jquery.js

jquery.js

48 ms

467b9e7d3db26fb6e337529cfa7d173b5f45ba8c.css

467b9e7d3db26fb6e337529cfa7d173b5f45ba8c.css

34 ms

js

js

389 ms

email-decode.min.js

email-decode.min.js

29 ms

plugins.js

plugins.js

64 ms

functions.js

functions.js

65 ms

load.js

load.js

65 ms

9772216c75e6c44d1fa650f3222fea25af96cd35.js

9772216c75e6c44d1fa650f3222fea25af96cd35.js

63 ms

radio-checkbox.css

radio-checkbox.css

22 ms

animate.css

animate.css

22 ms

magnific-popup.css

magnific-popup.css

19 ms

swiper.css

swiper.css

20 ms

gtm.js

gtm.js

241 ms

floristware_website_wordmark_lite_back-100pxH.png

floristware_website_wordmark_lite_back-100pxH.png

36 ms

floristware_website_wordmark_lite_back-200pxH.png

floristware_website_wordmark_lite_back-200pxH.png

150 ms

pattern2.png

pattern2.png

154 ms

periwinkle-flowers-jess-floristware-client-02.jpg

periwinkle-flowers-jess-floristware-client-02.jpg

36 ms

floristware_green_card_large.png

floristware_green_card_large.png

152 ms

iconalt.svg

iconalt.svg

37 ms

florist-frustrated-by-wire-service-statement_550x367.jpg

florist-frustrated-by-wire-service-statement_550x367.jpg

151 ms

florist-frustrated-by-overseas-phone-support_550x367.jpg

florist-frustrated-by-overseas-phone-support_550x367.jpg

150 ms

florist-optimistic-about-the-future_550x367.jpg

florist-optimistic-about-the-future_550x367.jpg

151 ms

cross-platform-compatible-pos-for-florists-550-300.png

cross-platform-compatible-pos-for-florists-550-300.png

265 ms

flower-shop-pos-credit-card-processing-550-300.png

flower-shop-pos-credit-card-processing-550-300.png

265 ms

pos-reporting-for-florists-550-300.png

pos-reporting-for-florists-550-300.png

264 ms

fsn_logo_550x300_zoom.jpg

fsn_logo_550x300_zoom.jpg

264 ms

shopify-integration-for-florists.png

shopify-integration-for-florists.png

264 ms

floralstrategies_wordmark_550x300__zoom.png

floralstrategies_wordmark_550x300__zoom.png

263 ms

mapping_feature__550x350_zoom.png

mapping_feature__550x350_zoom.png

319 ms

FloristWare_mobile_delivery_app__550x300_zoom.png

FloristWare_mobile_delivery_app__550x300_zoom.png

319 ms

clover_for_flower_shops_550x300.jpg

clover_for_flower_shops_550x300.jpg

319 ms

real-time-delivery-confirmations-for-florists_550x300.jpg

real-time-delivery-confirmations-for-florists_550x300.jpg

319 ms

gravityfree-websites-for-florists_550x300.png

gravityfree-websites-for-florists_550x300.png

319 ms

print-dialog-sample-01_550x300.jpg

print-dialog-sample-01_550x300.jpg

317 ms

floristware_website_wordmark_dark_back-footer.png

floristware_website_wordmark_dark_back-footer.png

373 ms

KFOmCnqEu92Fr1Me5g.woff

KFOmCnqEu92Fr1Me5g.woff

150 ms

KFOlCnqEu92Fr1MmEU9vAA.woff

KFOlCnqEu92Fr1MmEU9vAA.woff

263 ms

KFOlCnqEu92Fr1MmSU5vAA.woff

KFOlCnqEu92Fr1MmSU5vAA.woff

301 ms

KFOkCnqEu92Fr1MmgWxM.woff

KFOkCnqEu92Fr1MmgWxM.woff

300 ms

KFOlCnqEu92Fr1MmWUlvAA.woff

KFOlCnqEu92Fr1MmWUlvAA.woff

317 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pYCM.woff

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pYCM.woff

316 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvoooCM.woff

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvoooCM.woff

317 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaooCM.woff

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaooCM.woff

318 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVuEooCM.woff

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVuEooCM.woff

373 ms

KFOkCnqEu92Fr1Mu52xM.woff

KFOkCnqEu92Fr1Mu52xM.woff

371 ms

KFOjCnqEu92Fr1Mu51TjARc-.woff

KFOjCnqEu92Fr1Mu51TjARc-.woff

441 ms

KFOjCnqEu92Fr1Mu51TzBhc-.woff

KFOjCnqEu92Fr1Mu51TzBhc-.woff

373 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

442 ms

fbevents.js

fbevents.js

331 ms

gp

gp

401 ms

floristware_website_wordmark_dark_back-100pxH.png

floristware_website_wordmark_dark_back-100pxH.png

295 ms

floristware_website_wordmark_dark_back-200pxH.png

floristware_website_wordmark_dark_back-200pxH.png

294 ms

events.js

events.js

215 ms

QipqThPeoRsWCHVMX0TyBQ

QipqThPeoRsWCHVMX0TyBQ

229 ms

main.js

main.js

69 ms

Accessibility Review

floristware.com accessibility score

94

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.

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

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

SEO Factors

floristware.com SEO score

86

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

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

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

floristware.com

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