Tools & Wizards About Us

Report Summary

  • 15

    Performance

    Renders faster than
    27% of other websites

  • 77

    Accessibility

    Visual factors better than
    that of 45% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 85

    SEO

    Google-friendlier than
    56% of websites

blogs.workday.com

Workday Blog Homepage

Page Load Speed

3.4 sec in total

First Response

829 ms

Resources Loaded

2 sec

Page Rendered

543 ms

About Website

Click here to check amazing Blog S Workday content for United States. Otherwise, check out these important facts you probably never knew about blogs.workday.com

Your source for information on business and technology trends, including stories on best practices and tech solutions for finance, HR, and IT. Learn more.

Visit blogs.workday.com

Key Findings

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

Performance Metrics

blogs.workday.com performance score

15

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.7 s

2/100

10%

LCP (Largest Contentful Paint)

Value21.8 s

0/100

25%

SI (Speed Index)

Value19.2 s

0/100

10%

TBT (Total Blocking Time)

Value14,000 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value29.9 s

0/100

10%

Network Requests Diagram

blogs.workday.com

829 ms

wp-emoji-release.min.js

119 ms

css

79 ms

style.css

46 ms

blogs-head.js

64 ms

Our browser made a total of 52 requests to load all elements on the main page. We found that 6% of them (3 requests) were addressed to the original Blogs.workday.com, 50% (26 requests) were made to Cdn.workday.com and 8% (4 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (829 ms) belongs to the original domain Blogs.workday.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 566.2 kB (38%)

Content Size

1.5 MB

After Optimization

919.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Blogs.workday.com main page is 1.5 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. Images take 783.8 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 32.0 kB

  • Original 41.7 kB
  • After minification 38.0 kB
  • After compression 9.7 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 32.0 kB or 77% of the original size.

Image Optimization

-7%

Potential reduce by 58.8 kB

  • Original 783.8 kB
  • After minification 725.0 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. Blog S Workday images are well optimized though.

JavaScript Optimization

-66%

Potential reduce by 299.6 kB

  • Original 453.3 kB
  • After minification 430.8 kB
  • After compression 153.7 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 299.6 kB or 66% of the original size.

CSS Optimization

-85%

Potential reduce by 175.9 kB

  • Original 207.1 kB
  • After minification 206.0 kB
  • After compression 31.2 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. Blogs.workday.com needs all CSS files to be minified and compressed as it can save up to 175.9 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 23 (52%)

Requests Now

44

After Optimization

21

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

blogs.workday.com accessibility score

77

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-hidden="true"] elements contain focusable descendents

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

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

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Some elements have a [tabindex] value greater than 0

Best Practices

blogs.workday.com 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

blogs.workday.com SEO score

85

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

Image elements do not have [alt] attributes

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 Blogs.workday.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 Blogs.workday.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

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