5.3 sec in total
339 ms
4.7 sec
303 ms
Welcome to ui.de homepage info - get ready to check Ui best content right away, or after learning these important things about ui.de
Your fund service partner and Super ManCo. Put your trust in us, one of Europe's leading fund service platforms and Super ManCos.
Visit ui.deWe analyzed Ui.de page load time and found that the first response time was 339 ms and then it took 5 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
ui.de performance score
name
value
score
weighting
Value4.7 s
13/100
10%
Value14.0 s
0/100
25%
Value9.4 s
12/100
10%
Value350 ms
73/100
30%
Value0.001
100/100
15%
Value15.1 s
7/100
10%
339 ms
321 ms
813 ms
90 ms
136 ms
Our browser made a total of 56 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Ui.de, 79% (44 requests) were made to Universal-investment.com and 5% (3 requests) were made to Etracker.de. The less responsive or slowest element that took the longest time to load (2.2 sec) relates to the external source Universal-investment.com.
Page size can be reduced by 117.7 kB (16%)
722.0 kB
604.3 kB
In fact, the total size of Ui.de main page is 722.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. 25% of websites need less resources to load. Images take 523.8 kB which makes up the majority of the site volume.
Potential reduce by 37.0 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 37.0 kB or 83% of the original size.
Potential reduce by 20.0 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. Ui images are well optimized though.
Potential reduce by 60.7 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 60.7 kB or 40% of the original size.
Number of requests can be reduced by 34 (69%)
49
15
The browser has sent 49 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ui. 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 as a result speed up the page load time.
ui.de
339 ms
www.universal-investment.de
321 ms
813 ms
www.universal-investment.com
90 ms
en
136 ms
55fdf522e5f24ca4beb1614dbad2b563
279 ms
e.js
231 ms
aa50f038a7ec49329f8096e027be33d1
772 ms
ai.0.js
82 ms
jquery-1.8.3.min.js
305 ms
205 ms
t.js
301 ms
meta-search.svg
113 ms
close.svg
205 ms
h2-klapper-right.svg
201 ms
ui-logo.png
254 ms
meta-menu.svg
193 ms
0ca2a666f4e5e51181090050c0185231
234 ms
0ca2a666f4e5e51181090050c0185231
1038 ms
fd66dd4b0ce6e51181090050c0185231
287 ms
fd66dd4b0ce6e51181090050c0185231
844 ms
d9389b38e3a3e51181070050c0185231
325 ms
d9389b38e3a3e51181070050c0185231
893 ms
a5fbc581d3a4e51181070050c0185231
389 ms
a5fbc581d3a4e51181070050c0185231
1263 ms
9e8ea548f170e511810d0050c0185226
690 ms
9e8ea548f170e511810d0050c0185226
935 ms
d54702a4ef70e511810d0050c0185226
803 ms
d54702a4ef70e511810d0050c0185226
2025 ms
arrow-magazin-archiv.svg
933 ms
arrow-magazin-archiv.svg
998 ms
arrow-right-01.svg
1033 ms
link-arrow-right.svg
1040 ms
9b253ff5db70e511810f0050c0185227
1108 ms
9b253ff5db70e511810f0050c0185227
1899 ms
1c0beb994876e511810d0050c0185226
1643 ms
1c0beb994876e511810d0050c0185226
1585 ms
933d1eea6881e511810f0050c0185227
1263 ms
933d1eea6881e511810f0050c0185227
1352 ms
115e5dcaf170e511810f0050c0185227
1644 ms
115e5dcaf170e511810f0050c0185227
1825 ms
7ab9e7f8-e5ef-482f-a436-e159402ee6ea.woff
1693 ms
b263ec73-3337-45b9-9e86-933d27164f2c.woff
2189 ms
cnt_js.php
205 ms
meta-search.svg
1232 ms
close.svg
1423 ms
h2-klapper-right.svg
1449 ms
meta-menu.svg
1408 ms
arrow-magazin-archiv.svg
1475 ms
arrow-magazin-archiv.svg
1496 ms
arrow-right-01.svg
1509 ms
link-arrow-right.svg
1537 ms
in.js
6 ms
share.js
430 ms
secureAnonymousFramework
27 ms
track
154 ms
ui.de 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.
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
Image elements do not have [alt] attributes
Links do not have a discernible name
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>).
ui.de 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
ui.de 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
Image elements do not have [alt] attributes
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
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 Ui.de 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 Ui.de 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.
ui.de
Open Graph description is not detected on the main page of Ui. 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: