12.9 sec in total
1.3 sec
10.9 sec
637 ms
Welcome to ijump.co.za homepage info - get ready to check IJUMP best content for South Africa right away, or after learning these important things about ijump.co.za
Trampoline Arena
Visit ijump.co.zaWe analyzed Ijump.co.za page load time and found that the first response time was 1.3 sec and then it took 11.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
ijump.co.za performance score
name
value
score
weighting
Value6.2 s
3/100
10%
Value7.2 s
5/100
25%
Value14.5 s
1/100
10%
Value820 ms
35/100
30%
Value0.022
100/100
15%
Value14.5 s
9/100
10%
1348 ms
614 ms
545 ms
1382 ms
562 ms
Our browser made a total of 106 requests to load all elements on the main page. We found that 23% of them (24 requests) were addressed to the original Ijump.co.za, 25% (26 requests) were made to Static.xx.fbcdn.net and 18% (19 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (5.3 sec) belongs to the original domain Ijump.co.za.
Page size can be reduced by 285.0 kB (10%)
2.8 MB
2.5 MB
In fact, the total size of Ijump.co.za main page is 2.8 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 2.6 MB which makes up the majority of the site volume.
Potential reduce by 29.1 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 11.4 kB, which is 31% 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 29.1 kB or 79% of the original size.
Potential reduce by 146.7 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. IJUMP images are well optimized though.
Potential reduce by 70.4 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 70.4 kB or 68% of the original size.
Potential reduce by 38.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. Ijump.co.za needs all CSS files to be minified and compressed as it can save up to 38.8 kB or 83% of the original size.
Number of requests can be reduced by 38 (38%)
100
62
The browser has sent 100 CSS, Javascripts, AJAX and image requests in order to completely render the main page of IJUMP. 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 13 to 1 for CSS and as a result speed up the page load time.
ijump.co.za
1348 ms
home.php
614 ms
slick.css
545 ms
slick-theme.css
1382 ms
style.css
562 ms
jquery-1.11.0.min.js
9 ms
jquery-migrate-1.2.1.min.js
9 ms
jquery-ui.js
18 ms
slick.min.js
810 ms
jquery.smooth-scroll.js
561 ms
config.js
573 ms
expander.js
827 ms
css
99 ms
logo_small.png
308 ms
slideshow13.jpg
2564 ms
extrmfun.jpg
1676 ms
mascotfooter.jpg
954 ms
newsletterbutton.jpg
373 ms
virtualcardservicelogo.png
790 ms
SM_twitter.png
791 ms
SM_instagram.png
881 ms
SM_youtube.png
952 ms
SM_facebook.png
1194 ms
widgets.js
175 ms
dI-qzxlKVQA6TUC5RKSb36CWcynf_cDxXwCLxiixG1c.ttf
108 ms
AWM5wXtMJeRP-AcRTgT4qQ.ttf
116 ms
l1cOQ90roY9yC7voEhngDKCWcynf_cDxXwCLxiixG1c.ttf
117 ms
analytics.js
96 ms
likebox.php
286 ms
collect
24 ms
timeline.d11f7a3b3287fb94220e8ee6d03cc772.js
124 ms
collect
74 ms
syndication
199 ms
656749541866229760
427 ms
410ucuAGgaJ.css
65 ms
tSbl8xBI27R.css
84 ms
Czh0gDTFcBt.css
89 ms
VyhHmC9SnBT.css
94 ms
Ek6lpayKeeB.css
86 ms
q68gy-v_YMF.js
100 ms
FJmpeSpHpjS.js
148 ms
0wM5s1Khldu.js
165 ms
1bNoFZUdlYZ.js
169 ms
njO1TPvGzoR.js
164 ms
OloiM1PZafe.js
157 ms
LTv6ZK-5zxz.js
177 ms
1FCa-btixu2.js
162 ms
Oagsvfb4VWi.js
168 ms
pObvZSrFc_4.js
171 ms
Kt4tkgSRvHH.js
170 ms
H3EKDTObx05.js
170 ms
eR-qA8bp1RM.js
172 ms
1QuX41zDRrx.js
172 ms
10603349_932199933532871_1107050885797612804_n.jpg
197 ms
12278906_914344458651752_1118063399920222463_n.png
207 ms
11880319_10206301833198963_10512724546879490_n.jpg
206 ms
12718067_10154098017484474_4845496582742868104_n.jpg
241 ms
12278829_916889488377833_5401228789907151776_n.jpg
208 ms
12540717_215681858767155_1707959937026832982_n.jpg
206 ms
12438947_771768192929814_7114358765964273361_n.jpg
206 ms
12744370_899308713500592_8052318506885116301_n.jpg
329 ms
11536059_916390761758113_1897719879036583040_n.jpg
312 ms
12790911_10153284345907032_6786661141709061745_n.jpg
218 ms
12800173_472169989636018_5883667226298093803_n.jpg
216 ms
11205556_149075225435149_5620838196647701155_n.jpg
209 ms
12832339_974105869342277_6575270533937290802_n.jpg
217 ms
10426813_973188236100707_2405404376538923168_n.png
530 ms
944896_971853212900876_8096530817924029667_n.png
240 ms
1186204_971277122958485_1990679815774553863_n.jpg
240 ms
10527448_971277142958483_4252923051870021068_n.jpg
302 ms
1013343_971277119625152_6244922640309649841_n.jpg
272 ms
12809588_969526636466867_4992334015137506776_n.png
316 ms
wL6VQj7Ab77.png
154 ms
s7jcwEQH7Sx.png
155 ms
QDwYpIaRyfG.png
152 ms
K00K-UgnsKu.png
153 ms
gxbPuQdXIZP.png
38 ms
proxy.jpg
130 ms
proxy.jpg
148 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.dark.ltr.css
36 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.dark.ltr.css
89 ms
ligEPCOQ_normal.jpg
187 ms
Mv4fgDci_normal.jpg
102 ms
Cd1QI5DWIAEINxJ.jpg
120 ms
CdvSSCSW0AA-gF2.jpg:large
166 ms
CdlgBzLXIAEeDTu.jpg:small
156 ms
CdQZvQgVIAEwpwX.jpg
157 ms
CdGvP7rWIAE7eHL.jpg:large
188 ms
CdCvbvxVIAAVIaD.jpg
165 ms
Cc3OGdEWwAAcsg8.jpg
178 ms
CciuEGQWwAAtr-o.jpg:large
176 ms
CcC88WuWoAAYkXS.jpg:small
207 ms
Cb5VeCyUkAI_BHw.jpg:small
224 ms
CcIXwR7UEAEGJes.jpg:small
178 ms
CcIX0aNUMAEQZoi.jpg:small
180 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
101 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
146 ms
proxy.jpg
16 ms
I6-MnjEovm5.js
11 ms
pQrUxxo5oQp.js
4 ms
jot.html
29 ms
ajax-loader.gif
281 ms
slideshow01.jpg
5266 ms
slideshow02.jpg
3322 ms
slideshow03.jpg
2788 ms
slideshow05.jpg
2217 ms
ijump.co.za accessibility score
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
[aria-*] attributes do not match their roles
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Some elements have a [tabindex] value greater than 0
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
ijump.co.za best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
ijump.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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ijump.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 Ijump.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.
ijump.co.za
Open Graph description is not detected on the main page of IJUMP. 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: