Report Summary

  • 15

    Performance

    Renders faster than
    27% of other websites

  • 67

    Accessibility

    Visual factors better than
    that of 32% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 79

    SEO

    Google-friendlier than
    40% of websites

helloyes.co.za

HOME | HelloYes Marketing

Page Load Speed

14.1 sec in total

First Response

1.6 sec

Resources Loaded

10.3 sec

Page Rendered

2.2 sec

helloyes.co.za screenshot

About Website

Welcome to helloyes.co.za homepage info - get ready to check Hello Yes best content for South Africa right away, or after learning these important things about helloyes.co.za

We are a global, brand, creative, digital & technology-driven marketing agency. Say #HelloYes for creative solutions that connect to people & build your brand.

Visit helloyes.co.za

Key Findings

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

Performance Metrics

helloyes.co.za performance score

15

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value9.3 s

0/100

10%

LCP (Largest Contentful Paint)

Value19.8 s

0/100

25%

SI (Speed Index)

Value42.5 s

0/100

10%

TBT (Total Blocking Time)

Value58,130 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.026

100/100

15%

TTI (Time to Interactive)

Value77.1 s

0/100

10%

Network Requests Diagram

helloyes.co.za

1581 ms

cookie-law-info-public.css

39 ms

cookie-law-info-gdpr.css

36 ms

jquery.min.js

40 ms

jquery-migrate.min.js

992 ms

Our browser made a total of 67 requests to load all elements on the main page. We found that 49% of them (33 requests) were addressed to the original Helloyes.co.za, 10% (7 requests) were made to I.vimeocdn.com and 9% (6 requests) were made to Player.vimeo.com. The less responsive or slowest element that took the longest time to load (3.2 sec) relates to the external source Player.vimeo.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 428.8 kB (58%)

Content Size

741.4 kB

After Optimization

312.7 kB

In fact, the total size of Helloyes.co.za main page is 741.4 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. 65% of websites need less resources to load. HTML takes 481.7 kB which makes up the majority of the site volume.

HTML Optimization

-89%

Potential reduce by 426.7 kB

  • Original 481.7 kB
  • After minification 481.2 kB
  • After compression 54.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. 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 426.7 kB or 89% of the original size.

Image Optimization

-1%

Potential reduce by 1.7 kB

  • Original 147.2 kB
  • After minification 145.6 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. Hello Yes images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 257 B

  • Original 75.3 kB
  • After minification 75.3 kB
  • After compression 75.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.

CSS Optimization

-0%

Potential reduce by 67 B

  • Original 37.2 kB
  • After minification 37.2 kB
  • After compression 37.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. Helloyes.co.za has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 38 (66%)

Requests Now

58

After Optimization

20

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

Accessibility Review

helloyes.co.za accessibility score

67

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

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

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

helloyes.co.za SEO score

79

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

High

Image elements do not have [alt] attributes

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 Helloyes.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 Helloyes.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 Hello Yes. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: