5.5 sec in total
149 ms
5 sec
329 ms
Click here to check amazing Concur content. Otherwise, check out these important facts you probably never knew about concur.fi
SAP Concur simplifies travel, expense, and invoice management for total visibility and greater control. Start your test drive now!
Visit concur.fiWe analyzed Concur.fi page load time and found that the first response time was 149 ms and then it took 5.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
concur.fi performance score
name
value
score
weighting
Value3.9 s
26/100
10%
Value8.2 s
2/100
25%
Value4.0 s
81/100
10%
Value1,550 ms
13/100
30%
Value0.133
81/100
15%
Value14.1 s
9/100
10%
149 ms
52 ms
86 ms
76 ms
166 ms
Our browser made a total of 50 requests to load all elements on the main page. We found that 86% of them (43 requests) were addressed to the original Concur.fi, 6% (3 requests) were made to Assets.concur.com and 2% (1 request) were made to Cdn.schemaapp.com. The less responsive or slowest element that took the longest time to load (2.6 sec) belongs to the original domain Concur.fi.
Page size can be reduced by 316.0 kB (39%)
820.0 kB
504.0 kB
In fact, the total size of Concur.fi main page is 820.0 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. 45% of websites need less resources to load. Javascripts take 379.5 kB which makes up the majority of the site volume.
Potential reduce by 27.6 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 27.6 kB or 74% of the original size.
Potential reduce by 11.3 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. Concur images are well optimized though.
Potential reduce by 225.1 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 225.1 kB or 59% of the original size.
Potential reduce by 52.0 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. Concur.fi needs all CSS files to be minified and compressed as it can save up to 52.0 kB or 59% of the original size.
Number of requests can be reduced by 23 (58%)
40
17
The browser has sent 40 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Concur. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 10 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
www.concur.fi
149 ms
highlight.js
52 ms
css_xE-rWrJf-fncB6ztZfd2huxqgxu4WO-qwma6Xer30m4.css
86 ms
css_EReeAjtYNndwVFRshrDRvv9Pmh5M3h_a3gImBrBhFoM.css
76 ms
css_G7FOau9ZAmgxR2omMwirPHu8v6HY-4w019dHs2flZdg.css
166 ms
css_S_PkHq7zdgjToEWz_75cEtgLM4_x7SfMIGpeH3gW0XE.css
812 ms
css_I_wpGH4Uc9T1wqFQw80t8qvf3MDYtP02RXeXaXkRDG8.css
80 ms
js_PFctIrDh0JUCLrw-Jja4Pt1KFj1RcU33H9fUY9PLxhc.js
126 ms
demandbase_loader.js
166 ms
js_vdfkf7jdrmcbWbH5unWlNpvf4OzDzhwUVlkPEEEuTyc.js
124 ms
js_qg5O-A6QNU3ZzvTN6arQ-BoU2dE_LA--M_kZFoKwn_E.js
143 ms
js_Y13oNpQ4OPJgaBtKqimRNLtLbZTYVJGH_qCbRxnszhU.js
171 ms
js_r9-AARDvulegGsTKa_GTOZ6teZkjKuA6pg6Ni9JlokI.js
137 ms
homepage-2021.css
221 ms
homepage-2021.js
243 ms
js_ijBagfNggBA1NPNky3-2GnEKcnOZ_xkQjP0q9RzvMWc.js
326 ms
56VGK-KZ5VS-7BMLL-58DHU-CTJGD
96 ms
sap-concur.svg
130 ms
ico-search.png
380 ms
fa--arrow.svg
104 ms
image--concur-expense-demo.jpg
145 ms
image--concur-invoice-demo.jpg
122 ms
fi.svg
120 ms
ico-arrow.png
126 ms
expense_pictogram_1.png
580 ms
travel-pictogram.png
912 ms
invoice-pictogram.png
196 ms
0423_beginners-guide_video.png
719 ms
tande-homepage.png
269 ms
barclays.jpg
1314 ms
edf-energy_logo_90px.png
775 ms
vodafone.jpg
453 ms
hammerson.jpg
1150 ms
devon-air-ambulance.jpg
1423 ms
harrow-print-logo.jpg
1128 ms
05_twitter_logo.png
1001 ms
10_ibm_logo.png
2578 ms
blick_rothenberg_0.jpg
2034 ms
das.jpg
2145 ms
x.svg
1331 ms
benton-light.woff
1280 ms
benton-reg.woff
1308 ms
benton-medium.woff
1328 ms
benton-bold.woff
1338 ms
fontawesome-webfont.woff
1354 ms
benton-bold-italic.woff
1382 ms
benton-medium-italic.woff
1477 ms
benton-reg-italic.woff
1436 ms
benton-light-italic.woff
1428 ms
config.json
53 ms
concur.fi 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
Buttons do not have an accessible name
Image elements do not have [alt] attributes
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
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
concur.fi 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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
concur.fi SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Concur.fi 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 Concur.fi 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.
concur.fi
Open Graph description is not detected on the main page of Concur. 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: