9.7 sec in total
655 ms
8.8 sec
291 ms
Click here to check amazing Digisource content. Otherwise, check out these important facts you probably never knew about digisource.co.za
We are a full-service IT support organisation, offering your business, big or small, comprehensive solutions across all aspects of IT.
Visit digisource.co.zaWe analyzed Digisource.co.za page load time and found that the first response time was 655 ms and then it took 9.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
digisource.co.za performance score
name
value
score
weighting
Value7.4 s
1/100
10%
Value16.0 s
0/100
25%
Value19.8 s
0/100
10%
Value27,950 ms
0/100
30%
Value0.116
85/100
15%
Value38.4 s
0/100
10%
655 ms
1577 ms
290 ms
579 ms
1438 ms
Our browser made a total of 107 requests to load all elements on the main page. We found that 45% of them (48 requests) were addressed to the original Digisource.co.za, 42% (45 requests) were made to Fonts.gstatic.com and 6% (6 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain Digisource.co.za.
Page size can be reduced by 199.6 kB (16%)
1.3 MB
1.1 MB
In fact, the total size of Digisource.co.za main page is 1.3 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. 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 996.4 kB which makes up the majority of the site volume.
Potential reduce by 86.0 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 86.0 kB or 87% of the original size.
Potential reduce by 112.3 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, Digisource needs image optimization as it can save up to 112.3 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 889 B
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.
Potential reduce by 451 B
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. Digisource.co.za has all CSS files already compressed.
Number of requests can be reduced by 27 (48%)
56
29
The browser has sent 56 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Digisource. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 21 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
digisource.co.za
655 ms
www.digisource.co.za
1577 ms
styles.css
290 ms
style.min.css
579 ms
style-static.min.css
1438 ms
style.css
864 ms
jquery.min.js
1155 ms
jquery-migrate.min.js
872 ms
js
87 ms
et-core-unified-tb-174-888.min.css
869 ms
et-core-unified-888.min.css
869 ms
et-core-unified-tb-174-deferred-888.min.css
1144 ms
index.js
1148 ms
index.js
1143 ms
scripts.min.js
1746 ms
smoothscroll.js
1592 ms
es6-promise.auto.min.js
1593 ms
api.js
80 ms
recaptcha.js
1592 ms
frontend-bundle.min.js
1592 ms
common.js
1733 ms
api.js
101 ms
regenerator-runtime.min.js
1732 ms
wp-polyfill.min.js
1733 ms
index.js
1734 ms
Digisource-Logo-vector-with-text.svg
337 ms
Digisource-Home-1.jpg
1626 ms
Our-Services-1.jpg
1059 ms
computer.png
548 ms
cloud-computing.png
590 ms
digital-services.png
635 ms
vpn.png
862 ms
Digisource-Client-Logos_9.png
798 ms
Digisource-Client-Logos_13.png
797 ms
Digisource-Client-Logos_11.png
817 ms
Digisource-Client-Logos_15.png
1068 ms
Digisource-Client-Logos_14.png
1076 ms
Digisource-Client-Logos_8.png
1084 ms
Digisource-Client-Logos_3.png
1141 ms
Digisource-Client-Logos_10.png
1341 ms
Digisource-Client-Logos_5.png
1355 ms
Digisource-Client-Logos_12.png
1365 ms
Digisource-Client-Logos_7.png
1371 ms
Digisource-Client-Logos_4.png
1429 ms
Digisource-Client-Logos_1.png
1905 ms
Digisource-Client-Logos_6.png
1926 ms
Digisource-Client-Logos_2.png
1650 ms
analytics.js
31 ms
h0GsssGi7VdzDgKjM-4d8hjWx-g.woff
47 ms
h0GsssGi7VdzDgKjM-4d8hjWx-s.ttf
56 ms
h0GxssGi7VdzDgKjM-4d8hBz5fuOH04.woff
70 ms
h0GxssGi7VdzDgKjM-4d8hBz5fuOH00.ttf
77 ms
h0GxssGi7VdzDgKjM-4d8hAX5vuOH04.woff
78 ms
h0GxssGi7VdzDgKjM-4d8hAX5vuOH00.ttf
82 ms
h0GxssGi7VdzDgKjM-4d8hAH4_uOH04.woff
79 ms
h0GxssGi7VdzDgKjM-4d8hAH4_uOH00.ttf
81 ms
h0GxssGi7VdzDgKjM-4d8hBj4vuOH04.woff
79 ms
h0GxssGi7VdzDgKjM-4d8hBj4vuOH00.ttf
80 ms
h0GxssGi7VdzDgKjM-4d8hB_4fuOH04.woff
82 ms
h0GxssGi7VdzDgKjM-4d8hB_4fuOH00.ttf
110 ms
h0GxssGi7VdzDgKjM-4d8hBb4PuOH04.woff
83 ms
h0GxssGi7VdzDgKjM-4d8hBb4PuOH00.ttf
109 ms
pxiByp8kv8JHgFVrLCz7Z1JlEw.woff
82 ms
pxiByp8kv8JHgFVrLCz7Z1JlEA.ttf
108 ms
pxiByp8kv8JHgFVrLDD4Z1JlEw.woff
110 ms
pxiByp8kv8JHgFVrLDD4Z1JlEA.ttf
113 ms
pxiByp8kv8JHgFVrLBT5Z1JlEw.woff
111 ms
pxiByp8kv8JHgFVrLBT5Z1JlEA.ttf
111 ms
pxiByp8kv8JHgFVrLEj6Z1JlEw.woff
111 ms
pxiByp8kv8JHgFVrLEj6Z1JlEA.ttf
112 ms
pxiByp8kv8JHgFVrLGT9Z1JlEw.woff
113 ms
pxiByp8kv8JHgFVrLGT9Z1JlEA.ttf
114 ms
pxiEyp8kv8JHgFVrJJnedA.woff
114 ms
pxiEyp8kv8JHgFVrJJnedw.ttf
114 ms
pxiByp8kv8JHgFVrLDz8Z1JlEw.woff
115 ms
pxiByp8kv8JHgFVrLDz8Z1JlEA.ttf
116 ms
pxiByp8kv8JHgFVrLFj_Z1JlEw.woff
116 ms
pxiByp8kv8JHgFVrLFj_Z1JlEA.ttf
117 ms
pxiGyp8kv8JHgFVrLPTufntG.woff
116 ms
pxiGyp8kv8JHgFVrLPTufntF.ttf
118 ms
modules.ttf
1555 ms
1Pt_g8LJRfWJmhDAuUsSQamb1W0lwk4S4VrMDr0fJg.woff
117 ms
1Pt_g8LJRfWJmhDAuUsSQamb1W0lwk4S4VrMDr0fJQ.ttf
118 ms
1Pt_g8LJRfWJmhDAuUsSQamb1W0lwk4S4WjMDr0fJg.woff
119 ms
1Pt_g8LJRfWJmhDAuUsSQamb1W0lwk4S4WjMDr0fJQ.ttf
119 ms
fa-brands-400.woff
1900 ms
fa-regular-400.woff
1801 ms
fa-solid-900.woff
2119 ms
collect
66 ms
1Pt_g8LJRfWJmhDAuUsSQamb1W0lwk4S4TbMDr0fJg.woff
71 ms
1Pt_g8LJRfWJmhDAuUsSQamb1W0lwk4S4TbMDr0fJQ.ttf
60 ms
1Pt_g8LJRfWJmhDAuUsSQamb1W0lwk4S4bbLDr0fJg.woff
51 ms
1Pt_g8LJRfWJmhDAuUsSQamb1W0lwk4S4bbLDr0fJQ.ttf
50 ms
1Pt_g8LJRfWJmhDAuUsSQamb1W0lwk4S4Y_LDr0fJg.woff
49 ms
1Pt_g8LJRfWJmhDAuUsSQamb1W0lwk4S4Y_LDr0fJQ.ttf
49 ms
recaptcha__en.js
57 ms
anchor
52 ms
anchor
128 ms
styles__ltr.css
4 ms
recaptcha__en.js
10 ms
webworker.js
114 ms
logo_48.png
100 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
33 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
34 ms
KFOlCnqEu92Fr1MmYUtfBBc9.ttf
35 ms
recaptcha__en.js
36 ms
reload
65 ms
digisource.co.za accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
digisource.co.za best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
digisource.co.za SEO score
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
Document uses legible font sizes
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Digisource.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 Digisource.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.
digisource.co.za
Open Graph data is detected on the main page of Digisource. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: