Report Summary

  • 55

    Performance

    Renders faster than
    72% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

workpapers.xero.com

Login | Xero Accounting Software

Page Load Speed

692 ms in total

First Response

88 ms

Resources Loaded

604 ms

Page Rendered

0 ms

workpapers.xero.com screenshot

About Website

Click here to check amazing Workpapers Xero content for Australia. Otherwise, check out these important facts you probably never knew about workpapers.xero.com

Customer Login for Xero Accounting Software. Welcome to Xero, if you don't have an account, try Xero for free.

Visit workpapers.xero.com

Key Findings

We analyzed Workpapers.xero.com page load time and found that the first response time was 88 ms and then it took 604 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 10% of websites can load faster.

Performance Metrics

workpapers.xero.com performance score

55

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

47/100

10%

LCP (Largest Contentful Paint)

Value3.4 s

66/100

25%

SI (Speed Index)

Value3.1 s

93/100

10%

TBT (Total Blocking Time)

Value1,180 ms

21/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value9.2 s

32/100

10%

Network Requests Diagram

login

88 ms

xui.min.css

47 ms

site.css

23 ms

beanie.js

80 ms

xobs-banner.js

43 ms

Our browser made a total of 10 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Workpapers.xero.com, 30% (3 requests) were made to Login.xero.com and 10% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (122 ms) relates to the external source Googletagmanager.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 160.5 kB (50%)

Content Size

319.3 kB

After Optimization

158.8 kB

In fact, the total size of Workpapers.xero.com main page is 319.3 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. 20% of websites need less resources to load. Javascripts take 251.7 kB which makes up the majority of the site volume.

HTML Optimization

-65%

Potential reduce by 25.5 kB

  • Original 39.0 kB
  • After minification 37.9 kB
  • After compression 13.5 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 25.5 kB or 65% of the original size.

JavaScript Optimization

-54%

Potential reduce by 134.8 kB

  • Original 251.7 kB
  • After minification 251.1 kB
  • After compression 116.9 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 134.8 kB or 54% of the original size.

CSS Optimization

-1%

Potential reduce by 178 B

  • Original 28.6 kB
  • After minification 28.6 kB
  • After compression 28.4 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. Workpapers.xero.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 5 (56%)

Requests Now

9

After Optimization

4

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

Accessibility Review

workpapers.xero.com accessibility score

100

Accessibility Issues

Best Practices

workpapers.xero.com best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

workpapers.xero.com SEO score

83

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

High

Page is blocked from indexing

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

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 Workpapers.xero.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 Workpapers.xero.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 Workpapers Xero. 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: