Tools & Wizards About Us
geotab.co.za screenshot

Report Summary

  • 52

    Performance

    Renders faster than
    69% of other websites

  • 94

    Accessibility

    Visual factors better than
    that of 83% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

geotab.co.za

Home - Geotab Africa

Page Load Speed

2.4 sec in total

First Response

646 ms

Resources Loaded

1.2 sec

Page Rendered

499 ms

geotab.co.za screenshot

About Website

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

Visit geotab.co.za

Key Findings

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

Performance Metrics

geotab.co.za performance score

52

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

49/100

10%

LCP (Largest Contentful Paint)

Value3.4 s

67/100

25%

SI (Speed Index)

Value6.7 s

36/100

10%

TBT (Total Blocking Time)

Value940 ms

30/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value9.8 s

28/100

10%

Network Requests Diagram

geotab.co.za

646 ms

geotabafrica.com

64 ms

dashicons.min.css

86 ms

flatsome.css

37 ms

style.css

26 ms

Our browser made a total of 58 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Geotab.co.za, 81% (47 requests) were made to Geotabafrica.com and 3% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (646 ms) belongs to the original domain Geotab.co.za.

Page Optimization Overview & Recommendations

Page size can be reduced by 149.5 kB (30%)

Content Size

501.6 kB

After Optimization

352.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-83%

Potential reduce by 117.9 kB

  • Original 141.2 kB
  • After minification 135.2 kB
  • After compression 23.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 117.9 kB or 83% of the original size.

Image Optimization

-14%

Potential reduce by 21.5 kB

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

JavaScript Optimization

-7%

Potential reduce by 9.4 kB

  • Original 137.3 kB
  • After minification 137.3 kB
  • After compression 127.9 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

-1%

Potential reduce by 717 B

  • Original 65.6 kB
  • After minification 65.3 kB
  • After compression 64.9 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. Geotab.co.za has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 18 (42%)

Requests Now

43

After Optimization

25

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

geotab.co.za

geotab.co.za

646 ms

geotabafrica.com

geotabafrica.com

64 ms

dashicons.min.css

dashicons.min.css

86 ms

flatsome.css

flatsome.css

37 ms

style.css

style.css

26 ms

jquery.min.js

jquery.min.js

30 ms

jquery-migrate.min.js

jquery-migrate.min.js

26 ms

js

js

198 ms

js

js

199 ms

v2.js

v2.js

82 ms

bilmur.min.js

bilmur.min.js

48 ms

3336865.js

3336865.js

256 ms

flatsome-live-search.js

flatsome-live-search.js

46 ms

wp-polyfill.min.js

wp-polyfill.min.js

46 ms

hoverIntent.min.js

hoverIntent.min.js

45 ms

flatsome.js

flatsome.js

46 ms

e-202434.js

e-202434.js

47 ms

maxmegamenu.js

maxmegamenu.js

46 ms

Geotab-Africa-Logo-White-1024x168.webp

Geotab-Africa-Logo-White-1024x168.webp

5 ms

Untitled-1.png

Untitled-1.png

155 ms

Untitled-2.png

Untitled-2.png

5 ms

Untitled-3.png

Untitled-3.png

155 ms

FleetManSol-Icons-01.svg

FleetManSol-Icons-01.svg

54 ms

Untitled-CTA1.png

Untitled-CTA1.png

154 ms

FleetManSol-Icons-02.svg

FleetManSol-Icons-02.svg

55 ms

Untitled-CTA2-150x150.png

Untitled-CTA2-150x150.png

154 ms

FleetManSol-Icons-03.svg

FleetManSol-Icons-03.svg

56 ms

Untitled-CTA3.png

Untitled-CTA3.png

57 ms

FleetManSol-Icons-04.svg

FleetManSol-Icons-04.svg

58 ms

Untitled-CTA4.png

Untitled-CTA4.png

59 ms

FleetManSol-Icons-05.svg

FleetManSol-Icons-05.svg

58 ms

Untitled-CTA5.png

Untitled-CTA5.png

59 ms

FleetManSol-Icons-06.svg

FleetManSol-Icons-06.svg

60 ms

Untitled-CTA6.png

Untitled-CTA6.png

60 ms

image-16-300x300.png

image-16-300x300.png

154 ms

image-15-300x300.png

image-15-300x300.png

168 ms

image-14-300x300.png

image-14-300x300.png

167 ms

image-13-300x300.png

image-13-300x300.png

168 ms

Geotab-Authorized-Reseller.png

Geotab-Authorized-Reseller.png

166 ms

S6uyw4BMUTPHjx4wWCWtFCc.woff

S6uyw4BMUTPHjx4wWCWtFCc.woff

115 ms

S6uyw4BMUTPHjxAwWCWtFCfQ7A.woff

S6uyw4BMUTPHjxAwWCWtFCfQ7A.woff

115 ms

banner.js

banner.js

240 ms

3336865.js

3336865.js

235 ms

leadflows.js

leadflows.js

181 ms

collectedforms.js

collectedforms.js

221 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aXx-p7K4GLs.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aXx-p7K4GLs.woff

49 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w3aXx-p7K4GLvztg.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w3aXx-p7K4GLvztg.woff

48 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w2aXx-p7K4GLvztg.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w2aXx-p7K4GLvztg.woff

48 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w9aXx-p7K4GLvztg.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w9aXx-p7K4GLvztg.woff

48 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w0aXx-p7K4GLvztg.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w0aXx-p7K4GLvztg.woff

47 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aXx-p7K4GLs.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aXx-p7K4GLs.woff

47 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw3aXx-p7K4GLvztg.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw3aXx-p7K4GLvztg.woff

83 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw2aXx-p7K4GLvztg.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw2aXx-p7K4GLvztg.woff

82 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw9aXx-p7K4GLvztg.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw9aXx-p7K4GLvztg.woff

81 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw0aXx-p7K4GLvztg.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw0aXx-p7K4GLvztg.woff

82 ms

fl-icons.ttf

fl-icons.ttf

81 ms

chunk.countup.js

chunk.countup.js

39 ms

chunk.sticky-sidebar.js

chunk.sticky-sidebar.js

3 ms

Accessibility Review

geotab.co.za accessibility score

94

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.

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

Links do not have a discernible name

Best Practices

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

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

geotab.co.za SEO score

91

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

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

geotab.co.za

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