27.8 sec in total
52 ms
15 sec
12.7 sec
Click here to check amazing BILL content for United States. Otherwise, check out these important facts you probably never knew about bill.com
The AP, AR, and spend & expense solution that let's you create and pay bills, manage expenses, control budgets, and get the credit your business/firm needs to grow.
Visit bill.comWe analyzed Bill.com page load time and found that the first response time was 52 ms and then it took 27.7 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.
bill.com performance score
name
value
score
weighting
Value5.9 s
4/100
10%
Value10.3 s
0/100
25%
Value6.3 s
41/100
10%
Value3,160 ms
2/100
30%
Value0.126
83/100
15%
Value18.1 s
3/100
10%
52 ms
536 ms
337 ms
758 ms
757 ms
Our browser made a total of 102 requests to load all elements on the main page. We found that 73% of them (74 requests) were addressed to the original Bill.com, 4% (4 requests) were made to Api.mixpanel.com and 2% (2 requests) were made to Gtrk.s3.amazonaws.com. The less responsive or slowest element that took the longest time to load (5.1 sec) belongs to the original domain Bill.com.
Page size can be reduced by 2.0 MB (30%)
6.9 MB
4.8 MB
In fact, the total size of Bill.com main page is 6.9 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. 70% of websites need less resources to load. Images take 4.5 MB which makes up the majority of the site volume.
Potential reduce by 51.4 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 14.5 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 51.4 kB or 80% of the original size.
Potential reduce by 203.7 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. BILL images are well optimized though.
Potential reduce by 664.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 664.9 kB or 64% of the original size.
Potential reduce by 1.1 MB
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. Bill.com needs all CSS files to be minified and compressed as it can save up to 1.1 MB or 89% of the original size.
Number of requests can be reduced by 43 (44%)
97
54
The browser has sent 97 CSS, Javascripts, AJAX and image requests in order to completely render the main page of BILL. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 34 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
bill.com
52 ms
www.bill.com
536 ms
system.base.css
337 ms
date.css
758 ms
field.css
757 ms
node.css
744 ms
views.css
744 ms
ckeditor.css
819 ms
ctools.css
820 ms
style.css
818 ms
home.css
771 ms
respond.min.js
786 ms
jquery.min.js
1810 ms
jquery.once.js
785 ms
drupal.js
1810 ms
293502076.js
1895 ms
admin_devel.js
1809 ms
auto-submit.js
1809 ms
t13.js
1809 ms
affix.js
1670 ms
button.js
1670 ms
carousel.js
1757 ms
collapse.js
1751 ms
dropdown.js
1755 ms
modal.js
1749 ms
tooltip.js
1756 ms
scrollspy.js
1753 ms
transition.js
1806 ms
video_autoplay.js
1804 ms
typed.js
1805 ms
adTracking_getParameterByName_createCookie_readCookie.js
1805 ms
jquery-ui.css
1727 ms
bootstrap.js
1786 ms
page_chunks.js
1787 ms
css
1040 ms
event
1198 ms
mixpanel-2.2.min.js
4194 ms
gtm.js
4024 ms
BDC_LOGO_RGB.svg
947 ms
bdc_logo_252x70.png
2945 ms
nav_select.png
3149 ms
hero_screen_1034x778.jpg
3173 ms
qb338x68.png
3149 ms
xero160x48.png
3058 ms
sage-intacct.png
3057 ms
netsuite274x58.png
3189 ms
ach.png
3471 ms
vendors.png
3470 ms
savetime.png
3360 ms
icon1_70x84.png
3139 ms
icon2_106x78.png
3139 ms
icon3_96x68.png
3418 ms
icon4_88x68.png
3140 ms
icon5_100x80.png
3419 ms
icon6_84x84.png
3421 ms
bdc_logo.png
3420 ms
logo-cpa-dot-com.png
3420 ms
illo1_708x334.png
3893 ms
mobile_bg2564x1006.jpg
3894 ms
apple58x72.png
3853 ms
android62x74.png
3852 ms
phone_frame488x858.png
3645 ms
home_phone_screen1_428x790.png
3853 ms
arrow_up70x70.png
4639 ms
arrow_down70x70.png
4655 ms
illo2_702x380.png
4655 ms
testimonial_gradient10x690.png
4655 ms
quote_img234x226.png
4656 ms
illo3588x368.png
4655 ms
gridicon1_116x136.png
4749 ms
gridicon2_144x130.png
4749 ms
gridicon3_148x144.png
5069 ms
gridicon4_130x112.png
4802 ms
gridicon5_116x116.png
4801 ms
cgt.js
3374 ms
munchkin.js
4277 ms
gridicon6_146x140.png
1953 ms
facebook_60x60.png
2638 ms
twitter_60x60.png
2636 ms
linkedin_60x60.png
2546 ms
g_plus_60x60.png
2546 ms
youtube_60x60.png
2522 ms
bdc-fonts.ttf
1731 ms
5946.js
3305 ms
2793 ms
2715 ms
2955 ms
analytics.js
2260 ms
conversion.js
2109 ms
fbevents.js
2482 ms
insight.min.js
2481 ms
munchkin.js
886 ms
visitWebPage
1261 ms
960 ms
collect
496 ms
1543798229207252
68 ms
454 ms
259 ms
ga-audiences
131 ms
s
313 ms
u
222 ms
15 ms
bill.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Links do not have a discernible name
bill.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
bill.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
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
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Bill.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 Bill.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.
bill.com
Open Graph description is not detected on the main page of BILL. 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: