Tools & Wizards About Us
focom.co.za screenshot

Report Summary

  • 16

    Performance

    Renders faster than
    30% of other websites

  • 95

    Accessibility

    Visual factors better than
    that of 87% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 84

    SEO

    Google-friendlier than
    53% of websites

focom.co.za

Home - GIG Network Solutions

Page Load Speed

13.4 sec in total

First Response

902 ms

Resources Loaded

10.2 sec

Page Rendered

2.3 sec

focom.co.za screenshot

About Website

Welcome to focom.co.za homepage info - get ready to check Focom best content right away, or after learning these important things about focom.co.za

GIG Network Solutions, your leading fibre optic cable and communications equipment installer on the South African Eastern Seaboard

Visit focom.co.za

Key Findings

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

Performance Metrics

focom.co.za performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.1 s

3/100

10%

LCP (Largest Contentful Paint)

Value10.4 s

0/100

25%

SI (Speed Index)

Value13.4 s

2/100

10%

TBT (Total Blocking Time)

Value3,990 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.014

100/100

15%

TTI (Time to Interactive)

Value17.3 s

4/100

10%

Network Requests Diagram

focom.co.za

902 ms

focom.co.za

4262 ms

wp-emoji-release.min.js

494 ms

main.min.css

767 ms

css

30 ms

Our browser made a total of 71 requests to load all elements on the main page. We found that 85% of them (60 requests) were addressed to the original Focom.co.za, 10% (7 requests) were made to Fonts.gstatic.com and 3% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (4.3 sec) belongs to the original domain Focom.co.za.

Page Optimization Overview & Recommendations

Page size can be reduced by 303.8 kB (9%)

Content Size

3.4 MB

After Optimization

3.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Focom.co.za main page is 3.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. 55% of websites need less resources to load. Images take 3.0 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 147.6 kB

  • Original 175.6 kB
  • After minification 172.3 kB
  • After compression 28.1 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 147.6 kB or 84% of the original size.

Image Optimization

-2%

Potential reduce by 60.4 kB

  • Original 3.0 MB
  • After minification 3.0 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. Focom images are well optimized though.

JavaScript Optimization

-5%

Potential reduce by 4.0 kB

  • Original 75.1 kB
  • After minification 75.0 kB
  • After compression 71.1 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

-59%

Potential reduce by 91.9 kB

  • Original 155.5 kB
  • After minification 152.3 kB
  • After compression 63.5 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. Focom.co.za needs all CSS files to be minified and compressed as it can save up to 91.9 kB or 59% of the original size.

Requests Breakdown

Number of requests can be reduced by 40 (73%)

Requests Now

55

After Optimization

15

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 55 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Focom. 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 18 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

focom.co.za

focom.co.za

902 ms

focom.co.za

focom.co.za

4262 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

494 ms

main.min.css

main.min.css

767 ms

css

css

30 ms

style.min.css

style.min.css

571 ms

blocks.style.build.css

blocks.style.build.css

597 ms

styles.css

styles.css

758 ms

embedpress.css

embedpress.css

773 ms

wpforms-base.min.css

wpforms-base.min.css

789 ms

elementor-icons.min.css

elementor-icons.min.css

850 ms

frontend-lite.min.css

frontend-lite.min.css

861 ms

post-247.css

post-247.css

883 ms

embedpress-elementor.css

embedpress-elementor.css

1050 ms

post-25.css

post-25.css

1057 ms

dashicons.min.css

dashicons.min.css

1318 ms

css

css

25 ms

fontawesome.min.css

fontawesome.min.css

1131 ms

solid.min.css

solid.min.css

1149 ms

jquery.min.js

jquery.min.js

1423 ms

jquery-migrate.min.js

jquery-migrate.min.js

1337 ms

pdfobject.min.js

pdfobject.min.js

1328 ms

widget-icon-box.min.css

widget-icon-box.min.css

268 ms

widget-icon-list.min.css

widget-icon-list.min.css

516 ms

frontend.min.js

frontend.min.js

1476 ms

be_popia_compliant_validation_script.js

be_popia_compliant_validation_script.js

1476 ms

be_popia_compliant_validation_script_bill.js

be_popia_compliant_validation_script_bill.js

1625 ms

front.js

front.js

1604 ms

flying-pages.min.js

flying-pages.min.js

1625 ms

jquery-numerator.min.js

jquery-numerator.min.js

1697 ms

srs_simple_hits_counter_js.js

srs_simple_hits_counter_js.js

1701 ms

webpack.runtime.min.js

webpack.runtime.min.js

1732 ms

frontend-modules.min.js

frontend-modules.min.js

1897 ms

waypoints.min.js

waypoints.min.js

1919 ms

core.min.js

core.min.js

1912 ms

frontend.min.js

frontend.min.js

2018 ms

underscore.min.js

underscore.min.js

2015 ms

wp-util.min.js

wp-util.min.js

2564 ms

frontend.min.js

frontend.min.js

2200 ms

jquery.validate.min.js

jquery.validate.min.js

2205 ms

widget-icon-box.min.css

widget-icon-box.min.css

1957 ms

mailcheck.min.js

mailcheck.min.js

2061 ms

widget-icon-list.min.css

widget-icon-list.min.css

1784 ms

punycode.min.js

punycode.min.js

1960 ms

wpforms.min.js

wpforms.min.js

1956 ms

GIG-6-296x296.png

GIG-6-296x296.png

1324 ms

GIGNetwork.jpg

GIGNetwork.jpg

268 ms

cloud-3843352_1920.jpg

cloud-3843352_1920.jpg

2329 ms

factory-1639990_1920.jpg

factory-1639990_1920.jpg

1854 ms

network-3864383_1920.jpg

network-3864383_1920.jpg

2990 ms

patch-panel-6267791_1920.jpg

patch-panel-6267791_1920.jpg

2318 ms

security-service-service-img-4.jpg

security-service-service-img-4.jpg

1884 ms

mika-baumeister-9Qq_G14hNC8-unsplash-scaled.jpg

mika-baumeister-9Qq_G14hNC8-unsplash-scaled.jpg

3568 ms

GIG-6.png

GIG-6.png

262 ms

ieVi2ZhZI2eCN5jzbjEETS9weq8-32meGCQYaQ.woff

ieVi2ZhZI2eCN5jzbjEETS9weq8-32meGCQYaQ.woff

26 ms

KFOlCnqEu92Fr1MmWUlfBBc-.woff

KFOlCnqEu92Fr1MmWUlfBBc-.woff

29 ms

KFOlCnqEu92Fr1MmYUtfBBc-.woff

KFOlCnqEu92Fr1MmYUtfBBc-.woff

27 ms

KFOlCnqEu92Fr1MmEU9fBBc-.woff

KFOlCnqEu92Fr1MmEU9fBBc-.woff

31 ms

KFOmCnqEu92Fr1Mu4mxM.woff

KFOmCnqEu92Fr1Mu4mxM.woff

30 ms

KFOlCnqEu92Fr1MmSU5fBBc-.woff

KFOlCnqEu92Fr1MmSU5fBBc-.woff

29 ms

KFOkCnqEu92Fr1MmgVxIIzQ.woff

KFOkCnqEu92Fr1MmgVxIIzQ.woff

28 ms

GIG-6.png

GIG-6.png

1885 ms

GIGNetwork.jpg

GIGNetwork.jpg

3358 ms

xfbml.customerchat.js

xfbml.customerchat.js

38 ms

shield-shape-bg-img.svg

shield-shape-bg-img.svg

282 ms

patch-panel-6267793_1920.jpg

patch-panel-6267793_1920.jpg

282 ms

fa-solid-900.woff

fa-solid-900.woff

1537 ms

29 ms

shield-shape-bg-img.svg

shield-shape-bg-img.svg

1466 ms

patch-panel-6267793_1920.jpg

patch-panel-6267793_1920.jpg

1476 ms

admin-ajax.php

admin-ajax.php

2399 ms

Accessibility Review

focom.co.za accessibility score

95

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

<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

focom.co.za best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

focom.co.za SEO score

84

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

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

focom.co.za

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