18.4 sec in total
1 sec
16.9 sec
475 ms
Visit perpetuaim.co.za now to see the best up-to-date Perpetua Im content and also check out these interesting facts you probably never knew about perpetuaim.co.za
Investing with clarity, conviction and discipline, we are rooted in the pursuit of investment insight and continuous excellence for our clients.
Visit perpetuaim.co.zaWe analyzed Perpetuaim.co.za page load time and found that the first response time was 1 sec and then it took 17.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster.
perpetuaim.co.za performance score
name
value
score
weighting
Value7.3 s
1/100
10%
Value25.4 s
0/100
25%
Value27.5 s
0/100
10%
Value2,060 ms
7/100
30%
Value0.001
100/100
15%
Value26.3 s
0/100
10%
1048 ms
7317 ms
757 ms
1459 ms
1098 ms
Our browser made a total of 116 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Perpetuaim.co.za, 89% (103 requests) were made to Perpetua.co.za and 8% (9 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (7.3 sec) relates to the external source Perpetua.co.za.
Page size can be reduced by 330.7 kB (10%)
3.2 MB
2.8 MB
In fact, the total size of Perpetuaim.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. 70% of websites need less resources to load. Images take 2.1 MB which makes up the majority of the site volume.
Potential reduce by 215.7 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 215.7 kB or 87% of the original size.
Potential reduce by 107.9 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. Perpetua Im images are well optimized though.
Potential reduce by 1.7 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.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. Perpetuaim.co.za has all CSS files already compressed.
Number of requests can be reduced by 84 (87%)
97
13
The browser has sent 97 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Perpetua Im. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 49 to 1 for JavaScripts and from 37 to 1 for CSS and as a result speed up the page load time.
perpetuaim.co.za
1048 ms
perpetua.co.za
7317 ms
animate.min.css
757 ms
style.css
1459 ms
jet-popup-frontend.css
1098 ms
style.css
1136 ms
jet-elements.css
1146 ms
jet-elements-skin.css
1144 ms
elementor-icons.min.css
1155 ms
frontend.min.css
1830 ms
swiper.min.css
1520 ms
font-awesome.min.css
1532 ms
frontend.min.css
1915 ms
post-7877.css
1540 ms
frontend.min.css
2195 ms
jet-tabs-frontend.css
1905 ms
flatpickr.min.css
1958 ms
style.css
1959 ms
she-header-style.css
2214 ms
global.css
2293 ms
post-6.css
2298 ms
all.min.css
2307 ms
v4-shims.min.css
2312 ms
post-56.css
2563 ms
post-20443.css
2560 ms
general.min.css
2675 ms
post-25.css
2676 ms
post-49.css
2694 ms
css
41 ms
fontawesome.min.css
2696 ms
brands.min.css
2930 ms
solid.min.css
2932 ms
wplp_front.css
3056 ms
jquery.min.js
3068 ms
jquery-migrate.min.js
3079 ms
webfont.min.js
3083 ms
utils.min.js
3301 ms
v4-shims.min.js
3302 ms
js
68 ms
post-22382.css
3073 ms
post-22385.css
2693 ms
post-22397.css
2375 ms
post-36163.css
2339 ms
animations.min.css
2615 ms
she-header.js
2522 ms
wc-quick-view.js
2826 ms
underscore.min.js
2517 ms
frontend.min.js
2762 ms
jet-plugins.js
2452 ms
anime.min.js
2510 ms
jquery.waypoints.min.js
2214 ms
jet-popup-frontend.js
2461 ms
jquery.sonar.min.js
2413 ms
lazy-load.js
2408 ms
general.min.js
2461 ms
jquery.smartmenus.min.js
2212 ms
url-polyfill.min.js
2455 ms
imagesloaded.min.js
2454 ms
wdt.chartsRender.min.js
2455 ms
Chart.js
2831 ms
wdt.chartJS.min.js
2474 ms
slick.min.js
2229 ms
webpack-pro.runtime.min.js
2488 ms
webpack.runtime.min.js
2456 ms
frontend-modules.min.js
2458 ms
wp-polyfill-inert.min.js
2460 ms
regenerator-runtime.min.js
2458 ms
wp-polyfill.min.js
2508 ms
hooks.min.js
2581 ms
i18n.min.js
2448 ms
frontend.min.js
2448 ms
waypoints.min.js
2439 ms
css
44 ms
core.min.js
2441 ms
swiper.min.js
2524 ms
share-link.min.js
2588 ms
dialog.min.js
2463 ms
frontend.min.js
2448 ms
preloaded-elements-handlers.min.js
2454 ms
jet-elements.min.js
2429 ms
jet-popup-elementor-frontend.js
2462 ms
UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuLyfAZ9hjg.woff
158 ms
UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuI6fAZ9hjg.woff
158 ms
UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuOKfAZ9hjg.woff
222 ms
UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuDyfAZ9hjg.woff
227 ms
UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuLyeAZ9hjg.woff
248 ms
UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuGKYAZ9hjg.woff
249 ms
UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuFuYAZ9hjg.woff
248 ms
UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuDyYAZ9hjg.woff
247 ms
UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuBWYAZ9hjg.woff
246 ms
jet-tabs-frontend.min.js
2503 ms
preloaded-modules.min.js
2300 ms
jquery.sticky.min.js
2285 ms
wp-util.min.js
2305 ms
frontend.min.js
2647 ms
frontend.min.js
2554 ms
flatpickr.min.js
2342 ms
Signika-Light.woff
2634 ms
Signika-Regular.woff
2671 ms
Signika-SemiBold.woff
2303 ms
Signika-Bold.woff
2959 ms
fa-solid-900.woff
2941 ms
fa-regular-400.woff
2395 ms
fa-brands-400.woff
2343 ms
jupiterx.woff
2628 ms
Perp-white-logo-no-copyright-1024x355.png
2636 ms
perp-colour-logo.png
3407 ms
perp-colour-logo-1024x355.png
2416 ms
Individual-home-page-1-scaled.jpg
3329 ms
Perpetua_Values1.jpg
3758 ms
MicrosoftTeams-image-73.jpg
2960 ms
Perpetua_Values3.jpg
3410 ms
1x1.trans.gif
2699 ms
MicrosoftTeams-image-34.png
2792 ms
arrow-blue.png
2960 ms
arrow-device.png
3062 ms
perpetuaim.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
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
Buttons do not have an accessible name
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
perpetuaim.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
perpetuaim.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
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 Perpetuaim.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 Perpetuaim.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.
perpetuaim.co.za
Open Graph data is detected on the main page of Perpetua Im. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: