9.9 sec in total
870 ms
8.3 sec
731 ms
Visit prisma.co.za now to see the best up-to-date Prisma content and also check out these interesting facts you probably never knew about prisma.co.za
Visit prisma.co.zaWe analyzed Prisma.co.za page load time and found that the first response time was 870 ms and then it took 9 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
prisma.co.za performance score
name
value
score
weighting
Value10.1 s
0/100
10%
Value13.3 s
0/100
25%
Value18.7 s
0/100
10%
Value1,520 ms
13/100
30%
Value0.038
100/100
15%
Value26.7 s
0/100
10%
870 ms
2704 ms
71 ms
938 ms
707 ms
Our browser made a total of 88 requests to load all elements on the main page. We found that 83% of them (73 requests) were addressed to the original Prisma.co.za, 7% (6 requests) were made to Fonts.gstatic.com and 2% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (2.9 sec) belongs to the original domain Prisma.co.za.
Page size can be reduced by 1.5 MB (26%)
5.9 MB
4.3 MB
In fact, the total size of Prisma.co.za main page is 5.9 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 3.7 MB which makes up the majority of the site volume.
Potential reduce by 78.8 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 78.8 kB or 77% of the original size.
Potential reduce by 2.2 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. Prisma images are well optimized though.
Potential reduce by 790.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 790.3 kB or 63% of the original size.
Potential reduce by 670.5 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. Prisma.co.za needs all CSS files to be minified and compressed as it can save up to 670.5 kB or 84% of the original size.
Number of requests can be reduced by 51 (66%)
77
26
The browser has sent 77 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Prisma. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 33 to 1 for JavaScripts and from 20 to 1 for CSS and as a result speed up the page load time.
prisma.co.za
870 ms
prisma.co.za
2704 ms
js
71 ms
style.min.css
938 ms
styles.css
707 ms
nectar-slider.css
1182 ms
font-awesome-legacy.min.css
1209 ms
grid-system.css
965 ms
style.css
1712 ms
header-secondary-nav.css
943 ms
element-fancy-box.css
1171 ms
cf7.css
1176 ms
css
40 ms
responsive.css
1443 ms
flickity.css
1405 ms
skin-original.css
1411 ms
menu-dynamic.css
1414 ms
js_composer.min.css
1447 ms
salient-dynamic-styles.css
2110 ms
css
13 ms
frontend-gtag.min.js
1418 ms
jquery.min.js
1655 ms
jquery-migrate.min.js
1453 ms
style-non-critical.css
1229 ms
magnific.css
1420 ms
core.css
1461 ms
wpcf7-redirect-script.js
1470 ms
index.js
1493 ms
index.js
1718 ms
anime.min.js
1718 ms
nectar-slider.js
2439 ms
jquery.easing.min.js
1785 ms
jquery.mousewheel.min.js
1849 ms
priority.js
1887 ms
nectar-slider-priority.js
1888 ms
transit.min.js
1911 ms
waypoints.js
1971 ms
imagesLoaded.min.js
2031 ms
hoverintent.min.js
2121 ms
magnific.js
2122 ms
api.js
36 ms
flickity.js
2129 ms
superfish.js
1965 ms
init.js
2803 ms
touchswipe.min.js
1880 ms
comment-reply.min.js
1858 ms
wp-polyfill-inert.min.js
1663 ms
regenerator-runtime.min.js
1744 ms
wp-polyfill.min.js
2350 ms
index.js
1849 ms
js_composer_front.min.js
1673 ms
analytics.js
176 ms
site24x7rum-min.js
406 ms
gtm.js
110 ms
logomain.png
1006 ms
2.jpg
1013 ms
3.jpg
1166 ms
4.jpg
1176 ms
5.jpg
1267 ms
6.jpg
1275 ms
8.jpg
1407 ms
9.jpg
1411 ms
10.jpg
1509 ms
12.jpg
1518 ms
Artboard1-100.jpg
2361 ms
Artboard2-100.jpg
2826 ms
Artboard3-100.jpg
2857 ms
footerlogo.png
1716 ms
4001new.jpg
2728 ms
undergroundminignhome2.jpg
2002 ms
trainingdev.jpg
2154 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf
57 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVc.ttf
77 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVc.ttf
120 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVc.ttf
137 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf
121 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVc.ttf
138 ms
collect
68 ms
Lovelo_Black.woff
2146 ms
icomoon.woff
2291 ms
fontawesome-webfont.svg
2421 ms
mineralhomepage.jpg
2411 ms
background-texture1.jpg
2424 ms
bottomimagebg.jpg
2533 ms
dumptruckmining1.jpg
2438 ms
footerbg.jpg
2539 ms
recaptcha__en.js
45 ms
fontawesome-webfont.woff
348 ms
prisma.co.za accessibility score
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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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.
prisma.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
prisma.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
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Prisma.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 Prisma.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.
prisma.co.za
Open Graph description is not detected on the main page of Prisma. 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: