5.2 sec in total
343 ms
4.4 sec
439 ms
Welcome to iou.ch homepage info - get ready to check IOU best content for Germany right away, or after learning these important things about iou.ch
IOU helps you manage expenses between multiple people and assists in splitting costs. Use IOU with your roommates or for trips with your friends. Free of charge and without registration.
Visit iou.chWe analyzed Iou.ch page load time and found that the first response time was 343 ms and then it took 4.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
iou.ch performance score
name
value
score
weighting
Value5.8 s
4/100
10%
Value11.7 s
0/100
25%
Value6.0 s
46/100
10%
Value780 ms
38/100
30%
Value0.204
61/100
15%
Value9.6 s
29/100
10%
343 ms
889 ms
353 ms
592 ms
380 ms
Our browser made a total of 67 requests to load all elements on the main page. We found that 60% of them (40 requests) were addressed to the original Iou.ch, 15% (10 requests) were made to Google.com and 4% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.2 sec) belongs to the original domain Iou.ch.
Page size can be reduced by 1.6 MB (78%)
2.0 MB
431.0 kB
In fact, the total size of Iou.ch main page is 2.0 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. 35% of websites need less resources to load. Javascripts take 1.6 MB which makes up the majority of the site volume.
Potential reduce by 55.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 55.5 kB or 76% of the original size.
Potential reduce by 17.1 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. Obviously, IOU needs image optimization as it can save up to 17.1 kB or 16% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 1.3 MB
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 1.3 MB or 82% of the original size.
Potential reduce by 166.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. Iou.ch needs all CSS files to be minified and compressed as it can save up to 166.0 kB or 85% of the original size.
Number of requests can be reduced by 33 (52%)
64
31
The browser has sent 64 CSS, Javascripts, AJAX and image requests in order to completely render the main page of IOU. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 16 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
iou.ch
343 ms
www.iou.ch
889 ms
screen.css
353 ms
ext-all.css
592 ms
form.css
380 ms
messageBox.css
273 ms
message.css
275 ms
pott.css
522 ms
buttons.css
416 ms
ext-base.js
689 ms
ext-all-debug.js
2197 ms
ext-lang-en_US.js
509 ms
message.js
530 ms
analytics.js
621 ms
challenge
33 ms
_index_index.css
413 ms
fo.js
203 ms
_partials_footer.css
448 ms
bg3.jpg
214 ms
ga.js
39 ms
loadbar.gif
417 ms
dialog-close.png
236 ms
logo.png
337 ms
facebook-login.png
235 ms
feedback_trans_tab.png
234 ms
recaptcha.js
7 ms
g6qlE9hbcrtCq0agucy03kPIdFYel5UicYHotHMXHKo.js
64 ms
gradient_org.png
200 ms
all.js
134 ms
__utm.gif
74 ms
__utm.gif
67 ms
toggle_down_light.png
240 ms
bg-btn-blue.png
240 ms
refresh.png
57 ms
collect
135 ms
audio.png
68 ms
text.png
67 ms
help.png
68 ms
logo.png
67 ms
block_en.jpg
987 ms
get_started.png
397 ms
note-yellow.png
493 ms
checkmark-ul-orange.png
284 ms
note-orange.png
275 ms
checkmark-ul-white.png
395 ms
note-blue.png
400 ms
tutorial.png
515 ms
App_Store_Badge_EN.png
476 ms
fo.js
64 ms
gethomestats
498 ms
162 ms
reload
55 ms
xd_arbiter.php
85 ms
xd_arbiter.php
145 ms
image
26 ms
fmr.js
94 ms
blank.gif
50 ms
666666-2.png
146 ms
twitter.png
240 ms
getnews
246 ms
tip-sprite.gif
210 ms
tip-anchor-sprite.gif
246 ms
xd_arbiter.php
38 ms
like.php
88 ms
qeKvIRsJabD.js
137 ms
LVx-xkvaJ0b.png
148 ms
qeKvIRsJabD.js
57 ms
iou.ch 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
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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.
iou.ch 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
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
iou.ch SEO score
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 Iou.ch 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 Iou.ch 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.
iou.ch
Open Graph data is detected on the main page of IOU. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: