Tools & Wizards About Us
origin.co.za screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

origin.co.za

Online 360 Assessments, Web-based Surveys, Enterprise Feedback

Page Load Speed

11.2 sec in total

First Response

2.8 sec

Resources Loaded

8.3 sec

Page Rendered

99 ms

origin.co.za screenshot

About Website

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

Origin is a South African organisation that specialises in online 360 Assessments and web-based surveys, providing enterprise feedback from your key

Visit origin.co.za

Key Findings

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

Performance Metrics

origin.co.za performance score

0

Network Requests Diagram

2779 ms

style.css

427 ms

styles.css

526 ms

www.origin.co.za

1792 ms

style_2.1.2.css

514 ms

Our browser made a total of 67 requests to load all elements on the main page. We found that 57% of them (38 requests) were addressed to the original Origin.co.za, 9% (6 requests) were made to Apis.google.com and 6% (4 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (2.8 sec) belongs to the original domain Origin.co.za.

Page Optimization Overview & Recommendations

Page size can be reduced by 109.3 kB (18%)

Content Size

608.6 kB

After Optimization

499.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-77%

Potential reduce by 56.6 kB

  • Original 73.9 kB
  • After minification 73.8 kB
  • After compression 17.3 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 56.6 kB or 77% of the original size.

Image Optimization

-2%

Potential reduce by 2.3 kB

  • Original 106.1 kB
  • After minification 103.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. Origin images are well optimized though.

JavaScript Optimization

-12%

Potential reduce by 50.0 kB

  • Original 414.5 kB
  • After minification 410.1 kB
  • After compression 364.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 50.0 kB or 12% of the original size.

CSS Optimization

-3%

Potential reduce by 403 B

  • Original 14.2 kB
  • After minification 14.2 kB
  • After compression 13.8 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. Origin.co.za has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 31 (53%)

Requests Now

58

After Optimization

27

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

2779 ms

style.css

style.css

427 ms

styles.css

styles.css

526 ms

www.origin.co.za

www.origin.co.za

1792 ms

style_2.1.2.css

style_2.1.2.css

514 ms

n2-ss-2.css

n2-ss-2.css

732 ms

jquery.min.js

jquery.min.js

17 ms

suckerfish.js

suckerfish.js

786 ms

button.facebook.js

button.facebook.js

803 ms

n2.js

n2.js

1012 ms

nextend-frontend.min.js

nextend-frontend.min.js

1304 ms

smartslider-frontend.min.js

smartslider-frontend.min.js

1325 ms

smartslider-simple-type-frontend.min.js

smartslider-simple-type-frontend.min.js

1291 ms

nextend-webfontloader.min.js

nextend-webfontloader.min.js

1546 ms

loader_iconbox.js

loader_iconbox.js

95 ms

comment-reply.min.js

comment-reply.min.js

1547 ms

scripts.js

scripts.js

1573 ms

jscripts-ftr2-min.js

jscripts-ftr2-min.js

1587 ms

script_no_follow_2.1.2.js

script_no_follow_2.1.2.js

1596 ms

in.js

in.js

20 ms

widgets.js

widgets.js

23 ms

button.googleplus.js

button.googleplus.js

1842 ms

all.js

all.js

12 ms

wp-embed.min.js

wp-embed.min.js

1843 ms

analytics.js

analytics.js

28 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

1396 ms

collect

collect

28 ms

css

css

27 ms

twit.gif

twit.gif

277 ms

social_share_button.png

social_share_button.png

99 ms

fb.gif

fb.gif

333 ms

linkin.gif

linkin.gif

288 ms

gplus.gif

gplus.gif

275 ms

logo1.jpg

logo1.jpg

286 ms

Homepagebanner.jpg

Homepagebanner.jpg

548 ms

banner-1.jpg

banner-1.jpg

554 ms

banner-2.jpg

banner-2.jpg

559 ms

banner-4.jpg

banner-4.jpg

579 ms

banner-5.jpg

banner-5.jpg

811 ms

icon-01.gif

icon-01.gif

605 ms

icon-02.gif

icon-02.gif

843 ms

icon-03.gif

icon-03.gif

859 ms

icon-04.gif

icon-04.gif

828 ms

Wondering.jpg

Wondering.jpg

845 ms

tick.png

tick.png

917 ms

ebook.jpg

ebook.jpg

1089 ms

css.php

css.php

1123 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aX8.ttf

73 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf

74 ms

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

79 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

79 ms

plusone.js

plusone.js

24 ms

all.js

all.js

37 ms

widget_iframe.7dae38096d06923d683a2a807172322a.html

widget_iframe.7dae38096d06923d683a2a807172322a.html

41 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

71 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

64 ms

fastbutton

fastbutton

103 ms

settings

settings

135 ms

87 ms

postmessageRelay

postmessageRelay

201 ms

developers.google.com

developers.google.com

245 ms

button.d2f864f87f544dc0c11d7d712a191c1f.js

button.d2f864f87f544dc0c11d7d712a191c1f.js

3 ms

embeds

embeds

25 ms

tweet_button.7dae38096d06923d683a2a807172322a.en.html

tweet_button.7dae38096d06923d683a2a807172322a.en.html

12 ms

1832714284-postmessagerelay.js

1832714284-postmessagerelay.js

17 ms

rpc:shindig_random.js

rpc:shindig_random.js

12 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

4 ms

SEO Factors

origin.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 Origin.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 Origin.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

origin.co.za

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