3.4 sec in total
403 ms
1.5 sec
1.5 sec
Visit morningstar.ch now to see the best up-to-date Morningstar content for Switzerland and also check out these interesting facts you probably never knew about morningstar.ch
Analysen zu Investmentfonds und ETFs, Fondsdaten, Aktienkurse, Musterportfolios und Research-Tools, damit Sie bessere Anlageentscheidungen treffen
Visit morningstar.chWe analyzed Morningstar.ch page load time and found that the first response time was 403 ms and then it took 3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
morningstar.ch performance score
name
value
score
weighting
Value6.3 s
3/100
10%
Value11.5 s
0/100
25%
Value17.1 s
0/100
10%
Value3,820 ms
1/100
30%
Value0.09
92/100
15%
Value23.5 s
1/100
10%
403 ms
87 ms
151 ms
115 ms
158 ms
Our browser made a total of 106 requests to load all elements on the main page. We found that 15% of them (16 requests) were addressed to the original Morningstar.ch, 52% (55 requests) were made to Euim.mstar.com and 8% (9 requests) were made to Morningstar.co.uk. The less responsive or slowest element that took the longest time to load (608 ms) relates to the external source Morningstar.co.uk.
Page size can be reduced by 238.1 kB (12%)
1.9 MB
1.7 MB
In fact, the total size of Morningstar.ch main page is 1.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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 958.9 kB which makes up the majority of the site volume.
Potential reduce by 126.2 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 126.2 kB or 73% of the original size.
Potential reduce by 17.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. Morningstar images are well optimized though.
Potential reduce by 87.0 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. This website has mostly compressed JavaScripts.
Potential reduce by 8.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. Morningstar.ch has all CSS files already compressed.
Number of requests can be reduced by 79 (81%)
98
19
The browser has sent 98 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Morningstar. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 55 to 1 for JavaScripts and from 20 to 1 for CSS and as a result speed up the page load time.
403 ms
gtm.js
87 ms
cookieConsent.min.css
151 ms
mds.css
115 ms
autocomplete.css
158 ms
jqtransform.css
158 ms
mobileOverlay.css
158 ms
jquery.min.js
145 ms
jquery-migrate-1.4.1.min.js
113 ms
ads.js
183 ms
jquery.autocomplete-1.4.2.js
188 ms
jquery.json-2.2.min.js
187 ms
jquery.cookie.js
190 ms
loginPop.js
190 ms
mobile-overlay.js
190 ms
jquery.jqtransform.js
187 ms
jquery.validate.min.js
145 ms
additional-methods.min.js
144 ms
colortip-1.0-jquery.js
195 ms
clipboard.min.js
194 ms
mds_com.min.js
200 ms
script.js
143 ms
homefunctions.js
203 ms
usabilla.js
203 ms
core.js
202 ms
images.css
100 ms
m-global_v_EU.css
205 ms
main5.css
96 ms
newRegistrationProcess.css
206 ms
responsive.css
210 ms
pmaster5.css
212 ms
NavMenu-button.css
211 ms
NLdropdown.css
209 ms
headerNewDesing.css
209 ms
core.css
210 ms
bootstrap.min.js
139 ms
logOut.js
212 ms
eumodaldialog.min.js
211 ms
crossdomain.min.js
212 ms
jquery.modaldialog.css
211 ms
responsive.js
212 ms
DynamicGAFunctions.js
216 ms
WebResource.axd
104 ms
ScriptResource.axd
328 ms
ScriptResource.axd
119 ms
apimanager.js
112 ms
jquery.audiencetarget.js
138 ms
MPUAdHelper.js
139 ms
Images.css
19 ms
main5.css
21 ms
9e74d6dad1f3.js
81 ms
print.css
38 ms
news_icon_80x80.png
195 ms
MCOHMFJ2MVEVPAJNB73ASRA4EA.jpg
378 ms
ETF_UK_Main_(1).jpg
280 ms
Euro_EU_Parliament_Large.jpg
193 ms
347BSP2KJNBCLKVD7DGXSFLDLU.jpg
525 ms
xml_36x14.gif
66 ms
e843315.svg
66 ms
facebook-03.svg
64 ms
twitter-01.svg
62 ms
linkedin-02.svg
60 ms
youtube-06.svg
92 ms
instagram-07.svg
120 ms
lightbulb_30x30.png
190 ms
new_open_icon.png
190 ms
shield_icon_80x80.png
188 ms
Sparkly%20European%20digital%20map%20article.jpg
608 ms
money%20and%20globe%20article.jpg
228 ms
leaf_icon_80x80.png
258 ms
shield_icon_80x80.png
258 ms
indexes_icon_80x80.png
258 ms
rampopen.gif
76 ms
600bda4e-11fe-4903-9a39-bb6b77389170.woff
72 ms
5a67b0ed-239e-4f3e-adeb-8b1e517a5bd3.woff
134 ms
f9c3797f-895f-42e2-9e83-9340081311d6.woff
139 ms
3b5a7b6a-e026-4ee8-b80f-6aa5e44b2977.woff
180 ms
656bb203-0436-41f9-8266-de61f5c29096.woff
132 ms
a55d5255-e095-4e87-ac0d-fe0968b0a9c6.woff
137 ms
ga.js
150 ms
gmb.aspx
123 ms
mds.css
8 ms
polyfill.min.js
39 ms
jquery.min.js
27 ms
jquery-migrate.min.js
27 ms
eq.min.js
27 ms
angular.min.js
29 ms
lodash.js
28 ms
vue.min.js
26 ms
vue-custom-element.min.js
35 ms
main.js
34 ms
main.js
34 ms
sal-components-font.js
113 ms
sal-components-foundation-tiny.js
33 ms
sal-components-core.js
33 ms
sal-components-symbol-icon.js
178 ms
mwc-tabs.js
174 ms
sal-components-segment-band.js
173 ms
sal-components-chiclet.js
173 ms
sal-components-report-table.js
173 ms
sal-components-mds-icon.js
175 ms
d3.js
237 ms
sal-components-gmb.js
235 ms
interact.min.js
257 ms
mds.svg
114 ms
nr-spa-1216.min.js
32 ms
morningstar.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
<frame> or <iframe> elements do not have a title
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>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
morningstar.ch 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
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
morningstar.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
Tap targets are not sized appropriately
DE
DE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Morningstar.ch can be misinterpreted by Google and other search engines. Our service has detected that German is used on the page, and it matches the claimed language. Our system also found out that Morningstar.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.
morningstar.ch
Open Graph description is not detected on the main page of Morningstar. 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: