5.4 sec in total
428 ms
4.4 sec
560 ms
Welcome to waverex.de homepage info - get ready to check Waverex best content right away, or after learning these important things about waverex.de
WaveReX Karte Refill Expansion für Korg M1, M1r und Wavestation. Eigene Samples und Waves im M1 und der Korg Wavestation. Startseite
Visit waverex.deWe analyzed Waverex.de page load time and found that the first response time was 428 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.
waverex.de performance score
name
value
score
weighting
Value3.6 s
33/100
10%
Value7.6 s
3/100
25%
Value8.2 s
20/100
10%
Value110 ms
97/100
30%
Value0.007
100/100
15%
Value6.9 s
54/100
10%
428 ms
215 ms
324 ms
327 ms
441 ms
Our browser made a total of 72 requests to load all elements on the main page. We found that 56% of them (40 requests) were addressed to the original Waverex.de, 32% (23 requests) were made to Fonts.gstatic.com and 6% (4 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (2.3 sec) belongs to the original domain Waverex.de.
Page size can be reduced by 61.5 kB (4%)
1.7 MB
1.7 MB
In fact, the total size of Waverex.de main page is 1.7 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. 65% of websites need less resources to load. Images take 1.5 MB which makes up the majority of the site volume.
Potential reduce by 47.4 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 47.4 kB or 80% of the original size.
Potential reduce by 11.4 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. Waverex images are well optimized though.
Potential reduce by 1.4 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 1.3 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. Waverex.de has all CSS files already compressed.
Number of requests can be reduced by 29 (62%)
47
18
The browser has sent 47 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Waverex. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 13 to 1 for JavaScripts and from 18 to 1 for CSS and as a result speed up the page load time.
428 ms
font-awesome-5.min.css
215 ms
font-awesome-v4-shims.css
324 ms
animate.min.css
327 ms
sppagebuilder.css
441 ms
css
31 ms
magnific-popup.css
331 ms
css
46 ms
content.min.css
329 ms
css
51 ms
css
50 ms
bootstrap.min.css
448 ms
font-awesome.min.css
431 ms
legacy.css
433 ms
template.css
543 ms
preset1.css
434 ms
pagebuilder.css
540 ms
frontend-edit.css
542 ms
jquery.min.js
652 ms
jquery-noconflict.js
553 ms
jquery-migrate.min.js
553 ms
jquery.parallax.js
645 ms
sppagebuilder.js
757 ms
jquery.magnific-popup.min.js
648 ms
bootstrap.min.js
667 ms
jquery.sticky.js
671 ms
main.js
753 ms
frontend-edit.js
756 ms
core.js
759 ms
cookieconsent.min.css
23 ms
cookieconsent.min.js
30 ms
analytics.js
176 ms
wavrex_logo_copy.png
215 ms
wavrex_logo_copy.png
216 ms
slide_20-1.jpg
2314 ms
slide_20-m1.jpg
401 ms
slide_20-2.jpg
507 ms
keys_0420.jpg
402 ms
dummycard.png
832 ms
m1betacard2.png
1047 ms
beta_frei2.jpg
512 ms
old1.jpg
512 ms
wr_r8_ucard.jpg
616 ms
wavrex_logo_copy.png
620 ms
fblogo2.png
620 ms
instgr.png
725 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4saVc.ttf
45 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf
28 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjr0B4gaVc.ttf
44 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4saVc.ttf
86 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf
45 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4saVc.ttf
87 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf
45 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4saVc.ttf
48 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf
45 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4saVc.ttf
91 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVc.ttf
49 ms
mem9YaCnxnKRiYZOCIYScr0.ttf
50 ms
fontawesome-webfont.woff
1096 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk8ZkWVwexQ.ttf
91 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk8ZkWVAexQ.ttf
50 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk_RkWVAexQ.ttf
51 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk5hkWVwexQ.ttf
92 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk5hkWVAexQ.ttf
83 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkxhjWVwexQ.ttf
93 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkxhjWVAexQ.ttf
88 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkyFjWVwexQ.ttf
92 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkyFjWVAexQ.ttf
88 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk0ZjWVwexQ.ttf
119 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk0ZjWVAexQ.ttf
90 ms
collect
28 ms
collect
91 ms
waverex.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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Links do not have a discernible name
waverex.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
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
waverex.de 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
EN
DE
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Waverex.de can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed German language. Our system also found out that Waverex.de main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
waverex.de
Open Graph data is detected on the main page of Waverex. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: