10.1 sec in total
1.3 sec
8 sec
777 ms
Click here to check amazing Genergy content. Otherwise, check out these important facts you probably never knew about genergy.co.za
South Africa Commercial Solar Solutions to reduce electricity costs and the Impact of Loadshedding. Solar Panel installers | Renewable Energy
Visit genergy.co.zaWe analyzed Genergy.co.za page load time and found that the first response time was 1.3 sec and then it took 8.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
genergy.co.za performance score
name
value
score
weighting
Value5.3 s
7/100
10%
Value8.6 s
1/100
25%
Value18.6 s
0/100
10%
Value1,380 ms
16/100
30%
Value0
100/100
15%
Value25.0 s
0/100
10%
1290 ms
259 ms
520 ms
744 ms
743 ms
Our browser made a total of 101 requests to load all elements on the main page. We found that 76% of them (77 requests) were addressed to the original Genergy.co.za, 21% (21 requests) were made to Fonts.gstatic.com and 1% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (3.2 sec) belongs to the original domain Genergy.co.za.
Page size can be reduced by 143.0 kB (11%)
1.3 MB
1.1 MB
In fact, the total size of Genergy.co.za main page is 1.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. 65% of websites need less resources to load. Images take 664.8 kB which makes up the majority of the site volume.
Potential reduce by 131.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. 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 131.1 kB or 80% of the original size.
Potential reduce by 1.8 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. Genergy images are well optimized though.
Potential reduce by 7.3 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 2.9 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. Genergy.co.za has all CSS files already compressed.
Number of requests can be reduced by 69 (90%)
77
8
The browser has sent 77 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Genergy. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 41 to 1 for JavaScripts and from 30 to 1 for CSS and as a result speed up the page load time.
genergy.co.za
1290 ms
frontend.css
259 ms
style.css
520 ms
style.css
744 ms
style.min.css
743 ms
theme.min.css
750 ms
header-footer.min.css
760 ms
frontend-lite.min.css
1012 ms
post-7.css
773 ms
custom-jet-blocks.css
1000 ms
jet-elements.css
1003 ms
jet-elements-skin.css
1011 ms
swiper.min.css
1018 ms
frontend-lite.min.css
1033 ms
uael-frontend.min.css
1509 ms
jet-tricks-frontend.css
1256 ms
all.min.css
1266 ms
v4-shims.min.css
1589 ms
post-2.css
1270 ms
post-105.css
1293 ms
post-113.css
1504 ms
post-10360.css
1517 ms
style.css
1522 ms
css
63 ms
jquery.min.js
1547 ms
jquery-migrate.min.js
1750 ms
v4-shims.min.js
1755 ms
js
72 ms
widget-icon-list.min.css
1795 ms
widget-nav-menu.min.css
1795 ms
animations.min.css
1877 ms
post-10410.css
1883 ms
basic.min.css
1998 ms
theme-ie11.min.css
2012 ms
theme.min.css
2027 ms
scripts.js
2070 ms
element.js
47 ms
njt-whatsapp.js
2128 ms
whatsapp-button.js
2245 ms
hello-frontend.min.js
1994 ms
jquery.sticky.min.js
1750 ms
jquery.smartmenus.min.js
1545 ms
uael-nav-menu.min.js
1578 ms
jquery_resize.min.js
1643 ms
js_cookie.min.js
1743 ms
imagesloaded.min.js
1732 ms
jquery-numerator.min.js
1537 ms
dom-ready.min.js
1533 ms
hooks.min.js
1589 ms
i18n.min.js
1627 ms
a11y.min.js
1733 ms
jquery.json.min.js
1719 ms
gravityforms.min.js
1533 ms
placeholders.jquery.min.js
1528 ms
utils.min.js
1585 ms
vendor-theme.min.js
1603 ms
scripts-theme.min.js
1495 ms
uael-frontend.min.js
1484 ms
webpack-pro.runtime.min.js
1521 ms
webpack.runtime.min.js
1526 ms
frontend-modules.min.js
1563 ms
frontend.min.js
1866 ms
waypoints.min.js
1494 ms
core.min.js
1454 ms
frontend.min.js
1484 ms
UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuOKfAZ9hjQ.ttf
81 ms
UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuDyfAZ9hjQ.ttf
87 ms
UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuLyeAZ9hjQ.ttf
108 ms
UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuLyfAZ9hjQ.ttf
108 ms
UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuI6fAZ9hjQ.ttf
100 ms
UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuGKYAZ9hjQ.ttf
108 ms
UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuFuYAZ9hjQ.ttf
108 ms
UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuDyYAZ9hjQ.ttf
107 ms
UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuBWYAZ9hjQ.ttf
116 ms
elements-handlers.min.js
1501 ms
LDI2apCSOBg7S-QT7pa8FvOreeI.ttf
33 ms
LDI2apCSOBg7S-QT7pbYF_OreeI.ttf
41 ms
LDI2apCSOBg7S-QT7pb0EPOreeI.ttf
41 ms
LDIxapCSOBg7S-QT7p4HM-M.ttf
42 ms
LDI2apCSOBg7S-QT7pasEfOreeI.ttf
40 ms
iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-WYiFV0Uw.ttf
41 ms
iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-B4iFV0Uw.ttf
43 ms
iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-NYiFV0Uw.ttf
44 ms
iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-2Y-FV0Uw.ttf
43 ms
iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-4I-FV0Uw.ttf
43 ms
iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-h4-FV0Uw.ttf
44 ms
iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-ro-FV0Uw.ttf
45 ms
jet-blocks.min.js
1519 ms
waypoints.js
1608 ms
jet-elements.min.js
1493 ms
popperjs.js
1538 ms
tippy-bundle.js
1550 ms
jet-tricks-frontend.js
1588 ms
fa-solid-900.woff
3154 ms
fa-regular-400.woff
1613 ms
Genergy-Logo-Reverse.svg
1508 ms
G0181308E-1024x683.jpg
2285 ms
solar-power-solutions-south-africa.jpg
2304 ms
Terry-Billson.jpg
2135 ms
Astrid-Forbes.jpg
2204 ms
Genergy-Logo.svg
1613 ms
genergy.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.
genergy.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
Page has valid source maps
genergy.co.za SEO score
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 Genergy.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 Genergy.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.
genergy.co.za
Open Graph data is detected on the main page of Genergy. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: