Tools & Wizards About Us
rworks.com screenshot

Report Summary

  • 49

    Performance

    Renders faster than
    67% of other websites

  • 76

    Accessibility

    Visual factors better than
    that of 42% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 62

    SEO

    Google-friendlier than
    23% of websites

rworks.com

RWorks - Manage remote workers, tasks, productivity and projects

Page Load Speed

2.5 sec in total

First Response

498 ms

Resources Loaded

1.9 sec

Page Rendered

182 ms

rworks.com screenshot

About Website

Visit rworks.com now to see the best up-to-date RWorks content and also check out these interesting facts you probably never knew about rworks.com

Web based tool for managing the tasks, time and attendance, activities and productivity of workers including teleworkers and freelance workers

Visit rworks.com

Key Findings

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

Performance Metrics

rworks.com performance score

49

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.5 s

35/100

10%

LCP (Largest Contentful Paint)

Value5.9 s

14/100

25%

SI (Speed Index)

Value6.7 s

36/100

10%

TBT (Total Blocking Time)

Value530 ms

56/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value5.9 s

66/100

10%

Network Requests Diagram

rworks.com

498 ms

nivo-slider.css

178 ms

default.css

187 ms

mootools.js

422 ms

caption.js

187 ms

Our browser made a total of 49 requests to load all elements on the main page. We found that 92% of them (45 requests) were addressed to the original Rworks.com, 4% (2 requests) were made to Cdn.survey.io and 4% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (699 ms) belongs to the original domain Rworks.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 253.1 kB (33%)

Content Size

764.5 kB

After Optimization

511.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Rworks.com main page is 764.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. 30% of websites need less resources to load. Images take 428.8 kB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 19.2 kB

  • Original 25.4 kB
  • After minification 23.0 kB
  • After compression 6.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. 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 19.2 kB or 76% of the original size.

Image Optimization

-5%

Potential reduce by 22.7 kB

  • Original 428.8 kB
  • After minification 406.1 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. RWorks images are well optimized though.

JavaScript Optimization

-65%

Potential reduce by 171.1 kB

  • Original 262.5 kB
  • After minification 245.0 kB
  • After compression 91.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 171.1 kB or 65% of the original size.

CSS Optimization

-84%

Potential reduce by 40.0 kB

  • Original 47.8 kB
  • After minification 36.5 kB
  • After compression 7.8 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. Rworks.com needs all CSS files to be minified and compressed as it can save up to 40.0 kB or 84% of the original size.

Requests Breakdown

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

Requests Now

48

After Optimization

34

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

rworks.com

rworks.com

498 ms

nivo-slider.css

nivo-slider.css

178 ms

default.css

default.css

187 ms

mootools.js

mootools.js

422 ms

caption.js

caption.js

187 ms

cufon-yui.js

cufon-yui.js

284 ms

Futura_BdCn_BT_400.font.js

Futura_BdCn_BT_400.font.js

282 ms

cufon-replace.js

cufon-replace.js

273 ms

maxheight.js

maxheight.js

281 ms

the-tooltip.min.js

the-tooltip.min.js

281 ms

constant.css

constant.css

371 ms

template.css

template.css

604 ms

the-tooltip.css

the-tooltip.css

378 ms

jquery-1.6.1.min.js

jquery-1.6.1.min.js

650 ms

jquery.nivo.slider.js

jquery.nivo.slider.js

413 ms

survey.js

survey.js

33 ms

twittersocialsmall.png

twittersocialsmall.png

118 ms

facebooksocialsmall.png

facebooksocialsmall.png

118 ms

pinterestsocialsmall.png

pinterestsocialsmall.png

116 ms

googlesocialsmall.png

googlesocialsmall.png

184 ms

freetrial.png

freetrial.png

235 ms

phonesmall.png

phonesmall.png

236 ms

europesmall.png

europesmall.png

236 ms

uksmall.png

uksmall.png

285 ms

ussmall.png

ussmall.png

304 ms

logo.gif

logo.gif

358 ms

intelligentsmall.jpg

intelligentsmall.jpg

358 ms

bottom-shadow.png

bottom-shadow.png

190 ms

menu_bg.gif

menu_bg.gif

232 ms

diagonal-noise.png

diagonal-noise.png

233 ms

slide1.jpg

slide1.jpg

699 ms

slide3.jpg

slide3.jpg

524 ms

slide2.jpg

slide2.jpg

527 ms

slide4.jpg

slide4.jpg

414 ms

newtaskmatch.png

newtaskmatch.png

351 ms

newmanage.png

newmanage.png

352 ms

newimprove.png

newimprove.png

467 ms

newmaintainsprivacy.png

newmaintainsprivacy.png

467 ms

newscreengrab.png

newscreengrab.png

528 ms

newnokeyrecording.png

newnokeyrecording.png

584 ms

demofront.png

demofront.png

585 ms

freetrialfront.png

freetrialfront.png

639 ms

loading.gif

loading.gif

512 ms

frontpagebackground.png

frontpagebackground.png

510 ms

top-shadow.png

top-shadow.png

566 ms

right_bottom_green.png

right_bottom_green.png

43 ms

ga.js

ga.js

4 ms

__utm.gif

__utm.gif

13 ms

arrows.png

arrows.png

115 ms

Accessibility Review

rworks.com accessibility score

76

Accessibility Issues

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

Best Practices

rworks.com 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

High

Browser errors were logged to the console

SEO Factors

rworks.com SEO score

62

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Rworks.com 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 Rworks.com 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

rworks.com

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