27.1 sec in total
8.1 sec
18.5 sec
509 ms
Visit livingwaters.co.za now to see the best up-to-date Livingwaters content and also check out these interesting facts you probably never knew about livingwaters.co.za
Towards Jesus
Visit livingwaters.co.zaWe analyzed Livingwaters.co.za page load time and found that the first response time was 8.1 sec and then it took 19.1 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.
livingwaters.co.za performance score
name
value
score
weighting
Value0.8 s
100/100
10%
Value0.8 s
100/100
25%
Value0.9 s
100/100
10%
Value0 ms
100/100
30%
Value0.123
84/100
15%
Value0.8 s
100/100
10%
8052 ms
559 ms
801 ms
812 ms
1057 ms
Our browser made a total of 107 requests to load all elements on the main page. We found that 68% of them (73 requests) were addressed to the original Livingwaters.co.za, 11% (12 requests) were made to 0 and 4% (4 requests) were made to F.vimeocdn.com. The less responsive or slowest element that took the longest time to load (8.1 sec) belongs to the original domain Livingwaters.co.za.
Page size can be reduced by 1.2 MB (40%)
3.0 MB
1.8 MB
In fact, the total size of Livingwaters.co.za main page is 3.0 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 1.6 MB which makes up the majority of the site volume.
Potential reduce by 79.6 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 22.2 kB, which is 23% 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 79.6 kB or 84% of the original size.
Potential reduce by 83.5 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. Livingwaters images are well optimized though.
Potential reduce by 581.6 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 581.6 kB or 68% of the original size.
Potential reduce by 453.7 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. Livingwaters.co.za needs all CSS files to be minified and compressed as it can save up to 453.7 kB or 87% of the original size.
Number of requests can be reduced by 55 (56%)
98
43
The browser has sent 98 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Livingwaters. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 34 to 1 for JavaScripts and from 23 to 1 for CSS and as a result speed up the page load time.
livingwaters.co.za
8052 ms
wp-emoji-release.min.js
559 ms
ut-responsive-grid.css
801 ms
font-awesome.css
812 ms
ut.animate.css
1057 ms
ut.elastislide.css
560 ms
ut.fancyrotator.css
1315 ms
ut.shortcode.css
1326 ms
sb-style.css
2157 ms
styles.css
1325 ms
settings.css
1827 ms
checkbox.min.css
1661 ms
ut-fontface.css
1855 ms
css
22 ms
css
32 ms
flexslider.css
1846 ms
prettyPhoto.css
2098 ms
ut-superfish.css
2170 ms
style.css
2338 ms
jetpack.css
2895 ms
wpgmza_style.css
2378 ms
jquery.js
3327 ms
jquery-migrate.min.js
2646 ms
jquery.themepunch.tools.min.js
3420 ms
jquery.themepunch.revolution.min.js
3582 ms
modernizr.min.js
2939 ms
jquery.flexslider-min.js
3415 ms
jquery.elastislide.js
3452 ms
jquery.queryloader2.min.js
3458 ms
jquery.lazy.load.js
3838 ms
jquery.form.min.js
3218 ms
scripts.js
3215 ms
tabs.collapse.min.js
3258 ms
jquery.visible.min.js
3259 ms
jquery.appear.js
3377 ms
jquery.fitvids.js
3644 ms
ut.scplugin.js
3728 ms
devicepx-jetpack.js
3 ms
gprofiles.js
59 ms
wpgroho.js
3741 ms
toucheffects.min.js
3784 ms
jquery.easing.min.js
3781 ms
e-201611.js
3 ms
superfish.min.js
3900 ms
retina.min.js
4080 ms
jquery.parallax.min.js
4173 ms
jquery.scrollTo.min.js
3926 ms
jquery.waypoints.min.js
3692 ms
jquery.prettyPhoto.min.js
3957 ms
jquery.fittext.min.js
3808 ms
ut-init.js
4027 ms
style.css
3904 ms
lw-logo.png
555 ms
bg-blue.jpg
1838 ms
raleway-regular-webfont.woff
851 ms
raleway-semibold-webfont.woff
827 ms
pastors1.jpg
2052 ms
dynamic.png
1575 ms
creative.png
1800 ms
everyone.png
1315 ms
lw.png
562 ms
Towards-Jesus1.jpg
1571 ms
Easter-Web-Banner.jpg
1505 ms
Thrive-Vision.jpg
1537 ms
lw-logo.png
1347 ms
worship.jpg
1641 ms
bIcY3_3JNqUVRAQQRNVteQ.ttf
250 ms
raleway-bold-webfont.woff
1539 ms
raleway-light-webfont.woff
1582 ms
fontawesome-webfont.svg
3277 ms
fontawesome-webfont.woff
2480 ms
raleway-medium-webfont.woff
2238 ms
hovercard.css
124 ms
services.css
162 ms
loader.gif
1876 ms
shadow2.png
1875 ms
ajax-loader.gif
1916 ms
129194636
348 ms
157982233
98 ms
brooklyn-logo.png
525 ms
g.gif
5 ms
lw-logo.png
3461 ms
Towards-Jesus1.jpg
4245 ms
player.js
78 ms
player.css
53 ms
ga.js
132 ms
vuid.min.js
60 ms
proxy.html
50 ms
559388569.jpg
125 ms
9713708_60x60.jpg
46 ms
__utm.gif
13 ms
522097796.jpg
57 ms
__utm.gif
13 ms
bg-blue.jpg
1913 ms
pastors1.jpg
2016 ms
dynamic.png
1516 ms
everyone.png
1320 ms
worship.jpg
1490 ms
creative.png
1735 ms
lw.png
985 ms
Easter-Web-Banner.jpg
1858 ms
Thrive-Vision.jpg
1244 ms
loader.gif
712 ms
shadow2.png
1004 ms
ajax-loader.gif
1099 ms
lw-logo.png
1271 ms
welcome-home.png
509 ms
livingwaters.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.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
Image elements do not have [alt] attributes
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.
livingwaters.co.za best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
livingwaters.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
Image elements do not have [alt] attributes
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
N/A
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Livingwaters.co.za can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Livingwaters.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.
livingwaters.co.za
Open Graph data is detected on the main page of Livingwaters. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: