4.9 sec in total
780 ms
3.5 sec
654 ms
Visit zwift.de now to see the best up-to-date Zwift content and also check out these interesting facts you probably never knew about zwift.de
Visit zwift.deWe analyzed Zwift.de page load time and found that the first response time was 780 ms and then it took 4.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
zwift.de performance score
name
value
score
weighting
Value3.4 s
38/100
10%
Value20.5 s
0/100
25%
Value6.2 s
42/100
10%
Value170 ms
93/100
30%
Value0.008
100/100
15%
Value5.3 s
73/100
10%
780 ms
283 ms
505 ms
847 ms
18 ms
Our browser made a total of 46 requests to load all elements on the main page. We found that 98% of them (45 requests) were addressed to the original Zwift.de, 2% (1 request) were made to D3e54v103j8qbb.cloudfront.net. The less responsive or slowest element that took the longest time to load (2.3 sec) belongs to the original domain Zwift.de.
Page size can be reduced by 441.3 kB (17%)
2.6 MB
2.2 MB
In fact, the total size of Zwift.de main page is 2.6 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. Images take 2.1 MB which makes up the majority of the site volume.
Potential reduce by 102.3 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 24.3 kB, which is 22% 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 102.3 kB or 93% of the original size.
Potential reduce by 95.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. Zwift images are well optimized though.
Potential reduce by 108.5 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 108.5 kB or 54% of the original size.
Potential reduce by 134.8 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. Zwift.de needs all CSS files to be minified and compressed as it can save up to 134.8 kB or 88% of the original size.
We found no issues to fix!
26
26
The browser has sent 26 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Zwift. According to our analytics all requests are already optimized.
zwift.de
780 ms
normalize.css
283 ms
components.css
505 ms
zwift-ictrainer-vergleich.css
847 ms
jquery-3.5.1.min.dc5e7f18c8.js
18 ms
zwift-ictrainer-vergleich.js
480 ms
Hero_.png
2260 ms
WB_farbe_trans.svg
125 ms
zwift-seeklogo.com.svg
127 ms
check-outline.svg
168 ms
minus-outline.svg
217 ms
App-Store-Google2x2x.png
226 ms
Nico_Markgraf-176x300.webp
237 ms
App-Store-MacOS2x2x.png
241 ms
App-Store-Windows2x2x.png
284 ms
App-Store-iOS2x2x.png
325 ms
Garmin.png
338 ms
trainingpeaks.png
347 ms
todays-plan.png
364 ms
strava.png
396 ms
intervals.webp
435 ms
Logo-SpeedVille.webp
451 ms
tredict.png
459 ms
runalyze-300x65.webp
477 ms
2Peak_flach.webp
509 ms
tacx_kleiner.webp
545 ms
wahoo.png
563 ms
Elite_kleiner.webp
569 ms
saris_kleiner.webp
590 ms
Suunto-Big-300x117.webp
622 ms
Dare2Tri_red-flach.webp
654 ms
zycle-logo.png
677 ms
BH-Fitness.png
679 ms
CYCPLUS-logo.webp
702 ms
JetBlack.png
734 ms
kp-logo-black_flach.webp
766 ms
Core.webp
791 ms
concept2-rowing_50px.webp
790 ms
WaterRower_flach.webp
814 ms
WB_sw-negativ_trans.svg
847 ms
Facebook.svg
826 ms
Inter-Black.ttf
1402 ms
Inter-Bold.ttf
1342 ms
Inter-SemiBold.ttf
1465 ms
Inter-Regular.ttf
1128 ms
Youtube.svg
770 ms
zwift.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
Links do not have a discernible name
zwift.de 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
zwift.de 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
Tap targets are not sized appropriately
EN
DE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Zwift.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 Zwift.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.
zwift.de
Open Graph description is not detected on the main page of Zwift. 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: