3.3 sec in total
732 ms
2.3 sec
263 ms
Welcome to wilhelmbras.com homepage info - get ready to check Wilhelmbras best content right away, or after learning these important things about wilhelmbras.com
Experimental musician, producer and sound artist, working with advanced synthesizers and multichannel environments, also with sound design for theater and film.
Visit wilhelmbras.comWe analyzed Wilhelmbras.com page load time and found that the first response time was 732 ms and then it took 2.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
wilhelmbras.com performance score
name
value
score
weighting
Value3.2 s
44/100
10%
Value7.0 s
6/100
25%
Value6.2 s
44/100
10%
Value250 ms
84/100
30%
Value1.18
1/100
15%
Value6.9 s
53/100
10%
732 ms
73 ms
362 ms
38 ms
250 ms
Our browser made a total of 42 requests to load all elements on the main page. We found that 88% of them (37 requests) were addressed to the original Wilhelmbras.com, 5% (2 requests) were made to Fonts.gstatic.com and 2% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (996 ms) belongs to the original domain Wilhelmbras.com.
Page size can be reduced by 99.6 kB (4%)
2.5 MB
2.5 MB
In fact, the total size of Wilhelmbras.com main page is 2.5 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. 50% of websites need less resources to load. Images take 2.3 MB which makes up the majority of the site volume.
Potential reduce by 49.1 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 8.5 kB, which is 15% 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 49.1 kB or 86% of the original size.
Potential reduce by 41.6 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. Wilhelmbras images are well optimized though.
Potential reduce by 6.3 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 2.6 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. Wilhelmbras.com has all CSS files already compressed.
Number of requests can be reduced by 14 (36%)
39
25
The browser has sent 39 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Wilhelmbras. 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.
wilhelmbras.com
732 ms
js
73 ms
css-17720-29155.css
362 ms
simple-line-icons.css
38 ms
css-b819f-45735.css
250 ms
css-1bd2d-26200.css
379 ms
js-5c1d2-26200.js
388 ms
k2.frontend.js
257 ms
js-e1a17-84332.js
531 ms
behaviour.js
372 ms
silverlight.js
387 ms
wmvplayer.js
482 ms
AC_QuickTime.js
496 ms
jwplayer.js
500 ms
lazyloadforjoomla.js
501 ms
css
46 ms
system.css
128 ms
blank.gif
124 ms
S6u9w4BMUTPHh50XSwaPHA.ttf
70 ms
S6uyw4BMUTPHjxAwWw.ttf
77 ms
3fcd8f90952a19354e6b0c4b58be99e3_XL-c0b08ad1bfd6dadf1b9b4ecb69300d74.jpg
618 ms
7b0257640dc77a55cf753ae766e7db69_XL-9228e6567a0cedd7f040d77b5d9219a8.jpg
243 ms
84dcf8a8cba0259cf11299c1eef358f9_XL-e4342125c561da38fa9cfabeb7b2fada.jpg
371 ms
0afa57c41887ce47355dc00226c6156f_XL-22f3d3fc88b6ded62c1b02dc2891227d.jpg
621 ms
f6e095e44349bba4e0775cb7dacd0d59_XL-f0b604a302b64cdfc172833465e8a5d2.jpg
515 ms
0aa2526f21d94ec0cf0dfc24eb7661b7_XL-7d190217bf10a09588a0fabcf9165fb8.jpg
514 ms
4602f2f5153477027a754713438bf3d0_XL-cc5c8754b8d2efa4220808bdcc7dec23.jpg
609 ms
8181cbd90df5a1571a01396c2c96d8d0_XL-84c5630e62c09b70c62170b527168ff2.jpg
743 ms
1e8d6dc02986e7e13576b16a6f372759_XL-d7eef14e78914497d74a4d7cb1098c3e.jpg
758 ms
48e356cffadcfae02e8c0dc7e82338a0_XL-aceb04cac186c8a30457a221291e8368.jpg
773 ms
3d105248b10b0d962a881701f9482c8d_XL-dc90fb9487219d085655c487fb021b7b.jpg
744 ms
3fcd8f90952a19354e6b0c4b58be99e3_M-79d833a7698bbc9d7edd2fcffebe1c8c.jpg
745 ms
7b0257640dc77a55cf753ae766e7db69_M-f314134deb27c7d323c8dfcd07dc8b1b.jpg
747 ms
84dcf8a8cba0259cf11299c1eef358f9_M-295c40719ee578884b2c5734737c92df.jpg
865 ms
0afa57c41887ce47355dc00226c6156f_M-908273c7ec3faf995f1634fa4e884a55.jpg
866 ms
f6e095e44349bba4e0775cb7dacd0d59_M-58c9867858a834ef1032ac928a40f9a4.jpg
872 ms
0aa2526f21d94ec0cf0dfc24eb7661b7_M-9233f0a584ee1ee91f2e6d35f8d6dd19.jpg
871 ms
4602f2f5153477027a754713438bf3d0_M-a8aae5ee040d0df7c08755e84cef0e9d.jpg
880 ms
8181cbd90df5a1571a01396c2c96d8d0_M-ba03d1a28ebcb5a0e6e98fe4566d0491.jpg
902 ms
1e8d6dc02986e7e13576b16a6f372759_M-3edfa71eceac4b73f1c4d157d091375d.jpg
988 ms
48e356cffadcfae02e8c0dc7e82338a0_M-41c5cdd3c86bdeda41585aed2c5a0e33.jpg
990 ms
3d105248b10b0d962a881701f9482c8d_M-2ad2d19c96327f89077cbcf11c6f2f74.jpg
996 ms
wilhelmbras.com 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
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.
wilhelmbras.com 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
wilhelmbras.com SEO score
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 Wilhelmbras.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 Wilhelmbras.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.
wilhelmbras.com
Open Graph description is not detected on the main page of Wilhelmbras. 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: