Tools & Wizards About Us
verge.co.za screenshot

Report Summary

  • 86

    Performance

    Renders faster than
    89% of other websites

  • 24

    Accessibility

    Visual factors better than
    that of 18% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

verge.co.za

Award-winning Mobile App Development | Verge Technologies

Page Load Speed

2.4 sec in total

First Response

198 ms

Resources Loaded

1.8 sec

Page Rendered

419 ms

verge.co.za screenshot

About Website

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

Mobile App and Website Development Company in Pretoria, Rivonia, Sandton, Bryanston, Randburg, Cape Town, Johannesburg and South Africa

Visit verge.co.za

Key Findings

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

Performance Metrics

verge.co.za performance score

86

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.1 s

80/100

10%

LCP (Largest Contentful Paint)

Value3.2 s

72/100

25%

SI (Speed Index)

Value3.4 s

89/100

10%

TBT (Total Blocking Time)

Value180 ms

91/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value4.4 s

84/100

10%

Network Requests Diagram

verge.co.za

198 ms

verge.co.za

162 ms

css

31 ms

loader.css

111 ms

bootstrap.min.css

132 ms

Our browser made a total of 57 requests to load all elements on the main page. We found that 84% of them (48 requests) were addressed to the original Verge.co.za, 7% (4 requests) were made to Fonts.gstatic.com and 4% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Verge.co.za.

Page Optimization Overview & Recommendations

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

Content Size

1.7 MB

After Optimization

1.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-80%

Potential reduce by 41.8 kB

  • Original 51.9 kB
  • After minification 33.8 kB
  • After compression 10.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. This page needs HTML code to be minified as it can gain 18.1 kB, which is 35% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 41.8 kB or 80% of the original size.

Image Optimization

-29%

Potential reduce by 463.9 kB

  • Original 1.6 MB
  • After minification 1.1 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. Obviously, Verge needs image optimization as it can save up to 463.9 kB or 29% 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 67 B

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

-12%

Potential reduce by 2.2 kB

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

Requests Breakdown

Number of requests can be reduced by 12 (24%)

Requests Now

51

After Optimization

39

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

verge.co.za

verge.co.za

198 ms

verge.co.za

verge.co.za

162 ms

css

css

31 ms

loader.css

loader.css

111 ms

bootstrap.min.css

bootstrap.min.css

132 ms

animate.css

animate.css

173 ms

menu.css

menu.css

130 ms

main.css

main.css

130 ms

email-decode.min.js

email-decode.min.js

21 ms

jquery-3.1.1.min.js

jquery-3.1.1.min.js

136 ms

vivus.min.js

vivus.min.js

26 ms

typed.min.js

typed.min.js

524 ms

scrollreveal.min.js

scrollreveal.min.js

263 ms

main.js

main.js

263 ms

analytics.js

analytics.js

30 ms

particles.html

particles.html

145 ms

ui.svg

ui.svg

140 ms

web.svg

web.svg

126 ms

smartphone.svg

smartphone.svg

212 ms

analytics.svg

analytics.svg

210 ms

ai.svg

ai.svg

230 ms

down-@2.png

down-@2.png

231 ms

devices.png

devices.png

229 ms

quote.svg

quote.svg

559 ms

dstv.png

dstv.png

288 ms

castle.png

castle.png

348 ms

redds.png

redds.png

342 ms

virgin.png

virgin.png

361 ms

huggies.png

huggies.png

401 ms

unisa.png

unisa.png

464 ms

renault.png

renault.png

452 ms

astra.png

astra.png

455 ms

adt.png

adt.png

477 ms

csir.png

csir.png

510 ms

fnb.png

fnb.png

566 ms

iss.png

iss.png

568 ms

tcc.png

tcc.png

602 ms

ogilvy.png

ogilvy.png

597 ms

mccann.png

mccann.png

641 ms

promise.png

promise.png

666 ms

helpendehand.png

helpendehand.png

710 ms

boxel.png

boxel.png

929 ms

nhsa.png

nhsa.png

710 ms

atc.png

atc.png

741 ms

markplein.png

markplein.png

814 ms

crimehub.png

crimehub.png

893 ms

nhsa.png

nhsa.png

822 ms

blockchain.svg

blockchain.svg

834 ms

collect

collect

14 ms

enzy.png

enzy.png

791 ms

S6uyw4BMUTPHjx4wWyWtFCc.ttf

S6uyw4BMUTPHjx4wWyWtFCc.ttf

23 ms

S6u9w4BMUTPHh7USSwiPHA3q5d0.ttf

S6u9w4BMUTPHh7USSwiPHA3q5d0.ttf

33 ms

S6u9w4BMUTPHh6UVSwiPHA3q5d0.ttf

S6u9w4BMUTPHh6UVSwiPHA3q5d0.ttf

41 ms

S6u9w4BMUTPHh50XSwiPHA3q5d0.ttf

S6u9w4BMUTPHh50XSwiPHA3q5d0.ttf

49 ms

boxel.png

boxel.png

909 ms

js

js

60 ms

bg-contact.png

bg-contact.png

1091 ms

Accessibility Review

verge.co.za accessibility score

24

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

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

High

<object> elements do not have alternate text

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

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

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

SEO Factors

verge.co.za SEO score

92

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

Image elements do not have [alt] attributes

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Verge.co.za can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Verge.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

verge.co.za

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