Tools & Wizards About Us
floratech.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

floratech.com

Floratech | Cosmetic Ingredients, Natural, Biodegradable, Jojoba, Botanical, Sustainable, Stable, Oil-Free, Emollients, Scrubbing Beads

Page Load Speed

3.5 sec in total

First Response

1.5 sec

Resources Loaded

1.9 sec

Page Rendered

88 ms

floratech.com screenshot

About Website

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

Floratech is a premier provider of botanically-derived ingredients to formulators worldwide. Our oils, emollients, and specialty particles are key components in the skin/lip/nail/hair care, color cosm...

Visit floratech.com

Key Findings

We analyzed Floratech.com page load time and found that the first response time was 1.5 sec and then it took 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

floratech.com performance score

0

Network Requests Diagram

floratech.com

1475 ms

floratech.com

140 ms

Cargill.aspx

63 ms

main.css

29 ms

tooltip.css

26 ms

Our browser made a total of 35 requests to load all elements on the main page. We found that 94% of them (33 requests) were addressed to the original Floratech.com, 6% (2 requests) were made to Ssl.google-analytics.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Floratech.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 11.7 kB (36%)

Content Size

32.2 kB

After Optimization

20.5 kB

  • HTML
  • JavaScript

In fact, the total size of Floratech.com main page is 32.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. 30% of websites need less resources to load. Javascripts take 17.2 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 11.6 kB

  • Original 15.0 kB
  • After minification 10.5 kB
  • After compression 3.4 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 4.5 kB, which is 30% 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 11.6 kB or 77% of the original size.

JavaScript Optimization

-0%

Potential reduce by 34 B

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

Requests Breakdown

Number of requests can be reduced by 7 (25%)

Requests Now

28

After Optimization

21

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

floratech.com

floratech.com

1475 ms

floratech.com

floratech.com

140 ms

Cargill.aspx

Cargill.aspx

63 ms

main.css

main.css

29 ms

tooltip.css

tooltip.css

26 ms

tooltip2.css

tooltip2.css

27 ms

browsercheck.js

browsercheck.js

17 ms

nav.js

nav.js

17 ms

mootools.js

mootools.js

54 ms

moodalbox.js

moodalbox.js

44 ms

jquery-1.10.2.js

jquery-1.10.2.js

125 ms

moodalbox.css

moodalbox.css

28 ms

WebResource.axd

WebResource.axd

30 ms

404.aspx

404.aspx

27 ms

404.aspx

404.aspx

25 ms

404.aspx

404.aspx

43 ms

404.aspx

404.aspx

41 ms

ga.js

ga.js

23 ms

logo.png

logo.png

6 ms

masthead-about.jpg

masthead-about.jpg

62 ms

search.png

search.png

63 ms

nav-a.gif

nav-a.gif

63 ms

nav-b.gif

nav-b.gif

61 ms

nav-c.gif

nav-c.gif

62 ms

nav-d.gif

nav-d.gif

62 ms

nav-e.gif

nav-e.gif

63 ms

nav-f.gif

nav-f.gif

63 ms

About_Botanicals.png

About_Botanicals.png

66 ms

Cargill_Beauty_logo_CMJN_200x161px.png

Cargill_Beauty_logo_CMJN_200x161px.png

69 ms

Brochures_Download_smaller.jpg

Brochures_Download_smaller.jpg

64 ms

ilabel-footer.png

ilabel-footer.png

65 ms

footer-dot.gif

footer-dot.gif

64 ms

nav-on.gif

nav-on.gif

6 ms

beadbar_footer.jpg

beadbar_footer.jpg

6 ms

__utm.gif

__utm.gif

12 ms

SEO Factors

floratech.com SEO score

0

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Floratech.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Floratech.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

floratech.com

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