1.9 sec in total
267 ms
1 sec
557 ms
Visit wygs.org now to see the best up-to-date WYGS content and also check out these interesting facts you probably never knew about wygs.org
Southern Gospel Music radio station and media ministry
Visit wygs.orgWe analyzed Wygs.org page load time and found that the first response time was 267 ms and then it took 1.6 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.
wygs.org performance score
name
value
score
weighting
Value4.8 s
12/100
10%
Value8.4 s
2/100
25%
Value7.2 s
30/100
10%
Value1,860 ms
9/100
30%
Value0.001
100/100
15%
Value18.7 s
3/100
10%
267 ms
20 ms
76 ms
116 ms
114 ms
Our browser made a total of 85 requests to load all elements on the main page. We found that 13% of them (11 requests) were addressed to the original Wygs.org, 29% (25 requests) were made to Cdn-js.socastsrm.com and 19% (16 requests) were made to Media-cdn.socastsrm.com. The less responsive or slowest element that took the longest time to load (532 ms) relates to the external source Connect.soundcloud.com.
Page size can be reduced by 130.4 kB (14%)
918.8 kB
788.4 kB
In fact, the total size of Wygs.org main page is 918.8 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. 65% of websites need less resources to load. Javascripts take 700.0 kB which makes up the majority of the site volume.
Potential reduce by 76.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 76.0 kB or 75% of the original size.
Potential reduce by 0 B
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. WYGS images are well optimized though.
Potential reduce by 48.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.
Potential reduce by 5.6 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. Wygs.org has all CSS files already compressed.
Number of requests can be reduced by 55 (67%)
82
27
The browser has sent 82 CSS, Javascripts, AJAX and image requests in order to completely render the main page of WYGS. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 42 to 1 for JavaScripts and from 15 to 1 for CSS and as a result speed up the page load time.
www.wygs.org
267 ms
wp-emoji-release.min.js
20 ms
js_composer.min.css
76 ms
bootstrap.css
116 ms
custom.css
114 ms
global-theme.css
115 ms
frontend.css
124 ms
style.min.css
89 ms
socast-media-library-public.css
101 ms
jquery.js
135 ms
jquery-ui.min.js
135 ms
popper-1.14.3.min.js
156 ms
bootstrap.min.js
135 ms
json2.js
155 ms
custom.js
135 ms
lightBox.js
163 ms
socast.jquery.frontend.js
162 ms
frontend.js
162 ms
jquery.ui.kk-chronomasonry.js
166 ms
jquery.ui.socastTouch.js
162 ms
poll.js
162 ms
api.js
174 ms
OneSignalSDK.js
168 ms
css
173 ms
css
178 ms
style.css
167 ms
scripts.js
167 ms
votd.write.callback.js
160 ms
171 ms
weather.css
120 ms
eventDisplay.css
120 ms
activityStream.css
131 ms
multiColumnLayout.css
131 ms
css-var-polyfill.js
165 ms
wp-embed.min.js
105 ms
js_composer_front.min.js
105 ms
featureRotator.js
166 ms
skrollr.min.js
109 ms
nowPlaying.js
165 ms
lastPlayed.js
166 ms
eventCalendarList.js
166 ms
blogNews.js
168 ms
sdk.js
532 ms
activityStreamGlobal.js
166 ms
activityStreamObject.js
166 ms
polyfill.js
167 ms
iframe_api
175 ms
jquery.form.js
167 ms
api.js
169 ms
multiColumnLayout.js
168 ms
recaptcha__en.js
123 ms
gtm.js
162 ms
wygs-white.png
154 ms
sound.gif
72 ms
wsymbol_0008_clear_sky_night.png
220 ms
itunes_badge_small.svg
90 ms
id1551836350
346 ms
id1697554375
404 ms
225 ms
wygs-gold-give-uppercase-300x102.png
85 ms
facebook.png
84 ms
ios.png
84 ms
android.png
85 ms
oms-wnc-relief-2024.jpg
335 ms
sidewalk.png
142 ms
wygs-prayer-wall.png
133 ms
wygslogo-scaled.jpg
142 ms
placeholder-audio_1600x1600-opt.jpg
143 ms
indicator-big.gif
133 ms
i-voted-2-300x249-1.jpeg
155 ms
gobble-wobble-united-way-cummins.jpeg
158 ms
i-voted-1-300x226-1.jpeg
155 ms
blacksheep-craft-pizza-logo-300x300-1.jpeg
156 ms
PoweredBySoCastTagline-White.png
156 ms
font
129 ms
listenlive-black-300x95-1.gif
72 ms
js
52 ms
360057661571
174 ms
musickit.js
111 ms
web-embed.js
115 ms
musickit-components.js
115 ms
web-embed.css
63 ms
www-widgetapi.js
60 ms
eventCalendar
73 ms
eventCalendar
69 ms
wygs.org 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
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
wygs.org 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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
wygs.org 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
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 Wygs.org 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 Wygs.org 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.
wygs.org
Open Graph description is not detected on the main page of WYGS. 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: