1.3 sec in total
11 ms
992 ms
289 ms
Welcome to my.zwift.com homepage info - get ready to check My Zwift best content for United States right away, or after learning these important things about my.zwift.com
Zwift is virtual training for running and cycling. Smash your goals and compete with others around the world. With structured workouts and social group rides. iOS and Android compatible. Trusted by th...
Visit my.zwift.comWe analyzed My.zwift.com page load time and found that the first response time was 11 ms and then it took 1.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.
my.zwift.com performance score
name
value
score
weighting
Value9.4 s
0/100
10%
Value9.7 s
0/100
25%
Value24.4 s
0/100
10%
Value5,030 ms
0/100
30%
Value0.175
69/100
15%
Value46.3 s
0/100
10%
11 ms
24 ms
40 ms
45 ms
428 ms
Our browser made a total of 68 requests to load all elements on the main page. We found that 3% of them (2 requests) were addressed to the original My.zwift.com, 65% (44 requests) were made to Content-cdn.zwift.com and 15% (10 requests) were made to Cdn.segment.com. The less responsive or slowest element that took the longest time to load (428 ms) relates to the external source Cdn.segment.com.
Page size can be reduced by 205.5 kB (14%)
1.5 MB
1.3 MB
In fact, the total size of My.zwift.com main page is 1.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. 70% of websites need less resources to load. Javascripts take 938.0 kB which makes up the majority of the site volume.
Potential reduce by 203.9 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 203.9 kB or 76% of the original size.
Potential reduce by 615 B
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.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. My.zwift.com has all CSS files already compressed.
Number of requests can be reduced by 55 (93%)
59
4
The browser has sent 59 CSS, Javascripts, AJAX and image requests in order to completely render the main page of My Zwift. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 52 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
my.zwift.com
11 ms
my.zwift.com
24 ms
feed
40 ms
sign-in
45 ms
analytics.min.js
428 ms
chat-client.js
128 ms
3312120578.js
105 ms
keycloak.js
15 ms
prismic.js
83 ms
all.min.css
16 ms
61945e83c59876b60360543d287d0b81e23fe3a7_CSS.a75b5338.chunk.css
78 ms
3b0f11cf54005000c8749dc0497c96fc628dee9e_CSS.1538377f.chunk.css
78 ms
styles.893aabf3.chunk.css
93 ms
sign-in-page.js.e1002506.chunk.css
79 ms
polyfills-7c838cd9032a6e9f54a4.js
78 ms
sign-in-page.js
70 ms
_app.js
92 ms
webpack-de4be2cb2a0192863fdf.js
85 ms
framework.253c12291c6fa5fdea09.js
85 ms
c78d26b1.cc744ee6779cc7a51697.js
85 ms
6b859938.d870b58b727d86d7e6b1.js
90 ms
ebec3a01.08ec8254ac7734362b6e.js
94 ms
83adb279.a2b60d7e452765aaa2bb.js
91 ms
9be475604b1d9ae89e506a6bf89330df4f371d83.226057fb948fc4bb35f5.js
98 ms
ab647153e53316be1a24fa793e383e670b329394.1c3ff9ac501537f099a8.js
97 ms
d5a1b490c6a2c689a92db84f2de85d80819f2b0a.6b427dc90ad6edbf2f8d.js
97 ms
61945e83c59876b60360543d287d0b81e23fe3a7.4749a2f549a517964555.js
101 ms
61945e83c59876b60360543d287d0b81e23fe3a7_CSS.2c372599cf640b277883.js
93 ms
63c8018532d4f562c1d7ab95ebdf428b94de712c.f305971944ba64561a0b.js
101 ms
6d0e16c2a33993d1547415a4023c3bdace966a08.91490dae4f6a6f89dc77.js
101 ms
a63c3a5e8f2efb2d731c52226881200e84c60fd4.14d9ae1b381748c5df47.js
102 ms
9dfba78c1c27ce86f109def969f7b52928e2198c.1c30315eed0ef08002f9.js
102 ms
d0fc93e71040ecae933e5c5602806d45d8944087.a139232985d4459e1ffa.js
102 ms
3405bf5a04d699c4027cfc0ab966f9fcc0af449a.984caccdd1cbc4812c4a.js
103 ms
e9577fe4d2dd52d86a24c480d7d536be9725aafa.a5062e4d5ebe6e2fbff9.js
104 ms
b64216a27b978a1784b7ef3979243c184d1af92c.7ec8a3a7018d45ff5070.js
105 ms
f55d5101ce35a776a9c0fe74ad1c0ecd7fd5b869.fa001e0a3fdbb0546ee2.js
107 ms
612da70fe017f7a8e8d8320008c5bcdb21547514.9bebcfe4338cb87c7e9a.js
102 ms
67d07d8318ad988147f39efceca8de6795858a65.44bcc79fc385cf3864ce.js
104 ms
39176629c1da842e76180f74416101dca5b33e75.0fbe89e96c9ca1a39e00.js
106 ms
50f92e410053fedf886d55bb44a3be5a7e61b204.057a2fe9fba8b1a3031d.js
106 ms
3b0f11cf54005000c8749dc0497c96fc628dee9e_CSS.8acfccebf0888146e69c.js
106 ms
styles.7d2d1dbc6bf0ae587cef.js
107 ms
main-00889a5dc2870a427634.js
107 ms
a9ed89c4bd04d160e23732c74ab1c9418e00cc74.ef9873790d11d629a552.js
108 ms
b910428c63f21562b6df86af869989577c8158a1.496351e883152a25d09b.js
109 ms
dbc95eb93315d1690e82e961e00f6fd66fc0a272.79eef5bfcb6b09ae10e5.js
47 ms
_buildManifest.js
44 ms
_ssgManifest.js
41 ms
a3312120578.html
209 ms
ZwiftSprint-Medium.woff
115 ms
ZwiftSprint-Regular.woff
116 ms
ZwiftSprint-Black.woff
117 ms
ZwiftFondo-Regular.woff
115 ms
ZwiftSprint-Bold.woff
116 ms
settings
18 ms
vcd15cbe7772f49c399c6a5babf22c1241717689176015
144 ms
ajs-destination.bundle.ed53a26b6edc80c65d73.js
3 ms
schemaFilter.bundle.5c2661f67b4b71a6d9bd.js
3 ms
ad70603567d2fd1e96e9.js
5 ms
amplitude.dynamic.js.gz
3 ms
google-tag-manager.dynamic.js.gz
5 ms
hotjar.dynamic.js.gz
6 ms
optimizely.dynamic.js.gz
6 ms
commons.a61d7bea37d2de5d4b69.js.gz
19 ms
hotjar-504337.js
128 ms
amplitude-5.2.2-min.gz.js
19 ms
gtm.js
71 ms
my.zwift.com accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
button, link, and menuitem elements do not have accessible names.
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
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Some elements have a [tabindex] value greater than 0
my.zwift.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
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
my.zwift.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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 My.zwift.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 My.zwift.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.
my.zwift.com
Open Graph data is detected on the main page of My Zwift. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: