Tools & Wizards About Us
cargoinfo.co.za screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

cargoinfo.co.za

Freight News |

Page Load Speed

5.3 sec in total

First Response

601 ms

Resources Loaded

4.6 sec

Page Rendered

83 ms

cargoinfo.co.za screenshot

About Website

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

The leading news and information portal about transport and trade affecting Southern Africa. Freight & Trading Weekly was established in 1973, the online in 1997.

Visit cargoinfo.co.za

Key Findings

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

Performance Metrics

cargoinfo.co.za performance score

0

Network Requests Diagram

cargoinfo.co.za

601 ms

www.ftwonline.co.za

921 ms

bootstrap.css

1195 ms

app.min.css

420 ms

font-awesome.min.css

33 ms

Our browser made a total of 49 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Cargoinfo.co.za, 61% (30 requests) were made to Ftwonline.co.za and 20% (10 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (2.5 sec) relates to the external source Ftwonline.co.za.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.1 MB (65%)

Content Size

1.7 MB

After Optimization

590.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Cargoinfo.co.za main page is 1.7 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. 30% of websites need less resources to load. Javascripts take 991.2 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 28.0 kB

  • Original 34.2 kB
  • After minification 27.8 kB
  • After compression 6.2 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. This page needs HTML code to be minified as it can gain 6.4 kB, which is 19% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 28.0 kB or 82% of the original size.

Image Optimization

-29%

Potential reduce by 64.0 kB

  • Original 222.0 kB
  • After minification 157.9 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. Obviously, Cargoinfo needs image optimization as it can save up to 64.0 kB or 29% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-64%

Potential reduce by 634.6 kB

  • Original 991.2 kB
  • After minification 943.1 kB
  • After compression 356.6 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 634.6 kB or 64% of the original size.

CSS Optimization

-83%

Potential reduce by 348.3 kB

  • Original 418.2 kB
  • After minification 379.8 kB
  • After compression 69.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. Cargoinfo.co.za needs all CSS files to be minified and compressed as it can save up to 348.3 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 19 (54%)

Requests Now

35

After Optimization

16

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

cargoinfo.co.za

cargoinfo.co.za

601 ms

www.ftwonline.co.za

www.ftwonline.co.za

921 ms

bootstrap.css

bootstrap.css

1195 ms

app.min.css

app.min.css

420 ms

font-awesome.min.css

font-awesome.min.css

33 ms

jquery.min.js

jquery.min.js

991 ms

bootstrap.min.js

bootstrap.min.js

662 ms

asyncjs.php

asyncjs.php

751 ms

angular.min.js

angular.min.js

1459 ms

angular-resource.min.js

angular-resource.min.js

346 ms

angular-sanitize.min.js

angular-sanitize.min.js

563 ms

angular-ui-router.min.js

angular-ui-router.min.js

1245 ms

ui-bootstrap-tpls.min.js

ui-bootstrap-tpls.min.js

1640 ms

angular-cookies.min.js

angular-cookies.min.js

850 ms

angular-local-storage.min.js

angular-local-storage.min.js

1064 ms

ng-videosharing-embed.min.js

ng-videosharing-embed.min.js

1166 ms

angular-recaptcha.min.js

angular-recaptcha.min.js

1242 ms

app.js

app.js

2134 ms

app.min.js

app.min.js

2509 ms

constants.js

constants.js

2134 ms

css

css

33 ms

analytics.js

analytics.js

36 ms

em.js

em.js

349 ms

signin-modal.html

signin-modal.html

121 ms

search-modal.html

search-modal.html

129 ms

header.html

header.html

145 ms

menu.html

menu.html

182 ms

news.html

news.html

133 ms

signin-form.html

signin-form.html

199 ms

search-form.html

search-form.html

161 ms

collect

collect

69 ms

print-news.html

print-news.html

169 ms

featured-jobs.html

featured-jobs.html

180 ms

news-nav.html

news-nav.html

112 ms

loading.html

loading.html

165 ms

ftw-online-full-logo.png

ftw-online-full-logo.png

187 ms

collect

collect

61 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

15 ms

zhcz-_WihjSQC0oHJ9TCYL3hpw3pgy2gAi-Ip7WPMi0.woff

zhcz-_WihjSQC0oHJ9TCYL3hpw3pgy2gAi-Ip7WPMi0.woff

40 ms

gFXtEMCp1m_YzxsBpKl68jG_owQUHpNX9rkRdZ1lhPA.woff

gFXtEMCp1m_YzxsBpKl68jG_owQUHpNX9rkRdZ1lhPA.woff

44 ms

SKK6Nusyv8QPNMtI4j9J2zG_owQUHpNX9rkRdZ1lhPA.woff

SKK6Nusyv8QPNMtI4j9J2zG_owQUHpNX9rkRdZ1lhPA.woff

48 ms

ajax-loading.gif

ajax-loading.gif

87 ms

CrYjSnGjrRCn0pd9VQsnFOvvDin1pK8aKteLpeZ5c0A.woff

CrYjSnGjrRCn0pd9VQsnFOvvDin1pK8aKteLpeZ5c0A.woff

9 ms

Xu_FYwbs8k0teWf0uC8JpX-_kf6ByYO6CLYdB4HQE-Y.woff

Xu_FYwbs8k0teWf0uC8JpX-_kf6ByYO6CLYdB4HQE-Y.woff

7 ms

Svo1-WwNdc8q8K6pUofYJH-_kf6ByYO6CLYdB4HQE-Y.woff

Svo1-WwNdc8q8K6pUofYJH-_kf6ByYO6CLYdB4HQE-Y.woff

18 ms

xAgrA2k7n3Rmh_1Lx3YYI3-_kf6ByYO6CLYdB4HQE-Y.woff

xAgrA2k7n3Rmh_1Lx3YYI3-_kf6ByYO6CLYdB4HQE-Y.woff

8 ms

YQ4t7M-eeDSWa1BA2hnMJH-_kf6ByYO6CLYdB4HQE-Y.woff

YQ4t7M-eeDSWa1BA2hnMJH-_kf6ByYO6CLYdB4HQE-Y.woff

17 ms

mUdRVCMHGKUBOACHGTH1g3-_kf6ByYO6CLYdB4HQE-Y.woff

mUdRVCMHGKUBOACHGTH1g3-_kf6ByYO6CLYdB4HQE-Y.woff

17 ms

DDBbt_SKtg0EqyMEnMOuTX-_kf6ByYO6CLYdB4HQE-Y.woff

DDBbt_SKtg0EqyMEnMOuTX-_kf6ByYO6CLYdB4HQE-Y.woff

17 ms

SEO Factors

cargoinfo.co.za SEO score

0

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Cargoinfo.co.za can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Cargoinfo.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

cargoinfo.co.za

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