10.3 sec in total
2.2 sec
7.9 sec
237 ms
Visit comealive.co.za now to see the best up-to-date Come Alive content and also check out these interesting facts you probably never knew about comealive.co.za
Come Alive is a Website Development House focusing on web design & development, hosting, email, SEO, Google Ads, social media and more.
Visit comealive.co.zaWe analyzed Comealive.co.za page load time and found that the first response time was 2.2 sec and then it took 8.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.
comealive.co.za performance score
name
value
score
weighting
Value7.4 s
1/100
10%
Value38.3 s
0/100
25%
Value29.6 s
0/100
10%
Value1,330 ms
17/100
30%
Value0.535
14/100
15%
Value35.9 s
0/100
10%
2164 ms
524 ms
837 ms
840 ms
837 ms
Our browser made a total of 146 requests to load all elements on the main page. We found that 94% of them (137 requests) were addressed to the original Comealive.co.za, 3% (4 requests) were made to Google-analytics.com and 1% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (2.7 sec) belongs to the original domain Comealive.co.za.
Page size can be reduced by 952.2 kB (30%)
3.2 MB
2.2 MB
In fact, the total size of Comealive.co.za main page is 3.2 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. 55% of websites need less resources to load. Images take 2.0 MB which makes up the majority of the site volume.
Potential reduce by 89.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 89.0 kB or 79% of the original size.
Potential reduce by 101.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. Come Alive images are well optimized though.
Potential reduce by 427.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 427.4 kB or 64% of the original size.
Potential reduce by 334.4 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. Comealive.co.za needs all CSS files to be minified and compressed as it can save up to 334.4 kB or 84% of the original size.
Number of requests can be reduced by 91 (63%)
144
53
The browser has sent 144 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Come Alive. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 38 to 1 for JavaScripts and from 41 to 1 for CSS and as a result speed up the page load time.
comealive.co.za
2164 ms
k2.css
524 ms
jf_icheck_fixes.min.css
837 ms
jf_icheck_demo.min.css
840 ms
_all.min.css
837 ms
_all.min.css
841 ms
_all.min.css
843 ms
_all.min.css
839 ms
polaris.min.css
1103 ms
futurico.min.css
1102 ms
style.css
1106 ms
jf_menu.css
525 ms
master.css
529 ms
jf_custom_style-f714402ce283d16390e7c894f1430f5e.css
536 ms
jf_custom_kunena_style-d669080688a828ab7398b92abdc69d11.css
536 ms
jf_custom_jomsocial_style-68e00049ed014a261184e84cd3e77e94.css
536 ms
jf_mediaqueries.css
786 ms
jf_features_services.css
790 ms
jf_features_k2.css
793 ms
jf_features_testimonials.css
797 ms
jf_features_mobile_menu.css
796 ms
css
33 ms
jf_grid_responsive996.css
798 ms
jf_typo_00_base.css
1051 ms
jf_typo_01_core.css
1055 ms
font-awesome.min.css
22 ms
jf_typo_02_tabs.css
1059 ms
jf_typo_03_accordions.css
1058 ms
jf_typo_04_toggles.css
1060 ms
jf_typo_05_tables.css
1061 ms
jf_typo_06_pricing_tables.css
1316 ms
jf_typo_07_image_video_frames.css
1318 ms
jf_typo_09_social_icons.css
1319 ms
jf_typo_10_special_boxes.css
1321 ms
jf_custom.css
1322 ms
jf_typo_08_tooltips.css
1324 ms
jf_contact_info.min.css
1101 ms
jf_quovolver.min.css
1097 ms
jf_recent_tweets.min.css
1098 ms
jf_elastislide.min.css
1353 ms
jf_our_friends.min.css
1354 ms
jf_flexslider.min.css
1357 ms
mootools-core.js
1839 ms
core.js
1575 ms
caption.js
1572 ms
mootools-more.js
2374 ms
jquery.min.js
38 ms
jquerynoconflict.js
1579 ms
jquery-migrate.min.js
1580 ms
k2.js
1834 ms
jf_mouse_loader.min.js
1361 ms
jquery.nicescroll.min.js
1621 ms
jquery.icheck.min.js
1361 ms
jf_icheck_demo.min.js
1611 ms
responsiveslides.min.js
1612 ms
pirobox_jquery_ui.min.js
1618 ms
pirobox_extended-1.3.min.js
1627 ms
modernizr.custom.js
1627 ms
jquery.dlmenu.min.js
1873 ms
jf_mobile_menu.min.js
1875 ms
jf_typo_02_tabs.min.js
1880 ms
jf_typo_10_special_boxes.min.js
1883 ms
jquery.easing.min.js
1891 ms
jf.min.js
1891 ms
jf_typo_08_tooltips.min.js
2138 ms
browser-engines.js
1832 ms
rokmediaqueries.js
1853 ms
rokmediaqueries.js
1854 ms
responsive.js
2093 ms
jquery.quovolver.min.js
2138 ms
twitterFetcher_v9_min.js
2143 ms
modernizr.custom.17475.js
2147 ms
jquerypp.custom.min.js
2156 ms
jquery.elastislide.min.js
2156 ms
jquery.flexslider-min-2.1.js
2442 ms
responsive-selectbox.js
1864 ms
jquery.waitforimages.js
1631 ms
jquery.tipsy.min.js
1652 ms
ga.js
46 ms
logo_200x210.png
536 ms
jf_header_shadow.png
273 ms
jf_header_bg.png
272 ms
jf_logo.png
790 ms
jf_menutop_parent.png
267 ms
jf_menutop_subparent.png
268 ms
jf_search.png
531 ms
fibre_1.png
1885 ms
fibre-line-speed.png
540 ms
slide1_1.png
537 ms
slide1_2.png
1321 ms
slide2_1.png
1879 ms
slide2_2.png
1363 ms
slide5_1.png
1335 ms
slide5_2.png
1057 ms
slide4_1.png
1890 ms
slide4_2.png
1588 ms
slide3_1.png
2128 ms
slide3_2.png
1627 ms
slide8_1.png
2117 ms
slide8_2.png
1894 ms
jf_showcase_1.png
2142 ms
jf_showcase_2.png
2148 ms
jf_showcase_3.png
2154 ms
faces-thumb.jpg
2160 ms
bakerandpartners-thumb.jpg
2383 ms
gelvenor-thumb.png
2395 ms
StanleysFacebook_small.png
2407 ms
ASC.png
2415 ms
mason-west-thumb.jpg
2420 ms
033.png
2427 ms
supashape-thumb.jpg
2648 ms
Camp_Orchards.png
2660 ms
colleco-thumb.jpg
2669 ms
southy-thumb.jpg
2679 ms
Gemlab-thumb.jpg
2683 ms
jf_search.png
267 ms
429260229599977472
189 ms
YDAoLskQQ5MOAgvHUQCcLRTHiN2BPBirwIkMLKUspj4.woff
116 ms
analytics.js
110 ms
new_skin.png
271 ms
new_skin_top.png
273 ms
new_skin_left.png
270 ms
mlp-loader-2.gif
268 ms
close.png
275 ms
buttons.png
389 ms
loading_2.gif
530 ms
jf_flex_arrows.png
533 ms
__utm.gif
12 ms
collect
11 ms
supashape_2.png
2434 ms
MyBG_final.png
2649 ms
HWT.jpg
2661 ms
FM.jpg
2664 ms
gelvenor-logo.jpg
2424 ms
jf_bottom_pattern.png
2422 ms
jf_footer_shadow.png
2424 ms
social_login_illustr.jpg
2642 ms
jf_list.png
2407 ms
jf_social_icons_v3.png
2144 ms
jf_powered_by.png
1891 ms
jf_scrolltop_btn.png
1878 ms
jf_system_msg_close.png
1862 ms
jf_loadtransition.gif
1856 ms
jf_ie_opaciry_050.png
264 ms
jf_elastislide_zoom.png
266 ms
jf_elastislide_nav.png
264 ms
comealive.co.za accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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.
comealive.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
Browser errors were logged to the console
Page has valid source maps
comealive.co.za SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Comealive.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 Comealive.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.
comealive.co.za
Open Graph description is not detected on the main page of Come Alive. 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: