2 sec in total
27 ms
1.6 sec
310 ms
Click here to check amazing Workday Rising content for United States. Otherwise, check out these important facts you probably never knew about workdayrising.com
Join us for Workday Rising and Workday Rising EMEA! Workday Rising in San Francisco, September 26-29, 2023; Workday Rising EMEA Barcelona, Spain 14–16 November 2023. Learn more.
Visit workdayrising.comWe analyzed Workdayrising.com page load time and found that the first response time was 27 ms and then it took 1.9 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.
workdayrising.com performance score
name
value
score
weighting
Value7.8 s
0/100
10%
Value16.9 s
0/100
25%
Value8.4 s
18/100
10%
Value8,670 ms
0/100
30%
Value0
100/100
15%
Value16.7 s
5/100
10%
27 ms
258 ms
26 ms
213 ms
170 ms
Our browser made a total of 64 requests to load all elements on the main page. We found that 38% of them (24 requests) were addressed to the original Workdayrising.com, 9% (6 requests) were made to Fonts.gstatic.com and 9% (6 requests) were made to Pixel.mathtag.com. The less responsive or slowest element that took the longest time to load (820 ms) relates to the external source Workday.com.
Page size can be reduced by 821.6 kB (46%)
1.8 MB
945.4 kB
In fact, the total size of Workdayrising.com main page is 1.8 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 50% of websites need less resources to load. Javascripts take 765.4 kB which makes up the majority of the site volume.
Potential reduce by 15.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. This page needs HTML code to be minified as it can gain 4.8 kB, which is 23% 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 15.9 kB or 77% of the original size.
Potential reduce by 18.9 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. Workday Rising images are well optimized though.
Potential reduce by 497.0 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 497.0 kB or 65% of the original size.
Potential reduce by 289.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. Workdayrising.com needs all CSS files to be minified and compressed as it can save up to 289.7 kB or 83% of the original size.
Number of requests can be reduced by 29 (53%)
55
26
The browser has sent 55 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Workday Rising. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 22 to 1 for JavaScripts and as a result speed up the page load time.
workdayrising.com
27 ms
www.workdayrising.com
258 ms
css
26 ms
rising-global.css
213 ms
rising-head.js
170 ms
satelliteLib-096b8d5559393c19698ce1a6d53a75f06e46dae1.js
80 ms
rising-global.js
394 ms
munchkin.js
90 ms
satellite-5601e5673061340017000b6c.js
32 ms
satellite-560eb29e36346100170007e6.js
56 ms
tiled-bg.png
93 ms
munchkin.js
7 ms
s_code.min.js
38 ms
demandBase.min.js
27 ms
analytics.js
5 ms
mbox.min.js
26 ms
collect
19 ms
visitWebPage
17 ms
target.js
69 ms
collect
55 ms
ajax
10 ms
logo.png
112 ms
cta-calendar-small.svg
408 ms
hero-logo.png
106 ms
global-footer-bg.png
116 ms
aneel.jpg
421 ms
photo2.jpg
313 ms
photo3.jpg
312 ms
twitter-icon.svg
271 ms
play-btn.png
271 ms
image1.jpg
422 ms
image2.jpg
421 ms
image3.jpg
516 ms
facebook.svg
405 ms
twitter.svg
420 ms
linkedin.svg
492 ms
youtube.svg
507 ms
google.svg
494 ms
back-to-top.svg
503 ms
cta-clock-large.svg
445 ms
happy_faces.jpg
820 ms
HtPQWuY_isk
92 ms
satellite-556604eb3363360014f00500.js
125 ms
DXI1ORHCpsQm3Vp6mXoaTZS3E-kSBmtLoNJPDtbj2Pk.ttf
24 ms
cJZKeOuBrn4kERxqtaUH3SZ2oysoEQEeKwjgmXLRnTc.ttf
28 ms
MTP_ySUJH_bn48VBG8sNSpS3E-kSBmtLoNJPDtbj2Pk.ttf
35 ms
k3k702ZOKiLJc3WVjuplzJS3E-kSBmtLoNJPDtbj2Pk.ttf
36 ms
js
63 ms
www-embed-player-vflfNyN_r.css
40 ms
www-embed-player.js
113 ms
i.js
178 ms
ip.js
81 ms
menu-close-btn.png
248 ms
fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js
39 ms
ad_status.js
77 ms
QHD8zigcbDB8aPfIoaupKOvvDin1pK8aKteLpeZ5c0A.ttf
37 ms
RxZJdnzeo3R5zSexge8UUSZ2oysoEQEeKwjgmXLRnTc.ttf
70 ms
ajax
27 ms
s77878925499971
43 ms
js
36 ms
img
27 ms
iframe
38 ms
img
39 ms
img
43 ms
workdayrising.com accessibility score
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
Image elements do not have [alt] attributes
Links do not have a discernible name
workdayrising.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
workdayrising.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Image elements do not have [alt] attributes
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Workdayrising.com 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 Workdayrising.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.
workdayrising.com
Open Graph description is not detected on the main page of Workday Rising. 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: