Tools & Wizards About Us
hugeedge.co.za screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

hugeedge.co.za

Website Design | Company Registration | Graphic Design | Promotional Products

Page Load Speed

3.3 sec in total

First Response

284 ms

Resources Loaded

2.7 sec

Page Rendered

343 ms

hugeedge.co.za screenshot

About Website

Click here to check amazing Hugeedge content. Otherwise, check out these important facts you probably never knew about hugeedge.co.za

Web Design, Graphic Design, Company Registration

Visit hugeedge.co.za

Key Findings

We analyzed Hugeedge.co.za page load time and found that the first response time was 284 ms and then it took 3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

hugeedge.co.za performance score

0

Network Requests Diagram

www.hugeedge.co.za

284 ms

style.css

92 ms

flick.css

133 ms

www.hugeedge.co.za

688 ms

layerslider.css

106 ms

Our browser made a total of 145 requests to load all elements on the main page. We found that 55% of them (80 requests) were addressed to the original Hugeedge.co.za, 24% (35 requests) were made to Maps.google.com and 6% (8 requests) were made to Maps.gstatic.com. The less responsive or slowest element that took the longest time to load (797 ms) belongs to the original domain Hugeedge.co.za.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.6 MB (55%)

Content Size

3.0 MB

After Optimization

1.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Hugeedge.co.za 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. 60% of websites need less resources to load. Javascripts take 1.7 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 68.4 kB

  • Original 80.3 kB
  • After minification 78.7 kB
  • After compression 11.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 68.4 kB or 85% of the original size.

Image Optimization

-2%

Potential reduce by 13.8 kB

  • Original 826.4 kB
  • After minification 812.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. Hugeedge images are well optimized though.

JavaScript Optimization

-74%

Potential reduce by 1.3 MB

  • Original 1.7 MB
  • After minification 1.5 MB
  • After compression 446.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 1.3 MB or 74% of the original size.

CSS Optimization

-84%

Potential reduce by 271.7 kB

  • Original 321.6 kB
  • After minification 289.6 kB
  • After compression 49.9 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. Hugeedge.co.za needs all CSS files to be minified and compressed as it can save up to 271.7 kB or 84% of the original size.

Requests Breakdown

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

Requests Now

136

After Optimization

35

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.hugeedge.co.za

www.hugeedge.co.za

284 ms

style.css

style.css

92 ms

flick.css

flick.css

133 ms

www.hugeedge.co.za

www.hugeedge.co.za

688 ms

layerslider.css

layerslider.css

106 ms

css

css

75 ms

styles.css

styles.css

90 ms

style_for_map.css

style_for_map.css

124 ms

calendar-jos.css

calendar-jos.css

153 ms

jquery-ui-spinner.css

jquery-ui-spinner.css

162 ms

page-list.css

page-list.css

174 ms

settings.css

settings.css

196 ms

dynamic-captions.css

dynamic-captions.css

193 ms

static-captions.css

static-captions.css

221 ms

font-awesome.css

font-awesome.css

210 ms

fancybox.css

fancybox.css

270 ms

flexslider.css

flexslider.css

503 ms

animate.css

animate.css

258 ms

style.min.css

style.min.css

278 ms

jquery.js

jquery.js

330 ms

jquery-migrate.min.js

jquery-migrate.min.js

330 ms

scrollTo.js

scrollTo.js

347 ms

jquery.form.min.js

jquery.form.min.js

346 ms

mailchimp.js

mailchimp.js

370 ms

core.min.js

core.min.js

405 ms

datepicker.js

datepicker.js

446 ms

layerslider.kreaturamedia.jquery.js

layerslider.kreaturamedia.jquery.js

462 ms

greensock.js

greensock.js

460 ms

layerslider.transitions.js

layerslider.transitions.js

474 ms

main_front_end.js

main_front_end.js

508 ms

js

js

55 ms

if_gmap_front_end.js

if_gmap_front_end.js

506 ms

calendar.js

calendar.js

541 ms

calendar-setup.js

calendar-setup.js

540 ms

calendar_function.js

calendar_function.js

557 ms

jquery-ui.js

jquery-ui.js

660 ms

jquery.ui.slider.js

jquery.ui.slider.js

568 ms

jquery.themepunch.plugins.min.js

jquery.themepunch.plugins.min.js

645 ms

js

js

93 ms

jquery.themepunch.revolution.min.js

jquery.themepunch.revolution.min.js

797 ms

style.css

style.css

562 ms

jquery.backstretch.js

jquery.backstretch.js

570 ms

jquery.isotope.js

jquery.isotope.js

724 ms

jquery.custom.js

jquery.custom.js

708 ms

scripts.js

scripts.js

693 ms

jquery.gmap.js

jquery.gmap.js

682 ms

jquery.easing.js

jquery.easing.js

671 ms

jquery.flexslider.js

jquery.flexslider.js

651 ms

jquery.hbstreams.js

jquery.hbstreams.js

648 ms

