Tools & Wizards About Us
fountainflair.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

fountainflair.com

Page Load Speed

2.7 sec in total

First Response

408 ms

Resources Loaded

2.1 sec

Page Rendered

267 ms

fountainflair.com screenshot

About Website

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

Decorative water garden fountains, concrete fountain, copper fountain, garden wall, interior fountains & Garden Sculpture from at FountainFlair.com

Visit fountainflair.com

Key Findings

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

Performance Metrics

fountainflair.com performance score

0

Network Requests Diagram

www.fountainflair.com

408 ms

common.css

122 ms

layout.css

186 ms

input.css

189 ms

product.css

225 ms

Our browser made a total of 70 requests to load all elements on the main page. We found that 96% of them (67 requests) were addressed to the original Fountainflair.com, 3% (2 requests) were made to Google-analytics.com and 1% (1 request) were made to Assets.pinterest.com. The less responsive or slowest element that took the longest time to load (871 ms) belongs to the original domain Fountainflair.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 447.0 kB (39%)

Content Size

1.1 MB

After Optimization

699.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-82%

Potential reduce by 36.9 kB

  • Original 44.9 kB
  • After minification 44.8 kB
  • After compression 8.0 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 36.9 kB or 82% of the original size.

Image Optimization

-17%

Potential reduce by 119.5 kB

  • Original 722.5 kB
  • After minification 602.9 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. Obviously, Fountainflair needs image optimization as it can save up to 119.5 kB or 17% 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 241.9 kB

  • Original 318.2 kB
  • After minification 247.6 kB
  • After compression 76.3 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 241.9 kB or 76% of the original size.

CSS Optimization

-79%

Potential reduce by 48.7 kB

  • Original 61.4 kB
  • After minification 54.7 kB
  • After compression 12.8 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. Fountainflair.com needs all CSS files to be minified and compressed as it can save up to 48.7 kB or 79% of the original size.

Requests Breakdown

Number of requests can be reduced by 38 (55%)

Requests Now

69

After Optimization

31

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.fountainflair.com

www.fountainflair.com

408 ms

common.css

common.css

122 ms

layout.css

layout.css

186 ms

input.css

input.css

189 ms

product.css

product.css

225 ms

site.css

site.css

126 ms

pageelements.css

pageelements.css

130 ms

preview.css

preview.css

182 ms

prototype.js

prototype.js

381 ms

effects.js

effects.js

254 ms

server.js

server.js

245 ms

bounds.js

bounds.js

249 ms

tip.js

tip.js

250 ms

touch.js

touch.js

284 ms

site.js

site.js

308 ms

stats.js

stats.js

415 ms

form.js

form.js

318 ms

productPrice.js

productPrice.js

418 ms

table.js

table.js

348 ms

action.js

action.js

370 ms

pin_it_button.png

pin_it_button.png

15 ms

top_radius.png

top_radius.png

165 ms

site_radius.png

site_radius.png

174 ms

logo.img

logo.img

153 ms

bottom_radius.png

bottom_radius.png

168 ms

pagetitle.img

pagetitle.img

90 ms

corner.img

corner.img

90 ms

tabitem.img

tabitem.img

146 ms

tabitem.img

tabitem.img

239 ms

tabitem.img

tabitem.img

312 ms

tabitem.img

tabitem.img

218 ms

tabitem.img

tabitem.img

325 ms

tabitem.img

tabitem.img

228 ms

tabitem.img

tabitem.img

230 ms

tabitem.img

tabitem.img

381 ms

tabitem.img

tabitem.img

292 ms

tabitem.img

tabitem.img

395 ms

tabitem.img

tabitem.img

403 ms

tabitem.img

tabitem.img

361 ms

tabitem.img

tabitem.img

473 ms

tabitem.img

tabitem.img

485 ms

tabitem.img

tabitem.img

425 ms

tabitem.img

tabitem.img

549 ms

heading.img

heading.img

459 ms

heading.img

heading.img

468 ms

thumbnail.img

thumbnail.img

683 ms

thumbnail.img

thumbnail.img

653 ms

thumbnail.img

thumbnail.img

668 ms

heading.img

heading.img

543 ms

thumbnail.img

thumbnail.img

610 ms

thumbnail.img

thumbnail.img

618 ms

thumbnail.img

thumbnail.img

678 ms

thumbnail.img

thumbnail.img

684 ms

thumbnail.img

thumbnail.img

747 ms

image.img

image.img

733 ms

Contact%20Us.jpg

Contact%20Us.jpg

735 ms

ga.js

ga.js

5 ms

autoresize.img

autoresize.img

871 ms

__utm.gif

__utm.gif

12 ms

image.img

image.img

665 ms

image.img

image.img

743 ms

heading.img

heading.img

757 ms

thumbnail.img

thumbnail.img

665 ms

corner.img

corner.img

758 ms

image.img

image.img

655 ms

image.img

image.img

709 ms

1458478670317

1458478670317

770 ms

siteimage.img

siteimage.img

791 ms

gradient.png

gradient.png

714 ms

email_friend_left.png

email_friend_left.png

814 ms

SEO Factors

fountainflair.com SEO score

0

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    N/A

  • Encoding

    ISO8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fountainflair.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 Fountainflair.com main page’s claimed encoding is iso8859-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

fountainflair.com

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