Tools & Wizards About Us

Report Summary

  • 10

    Performance

    Renders faster than
    23% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 88

    SEO

    Google-friendlier than
    65% of websites

my.zwift.com

The at Home Cycling & Running Virtual Training App

Page Load Speed

1.3 sec in total

First Response

11 ms

Resources Loaded

992 ms

Page Rendered

289 ms

About Website

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.com

Key Findings

We 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.

Performance Metrics

my.zwift.com performance score

10

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value9.4 s

0/100

10%

LCP (Largest Contentful Paint)

Value9.7 s

0/100

25%

SI (Speed Index)

Value24.4 s

0/100

10%

TBT (Total Blocking Time)

Value5,030 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.175

69/100

15%

TTI (Time to Interactive)

Value46.3 s

0/100

10%

Network Requests Diagram

my.zwift.com

11 ms

my.zwift.com

24 ms

feed

40 ms

sign-in

45 ms

analytics.min.js

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 Optimization Overview & Recommendations

Page size can be reduced by 205.5 kB (14%)

Content Size

1.5 MB

After Optimization

1.3 MB

  • HTML
  • JavaScript
  • CSS

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.

HTML Optimization

-76%

Potential reduce by 203.9 kB

  • Original 269.6 kB
  • After minification 269.6 kB
  • After compression 65.7 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.

JavaScript Optimization

-0%

Potential reduce by 615 B

  • Original 938.0 kB
  • After minification 938.0 kB
  • After compression 937.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.

CSS Optimization

-0%

Potential reduce by 1.0 kB

  • Original 303.2 kB
  • After minification 303.2 kB
  • After compression 302.2 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.

Requests Breakdown

Number of requests can be reduced by 55 (93%)

Requests Now

59

After Optimization

4

  • AJAX
  • JavaScript
  • CSS

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.

Network Requests Diagram

Accessibility Review

my.zwift.com accessibility score

84

Accessibility Issues

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

High

button, link, and menuitem elements do not have accessible names.

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Some elements have a [tabindex] value greater than 0

Best Practices

my.zwift.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

my.zwift.com SEO score

88

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    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.

Social Sharing Optimization

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: