20.8 sec in total
886 ms
19.6 sec
271 ms
Welcome to proto.co.za homepage info - get ready to check PROTO best content for South Africa right away, or after learning these important things about proto.co.za
Visit proto.co.zaWe analyzed Proto.co.za page load time and found that the first response time was 886 ms and then it took 19.9 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.
proto.co.za performance score
name
value
score
weighting
Value7.0 s
1/100
10%
Value23.8 s
0/100
25%
Value19.5 s
0/100
10%
Value600 ms
50/100
30%
Value0.071
96/100
15%
Value22.2 s
1/100
10%
886 ms
1048 ms
1544 ms
927 ms
935 ms
Our browser made a total of 137 requests to load all elements on the main page. We found that 1% of them (2 requests) were addressed to the original Proto.co.za, 89% (122 requests) were made to Prototrading.co.za and 3% (4 requests) were made to Maps.googleapis.com. The less responsive or slowest element that took the longest time to load (5.2 sec) relates to the external source Prototrading.co.za.
Page size can be reduced by 231.1 kB (5%)
4.4 MB
4.2 MB
In fact, the total size of Proto.co.za main page is 4.4 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.8 MB which makes up the majority of the site volume.
Potential reduce by 92.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. This page needs HTML code to be minified as it can gain 20.2 kB, which is 19% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 92.0 kB or 85% of the original size.
Potential reduce by 125.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. PROTO images are well optimized though.
Potential reduce by 11.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 2.0 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. Proto.co.za has all CSS files already compressed.
Number of requests can be reduced by 92 (72%)
128
36
The browser has sent 128 CSS, Javascripts, AJAX and image requests in order to completely render the main page of PROTO. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 55 to 1 for JavaScripts and from 39 to 1 for CSS and as a result speed up the page load time.
proto.co.za
886 ms
proto.co.za
1048 ms
www.prototrading.co.za
1544 ms
style.css
927 ms
wpforms-full.min.css
935 ms
owl.carousel.min.css
950 ms
owl.theme.default.min.css
931 ms
cookieblocker.css
1271 ms
frontend.css
1174 ms
bootstrap.min.css
1846 ms
magnific-popup.min.css
1860 ms
flexslider.min.css
1869 ms
owl.carousel.min.css
1863 ms
animate.min.css
2086 ms
style.min.css
2193 ms
woocommerce.css
2776 ms
um-modal.css
2783 ms
jquery-ui.css
2788 ms
tipsy.css
2331 ms
um-raty.css
3011 ms
select2.css
3118 ms
um-fileupload.css
3256 ms
um-confirm.css
3696 ms
default.css
3694 ms
default.date.css
3704 ms
default.time.css
3930 ms
fonticons-ii.css
4034 ms
fonticons-fa.css
3266 ms
um-fontawesome.css
4211 ms
common.css
4611 ms
um-responsive.css
3941 ms
um-styles.css
4621 ms
cropper.css
4851 ms
um-profile.css
4858 ms
um-account.css
4946 ms
um-misc.css
5126 ms
embed
196 ms
js
52 ms
um-old-default.css
5189 ms
js
26 ms
search.js
4 ms
geometry.js
5 ms
main.js
11 ms
wc-blocks.css
4626 ms
email-decode.min.js
3928 ms
hooks.js
4168 ms
i18n.js
4170 ms
main.js
4914 ms
sourcebuster.js
4856 ms
order-attribution.js
4775 ms
underscore.min.js
4198 ms
wp-util.js
4604 ms
api-request.js
4632 ms
url.js
4916 ms
api-fetch.js
4857 ms
wp-polyfill.js
4945 ms
css
37 ms
css
56 ms
css
61 ms
slider.min.css
4767 ms
frontend.js
5060 ms
bootstrap.min.js
4633 ms
jquery.mb.YTPlayer.min.js
4012 ms
jqBootstrapValidation.min.js
4257 ms
jquery.flexslider.js
4863 ms
jquery.magnific-popup.min.js
4093 ms
jquery.fitvids.min.js
4645 ms
smoothscroll.min.js
4691 ms
owl.carousel.min.js
4433 ms
custom.min.js
3704 ms
navigation.min.js
4619 ms
skip-link-focus-fix.min.js
4404 ms
tipsy.js
4856 ms
um-confirm.js
4793 ms
picker.js
3972 ms
picker.date.js
4430 ms
picker.time.js
4503 ms
common.js
3710 ms
cropper.js
4400 ms
common-frontend.js
4627 ms
um-modal.js
4094 ms
jquery-form.js
4647 ms
fileupload.js
4851 ms
um-functions.js
4162 ms
um-responsive.js
4509 ms
um-conditional.js
4623 ms
select2.full.js
4350 ms
en.js
4386 ms
um-raty.js
4629 ms
um-scripts.js
4847 ms
um-profile.js
3604 ms
um-account.js
4491 ms
rocket-loader.min.js
3402 ms
ProtoLogoXS.png
4316 ms
BB-300x196.png
4181 ms
BEADS-300x196.png
3635 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf
29 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf
41 ms
ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyWyosBO5Xk.ttf
49 ms
ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyVVpcBO5Xk.ttf
49 ms
glyphicons-halflings-regular.woff
4579 ms
ElegantIcons.woff
4536 ms
FASHION-ACCESSORIES-300x196.png
4607 ms
ARTSn-300x196.png
4554 ms
FUNCTIONS-300x196.png
4631 ms
TECHNOLOGY-300x196.png
4629 ms
KIDS-300x196.png
4642 ms
BUILDING-MATERIALS-300x196.png
4635 ms
COSMETICS-MAKEUP-CREAMS-300x196.png
4778 ms
F42-GRN.jpg
4064 ms
F42-GRN1.jpg
4071 ms
F42-RED.jpg
4632 ms
F42-RED1.jpg
4777 ms
F42-PUR.jpg
4629 ms
F42-PUR1.jpg
4645 ms
F42-ORG.jpg
4629 ms
F42-ORG1.jpg
4614 ms
F27-BLU.jpg
4153 ms
F27-BLU1.jpg
4907 ms
F27-BLK.jpg
4185 ms
F27-BLK1.jpg
4152 ms
F27-PUR.jpg
4878 ms
F27-PUR1.jpg
4614 ms
F27-RED.jpg
4393 ms
F27-RED1.jpg
4325 ms
Ribbon.jpg
4517 ms
Fragrance-1.jpg
4787 ms
SCENTED-CANDLES.jpg
5087 ms
art.jpg
4884 ms
bnb.jpg
4624 ms
function-1.jpg
3966 ms
beads.jpg
4630 ms
main.js
282 ms
timeme.js
919 ms
burst.js
934 ms
jquery.js
919 ms
jquery-migrate.js
13 ms
proto.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.
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
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.
proto.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
proto.co.za SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
robots.txt is not valid
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 Proto.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 Proto.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.
proto.co.za
Open Graph description is not detected on the main page of PROTO. 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: