Tools & Wizards About Us
rusk.hotgloo.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

rusk.hotgloo.com

HotGloo | Wireframe UX Prototyping Tool

Page Load Speed

2.2 sec in total

First Response

187 ms

Resources Loaded

1.9 sec

Page Rendered

97 ms

rusk.hotgloo.com screenshot

About Website

Welcome to rusk.hotgloo.com homepage info - get ready to check Rusk Hot Gloo best content for Canada right away, or after learning these important things about rusk.hotgloo.com

HotGloo is a UX, wireframe and prototyping tool designed to build wireframes for web, mobile and wearables.

Visit rusk.hotgloo.com

Key Findings

We analyzed Rusk.hotgloo.com page load time and found that the first response time was 187 ms 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

rusk.hotgloo.com performance score

0

Network Requests Diagram

rusk.hotgloo.com

187 ms

signin

45 ms

signin

204 ms

lookup

184 ms

lookup

199 ms

Our browser made a total of 28 requests to load all elements on the main page. We found that 11% of them (3 requests) were addressed to the original Rusk.hotgloo.com, 79% (22 requests) were made to Hotgloo.com and 4% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (618 ms) relates to the external source Pw.hotgloo.co.

Page Optimization Overview & Recommendations

Page size can be reduced by 138.2 kB (54%)

Content Size

254.6 kB

After Optimization

116.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Rusk.hotgloo.com main page is 254.6 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. Javascripts take 115.4 kB which makes up the majority of the site volume.

HTML Optimization

-66%

Potential reduce by 5.5 kB

  • Original 8.4 kB
  • After minification 8.4 kB
  • After compression 2.9 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 5.5 kB or 66% of the original size.

Image Optimization

-2%

Potential reduce by 917 B

  • Original 52.0 kB
  • After minification 51.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. Rusk Hot Gloo images are well optimized though.

JavaScript Optimization

-57%

Potential reduce by 65.9 kB

  • Original 115.4 kB
  • After minification 108.3 kB
  • After compression 49.5 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 65.9 kB or 57% of the original size.

CSS Optimization

-84%

Potential reduce by 65.8 kB

  • Original 78.8 kB
  • After minification 73.3 kB
  • After compression 13.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. Rusk.hotgloo.com needs all CSS files to be minified and compressed as it can save up to 65.8 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 17 (74%)

Requests Now

23

After Optimization

6

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

rusk.hotgloo.com

rusk.hotgloo.com

187 ms

signin

signin

45 ms

signin

signin

204 ms

lookup

lookup

184 ms

lookup

lookup

199 ms

grid.css

grid.css

38 ms

ilightbox.css

ilightbox.css

74 ms

tipsy.css

tipsy.css

109 ms

page-resp.css

page-resp.css

182 ms

jquery.min.js

jquery.min.js

28 ms

jquery.tipsy.js

jquery.tipsy.js

115 ms

jquery.fitvids.js

jquery.fitvids.js

116 ms

ilightbox.min.js

ilightbox.min.js

225 ms

gloobar.js

gloobar.js

116 ms

page-resp.js

page-resp.js

142 ms

skin.css

skin.css

115 ms

skin.css

skin.css

116 ms

skin.css

skin.css

116 ms

skin.css

skin.css

106 ms

skin.css

skin.css

151 ms

skin.css

skin.css

151 ms

skin.css

skin.css

146 ms

sbi8qgg.js

sbi8qgg.js

220 ms

logo_hotgloo.png

logo_hotgloo.png

55 ms

hamburger.png

hamburger.png

47 ms

alert-overlay.png

alert-overlay.png

108 ms

piwik.js

piwik.js

618 ms

gloobar

gloobar

50 ms

SEO Factors

rusk.hotgloo.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 Rusk.hotgloo.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 Rusk.hotgloo.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

rusk.hotgloo.com

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