Tools & Wizards About Us
proto.co.za screenshot

Report Summary

  • 30

    Performance

    Renders faster than
    50% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 51% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

proto.co.za

PROTO TRADING – Importers and Wholesalers to Traders Only

Page Load Speed

20.8 sec in total

First Response

886 ms

Resources Loaded

19.6 sec

Page Rendered

271 ms

proto.co.za screenshot

About Website

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.za

Key Findings

We 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 a poor result, as 95% of websites can load faster.

Performance Metrics

proto.co.za performance score

30

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.0 s

1/100

10%

LCP (Largest Contentful Paint)

Value23.8 s

0/100

25%

SI (Speed Index)

Value19.5 s

0/100

10%

TBT (Total Blocking Time)

Value600 ms

50/100

30%

CLS (Cumulative Layout Shift)

Value0.071

96/100

15%

TTI (Time to Interactive)

Value22.2 s

1/100

10%

Network Requests Diagram

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

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 Optimization Overview & Recommendations

Page size can be reduced by 358.8 kB (8%)

Content Size

4.5 MB

After Optimization

4.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Proto.co.za main page is 4.5 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.

HTML Optimization

-85%

Potential reduce by 92.0 kB

  • Original 108.6 kB
  • After minification 88.4 kB
  • After compression 16.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. 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.

Image Optimization

-3%

Potential reduce by 125.2 kB

  • Original 3.8 MB
  • After minification 3.7 MB

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.

JavaScript Optimization

-30%

Potential reduce by 139.6 kB

  • Original 463.2 kB
  • After minification 463.2 kB
  • After compression 323.6 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 139.6 kB or 30% of the original size.

CSS Optimization

-1%

Potential reduce by 2.0 kB

  • Original 159.0 kB
  • After minification 159.0 kB
  • After compression 157.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. Proto.co.za has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 92 (72%)

Requests Now

128

After Optimization

36

  • AJAX
  • Images
  • JavaScript
  • CSS

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.

Network Requests Diagram

proto.co.za

proto.co.za

886 ms

proto.co.za

proto.co.za

1048 ms

www.prototrading.co.za

www.prototrading.co.za

1544 ms

style.css

style.css

927 ms

wpforms-full.min.css

wpforms-full.min.css

935 ms

owl.carousel.min.css

owl.carousel.min.css

950 ms

owl.theme.default.min.css

owl.theme.default.min.css

931 ms

cookieblocker.css

cookieblocker.css

1271 ms

frontend.css

frontend.css

1174 ms

bootstrap.min.css

bootstrap.min.css

1846 ms

magnific-popup.min.css

magnific-popup.min.css

1860 ms

flexslider.min.css

flexslider.min.css

1869 ms

owl.carousel.min.css

owl.carousel.min.css

1863 ms

animate.min.css

animate.min.css

2086 ms

style.min.css

style.min.css

2193 ms

woocommerce.css

woocommerce.css

2776 ms

um-modal.css

um-modal.css

2783 ms

jquery-ui.css

jquery-ui.css

2788 ms

tipsy.css

tipsy.css

2331 ms

um-raty.css

um-raty.css

3011 ms

select2.css

select2.css

3118 ms

um-fileupload.css

um-fileupload.css

3256 ms

um-confirm.css

um-confirm.css

3696 ms

default.css

default.css

3694 ms

default.date.css

default.date.css

3704 ms

default.time.css

default.time.css

3930 ms

fonticons-ii.css

fonticons-ii.css

4034 ms

fonticons-fa.css

fonticons-fa.css

3266 ms

um-fontawesome.css

um-fontawesome.css

4211 ms

common.css

common.css

4611 ms

um-responsive.css

um-responsive.css

3941 ms

um-styles.css

um-styles.css

4621 ms

cropper.css

cropper.css

4851 ms

um-profile.css

um-profile.css

4858 ms

um-account.css

um-account.css

4946 ms

um-misc.css

um-misc.css

5126 ms

embed

embed

196 ms

js

js

52 ms

um-old-default.css

um-old-default.css

5189 ms

js

js

26 ms

search.js

search.js

4 ms

geometry.js

geometry.js

5 ms

main.js

main.js

11 ms

wc-blocks.css

wc-blocks.css

4626 ms

email-decode.min.js

email-decode.min.js

3928 ms

hooks.js

hooks.js

4168 ms

i18n.js

i18n.js

4170 ms

main.js

main.js

4914 ms

sourcebuster.js

sourcebuster.js

4856 ms

order-attribution.js

order-attribution.js

4775 ms

underscore.min.js

underscore.min.js

4198 ms

wp-util.js

wp-util.js

4604 ms

api-request.js

api-request.js

4632 ms

url.js

url.js

4916 ms

api-fetch.js

api-fetch.js

4857 ms

wp-polyfill.js

wp-polyfill.js

4945 ms

css

css

37 ms

css

css

56 ms

css

css

61 ms

slider.min.css

slider.min.css

4767 ms

frontend.js

frontend.js

5060 ms

bootstrap.min.js

bootstrap.min.js

4633 ms

jquery.mb.YTPlayer.min.js

jquery.mb.YTPlayer.min.js

4012 ms

jqBootstrapValidation.min.js

jqBootstrapValidation.min.js

4257 ms

jquery.flexslider.js

jquery.flexslider.js

4863 ms

jquery.magnific-popup.min.js

jquery.magnific-popup.min.js

4093 ms

jquery.fitvids.min.js

jquery.fitvids.min.js

4645 ms

smoothscroll.min.js

smoothscroll.min.js

4691 ms

owl.carousel.min.js

owl.carousel.min.js

4433 ms

custom.min.js

custom.min.js

3704 ms

navigation.min.js

navigation.min.js

4619 ms

skip-link-focus-fix.min.js

skip-link-focus-fix.min.js

4404 ms

tipsy.js

tipsy.js

4856 ms

um-confirm.js

um-confirm.js

4793 ms

picker.js

picker.js

3972 ms

picker.date.js

picker.date.js

4430 ms

picker.time.js

picker.time.js

4503 ms

common.js

common.js

3710 ms

cropper.js

cropper.js

4400 ms

common-frontend.js

common-frontend.js

4627 ms

um-modal.js

um-modal.js

4094 ms

jquery-form.js

jquery-form.js

4647 ms

fileupload.js

fileupload.js

4851 ms

um-functions.js

um-functions.js

4162 ms

um-responsive.js

um-responsive.js

4509 ms

um-conditional.js

um-conditional.js

4623 ms

select2.full.js

select2.full.js

4350 ms

en.js

en.js

4386 ms

um-raty.js

um-raty.js

4629 ms

um-scripts.js

um-scripts.js

4847 ms

um-profile.js

um-profile.js

3604 ms

um-account.js

um-account.js

4491 ms

rocket-loader.min.js

rocket-loader.min.js

3402 ms

ProtoLogoXS.png

ProtoLogoXS.png

4316 ms

BB-300x196.png

BB-300x196.png

4181 ms

BEADS-300x196.png

BEADS-300x196.png

3635 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

29 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

41 ms

ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyWyosBO5Xk.ttf

ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyWyosBO5Xk.ttf

49 ms

ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyVVpcBO5Xk.ttf

ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyVVpcBO5Xk.ttf

49 ms

glyphicons-halflings-regular.woff

glyphicons-halflings-regular.woff

4579 ms

ElegantIcons.woff

ElegantIcons.woff

4536 ms

FASHION-ACCESSORIES-300x196.png

FASHION-ACCESSORIES-300x196.png

4607 ms

ARTSn-300x196.png

ARTSn-300x196.png

4554 ms

FUNCTIONS-300x196.png

FUNCTIONS-300x196.png

4631 ms

TECHNOLOGY-300x196.png

TECHNOLOGY-300x196.png

4629 ms

KIDS-300x196.png

KIDS-300x196.png

4642 ms

BUILDING-MATERIALS-300x196.png

BUILDING-MATERIALS-300x196.png

4635 ms

COSMETICS-MAKEUP-CREAMS-300x196.png

COSMETICS-MAKEUP-CREAMS-300x196.png

4778 ms

F42-GRN.jpg

F42-GRN.jpg

4064 ms

F42-GRN1.jpg

F42-GRN1.jpg

4071 ms

F42-RED.jpg

F42-RED.jpg

4632 ms

F42-RED1.jpg

F42-RED1.jpg

4777 ms

F42-PUR.jpg

F42-PUR.jpg

4629 ms

F42-PUR1.jpg

F42-PUR1.jpg

4645 ms

F42-ORG.jpg

F42-ORG.jpg

4629 ms

F42-ORG1.jpg

F42-ORG1.jpg

4614 ms

F27-BLU.jpg

F27-BLU.jpg

4153 ms

F27-BLU1.jpg

F27-BLU1.jpg

4907 ms

F27-BLK.jpg

F27-BLK.jpg

4185 ms

F27-BLK1.jpg

F27-BLK1.jpg

4152 ms

F27-PUR.jpg

F27-PUR.jpg

4878 ms

F27-PUR1.jpg

F27-PUR1.jpg

4614 ms

F27-RED.jpg

F27-RED.jpg

4393 ms

F27-RED1.jpg

F27-RED1.jpg

4325 ms

Ribbon.jpg

Ribbon.jpg

4517 ms

Fragrance-1.jpg

Fragrance-1.jpg

4787 ms

SCENTED-CANDLES.jpg

SCENTED-CANDLES.jpg

5087 ms

art.jpg

art.jpg

4884 ms

bnb.jpg

bnb.jpg

4624 ms

function-1.jpg

function-1.jpg

3966 ms

beads.jpg

beads.jpg

4630 ms

main.js

main.js

282 ms

timeme.js

timeme.js

919 ms

burst.js

burst.js

934 ms

jquery.js

jquery.js

919 ms

jquery-migrate.js

jquery-migrate.js

13 ms

Accessibility Review

proto.co.za accessibility score

81

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

High

<frame> or <iframe> elements do not have a title

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

proto.co.za best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

proto.co.za SEO score

77

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

High

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    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.

Social Sharing Optimization

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: