Tools & Wizards About Us
brikk.hotgloo.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

brikk.hotgloo.com

HotGloo | Wireframe UX Prototyping Tool

Page Load Speed

2.2 sec in total

First Response

197 ms

Resources Loaded

1.9 sec

Page Rendered

91 ms

brikk.hotgloo.com screenshot

About Website

Click here to check amazing Brikk Hot Gloo content for Canada. Otherwise, check out these important facts you probably never knew about brikk.hotgloo.com

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

Visit brikk.hotgloo.com

Key Findings

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

brikk.hotgloo.com performance score

0

Network Requests Diagram

brikk.hotgloo.com

197 ms

signin

46 ms

signin

209 ms

lookup

184 ms

lookup

197 ms

Our browser made a total of 42 requests to load all elements on the main page. We found that 7% of them (3 requests) were addressed to the original Brikk.hotgloo.com, 52% (22 requests) were made to Hotgloo.com and 33% (14 requests) were made to Use.typekit.com. The less responsive or slowest element that took the longest time to load (603 ms) relates to the external source Pw.hotgloo.co.

Page Optimization Overview & Recommendations

Page size can be reduced by 150.6 kB (56%)

Content Size

268.0 kB

After Optimization

117.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-82%

Potential reduce by 18.0 kB

  • Original 21.8 kB
  • After minification 21.8 kB
  • After compression 3.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 18.0 kB or 82% 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. Brikk 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. Brikk.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 18 (72%)

Requests Now

25

After Optimization

7

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

brikk.hotgloo.com

brikk.hotgloo.com

197 ms

signin

signin

46 ms

signin

signin

209 ms

lookup

lookup

184 ms

lookup

lookup

197 ms

grid.css

grid.css

38 ms

ilightbox.css

ilightbox.css

76 ms

tipsy.css

tipsy.css

109 ms

page-resp.css

page-resp.css

180 ms

jquery.min.js

jquery.min.js

66 ms

jquery.tipsy.js

jquery.tipsy.js

110 ms

jquery.fitvids.js

jquery.fitvids.js

114 ms

ilightbox.min.js

ilightbox.min.js

221 ms

gloobar.js

gloobar.js

115 ms

page-resp.js

page-resp.js

142 ms

skin.css

skin.css

71 ms

skin.css

skin.css

75 ms

skin.css

skin.css

78 ms

skin.css

skin.css

111 ms

skin.css

skin.css

112 ms

skin.css

skin.css

115 ms

skin.css

skin.css

117 ms

sbi8qgg.js

sbi8qgg.js

125 ms

ddf

ddf

94 ms

logo_hotgloo.png

logo_hotgloo.png

37 ms

p.gif

p.gif

144 ms

hamburger.png

hamburger.png

40 ms

alert-overlay.png

alert-overlay.png

112 ms

piwik.js

piwik.js

603 ms

gloobar

gloobar

83 ms

SbOheo0MyDhwWPD3_OJWuc5FjikGhlBfqokzFkmmWovffw7EggMbeMI6MK6fw6NuSh90iY83ZAlTifoRdhXtgM.eot

SbOheo0MyDhwWPD3_OJWuc5FjikGhlBfqokzFkmmWovffw7EggMbeMI6MK6fw6NuSh90iY83ZAlTifoRdhXtgM.eot

30 ms

hhi6KfSFaMYTCB74seqWAG4YgtWSB8Jx7GE8VsISTgwffwkEggMbeMI6MK6fw6NuSh90iY83ZAlTifoRdhXtg6.eot

hhi6KfSFaMYTCB74seqWAG4YgtWSB8Jx7GE8VsISTgwffwkEggMbeMI6MK6fw6NuSh90iY83ZAlTifoRdhXtg6.eot

72 ms

vlwWBsc5RRP2qHpDMIActKuOEq6VfMiGTk86G32vstSffVRKMUMbeMI6MK6fw6NuSh90iY83ZAlTifoRdhXtgM.eot

vlwWBsc5RRP2qHpDMIActKuOEq6VfMiGTk86G32vstSffVRKMUMbeMI6MK6fw6NuSh90iY83ZAlTifoRdhXtgM.eot

128 ms

bV59QEt8_6PbygftHxj2b2BDWoJ0d71yb4KcHLK-gASffVnKMUMbeMI6MK6fw6NuSh90iY83ZAlTifoRdhXtgb.eot

bV59QEt8_6PbygftHxj2b2BDWoJ0d71yb4KcHLK-gASffVnKMUMbeMI6MK6fw6NuSh90iY83ZAlTifoRdhXtgb.eot

137 ms

DmWFKPudzhEdyqXBLmLKGo70fO7v_s6Bo0s8luO4LkjffHn8ggMbeMI6MK6fw6NuSh90iY83ZAlTifoRdhXt26.eot

DmWFKPudzhEdyqXBLmLKGo70fO7v_s6Bo0s8luO4LkjffHn8ggMbeMI6MK6fw6NuSh90iY83ZAlTifoRdhXt26.eot

149 ms

vvK-h6xE8ex4KbSBmmWwq1GNWgPsaEXiq66Vy58nE2qffH_8ggMbeMI6MK6fw6NuSh90iY83ZAlTifoRdhXtIb.eot

vvK-h6xE8ex4KbSBmmWwq1GNWgPsaEXiq66Vy58nE2qffH_8ggMbeMI6MK6fw6NuSh90iY83ZAlTifoRdhXtIb.eot

152 ms

fj7qxpRS4ZoDZa9J2noSha7RQI2iJKNa513u6CuoXvSffHW8ggMbeMI6MK6fw6NuSh90iY83ZAlTifoRdhXtgM.eot

fj7qxpRS4ZoDZa9J2noSha7RQI2iJKNa513u6CuoXvSffHW8ggMbeMI6MK6fw6NuSh90iY83ZAlTifoRdhXtgM.eot

157 ms

62brIMEsomNS9TRlaoFZ5BbD5huV3mbiNMTnYIl6atwffHa8ggMbeMI6MK6fw6NuSh90iY83ZAlTifoRdhXtg3.eot

62brIMEsomNS9TRlaoFZ5BbD5huV3mbiNMTnYIl6atwffHa8ggMbeMI6MK6fw6NuSh90iY83ZAlTifoRdhXtg3.eot

160 ms

cOiOr0PIrgHR0HOEUVB50GrTq2qFFYCdKYfDj0LrKGvffH18ggMbeMI6MK6fw6NuSh90iY83ZAlTifoRdhXt2b.eot

cOiOr0PIrgHR0HOEUVB50GrTq2qFFYCdKYfDj0LrKGvffH18ggMbeMI6MK6fw6NuSh90iY83ZAlTifoRdhXt2b.eot

183 ms

967xuIGfDt9m7ztj8QNJ5UvZCD_I_Dr4EMgh-3jtCUtffHz8ggMbeMI6MK6fw6NuSh90iY83ZAlTifoRdhXtg6.eot

967xuIGfDt9m7ztj8QNJ5UvZCD_I_Dr4EMgh-3jtCUtffHz8ggMbeMI6MK6fw6NuSh90iY83ZAlTifoRdhXtg6.eot

188 ms

WRFu72O5YjYajRPP3XmvxnqwJ_EunXX38s72lxgbnhCffw0EggMbeMI6MK6fw6NuSh90iY83ZAlTifoRdhXt26.eot

WRFu72O5YjYajRPP3XmvxnqwJ_EunXX38s72lxgbnhCffw0EggMbeMI6MK6fw6NuSh90iY83ZAlTifoRdhXt26.eot

177 ms

WlN-fNcwW2GGW9G41WaPtErZjwJxMW-uoGREa3_U2_wffV-uggMbeMI6MK6fw6NuSh90iY83ZAlTifoRdhXtIM.eot

WlN-fNcwW2GGW9G41WaPtErZjwJxMW-uoGREa3_U2_wffV-uggMbeMI6MK6fw6NuSh90iY83ZAlTifoRdhXtIM.eot

206 ms

SEO Factors

brikk.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 Brikk.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 Brikk.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

brikk.hotgloo.com

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