Tools & Wizards About Us
swim.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

swim.com

Swim.com | Compete, share and track your swimming workouts

Page Load Speed

2.6 sec in total

First Response

254 ms

Resources Loaded

1.7 sec

Page Rendered

599 ms

swim.com screenshot

About Website

Welcome to swim.com homepage info - get ready to check Swim best content for United States right away, or after learning these important things about swim.com

Log your workouts, track your progress and compete with friends on Swim.com

Visit swim.com

Key Findings

We analyzed Swim.com page load time and found that the first response time was 254 ms and then it took 2.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

swim.com performance score

0

Network Requests Diagram

www.swim.com

254 ms

all.js

130 ms

wantinv1.css

31 ms

commonLanding.js

16 ms

wantin.js

6 ms

Our browser made a total of 43 requests to load all elements on the main page. We found that 56% of them (24 requests) were addressed to the original Swim.com, 9% (4 requests) were made to Stats.g.doubleclick.net and 7% (3 requests) were made to Staticxx.facebook.com. The less responsive or slowest element that took the longest time to load (254 ms) belongs to the original domain Swim.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 31.2 kB (25%)

Content Size

123.2 kB

After Optimization

92.0 kB

  • HTML
  • JavaScript

In fact, the total size of Swim.com main page is 123.2 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. 60% of websites need less resources to load. Javascripts take 79.4 kB which makes up the majority of the site volume.

HTML Optimization

-71%

Potential reduce by 31.1 kB

  • Original 43.8 kB
  • After minification 38.3 kB
  • After compression 12.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. This page needs HTML code to be minified as it can gain 5.5 kB, which is 12% 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 31.1 kB or 71% of the original size.

JavaScript Optimization

-0%

Potential reduce by 111 B

  • Original 79.4 kB
  • After minification 79.4 kB
  • After compression 79.3 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.

Requests Breakdown

Number of requests can be reduced by 19 (54%)

Requests Now

35

After Optimization

16

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.swim.com

www.swim.com

254 ms

all.js

all.js

130 ms

wantinv1.css

wantinv1.css

31 ms

commonLanding.js

commonLanding.js

16 ms

wantin.js

wantin.js

6 ms

gtm.js

gtm.js

76 ms

bg-top-header.png

bg-top-header.png

74 ms

arrow_white.png

arrow_white.png

22 ms

sprite-header.png

sprite-header.png

18 ms

landing-pagee.jpg

landing-pagee.jpg

22 ms

new_dot.png

new_dot.png

19 ms

bgmobile.png

bgmobile.png

23 ms

thumbnailvideo.jpg

thumbnailvideo.jpg

55 ms

ico_video.png

ico_video.png

57 ms

arrow_grey.png

arrow_grey.png

19 ms

sprite_landing.png

sprite_landing.png

47 ms

other_landd.jpg

other_landd.jpg

54 ms

bg-gild.png

bg-gild.png

46 ms

arrow_bottomland.png

arrow_bottomland.png

48 ms

img-progress-climb.jpg

img-progress-climb.jpg

49 ms

bg_store.png

bg_store.png

49 ms

ico-footer-follow.png

ico-footer-follow.png

54 ms

146 ms

DINLigh.woff

DINLigh.woff

41 ms

DINBold.ttf

DINBold.ttf

41 ms

DINLightAlternate.ttf

DINLightAlternate.ttf

45 ms

DinMittelEFOP.ttf

DinMittelEFOP.ttf

46 ms

xd_arbiter.php

xd_arbiter.php

103 ms

xd_arbiter.php

xd_arbiter.php

165 ms

analytics.js

analytics.js

74 ms

ga.js

ga.js

99 ms

dc.js

dc.js

44 ms

__utm.gif

__utm.gif

35 ms

__utm.gif

__utm.gif

36 ms

collect

collect

16 ms

ga-audiences

ga-audiences

47 ms

collect

collect

60 ms

xd_arbiter.php

xd_arbiter.php

44 ms

ga-audiences

ga-audiences

17 ms

nr-885.min.js

nr-885.min.js

17 ms

chartbeat.js

chartbeat.js

24 ms

f484ca45fd

f484ca45fd

50 ms

ping

ping

7 ms

SEO Factors

swim.com SEO score

0

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

swim.com

Open Graph data is detected on the main page of Swim. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: