Tools & Wizards About Us
prodeo.co.za screenshot

Report Summary

  • 60

    Performance

    Renders faster than
    75% of other websites

  • 79

    Accessibility

    Visual factors better than
    that of 47% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

prodeo.co.za

Prodeo Petroleum

Page Load Speed

6.9 sec in total

First Response

1.1 sec

Resources Loaded

5.6 sec

Page Rendered

228 ms

prodeo.co.za screenshot

About Website

Visit prodeo.co.za now to see the best up-to-date Prodeo content and also check out these interesting facts you probably never knew about prodeo.co.za

Consultants

Visit prodeo.co.za

Key Findings

We analyzed Prodeo.co.za page load time and found that the first response time was 1.1 sec and then it took 5.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

prodeo.co.za performance score

60

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.6 s

32/100

10%

LCP (Largest Contentful Paint)

Value8.7 s

1/100

25%

SI (Speed Index)

Value6.9 s

33/100

10%

TBT (Total Blocking Time)

Value40 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value4.6 s

82/100

10%

Network Requests Diagram

prodeo.co.za

1121 ms

beng-proxy.js

1322 ms

font-awesome.min.css

1638 ms

widget-runtime.css

1353 ms

deploy.css

1352 ms

Our browser made a total of 35 requests to load all elements on the main page. We found that 29% of them (10 requests) were addressed to the original Prodeo.co.za, 51% (18 requests) were made to Sitebuilder.xneelo.com and 17% (6 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (2.3 sec) relates to the external source Sitebuilder.xneelo.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 132.8 kB (19%)

Content Size

689.3 kB

After Optimization

556.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Prodeo.co.za main page is 689.3 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 35% of websites need less resources to load. Images take 478.1 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 23.8 kB

  • Original 30.6 kB
  • After minification 30.2 kB
  • After compression 6.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 23.8 kB or 78% of the original size.

Image Optimization

-2%

Potential reduce by 10.8 kB

  • Original 478.1 kB
  • After minification 467.3 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. Prodeo images are well optimized though.

JavaScript Optimization

-50%

Potential reduce by 74.3 kB

  • Original 149.7 kB
  • After minification 148.9 kB
  • After compression 75.4 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 74.3 kB or 50% of the original size.

CSS Optimization

-77%

Potential reduce by 24.0 kB

  • Original 31.0 kB
  • After minification 31.0 kB
  • After compression 7.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. Prodeo.co.za needs all CSS files to be minified and compressed as it can save up to 24.0 kB or 77% of the original size.

Requests Breakdown

Number of requests can be reduced by 17 (68%)

Requests Now

25

After Optimization

8

  • Images
  • JavaScript
  • CSS

The browser has sent 25 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Prodeo. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

prodeo.co.za

prodeo.co.za

1121 ms

beng-proxy.js

beng-proxy.js

1322 ms

font-awesome.min.css

font-awesome.min.css

1638 ms

widget-runtime.css

widget-runtime.css

1353 ms

deploy.css

deploy.css

1352 ms

slideshow-common.css

slideshow-common.css

1369 ms

jquery.js

jquery.js

1679 ms

prototype.js

prototype.js

1916 ms

legacy.js

legacy.js

1650 ms

widget-runtime.js

widget-runtime.js

1958 ms

slideshow-common.js

slideshow-common.js

1671 ms

deploy.js

deploy.js

1949 ms

uro-min.js

uro-min.js

1954 ms

main.css

main.css

1973 ms

responsive.css

responsive.css

1980 ms

vars.css

vars.css

390 ms

doubletaptogo.js

doubletaptogo.js

2246 ms

cm-templates-global-script.js

cm-templates-global-script.js

2251 ms

show.js

show.js

708 ms

css

css

22 ms

bif_33022247_cm-a.jpg

bif_33022247_cm-a.jpg

2215 ms

KFOlCnqEu92Fr1MmWUlvAA.woff

KFOlCnqEu92Fr1MmWUlvAA.woff

15 ms

KFOlCnqEu92Fr1MmYUtvAA.woff

KFOlCnqEu92Fr1MmYUtvAA.woff

31 ms

KFOlCnqEu92Fr1MmEU9vAA.woff

KFOlCnqEu92Fr1MmEU9vAA.woff

32 ms

KFOmCnqEu92Fr1Me5g.woff

KFOmCnqEu92Fr1Me5g.woff

33 ms

KFOlCnqEu92Fr1MmSU5vAA.woff

KFOlCnqEu92Fr1MmSU5vAA.woff

50 ms

KFOkCnqEu92Fr1MmgWxM.woff

KFOkCnqEu92Fr1MmgWxM.woff

50 ms

_pixel.img

_pixel.img

308 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

616 ms

Propet%20Logo.jpg

Propet%20Logo.jpg

1915 ms

picture-200

picture-200

331 ms

picture-200

picture-200

976 ms

India%20Offshore.jpeg

India%20Offshore.jpeg

324 ms

empty.png

empty.png

328 ms

Energy_Efficiency2.jpg

Energy_Efficiency2.jpg

648 ms

Accessibility Review

prodeo.co.za accessibility score

79

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Form elements do not have associated labels

High

Links do not have a discernible name

Best Practices

prodeo.co.za best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

prodeo.co.za SEO score

85

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

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

prodeo.co.za

Open Graph description is not detected on the main page of Prodeo. 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: