Tools & Wizards About Us
futureworks.co.za screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

futureworks.co.za

Welcome to nginx!

Page Load Speed

16.5 sec in total

First Response

4 sec

Resources Loaded

11.8 sec

Page Rendered

724 ms

futureworks.co.za screenshot

About Website

Visit futureworks.co.za now to see the best up-to-date Futureworks content and also check out these interesting facts you probably never knew about futureworks.co.za

FutureWorks sustainability consulting

Visit futureworks.co.za

Key Findings

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

Performance Metrics

futureworks.co.za performance score

0

Network Requests Diagram

futureworks.co.za

4008 ms

gtm.js

121 ms

sc_bootstrap.css

502 ms

common.css

748 ms

content.css

778 ms

Our browser made a total of 60 requests to load all elements on the main page. We found that 78% of them (47 requests) were addressed to the original Futureworks.co.za, 7% (4 requests) were made to Fonts.gstatic.com and 5% (3 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (4 sec) belongs to the original domain Futureworks.co.za.

Page Optimization Overview & Recommendations

Page size can be reduced by 122.5 kB (12%)

Content Size

1.0 MB

After Optimization

914.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Futureworks.co.za main page is 1.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. 40% of websites need less resources to load. Images take 875.8 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 35.1 kB

  • Original 44.6 kB
  • After minification 42.8 kB
  • After compression 9.5 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 35.1 kB or 79% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 875.8 kB
  • After minification 875.8 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. Futureworks images are well optimized though.

JavaScript Optimization

-60%

Potential reduce by 32.0 kB

  • Original 52.9 kB
  • After minification 52.9 kB
  • After compression 20.9 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 32.0 kB or 60% of the original size.

CSS Optimization

-87%

Potential reduce by 55.3 kB

  • Original 63.6 kB
  • After minification 50.0 kB
  • After compression 8.3 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. Futureworks.co.za needs all CSS files to be minified and compressed as it can save up to 55.3 kB or 87% of the original size.

Requests Breakdown

Number of requests can be reduced by 10 (56%)

Requests Now

18

After Optimization

8

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

futureworks.co.za

futureworks.co.za

4008 ms

gtm.js

gtm.js

121 ms

sc_bootstrap.css

sc_bootstrap.css

502 ms

common.css

common.css

748 ms

content.css

content.css

778 ms

layerslider.css

layerslider.css

1184 ms

css

css

116 ms

style.css

style.css

1029 ms

animate.css

animate.css

511 ms

jux-font-awesome.css

jux-font-awesome.css

512 ms

blackwhite.css

blackwhite.css

511 ms

custom-112.css

custom-112.css

511 ms

greensock.js

greensock.js

511 ms

jfbconnect.js

jfbconnect.js

493 ms

jq-bootstrap-1.8.3.js

jq-bootstrap-1.8.3.js

470 ms

mootools-core.js

mootools-core.js

470 ms

core.js

core.js

470 ms

mootools-more.js

mootools-more.js

470 ms

jquery.min.js

jquery.min.js

470 ms

jquery-noconflict.js

jquery-noconflict.js

470 ms

jquery-migrate.min.js

jquery-migrate.min.js

469 ms

layerslider.js

layerslider.js

469 ms

layerslider.transitions.js

layerslider.transitions.js

469 ms

headroom.js

headroom.js

469 ms

navAccordion.js

navAccordion.js

468 ms

jquery-ui.js

jquery-ui.js

70 ms

system.css

system.css

468 ms

futureworx.css

futureworx.css

469 ms

css

css

65 ms

css

css

68 ms

animate.css

animate.css

468 ms

wow.min.js

wow.min.js

468 ms

general.css

general.css

467 ms

general_konqueror.css

general_konqueror.css

467 ms

analytics.js

analytics.js

30 ms

collect

collect

20 ms

logo.png

logo.png

1019 ms

header_bg_1.jpg

header_bg_1.jpg

2565 ms

header_bg_2.jpg

header_bg_2.jpg

2019 ms

cont_map_new.png

cont_map_new.png

1003 ms

climate_resilience.jpg

climate_resilience.jpg

810 ms

green_economy.jpg

green_economy.jpg

601 ms

decision_support.jpg

decision_support.jpg

600 ms

env_economics.jpg

env_economics.jpg

600 ms

env_planning.jpg

env_planning.jpg

601 ms

grid_img_large.jpg

grid_img_large.jpg

601 ms

grimd_img_small.jpg

grimd_img_small.jpg

601 ms

projects_bg_img.jpg

projects_bg_img.jpg

600 ms

footer_logo.png

footer_logo.png

600 ms

facebook_icon.png

facebook_icon.png

600 ms

twitter_icon.png

twitter_icon.png

600 ms

youtube_icon.png

youtube_icon.png

600 ms

linkedin_icon.png

linkedin_icon.png

599 ms

sdk.js

sdk.js

90 ms

sdk.js

sdk.js

30 ms

S6uyw4BMUTPHjx4wWw.ttf

S6uyw4BMUTPHjx4wWw.ttf

165 ms

S6uyw4BMUTPHjxAwWw.ttf

S6uyw4BMUTPHjxAwWw.ttf

225 ms

S6u9w4BMUTPHh6UVSwiPHA.ttf

S6u9w4BMUTPHh6UVSwiPHA.ttf

228 ms

S6u9w4BMUTPHh6UVSwaPHA.ttf

S6u9w4BMUTPHh6UVSwaPHA.ttf

228 ms

print.css

print.css

258 ms

SEO Factors

futureworks.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 Futureworks.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 Futureworks.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

futureworks.co.za

Open Graph data is detected on the main page of Futureworks. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: