6.4 sec in total
1.5 sec
4.6 sec
344 ms
Welcome to wghs.co.za homepage info - get ready to check Wghs best content for South Africa right away, or after learning these important things about wghs.co.za
Visit wghs.co.zaWe analyzed Wghs.co.za page load time and found that the first response time was 1.5 sec and then it took 5 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
wghs.co.za performance score
name
value
score
weighting
Value7.2 s
1/100
10%
Value8.4 s
2/100
25%
Value33.7 s
0/100
10%
Value520 ms
56/100
30%
Value0
100/100
15%
Value21.0 s
1/100
10%
1463 ms
80 ms
230 ms
154 ms
156 ms
Our browser made a total of 115 requests to load all elements on the main page. We found that 89% of them (102 requests) were addressed to the original Wghs.co.za, 3% (3 requests) were made to S.gravatar.com and 2% (2 requests) were made to Wghswebsite.netelligent.co.za. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Wghs.co.za.
Page size can be reduced by 1.7 MB (52%)
3.3 MB
1.6 MB
In fact, the total size of Wghs.co.za main page is 3.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. 70% of websites need less resources to load. Images take 1.3 MB which makes up the majority of the site volume.
Potential reduce by 43.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. 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 43.6 kB or 80% of the original size.
Potential reduce by 151.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. Obviously, Wghs needs image optimization as it can save up to 151.5 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 1.0 MB
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 1.0 MB or 78% of the original size.
Potential reduce by 516.1 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. Wghs.co.za needs all CSS files to be minified and compressed as it can save up to 516.1 kB or 81% of the original size.
Number of requests can be reduced by 91 (81%)
113
22
The browser has sent 113 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Wghs. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 54 to 1 for JavaScripts and from 32 to 1 for CSS and as a result speed up the page load time.
www.wghs.co.za
1463 ms
wp-emoji-release.min.js
80 ms
dashicons.min.css
230 ms
thickbox.css
154 ms
amazingslider-1.css
156 ms
style.css
239 ms
karma-cool-blue.css
164 ms
secondary-cherry.css
165 ms
_font-awesome.css
232 ms
_mobile.css
234 ms
gfullmap.css
250 ms
minitwitter.css
250 ms
pec-wp-user.css
304 ms
pec-wp-common.css
306 ms
bootstrap.min.css
317 ms
bootstrap-theme.min.css
313 ms
bootstrap-datetimepicker.min.css
331 ms
bootstrap-colorpicker.min.css
332 ms
ladda-themeless.min.css
379 ms
bootstrap-select.min.css
381 ms
jquery.fileupload.css
389 ms
simple-staff-list-public.css
392 ms
fullcalendar.css
408 ms
fullcalendar.custom.css
454 ms
jetpack.css
458 ms
lightbox.min.css
464 ms
jquery.js
475 ms
jquery-migrate.min.js
488 ms
amazingslider.js
577 ms
initslider-1.js
530 ms
swfobject.js
533 ms
moment.min.js
553 ms
fullcalendar.js
739 ms
gcal.js
606 ms
bootstrap.min.js
627 ms
js
33 ms
jquery.cu3er.js
205 ms
css
68 ms
font-awesome.min.css
250 ms
devicepx-jetpack.js
12 ms
gprofiles.js
58 ms
e-201611.js
5 ms
calendar-jos.css
654 ms
color-picker.min.css
626 ms
content-shortcodes.css
566 ms
bootstrap-datetimepicker.min.js
560 ms
bootstrap-colorpicker.min.js
609 ms
jquery.bootstrap-growl.min.js
622 ms
spin.min.js
567 ms
ladda.min.js
568 ms
bootstrap-select.min.js
587 ms
load-image.all.min.js
602 ms
jquery.ui.widget.js
619 ms
jquery.fileupload.js
628 ms
jquery.fileupload-process.js
578 ms
jquery.fileupload-image.js
594 ms
jquery.fileupload-validate.js
586 ms
calendar.js
681 ms
simple-staff-list-public.js
618 ms
calendar.js
623 ms
calendar-setup.js
583 ms
calendar_function.js
594 ms
thickbox.js
590 ms
custom-main.js
660 ms
superfish.js
646 ms
jquery.flexslider.js
643 ms
jquery.fitvids.js
617 ms
jquery.isotope.js
608 ms
core.min.js
625 ms
widget.min.js
622 ms
tabs.min.js
624 ms
accordion.min.js
597 ms
jquery.prettyPhoto.js
601 ms
comment-reply.js
611 ms
gfullmap.js
604 ms
mouse.min.js
601 ms
draggable.min.js
587 ms
droppable.min.js
584 ms
resizable.min.js
564 ms
wpgroho.js
561 ms
jquery.touchwipe.min.js
563 ms
jquery.lightbox.min.js
528 ms
wp-embed.min.js
575 ms
WGHSLOGOWEBSITEFINALWGHS.png
232 ms
overlay-rays.png
494 ms
global-sprite.png
495 ms
bg-div-main.png
492 ms
overlay-abstract.png
494 ms
s01.JPG
860 ms
s02.jpg
795 ms
s03.jpg
801 ms
s04.jpg
780 ms
loader-default.gif
528 ms
facERC-190x111.png
559 ms
wghs-50-190x111.jpg
605 ms
Johnstone-farewell-190x111.jpg
637 ms
bg-div-footer-top.png
682 ms
overlay-stars.png
715 ms
bg-footer-bottom-cool-blue.png
758 ms
widgets.js
15 ms
7.gif
812 ms
1.gif
832 ms
5.gif
845 ms
fontawesome-webfont.woff
1011 ms
2.gif
813 ms
0.gif
867 ms
fontawesome-webfont.woff
3 ms
hovercard.css
33 ms
services.css
54 ms
bottomshadow-110-95-1.png
454 ms
playvideo-64-64-0.png
463 ms
arrows-48-48-3.png
468 ms
loadingAnimation.gif
591 ms
g.gif
6 ms
fullcalendar.print.css
86 ms
wghs.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.
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
wghs.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
General
Impact
Issue
Detected JavaScript libraries
wghs.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 Wghs.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 Wghs.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.
wghs.co.za
Open Graph description is not detected on the main page of Wghs. 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: