Tools & Wizards About Us
jumpstart.co.za screenshot

Report Summary

  • 39

    Performance

    Renders faster than
    58% of other websites

  • 72

    Accessibility

    Visual factors better than
    that of 37% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

jumpstart.co.za

Capital Engine® | Capital Raising Made Easy | Request A Demo

Page Load Speed

2.2 sec in total

First Response

157 ms

Resources Loaded

1.5 sec

Page Rendered

480 ms

jumpstart.co.za screenshot

About Website

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

Scalable private market & investor management solutions, for traditional & digital assets. Our software & tools are built for high-performance capital raising.

Visit jumpstart.co.za

Key Findings

We analyzed Jumpstart.co.za page load time and found that the first response time was 157 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

jumpstart.co.za performance score

39

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.2 s

43/100

10%

LCP (Largest Contentful Paint)

Value8.2 s

2/100

25%

SI (Speed Index)

Value4.6 s

71/100

10%

TBT (Total Blocking Time)

Value790 ms

37/100

30%

CLS (Cumulative Layout Shift)

Value0.011

100/100

15%

TTI (Time to Interactive)

Value15.3 s

7/100

10%

Network Requests Diagram

jumpstart.co.za

157 ms

jumpstart.co.za

287 ms

capitalengine.io

457 ms

gtm.js

78 ms

js

185 ms

Our browser made a total of 80 requests to load all elements on the main page. We found that 3% of them (2 requests) were addressed to the original Jumpstart.co.za, 86% (69 requests) were made to Capitalengine.io and 6% (5 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (457 ms) relates to the external source Capitalengine.io.

Page Optimization Overview & Recommendations

Page size can be reduced by 218.0 kB (28%)

Content Size

789.4 kB

After Optimization

571.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Jumpstart.co.za main page is 789.4 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 466.1 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 62.0 kB

  • Original 80.5 kB
  • After minification 75.2 kB
  • After compression 18.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 62.0 kB or 77% of the original size.

Image Optimization

-21%

Potential reduce by 97.1 kB

  • Original 466.1 kB
  • After minification 369.0 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, Jumpstart needs image optimization as it can save up to 97.1 kB or 21% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-0%

Potential reduce by 589 B

  • Original 143.4 kB
  • After minification 143.4 kB
  • After compression 142.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. This website has mostly compressed JavaScripts.

CSS Optimization

-59%

Potential reduce by 58.2 kB

  • Original 99.4 kB
  • After minification 57.2 kB
  • After compression 41.2 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. Jumpstart.co.za needs all CSS files to be minified and compressed as it can save up to 58.2 kB or 59% of the original size.

Requests Breakdown

Number of requests can be reduced by 29 (41%)

Requests Now

71

After Optimization

42

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

jumpstart.co.za

jumpstart.co.za

157 ms

jumpstart.co.za

jumpstart.co.za

287 ms

capitalengine.io

capitalengine.io

457 ms

gtm.js

gtm.js

78 ms

js

js

185 ms

bootstrap.min.css

bootstrap.min.css

16 ms

home_style_for_home.css

home_style_for_home.css

28 ms

jquery.min.js

jquery.min.js

57 ms

bootstrap.min.js

bootstrap.min.js

40 ms

jquery.bank.js

jquery.bank.js

42 ms

jquery-ui.min.js

jquery-ui.min.js

76 ms

jquery.fancybox.pack.js

jquery.fancybox.pack.js

42 ms

icheck.min.js

icheck.min.js

43 ms

easy-numpad.min.js

easy-numpad.min.js

51 ms

flickity.pkgd.min.js

flickity.pkgd.min.js

73 ms

toastr.min.js

toastr.min.js

71 ms

toastr.min.js

toastr.min.js

73 ms

toastr.css

toastr.css

74 ms

home_style_1.css

home_style_1.css

119 ms

allImport_home.css

allImport_home.css

35 ms

95_71_14_whitelogo.png

95_71_14_whitelogo.png

50 ms

Curve.webp

Curve.webp

47 ms

Phone.webp

Phone.webp

51 ms

Lines1.png

Lines1.png

49 ms

tab.png

tab.png

59 ms

computer.webp

computer.webp

61 ms

arrow_right.webp

arrow_right.webp

60 ms

spin1.webp

spin1.webp

60 ms

spin2.webp

spin2.webp

95 ms

spin3.webp

spin3.webp

95 ms

spin4.webp

spin4.webp

95 ms

yap.png

yap.png

158 ms

investview.png

investview.png

94 ms

pledge.png

pledge.png

95 ms

alto.png

alto.png

157 ms

levelx.png

levelx.png

157 ms

cre.webp

cre.webp

189 ms

hubspot.webp

hubspot.webp

157 ms

amazon.webp

amazon.webp

157 ms

plaid.png

plaid.png

193 ms

rialto.png

rialto.png

193 ms

docusign.webp

docusign.webp

193 ms

stripe.webp

stripe.webp

192 ms

trulioo.webp

trulioo.webp

193 ms

twilio.webp

twilio.webp

223 ms

primetrust.png

primetrust.png

223 ms

gist.webp

gist.webp

224 ms

sendgrid.png

sendgrid.png

224 ms

sendinblue.png

sendinblue.png

223 ms

wepay.png

wepay.png

224 ms

North_capital.webp

North_capital.webp

258 ms

PPEX.png

PPEX.png

256 ms

blockengine.webp

blockengine.webp

256 ms

verifyinvestor.webp

verifyinvestor.webp

258 ms

js

js

139 ms

insight.min.js

insight.min.js

241 ms

destination

destination

173 ms

sa.js

sa.js

428 ms

js

js

197 ms

25_s3_uploaded__SumSubwhitelogo.png

25_s3_uploaded__SumSubwhitelogo.png

234 ms

font-awesome.min.css

font-awesome.min.css

212 ms

balloon.min.css

balloon.min.css

216 ms

card.css

card.css

216 ms

flickity.min.css

flickity.min.css

210 ms

jquery.bxslider.css

jquery.bxslider.css

204 ms

capital_engine_responsive.css

capital_engine_responsive.css

204 ms

toastr.css

toastr.css

206 ms

83_54_admin_logo.png

83_54_admin_logo.png

221 ms

Poppins-Light.ttf

Poppins-Light.ttf

244 ms

Poppins-SemiBold.ttf

Poppins-SemiBold.ttf

239 ms

Poppins-Bold.ttf

Poppins-Bold.ttf

177 ms

Poppins-Regular.ttf

Poppins-Regular.ttf

177 ms

render.8c1f05a4184defb54e3d.js

render.8c1f05a4184defb54e3d.js

89 ms

spin1.webp

spin1.webp

58 ms

spin2.webp

spin2.webp

57 ms

spin3.webp

spin3.webp

58 ms

spin4.webp

spin4.webp

58 ms

insight.old.min.js

insight.old.min.js

23 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

44 ms

fontawesome-webfont.ttf

fontawesome-webfont.ttf

27 ms

Accessibility Review

jumpstart.co.za accessibility score

72

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

Names and labels

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

Buttons do not have an accessible name

High

Links do not have a discernible name

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

jumpstart.co.za best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

jumpstart.co.za SEO score

77

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

Mobile Friendly

Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).

Impact

Issue

High

Document doesn't use legible font sizes

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 Jumpstart.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 Jumpstart.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

jumpstart.co.za

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