jquery.supersubs.js

jquery.supersubs.js

633 ms

jquery.superfish.js

jquery.superfish.js

626 ms

jquery.validate.js

jquery.validate.js

587 ms

jquery.tipsy.js

jquery.tipsy.js

602 ms

jquery.tweet.js

jquery.tweet.js

594 ms

jquery.fitvids.js

jquery.fitvids.js

520 ms

jquery.fancybox-1.3.4.pack.js

jquery.fancybox-1.3.4.pack.js

516 ms

jquery.sticky.js

jquery.sticky.js

576 ms

jquery.autosize.min.js

jquery.autosize.min.js

577 ms

cookie.min.js

cookie.min.js

552 ms

App.min.js

App.min.js

518 ms

css

css

16 ms

css

css

26 ms

css

css

35 ms

HE12.png

HE12.png

160 ms

slider-1-1024x7052.jpg

slider-1-1024x7052.jpg

182 ms

biking.jpg

biking.jpg

206 ms

food.jpg

food.jpg

372 ms

nature.jpg

nature.jpg

203 ms

web.jpg

web.jpg

201 ms

mailchimp.png

mailchimp.png

169 ms

6.png

6.png

264 ms

facebook-icon.png

facebook-icon.png

339 ms

google-icon.png

google-icon.png

299 ms

twitter-icon.png

twitter-icon.png

299 ms

youtube-icon.png

youtube-icon.png

277 ms

linkedin-icon.png

linkedin-icon.png

386 ms

search.png

search.png

395 ms

likebox.php

likebox.php

222 ms

shadow-top.png

shadow-top.png

375 ms

e1e2e3.png

e1e2e3.png

373 ms

arrow.png

arrow.png

374 ms

grass-1024x681.jpg

grass-1024x681.jpg

241 ms

common.js

common.js

47 ms

map.js

map.js

74 ms

util.js

util.js

138 ms

geocoder.js

geocoder.js

73 ms

marker.js

marker.js

73 ms

admin-ajax.php

admin-ajax.php

446 ms

trans-07.png

trans-07.png

276 ms

arrow-left.png

arrow-left.png

346 ms

arrow-right.png

arrow-right.png

377 ms

Entypo-webfont.woff

Entypo-webfont.woff

400 ms

Q-gJrFokeE7JydPpxASt20ERdfSURLZv58OmP7NOrmM.ttf

Q-gJrFokeE7JydPpxASt20ERdfSURLZv58OmP7NOrmM.ttf

152 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

461 ms

onion.js

onion.js

64 ms

openhand_8_8.cur

openhand_8_8.cur

128 ms

ViewportInfoService.GetViewportInfo

ViewportInfoService.GetViewportInfo

207 ms

stats.js

stats.js

73 ms

controls.js

controls.js

64 ms

kyEKgjk51ZE.css

kyEKgjk51ZE.css

161 ms

xgj7bXhJNEH.css

xgj7bXhJNEH.css

190 ms

q68gy-v_YMF.js

q68gy-v_YMF.js

268 ms

FJmpeSpHpjS.js

FJmpeSpHpjS.js

302 ms

0wM5s1Khldu.js

0wM5s1Khldu.js

244 ms

1bNoFZUdlYZ.js

1bNoFZUdlYZ.js

285 ms

css

css

71 ms

transparent.png

transparent.png

59 ms

google4.png

google4.png

50 ms

mapcnt6.png

mapcnt6.png

122 ms

sv5.png

sv5.png

95 ms

tmapctrl.png

tmapctrl.png

114 ms

cb_scout5.png

cb_scout5.png

183 ms

imgs8.png

imgs8.png

136 ms

zN7GBFwfMP4uA6AR0HCoLQ.ttf

zN7GBFwfMP4uA6AR0HCoLQ.ttf

49 ms

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

101 ms

Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf

Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf

146 ms

d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf

d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf

152 ms

vt

vt

72 ms

vt

vt

66 ms

vt

vt

64 ms

vt

vt

65 ms

vt

vt

62 ms

vt

vt

112 ms

vt

vt

110 ms

vt

vt

109 ms

vt

vt

113 ms

vt

vt

112 ms

vt

vt

121 ms

vt

vt

114 ms

vt

vt

115 ms

vt

vt

122 ms

vt

vt

117 ms

vt

vt

116 ms

vt

vt

117 ms

vt

vt

119 ms

vt

vt

118 ms

vt

vt

126 ms

vt

vt

123 ms

vt

vt

130 ms

vt

vt

128 ms

vt

vt

123 ms

vt

vt

124 ms

I6-MnjEovm5.js

I6-MnjEovm5.js

16 ms

pQrUxxo5oQp.js

pQrUxxo5oQp.js

16 ms

AuthenticationService.Authenticate

AuthenticationService.Authenticate

36 ms

SEO Factors

hugeedge.co.za 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 Hugeedge.co.za 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 Hugeedge.co.za 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

hugeedge.co.za

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