Report Summary

  • 19

    Performance

    Renders faster than
    36% of other websites

  • 68

    Accessibility

    Visual factors better than
    that of 33% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 76

    SEO

    Google-friendlier than
    35% of websites

roevin.ca

Adecco Staffing Agency - Permanent Staffing and Temp Agencies for Job Seekers

Page Load Speed

3.5 sec in total

First Response

38 ms

Resources Loaded

2.2 sec

Page Rendered

1.2 sec

roevin.ca screenshot

About Website

Visit roevin.ca now to see the best up-to-date Roevin content for Canada and also check out these interesting facts you probably never knew about roevin.ca

Looking for a job? Adecco is looking for candidates like you for permanent and temporary staffing job opportunities. Submit your resume or find a job that is hiring now.

Visit roevin.ca

Key Findings

We analyzed Roevin.ca page load time and found that the first response time was 38 ms and then it took 3.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

roevin.ca performance score

19

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.4 s

6/100

10%

LCP (Largest Contentful Paint)

Value13.3 s

0/100

25%

SI (Speed Index)

Value7.2 s

29/100

10%

TBT (Total Blocking Time)

Value4,390 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value43.2 s

0/100

10%

Network Requests Diagram

roevin.ca

38 ms

www.adecco.ca

135 ms

gtm.js

140 ms

js

185 ms

accessibility.js

120 ms

Our browser made a total of 92 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Roevin.ca, 43% (40 requests) were made to Www-nam-prd-cms930-com.azureedge.net and 24% (22 requests) were made to Adecco.ca. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source S3-us-west-2.amazonaws.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 217.9 kB (28%)

Content Size

767.4 kB

After Optimization

549.5 kB

In fact, the total size of Roevin.ca main page is 767.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. Only a small number of websites need less resources to load. CSS take 325.5 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 68.5 kB

  • Original 89.3 kB
  • After minification 76.4 kB
  • After compression 20.8 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 12.9 kB, which is 14% 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 68.5 kB or 77% of the original size.

Image Optimization

-0%

Potential reduce by 101 B

  • Original 139.7 kB
  • After minification 139.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. Roevin images are well optimized though.

JavaScript Optimization

-11%

Potential reduce by 23.6 kB

  • Original 212.9 kB
  • After minification 212.8 kB
  • After compression 189.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 23.6 kB or 11% of the original size.

CSS Optimization

-39%

Potential reduce by 125.7 kB

  • Original 325.5 kB
  • After minification 325.3 kB
  • After compression 199.7 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. Roevin.ca needs all CSS files to be minified and compressed as it can save up to 125.7 kB or 39% of the original size.

Requests Breakdown

Number of requests can be reduced by 53 (65%)

Requests Now

82

After Optimization

29

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

Accessibility Review

roevin.ca accessibility score

68

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-*] attributes do not match their roles

High

ARIA input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

High

[aria-*] attributes do not have valid values

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

Buttons do not have an accessible name

High

Links do not have a discernible name

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

[id] attributes on active, focusable elements are not unique

High

Heading elements are not in a sequentially-descending order

High

Some elements have a [tabindex] value greater than 0

Best Practices

roevin.ca 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

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

roevin.ca SEO score

76

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

High

robots.txt is not valid

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Roevin.ca 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 Roevin.ca 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 Roevin. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: