Report Summary

  • 97

    Performance

    Renders faster than
    95% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 69% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 55

    SEO

    Google-friendlier than
    20% of websites

Page Load Speed

4.6 sec in total

First Response

828 ms

Resources Loaded

3.4 sec

Page Rendered

318 ms

ttps.co.za screenshot

About Website

Click here to check amazing Ttps content. Otherwise, check out these important facts you probably never knew about ttps.co.za

Visit ttps.co.za

Key Findings

We analyzed Ttps.co.za page load time and found that the first response time was 828 ms and then it took 3.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster. This domain responded with an error, which can significantly jeopardize Ttps.co.za rating and web reputation

Performance Metrics

ttps.co.za performance score

97

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.0 s

83/100

10%

LCP (Largest Contentful Paint)

Value2.0 s

96/100

25%

SI (Speed Index)

Value2.3 s

98/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value2.0 s

99/100

10%

Network Requests Diagram

www.ttps.co.za

828 ms

css

418 ms

ttps.co.za

167 ms

WebResource.axd

170 ms

WebResource.axd

168 ms

Our browser made a total of 53 requests to load all elements on the main page. We found that 42% of them (22 requests) were addressed to the original Ttps.co.za, 28% (15 requests) were made to S3-eu-west-1.amazonaws.com and 23% (12 requests) were made to Img.entegral.net. The less responsive or slowest element that took the longest time to load (1.8 sec) relates to the external source Img.entegral.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 715.8 kB (27%)

Content Size

2.6 MB

After Optimization

1.9 MB

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

HTML Optimization

-87%

Potential reduce by 221.5 kB

  • Original 254.4 kB
  • After minification 197.2 kB
  • After compression 32.9 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 57.2 kB, which is 22% 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 221.5 kB or 87% of the original size.

Image Optimization

-6%

Potential reduce by 119.6 kB

  • Original 1.9 MB
  • After minification 1.8 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. Ttps images are well optimized though.

JavaScript Optimization

-74%

Potential reduce by 367.4 kB

  • Original 499.7 kB
  • After minification 479.6 kB
  • After compression 132.4 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 367.4 kB or 74% of the original size.

CSS Optimization

-68%

Potential reduce by 7.4 kB

  • Original 10.8 kB
  • After minification 10.8 kB
  • After compression 3.4 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. Ttps.co.za needs all CSS files to be minified and compressed as it can save up to 7.4 kB or 68% of the original size.

Requests Breakdown

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

Requests Now

48

After Optimization

36

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

Accessibility Review

ttps.co.za accessibility score

88

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

Document doesn't have a <title> element

Best Practices

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

SEO Factors

ttps.co.za SEO score

55

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

Document doesn't have a <title> element

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ttps.co.za can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Ttps.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 description is not detected on the main page of Ttps. 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: