Report Summary

  • 17

    Performance

    Renders faster than
    32% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 88% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

702.co.za

Primedia Plus

Page Load Speed

637 ms in total

First Response

77 ms

Resources Loaded

490 ms

Page Rendered

70 ms

702.co.za screenshot

About Website

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

Primedia+ is your brand-new online content hub, home to the iconic radio stations you love 947, 702, Kfm, CapeTalk, and EWN all in one convenient location. It's more than just radio and news, it's an ...

Visit 702.co.za

Key Findings

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

Performance Metrics

702.co.za performance score

17

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.5 s

15/100

10%

LCP (Largest Contentful Paint)

Value14.1 s

0/100

25%

SI (Speed Index)

Value7.9 s

22/100

10%

TBT (Total Blocking Time)

Value3,280 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0.131

81/100

15%

TTI (Time to Interactive)

Value14.2 s

9/100

10%

Network Requests Diagram

702.co.za

77 ms

69 ms

css2

42 ms

adsbygoogle.js

135 ms

gpt.js

106 ms

Our browser made a total of 11 requests to load all elements on the main page. We found that 9% of them (1 request) were addressed to the original 702.co.za, 27% (3 requests) were made to Primediaplus.com and 27% (3 requests) were made to Cdn.cookielaw.org. The less responsive or slowest element that took the longest time to load (135 ms) relates to the external source Pagead2.googlesyndication.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 124.4 kB (24%)

Content Size

527.1 kB

After Optimization

402.7 kB

In fact, the total size of 702.co.za main page is 527.1 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. Only 10% of websites need less resources to load. Javascripts take 505.3 kB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 6.5 kB

  • Original 8.7 kB
  • After minification 7.6 kB
  • After compression 2.2 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 1.2 kB, which is 13% 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 6.5 kB or 74% of the original size.

JavaScript Optimization

-23%

Potential reduce by 117.9 kB

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

CSS Optimization

-0%

Potential reduce by 0 B

  • Original 13.1 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.

Requests Breakdown

Number of requests can be reduced by 5 (56%)

Requests Now

9

After Optimization

4

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

Accessibility Review

702.co.za accessibility score

96

Accessibility Issues

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

702.co.za best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

702.co.za SEO score

83

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

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

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

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 702.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 702.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 data is detected on the main page of PARSED_DOMAIN, but there is no image specified in description. It would be a good idea for the website admin to select a nice image that can properly represent the website in Open Graph data, otherwise the first found image will be taken for this purpose and social media information block will look like this: