Tools & Wizards About Us
riteq.com.au screenshot

Report Summary

  • 22

    Performance

    Renders faster than
    40% of other websites

  • 90

    Accessibility

    Visual factors better than
    that of 74% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 81

    SEO

    Google-friendlier than
    42% of websites

riteq.com.au

Riteq is now a Ceridian company | Australia New Zealand

Page Load Speed

1.5 sec in total

First Response

66 ms

Resources Loaded

1.2 sec

Page Rendered

211 ms

riteq.com.au screenshot

About Website

Visit riteq.com.au now to see the best up-to-date Riteq content for Australia and also check out these interesting facts you probably never knew about riteq.com.au

For Riteq customer support, or to learn more about Dayforce human capital management suite for employers in Australia and New Zealand visit this page.

Visit riteq.com.au

Key Findings

We analyzed Riteq.com.au page load time and found that the first response time was 66 ms and then it took 1.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.

Performance Metrics

riteq.com.au performance score

22

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.0 s

24/100

10%

LCP (Largest Contentful Paint)

Value6.1 s

12/100

25%

SI (Speed Index)

Value8.6 s

17/100

10%

TBT (Total Blocking Time)

Value2,380 ms

5/100

30%

CLS (Cumulative Layout Shift)

Value0.103

89/100

15%

TTI (Time to Interactive)

Value23.1 s

1/100

10%

Network Requests Diagram

riteq.com.au

66 ms

103 ms

riteq

139 ms

marvel.js

21 ms

OtAutoBlock.js

35 ms

Our browser made a total of 20 requests to load all elements on the main page. We found that 5% of them (1 request) were addressed to the original Riteq.com.au, 65% (13 requests) were made to Ceridian.com and 15% (3 requests) were made to Cdn.cookielaw.org. The less responsive or slowest element that took the longest time to load (576 ms) relates to the external source Ceridian.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 55.5 kB (7%)

Content Size

801.5 kB

After Optimization

746.0 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Riteq.com.au main page is 801.5 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. Images take 709.6 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 49.5 kB

  • Original 59.6 kB
  • After minification 55.0 kB
  • After compression 10.0 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 49.5 kB or 83% of the original size.

Image Optimization

-1%

Potential reduce by 5.8 kB

  • Original 709.6 kB
  • After minification 703.8 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. Riteq images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 191 B

  • Original 32.4 kB
  • After minification 32.3 kB
  • After compression 32.2 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 8 (53%)

Requests Now

15

After Optimization

7

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

riteq.com.au

riteq.com.au

66 ms

103 ms

riteq

riteq

139 ms

marvel.js

marvel.js

21 ms

OtAutoBlock.js

OtAutoBlock.js

35 ms

otSDKStub.js

otSDKStub.js

99 ms

headScripts

headScripts

102 ms

css

css

121 ms

bodyScripts

bodyScripts

184 ms

hotjar.js

hotjar.js

22 ms

logger.js

logger.js

30 ms

conv_v3.js

conv_v3.js

19 ms

5a75e6b1-5d55-412e-a6ea-9cd67daa343e.json

5a75e6b1-5d55-412e-a6ea-9cd67daa343e.json

170 ms

icon-search-off.png

icon-search-off.png

95 ms

ceridian_wordmark_header.svg

ceridian_wordmark_header.svg

93 ms

get-started.png

get-started.png

97 ms

ceridian_wordmark_blue_footer.svg

ceridian_wordmark_blue_footer.svg

91 ms

359476_1_0.woff

359476_1_0.woff

576 ms

359476_2_0.woff

359476_2_0.woff

574 ms

brightedge3.php

brightedge3.php

36 ms

Accessibility Review

riteq.com.au accessibility score

90

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

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

High

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

Best Practices

riteq.com.au best practices score

67

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

High

Browser errors were logged to the console

High

Page has valid source maps

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

riteq.com.au SEO score

81

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

High

Tap targets are not sized appropriately

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 Riteq.com.au 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 Riteq.com.au 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

riteq.com.au

Open Graph description is not detected on the main page of Riteq. 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: