Report Summary

  • 95

    Performance

    Renders faster than
    93% of other websites

  • 78

    Accessibility

    Visual factors better than
    that of 46% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 67

    SEO

    Google-friendlier than
    25% of websites

classicsa.co.za

ClassicSA

Page Load Speed

5 sec in total

First Response

2.1 sec

Resources Loaded

2.7 sec

Page Rendered

266 ms

classicsa.co.za screenshot

About Website

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

Visit classicsa.co.za

Key Findings

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

Performance Metrics

classicsa.co.za performance score

95

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.9 s

87/100

10%

LCP (Largest Contentful Paint)

Value2.3 s

93/100

25%

SI (Speed Index)

Value4.0 s

81/100

10%

TBT (Total Blocking Time)

Value30 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.03

100/100

15%

TTI (Time to Interactive)

Value2.4 s

98/100

10%

Network Requests Diagram

classicsa.co.za

2067 ms

site

160 ms

256 ms

btn_search.png

153 ms

(Back)_Milano_Ryeneke,_Leo_Huan_(Front)_Swunhtat_Oo,_Louis_Nel,_Cindy_Ju_-_csa-90x70.jpg

76 ms

Our browser made a total of 35 requests to load all elements on the main page. We found that 94% of them (33 requests) were addressed to the original Classicsa.co.za, 6% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain Classicsa.co.za.

Page Optimization Overview & Recommendations

Page size can be reduced by 72.1 kB (42%)

Content Size

170.9 kB

After Optimization

98.8 kB

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

HTML Optimization

-86%

Potential reduce by 53.3 kB

  • Original 61.7 kB
  • After minification 51.5 kB
  • After compression 8.4 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 10.2 kB, which is 17% 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 53.3 kB or 86% of the original size.

Image Optimization

-20%

Potential reduce by 18.8 kB

  • Original 92.1 kB
  • After minification 73.3 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, ClassicSA needs image optimization as it can save up to 18.8 kB or 20% 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 34 B

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

Requests Breakdown

Number of requests can be reduced by 14 (41%)

Requests Now

34

After Optimization

20

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

Accessibility Review

classicsa.co.za accessibility score

78

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

ARIA input fields do not have accessible names

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.

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

Best Practices

classicsa.co.za best practices score

58

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

classicsa.co.za SEO score

67

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

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 Classicsa.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 Classicsa.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 ClassicSA. 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: