Tools & Wizards About Us
dutchflowers.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

dutchflowers.com

Page Load Speed

1.4 sec in total

First Response

101 ms

Resources Loaded

1.1 sec

Page Rendered

154 ms

dutchflowers.com screenshot

About Website

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

Visit dutchflowers.com

Key Findings

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

Performance Metrics

dutchflowers.com performance score

0

Network Requests Diagram

dutchflowers.com

101 ms

www.dutchflowers.com

47 ms

bt

79 ms

require.min.js

56 ms

main-r.min.js

60 ms

Our browser made a total of 59 requests to load all elements on the main page. We found that 5% of them (3 requests) were addressed to the original Dutchflowers.com, 63% (37 requests) were made to Static.parastorage.com and 14% (8 requests) were made to Frog.wix.com. The less responsive or slowest element that took the longest time to load (414 ms) relates to the external source Static.wixstatic.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 2.3 MB (77%)

Content Size

3.0 MB

After Optimization

695.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Dutchflowers.com main page is 3.0 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. 80% 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. Javascripts take 2.9 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 52.4 kB

  • Original 64.9 kB
  • After minification 64.7 kB
  • After compression 12.5 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 52.4 kB or 81% of the original size.

Image Optimization

-44%

Potential reduce by 236 B

  • Original 540 B
  • After minification 304 B

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. Obviously, Dutchflowers needs image optimization as it can save up to 236 B or 44% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-76%

Potential reduce by 2.2 MB

  • Original 2.9 MB
  • After minification 2.8 MB
  • After compression 672.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 2.2 MB or 76% of the original size.

CSS Optimization

-84%

Potential reduce by 51.7 kB

  • Original 61.7 kB
  • After minification 58.0 kB
  • After compression 10.0 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. Dutchflowers.com needs all CSS files to be minified and compressed as it can save up to 51.7 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 48 (86%)

Requests Now

56

After Optimization

8

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

dutchflowers.com

dutchflowers.com

101 ms

www.dutchflowers.com

www.dutchflowers.com

47 ms

bt

bt

79 ms

require.min.js

require.min.js

56 ms

main-r.min.js

main-r.min.js

60 ms

viewer.css

viewer.css

58 ms

dynamicmodel

dynamicmodel

10 ms

d219a7_11325c5920242cbc1569310a68450ec8_58.json.z

d219a7_11325c5920242cbc1569310a68450ec8_58.json.z

410 ms

d219a7_c8d4df17672ef43c2b59672a9e113d09_60.json.z

d219a7_c8d4df17672ef43c2b59672a9e113d09_60.json.z

414 ms

ugc-viewer

ugc-viewer

38 ms

bt

bt

85 ms

skins.min.js

skins.min.js

196 ms

components.min.js

components.min.js

197 ms

utils.min.js

utils.min.js

113 ms

core.min.js

core.min.js

197 ms

react-with-addons.min.js

react-with-addons.min.js

195 ms

lodash.min.js

lodash.min.js

30 ms

TweenMax.min.js

TweenMax.min.js

43 ms

layout.min.js

layout.min.js

70 ms

tpa.min.js

tpa.min.js

72 ms

fonts.min.js

fonts.min.js

72 ms

animations.min.js

animations.min.js

108 ms

swfobject.min.js

swfobject.min.js

110 ms

mousetrap.min.js

mousetrap.min.js

108 ms

tweenEngine.min.js

tweenEngine.min.js

107 ms

DrawSVGPlugin.min.js

DrawSVGPlugin.min.js

107 ms

react-dom.min.js

react-dom.min.js

108 ms

ScrollToPlugin.min.js

ScrollToPlugin.min.js

108 ms

widgets.min.js

widgets.min.js

108 ms

experiment.js

experiment.js

108 ms

render.min.js

render.min.js

107 ms

wixappsCore.min.js

wixappsCore.min.js

107 ms

wixappsClassics.min.js

wixappsClassics.min.js

178 ms

wixappsBuilder.min.js

wixappsBuilder.min.js

177 ms

zepto.min.js

zepto.min.js

178 ms

color.min.js

color.min.js

178 ms

bt

bt

221 ms

dc.js

dc.js

191 ms

react-dom-server.min.js

react-dom-server.min.js

80 ms

latin.css

latin.css

277 ms

bt

bt

39 ms

8463f60718194af748c49dddbe45b668_svgshape.v1.HollowCircle.svg

8463f60718194af748c49dddbe45b668_svgshape.v1.HollowCircle.svg

6 ms

6b1da864ef84b466c566b1aac7ed2e1e_svgshape.v1.Triangle.svg

6b1da864ef84b466c566b1aac7ed2e1e_svgshape.v1.Triangle.svg

8 ms

bt

bt

195 ms

css

css

128 ms

Carousel.html

Carousel.html

130 ms

Carousel.html

Carousel.html

130 ms

__utm.gif

__utm.gif

79 ms

11062b_240ceadfce144953be3b55434db78e92f000.jpg

11062b_240ceadfce144953be3b55434db78e92f000.jpg

22 ms

bt

bt

38 ms

bt

bt

38 ms

Wix.js

Wix.js

60 ms

jquery.min.js

jquery.min.js

89 ms

jquery.hammer-1.0.5.min.js

jquery.hammer-1.0.5.min.js

11 ms

jquery.mousewheel.js

jquery.mousewheel.js

10 ms

cloud-carousel.1.0.5.js

cloud-carousel.1.0.5.js

12 ms

ga-audiences

ga-audiences

35 ms

ga.js

ga.js

92 ms

cyrillic.css

cyrillic.css

61 ms

SEO Factors

dutchflowers.com SEO score

0

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Dutchflowers.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Dutchflowers.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

dutchflowers.com

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