Tools & Wizards About Us
floralfrog.com screenshot

Report Summary

  • 68

    Performance

    Renders faster than
    80% of other websites

  • 98

    Accessibility

    Visual factors better than
    that of 94% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

floralfrog.com

Request Rejected

Page Load Speed

4.1 sec in total

First Response

595 ms

Resources Loaded

2.8 sec

Page Rendered

675 ms

floralfrog.com screenshot

About Website

Click here to check amazing Floralfrog content. Otherwise, check out these important facts you probably never knew about floralfrog.com

Floral Frog Software was born out of the necessity for an easy to use software that could tie in all the aspects of running a florist.

Visit floralfrog.com

Key Findings

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

Performance Metrics

floralfrog.com performance score

68

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.6 s

32/100

10%

LCP (Largest Contentful Paint)

Value5.5 s

19/100

25%

SI (Speed Index)

Value4.3 s

76/100

10%

TBT (Total Blocking Time)

Value50 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.009

100/100

15%

TTI (Time to Interactive)

Value5.5 s

70/100

10%

Network Requests Diagram

floralfrog.co.uk

595 ms

global.css

115 ms

frontend.css

235 ms

styles.css

288 ms

header-footer-elementor.css

293 ms

Our browser made a total of 71 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Floralfrog.com, 3% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Floralfrog.co.uk.

Page Optimization Overview & Recommendations

Page size can be reduced by 275.8 kB (14%)

Content Size

1.9 MB

After Optimization

1.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-85%

Potential reduce by 108.1 kB

  • Original 127.4 kB
  • After minification 123.3 kB
  • After compression 19.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 108.1 kB or 85% of the original size.

Image Optimization

-8%

Potential reduce by 134.5 kB

  • Original 1.6 MB
  • After minification 1.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. Floralfrog images are well optimized though.

JavaScript Optimization

-12%

Potential reduce by 14.4 kB

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

CSS Optimization

-21%

Potential reduce by 18.6 kB

  • Original 90.3 kB
  • After minification 90.3 kB
  • After compression 71.7 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. Floralfrog.com needs all CSS files to be minified and compressed as it can save up to 18.6 kB or 21% of the original size.

Requests Breakdown

Number of requests can be reduced by 39 (56%)

Requests Now

70

After Optimization

31

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

floralfrog.co.uk

floralfrog.co.uk

595 ms

global.css

global.css

115 ms

frontend.css

frontend.css

235 ms

styles.css

styles.css

288 ms

header-footer-elementor.css

header-footer-elementor.css

293 ms

elementor-icons.min.css

elementor-icons.min.css

308 ms

frontend.min.css

frontend.min.css

358 ms

swiper.min.css

swiper.min.css

389 ms

e-swiper.min.css

e-swiper.min.css

391 ms

post-6.css

post-6.css

394 ms

animations.min.css

animations.min.css

393 ms

post-7.css

post-7.css

416 ms

widget-icon-list.min.css

widget-icon-list.min.css

465 ms

widget-social-icons.min.css

widget-social-icons.min.css

490 ms

brands.css

brands.css

494 ms

fontawesome.css

fontawesome.css

526 ms

solid.css

solid.css

493 ms

css2

css2

59 ms

main.min.css

main.min.css

575 ms

page-title.min.css

page-title.min.css

569 ms

elementor-frontend.min.css

elementor-frontend.min.css

596 ms

cf-7.min.css

cf-7.min.css

599 ms

general.min.css

general.min.css

598 ms

css

css

78 ms

jquery.min.js

jquery.min.js

718 ms

jquery-migrate.min.js

jquery-migrate.min.js

683 ms

widget-heading.min.css

widget-heading.min.css

681 ms

widget-text-editor.min.css

widget-text-editor.min.css

694 ms

widget-spacer.min.css

widget-spacer.min.css

705 ms

widget-image.min.css

widget-image.min.css

707 ms

widget-divider.min.css

widget-divider.min.css

793 ms

hooks.min.js

hooks.min.js

787 ms

i18n.min.js

i18n.min.js

807 ms

index.js

index.js

808 ms

index.js

index.js

813 ms

main.js

main.js

841 ms

main.js

main.js

892 ms

general.min.js

general.min.js

900 ms

webpack.runtime.min.js

webpack.runtime.min.js

898 ms

frontend-modules.min.js

frontend-modules.min.js

839 ms

core.min.js

core.min.js

694 ms

frontend.min.js

frontend.min.js

688 ms

Floral-Frog-1.png

Floral-Frog-1.png

294 ms

pexels-andrea-piacquadio-3932732.jpg

pexels-andrea-piacquadio-3932732.jpg

508 ms

344a27.webp

344a27.webp

608 ms

Frog_Payments.jpg

Frog_Payments.jpg

615 ms

mac-menu.webp

mac-menu.webp

558 ms

icon-6.png

icon-6.png

338 ms

icon-10.png

icon-10.png

420 ms

icon-8.png

icon-8.png

452 ms

icon-1.png

icon-1.png

554 ms

icon-2.png

icon-2.png

573 ms

icon-4.png

icon-4.png

617 ms

icon-5.png

icon-5.png

680 ms

icon-11.png

icon-11.png

667 ms

icon-9.png

icon-9.png

701 ms

icon-7.png

icon-7.png

721 ms

icon-12.png

icon-12.png

729 ms

icon-3.png

icon-3.png

733 ms

pexels-amina-filkins-5413725.jpg

pexels-amina-filkins-5413725.jpg

900 ms

Direct2Florist-transparent-logo-web-only.png

Direct2Florist-transparent-logo-web-only.png

807 ms

i8.png

i8.png

812 ms

i4.png

i4.png

839 ms

2560px-Stripe_Logo_revised_2016.svg.png

2560px-Stripe_Logo_revised_2016.svg.png

858 ms

woo-commerce-1024x260.png

woo-commerce-1024x260.png

952 ms

flowerstoreinabox-1024x276.png

flowerstoreinabox-1024x276.png

1113 ms

floristWindowLogo-dark.png

floristWindowLogo-dark.png

1049 ms

FP-Logo-Grey.png

FP-Logo-Grey.png

969 ms

Sumup_logo.svg.png

Sumup_logo.svg.png

911 ms

squarespace-logo-horizontal-black.jpg

squarespace-logo-horizontal-black.jpg

944 ms

pexels-amina-filkins-5410084.jpg

pexels-amina-filkins-5410084.jpg

1123 ms

Accessibility Review

floralfrog.com accessibility score

98

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.

Best Practices

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

SEO Factors

floralfrog.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 Floralfrog.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 Floralfrog.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

floralfrog.com

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