Tools & Wizards About Us
use.expensify.com screenshot

Report Summary

  • 29

    Performance

    Renders faster than
    49% of other websites

  • 63

    Accessibility

    Visual factors better than
    that of 28% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 84

    SEO

    Google-friendlier than
    52% of websites

use.expensify.com

Expense Report Software | Manage Your Company Spend

Page Load Speed

1.2 sec in total

First Response

82 ms

Resources Loaded

699 ms

Page Rendered

459 ms

use.expensify.com screenshot

About Website

Visit use.expensify.com now to see the best up-to-date Use Expensify content for United States and also check out these interesting facts you probably never knew about use.expensify.com

With Expensify, track expenses, scan receipts, submit expense reports, pay bills, generate invoices, and get cash back with the best corporate credit card.

Visit use.expensify.com

Key Findings

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

Performance Metrics

use.expensify.com performance score

29

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.8 s

2/100

10%

LCP (Largest Contentful Paint)

Value8.7 s

1/100

25%

SI (Speed Index)

Value6.8 s

35/100

10%

TBT (Total Blocking Time)

Value360 ms

72/100

30%

CLS (Cumulative Layout Shift)

Value1.178

1/100

15%

TTI (Time to Interactive)

Value9.0 s

34/100

10%

Network Requests Diagram

use.expensify.com

82 ms

common-0437e51819dd863618ab-min.js

63 ms

commerce-1d13bdbc93aaacbb9cbd-min.js

44 ms

commerce-2b4a0593bca72ff9bd48bd03804b62b2-min.css

33 ms

site.css

57 ms

Our browser made a total of 108 requests to load all elements on the main page. We found that 4% of them (4 requests) were addressed to the original Use.expensify.com, 56% (61 requests) were made to Static1.squarespace.com and 32% (35 requests) were made to Static.squarespace.com. The less responsive or slowest element that took the longest time to load (217 ms) belongs to the original domain Use.expensify.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 136.8 kB (14%)

Content Size

997.1 kB

After Optimization

860.2 kB

  • HTML
  • Images
  • JavaScript

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

HTML Optimization

-81%

Potential reduce by 59.5 kB

  • Original 73.2 kB
  • After minification 56.7 kB
  • After compression 13.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. This page needs HTML code to be minified as it can gain 16.6 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 59.5 kB or 81% of the original size.

Image Optimization

-5%

Potential reduce by 48.1 kB

  • Original 877.3 kB
  • After minification 829.2 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. Use Expensify images are well optimized though.

JavaScript Optimization

-63%

Potential reduce by 29.2 kB

  • Original 46.5 kB
  • After minification 46.5 kB
  • After compression 17.3 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 29.2 kB or 63% of the original size.

Requests Breakdown

Number of requests can be reduced by 13 (13%)

Requests Now

104

After Optimization

91

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

use.expensify.com

use.expensify.com

82 ms

common-0437e51819dd863618ab-min.js

common-0437e51819dd863618ab-min.js

63 ms

commerce-1d13bdbc93aaacbb9cbd-min.js

commerce-1d13bdbc93aaacbb9cbd-min.js

44 ms

commerce-2b4a0593bca72ff9bd48bd03804b62b2-min.css

commerce-2b4a0593bca72ff9bd48bd03804b62b2-min.css

33 ms

site.css

site.css

57 ms

jquery.min.js

jquery.min.js

26 ms

jquery.min.js

jquery.min.js

31 ms

plugins.js

plugins.js

214 ms

main.js

main.js

217 ms

intercom.js

intercom.js

47 ms

ga.js

ga.js

87 ms

logo@2x.png

logo@2x.png

110 ms

66 ms

eventbrite_02.png

eventbrite_02.png

68 ms

square.png

square.png

64 ms

mozilla.png

mozilla.png

68 ms

calalumni.png

calalumni.png

86 ms

github.png

github.png

67 ms

nutanix.png

nutanix.png

66 ms

uber.png

uber.png

85 ms

campkesem.png

campkesem.png

84 ms

zoosk.png

zoosk.png

84 ms

sbnation.png

sbnation.png

83 ms

linuxfoundation.png

linuxfoundation.png

83 ms

evernote.png

evernote.png

93 ms

mashable.png

mashable.png

91 ms

louisville.png

louisville.png

91 ms

change.png

change.png

92 ms

saymedia.png

saymedia.png

91 ms

kayak.png

kayak.png

91 ms

soundcloud.png

soundcloud.png

102 ms

bancorp.png

bancorp.png

103 ms

lyft.png

lyft.png

97 ms

denihan.png

denihan.png

96 ms

cbs.png

cbs.png

112 ms

boingo.png

boingo.png

111 ms

bigten.png

bigten.png

117 ms

causes.png

causes.png

111 ms

variety.png

variety.png

120 ms

pinterest.png

pinterest.png

125 ms

flipboard.png

flipboard.png

121 ms

mongodb.png

mongodb.png

125 ms

eventbrite.png

eventbrite.png

124 ms

ruf.png

ruf.png

126 ms

bg_pageHeader.jpg

bg_pageHeader.jpg

87 ms

receipt2.svg

receipt2.svg

84 ms

receipt.svg

receipt.svg

101 ms

bank.svg

bank.svg

96 ms

cc.svg

cc.svg

95 ms

arrow.svg

arrow.svg

92 ms

cloud.svg

cloud.svg

97 ms

expensify.svg

expensify.svg

100 ms

phone.svg

phone.svg

115 ms

report.svg

report.svg

116 ms

laptop.svg

laptop.svg

112 ms

ss_oracle.png

ss_oracle.png

117 ms

ss_sap.png

ss_sap.png

116 ms

ss_netsuite.png

ss_netsuite.png

110 ms

ss_intacct.png

ss_intacct.png

118 ms

ss_xero.png

ss_xero.png

120 ms

ss_qb.png

ss_qb.png

118 ms

bg_icons.png

bg_icons.png

134 ms

icon_expenses_lg.svg

icon_expenses_lg.svg

120 ms

img_expenses.png

img_expenses.png

121 ms

icon_receipts_lg.svg

icon_receipts_lg.svg

122 ms

img_receipts_02.jpg

img_receipts_02.jpg

134 ms

icon_admin_lg.svg

icon_admin_lg.svg

132 ms

img_admin.jpg

img_admin.jpg

144 ms

icon_compliance_lg.svg

icon_compliance_lg.svg

128 ms

img_compliance.jpg

img_compliance.jpg

135 ms

icon_mobile_lg.svg

icon_mobile_lg.svg

138 ms

bg_mobile.jpg

bg_mobile.jpg

163 ms

img_hand_02.png

img_hand_02.png

159 ms

icon_trips.png

icon_trips.png

143 ms

icon_offline.png

icon_offline.png

144 ms

icon_mileage.png

icon_mileage.png

146 ms

icon_time.png

icon_time.png

161 ms

bg_integrations.png

bg_integrations.png

159 ms

icon_integrations_lg.svg

icon_integrations_lg.svg

159 ms

__utm.gif

__utm.gif

18 ms

int_oracle.png

int_oracle.png

109 ms

int_sap.png

int_sap.png

92 ms

collect

collect

64 ms

int_xero2.jpg

int_xero2.jpg

93 ms

int_netsuite.png

int_netsuite.png

82 ms

int_msd.png

int_msd.png

79 ms

int_salesforce.png

int_salesforce.png

78 ms

int_ff.png

int_ff.png

84 ms

int_intacct.png

int_intacct.png

83 ms

int_qb.png

int_qb.png

82 ms

int_adp.png

int_adp.png

68 ms

img_bubbles.png

img_bubbles.png

69 ms

team_jason.jpg

team_jason.jpg

68 ms

team_puneet.jpg

team_puneet.jpg

69 ms

team_elissa.jpg

team_elissa.jpg

69 ms

team_kirk.jpg

team_kirk.jpg

68 ms

team_garrett.jpg

team_garrett.jpg

70 ms

team_david.jpg

team_david.jpg

66 ms

team_dan.jpg

team_dan.jpg

67 ms

team_jonah.jpg

team_jonah.jpg

69 ms

team_jake.jpg

team_jake.jpg

72 ms

bg_twitter.png

bg_twitter.png

67 ms

bg_fb.png

bg_fb.png

63 ms

bg_gp.png

bg_gp.png

63 ms

bg_linkedin.png

bg_linkedin.png

63 ms

ga-audiences

ga-audiences

39 ms

z6a86tef

z6a86tef

66 ms

intercom.189a9b05.js

intercom.189a9b05.js

31 ms

Accessibility Review

use.expensify.com accessibility score

63

Accessibility Issues

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

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 IDs are not unique

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

Low

No form fields have multiple labels

High

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

use.expensify.com best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

use.expensify.com SEO score

84

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

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 Use.expensify.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 Use.expensify.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

use.expensify.com

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