Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

sprue.com

The Home of Connected Fire Safety | FireAngel

Page Load Speed

9.5 sec in total

First Response

374 ms

Resources Loaded

8.8 sec

Page Rendered

326 ms

sprue.com screenshot

About Website

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

Since 1998, over 50 million devices have been installed and protection provided for 15 million homes. Find out more about FireAngel.

Visit sprue.com

Key Findings

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

Performance Metrics

sprue.com performance score

0

Network Requests Diagram

SprueSafetyProducts

374 ms

system.base.css

87 ms

field.css

172 ms

views.css

173 ms

back_to_top.css

173 ms

Our browser made a total of 114 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Sprue.com, 18% (20 requests) were made to Static.xx.fbcdn.net and 11% (13 requests) were made to Maps.google.com. The less responsive or slowest element that took the longest time to load (6.1 sec) relates to the external source Scontent.xx.fbcdn.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 766.6 kB (43%)

Content Size

1.8 MB

After Optimization

1.0 MB

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

HTML Optimization

-77%

Potential reduce by 39.5 kB

  • Original 51.0 kB
  • After minification 48.6 kB
  • After compression 11.6 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 39.5 kB or 77% of the original size.

Image Optimization

-9%

Potential reduce by 70.5 kB

  • Original 796.0 kB
  • After minification 725.6 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. Sprue images are well optimized though.

JavaScript Optimization

-67%

Potential reduce by 540.4 kB

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

CSS Optimization

-82%

Potential reduce by 116.3 kB

  • Original 141.8 kB
  • After minification 132.1 kB
  • After compression 25.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. Sprue.com needs all CSS files to be minified and compressed as it can save up to 116.3 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 62 (58%)

Requests Now

107

After Optimization

45

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

SEO Factors

sprue.com SEO score

0

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

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