Tools & Wizards About Us
floristexchange.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

floristexchange.com

Florist Exchange | International Florist Directory | Find a Florist Worldwide | Listing Local Florists Worldwide

Page Load Speed

2.5 sec in total

First Response

364 ms

Resources Loaded

1.5 sec

Page Rendered

653 ms

floristexchange.com screenshot

About Website

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

Connect with trusted local florists worldwide and send flowers direct with our leading international directory of florists.

Visit floristexchange.com

Key Findings

We analyzed Floristexchange.com page load time and found that the first response time was 364 ms and then it took 2.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.

Performance Metrics

floristexchange.com performance score

0

Network Requests Diagram

floristexchange.com

364 ms

floristexchange.com

390 ms

fx.css

92 ms

common.js

179 ms

fx_index.css

264 ms

Our browser made a total of 21 requests to load all elements on the main page. We found that 90% of them (19 requests) were addressed to the original Floristexchange.com, 10% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (390 ms) belongs to the original domain Floristexchange.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 17.3 kB (21%)

Content Size

80.9 kB

After Optimization

63.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Floristexchange.com main page is 80.9 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. 15% of websites need less resources to load. Images take 41.3 kB which makes up the majority of the site volume.

HTML Optimization

-68%

Potential reduce by 8.8 kB

  • Original 12.9 kB
  • After minification 11.5 kB
  • After compression 4.1 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 1.4 kB, which is 11% 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 8.8 kB or 68% of the original size.

Image Optimization

-10%

Potential reduce by 4.2 kB

  • Original 41.3 kB
  • After minification 37.1 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. Florist Exchange images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 50 B

  • Original 21.0 kB
  • After minification 21.0 kB
  • After compression 20.9 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

-74%

Potential reduce by 4.3 kB

  • Original 5.8 kB
  • After minification 5.0 kB
  • After compression 1.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. Floristexchange.com needs all CSS files to be minified and compressed as it can save up to 4.3 kB or 74% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

19

After Optimization

19

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 19 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Florist Exchange. According to our analytics all requests are already optimized.

Network Requests Diagram

floristexchange.com

floristexchange.com

364 ms

floristexchange.com

floristexchange.com

390 ms

fx.css

fx.css

92 ms

common.js

common.js

179 ms

fx_index.css

fx_index.css

264 ms

index.js

index.js

292 ms

fx_logo.gif

fx_logo.gif

162 ms

arc2.png

arc2.png

197 ms

but1.gif

but1.gif

139 ms

but2.gif

but2.gif

139 ms

but3.gif

but3.gif

175 ms

but4.gif

but4.gif

186 ms

tick.gif

tick.gif

186 ms

app_store_android_logo_inv.png

app_store_android_logo_inv.png

301 ms

app_store_logo_inv.gif

app_store_logo_inv.gif

299 ms

instagram.png

instagram.png

302 ms

facebook.png

facebook.png

293 ms

twitter.png

twitter.png

300 ms

analytics.js

analytics.js

67 ms

collect

collect

42 ms

fx_print.css

fx_print.css

89 ms

SEO Factors

floristexchange.com SEO score

0

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Floristexchange.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 Floristexchange.com main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

floristexchange.com

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