Tools & Wizards About Us
paxsa.co.za screenshot

Report Summary

  • 40

    Performance

    Renders faster than
    60% of other websites

  • 80

    Accessibility

    Visual factors better than
    that of 50% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 93

    SEO

    Google-friendlier than
    84% of websites

paxsa.co.za

Home - PAX

Page Load Speed

5.6 sec in total

First Response

2.1 sec

Resources Loaded

3.2 sec

Page Rendered

399 ms

paxsa.co.za screenshot

About Website

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

Our market access covers more than 22 countries in Africa; directly through our subsidiaries and partly indirectly through cooperations with other globally operating partners

Visit paxsa.co.za

Key Findings

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

Performance Metrics

paxsa.co.za performance score

40

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.9 s

53/100

10%

LCP (Largest Contentful Paint)

Value6.2 s

11/100

25%

SI (Speed Index)

Value10.4 s

8/100

10%

TBT (Total Blocking Time)

Value850 ms

34/100

30%

CLS (Cumulative Layout Shift)

Value0.006

100/100

15%

TTI (Time to Interactive)

Value6.2 s

61/100

10%

Network Requests Diagram

paxsa.co.za

2053 ms

style.css

233 ms

styles.css

285 ms

settings.css

278 ms

css

106 ms

Our browser made a total of 54 requests to load all elements on the main page. We found that 96% of them (52 requests) were addressed to the original Paxsa.co.za, 4% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain Paxsa.co.za.

Page Optimization Overview & Recommendations

Page size can be reduced by 740.9 kB (40%)

Content Size

1.8 MB

After Optimization

1.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Paxsa.co.za main page is 1.8 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. 50% of websites need less resources to load. Images take 976.8 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 31.0 kB

  • Original 38.3 kB
  • After minification 36.5 kB
  • After compression 7.3 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 31.0 kB or 81% of the original size.

Image Optimization

-6%

Potential reduce by 61.3 kB

  • Original 976.8 kB
  • After minification 915.4 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. PAX Sa images are well optimized though.

JavaScript Optimization

-73%

Potential reduce by 371.1 kB

  • Original 511.1 kB
  • After minification 460.4 kB
  • After compression 140.0 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 371.1 kB or 73% of the original size.

CSS Optimization

-88%

Potential reduce by 277.6 kB

  • Original 316.4 kB
  • After minification 216.9 kB
  • After compression 38.8 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. Paxsa.co.za needs all CSS files to be minified and compressed as it can save up to 277.6 kB or 88% of the original size.

Requests Breakdown

Number of requests can be reduced by 36 (71%)

Requests Now

51

After Optimization

15

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

paxsa.co.za

paxsa.co.za

2053 ms

style.css

style.css

233 ms

styles.css

styles.css

285 ms

settings.css

settings.css

278 ms

css

css

106 ms

css

css

131 ms

motioncss.css

motioncss.css

224 ms

motioncss-widgets.css

motioncss-widgets.css

294 ms

font-awesome.css

font-awesome.css

307 ms

magnific-popup.css

magnific-popup.css

315 ms

wp-widgets.css

wp-widgets.css

331 ms

style.css

style.css

394 ms

responsive.css

responsive.css

378 ms

animation.css

animation.css

375 ms

us_astra_custom_styles.css

us_astra_custom_styles.css

372 ms

userscripts.js

userscripts.js

359 ms

jquery.js

jquery.js

475 ms

jquery-migrate.min.js

jquery-migrate.min.js

416 ms

jquery.themepunch.tools.min.js

jquery.themepunch.tools.min.js

470 ms

jquery.themepunch.revolution.min.js

jquery.themepunch.revolution.min.js

519 ms

jquery.form.min.js

jquery.form.min.js

89 ms

scripts.js

scripts.js

160 ms

g-alert.js

g-alert.js

160 ms

jquery.carousello.js

jquery.carousello.js

135 ms

imagesloaded.js

imagesloaded.js

169 ms

jquery.isotope.js

jquery.isotope.js

169 ms

jquery.magnific-popup.js

jquery.magnific-popup.js

243 ms

jquery.smoothScroll.js

jquery.smoothScroll.js

171 ms

jquery.simpleplaceholder.js

jquery.simpleplaceholder.js

169 ms

w-search.js

w-search.js

171 ms

navToSelect.js

navToSelect.js

241 ms

w-tabs.js

w-tabs.js

240 ms

w-timeline.js

w-timeline.js

242 ms

waypoints.min.js

waypoints.min.js

241 ms

jquery.flexslider.js

jquery.flexslider.js

242 ms

w-lang.js

w-lang.js

245 ms

jquery.parallax.js

jquery.parallax.js

243 ms

plugins.js

plugins.js

243 ms

comment-reply.min.js

comment-reply.min.js

257 ms

logo_3.png

logo_3.png

796 ms

health_safety_slide1.jpg

health_safety_slide1.jpg

1013 ms

slider-banner001.jpg

slider-banner001.jpg

947 ms

renewsys-180x120.png

renewsys-180x120.png

296 ms

okulhaza-180x120.jpg

okulhaza-180x120.jpg

298 ms

worldbank-180x120.png

worldbank-180x120.png

296 ms

microsoft-180x120.png

microsoft-180x120.png

298 ms

UN-180x120.png

UN-180x120.png

297 ms

scaw-180x120.png

scaw-180x120.png

299 ms

saa-180x120.png

saa-180x120.png

303 ms

solareff-180x120.jpg

solareff-180x120.jpg

358 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

432 ms

loader.gif

loader.gif

78 ms

shadow2.png

shadow2.png

131 ms

bullet.png

bullet.png

128 ms

Accessibility Review

paxsa.co.za accessibility score

80

Accessibility Issues

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

Buttons do not have an accessible name

High

Links do not have a discernible name

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.

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

paxsa.co.za best practices score

75

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

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

paxsa.co.za SEO score

93

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

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

High

Document uses legible font sizes

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

paxsa.co.za

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