Report Summary

  • 51

    Performance

    Renders faster than
    69% of other websites

  • 97

    Accessibility

    Visual factors better than
    that of 91% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

apexsystems.co.za

SwiftCom | Home

Page Load Speed

1.4 sec in total

First Response

44 ms

Resources Loaded

784 ms

Page Rendered

608 ms

apexsystems.co.za screenshot

About Website

Visit apexsystems.co.za now to see the best up-to-date Apexsystems content for South Africa and also check out these interesting facts you probably never knew about apexsystems.co.za

We build full-stack web apps using a future-driven tech stack. Super-stable, bug-free and built to scale.

Visit apexsystems.co.za

Key Findings

We analyzed Apexsystems.co.za page load time and found that the first response time was 44 ms and then it took 1.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.

Performance Metrics

apexsystems.co.za performance score

51

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.5 s

15/100

10%

LCP (Largest Contentful Paint)

Value4.5 s

37/100

25%

SI (Speed Index)

Value4.5 s

72/100

10%

TBT (Total Blocking Time)

Value620 ms

48/100

30%

CLS (Cumulative Layout Shift)

Value0.1

90/100

15%

TTI (Time to Interactive)

Value7.0 s

53/100

10%

Network Requests Diagram

apexsystems.co.za

44 ms

www.swiftcom.co.za

54 ms

www.swiftcom.app

97 ms

swiftcom.app

73 ms

style.css

26 ms

Our browser made a total of 35 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Apexsystems.co.za, 80% (28 requests) were made to Swiftcom.app and 9% (3 requests) were made to Use.typekit.net. The less responsive or slowest element that took the longest time to load (219 ms) relates to the external source Swiftcom.app.

Page Optimization Overview & Recommendations

Page size can be reduced by 57.2 kB (66%)

Content Size

86.2 kB

After Optimization

29.1 kB

In fact, the total size of Apexsystems.co.za main page is 86.2 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. 20% of websites need less resources to load. HTML takes 58.6 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 48.3 kB

  • Original 58.6 kB
  • After minification 58.6 kB
  • After compression 10.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 48.3 kB or 82% of the original size.

Image Optimization

-38%

Potential reduce by 8.9 kB

  • Original 23.1 kB
  • After minification 14.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. Obviously, Apexsystems needs image optimization as it can save up to 8.9 kB or 38% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-0%

Potential reduce by 17 B

  • Original 4.5 kB
  • After minification 4.5 kB
  • After compression 4.5 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.

CSS Optimization

-0%

Potential reduce by 0 B

  • Original 5 B

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.

Requests Breakdown

Number of requests can be reduced by 8 (28%)

Requests Now

29

After Optimization

21

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

Accessibility Review

apexsystems.co.za accessibility score

97

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.

Best Practices

apexsystems.co.za best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

SEO Factors

apexsystems.co.za SEO score

100

Search Engine Optimization Advices

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

Open Graph data is detected on the main page of Apexsystems. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: