Tools & Wizards About Us
schwinn.com screenshot

Report Summary

  • 81

    Performance

    Renders faster than
    87% of other websites

  • 80

    Accessibility

    Visual factors better than
    that of 50% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

schwinn.com

Schwinn Bicycles | Schwinn Fitness

Page Load Speed

567 ms in total

First Response

93 ms

Resources Loaded

282 ms

Page Rendered

192 ms

schwinn.com screenshot

About Website

Click here to check amazing Schwinn content for United States. Otherwise, check out these important facts you probably never knew about schwinn.com

Official site of Schwinn bikes and fitness equipment. Find your next Schwinn bicycle or exercise bike here.

Visit schwinn.com

Key Findings

We analyzed Schwinn.com page load time and found that the first response time was 93 ms and then it took 474 ms to load all DOM resources and completely render a web page. This is an excellent result, as only 5% of websites can load faster.

Performance Metrics

schwinn.com performance score

81

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.8 s

58/100

10%

LCP (Largest Contentful Paint)

Value4.3 s

42/100

25%

SI (Speed Index)

Value2.8 s

96/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.003

100/100

15%

TTI (Time to Interactive)

Value2.8 s

97/100

10%

Network Requests Diagram

www.schwinn.com

93 ms

sifr.js

7 ms

base.js

13 ms

base.css

14 ms

ga.js

28 ms

Our browser made a total of 18 requests to load all elements on the main page. We found that 83% of them (15 requests) were addressed to the original Schwinn.com, 11% (2 requests) were made to Google-analytics.com and 6% (1 request) were made to Stats.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (93 ms) belongs to the original domain Schwinn.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 83.9 kB (18%)

Content Size

463.4 kB

After Optimization

379.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Schwinn.com main page is 463.4 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 25% of websites need less resources to load. Images take 388.8 kB which makes up the majority of the site volume.

HTML Optimization

-61%

Potential reduce by 3.2 kB

  • Original 5.3 kB
  • After minification 5.0 kB
  • After compression 2.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. 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 3.2 kB or 61% of the original size.

Image Optimization

-11%

Potential reduce by 43.3 kB

  • Original 388.8 kB
  • After minification 345.5 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. Obviously, Schwinn needs image optimization as it can save up to 43.3 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-42%

Potential reduce by 19.6 kB

  • Original 46.8 kB
  • After minification 46.4 kB
  • After compression 27.2 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 19.6 kB or 42% of the original size.

CSS Optimization

-79%

Potential reduce by 17.7 kB

  • Original 22.4 kB
  • After minification 15.2 kB
  • After compression 4.7 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. Schwinn.com needs all CSS files to be minified and compressed as it can save up to 17.7 kB or 79% of the original size.

Requests Breakdown

Number of requests can be reduced by 5 (31%)

Requests Now

16

After Optimization

11

  • Images
  • JavaScript
  • CSS

The browser has sent 16 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Schwinn. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests and as a result speed up the page load time.

Network Requests Diagram

www.schwinn.com

www.schwinn.com

93 ms

sifr.js

sifr.js

7 ms

base.js

base.js

13 ms

base.css

base.css

14 ms

ga.js

ga.js

28 ms

bg_tile.png

bg_tile.png

5 ms

bg_wrapper_shadow.png

bg_wrapper_shadow.png

6 ms

bg_landing_header.png

bg_landing_header.png

7 ms

logo.png

logo.png

7 ms

photo_schwinn_main.jpg

photo_schwinn_main.jpg

22 ms

photo_schwinn_fitness.jpg

photo_schwinn_fitness.jpg

13 ms

bg_footer.png

bg_footer.png

7 ms

logo_dorel.png

logo_dorel.png

8 ms

btn_facebook.png

btn_facebook.png

9 ms

btn_youtube.png

btn_youtube.png

10 ms

print.css

print.css

35 ms

__utm.gif

__utm.gif

12 ms

collect

collect

62 ms

Accessibility Review

schwinn.com accessibility score

80

Accessibility Issues

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

Best Practices

schwinn.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

SEO Factors

schwinn.com SEO score

92

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

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

schwinn.com

Open Graph description is not detected on the main page of Schwinn. 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: