Report Summary

  • 10

    Performance

    Renders faster than
    23% of other websites

  • 69

    Accessibility

    Visual factors better than
    that of 35% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

swim.org

SWIM

Page Load Speed

24.5 sec in total

First Response

2.9 sec

Resources Loaded

20.9 sec

Page Rendered

633 ms

swim.org screenshot

About Website

Visit swim.org now to see the best up-to-date SWIM content for United States and also check out these interesting facts you probably never knew about swim.org

Visit swim.org

Key Findings

We analyzed Swim.org page load time and found that the first response time was 2.9 sec and then it took 21.6 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.

Performance Metrics

swim.org performance score

10

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value19.7 s

0/100

10%

LCP (Largest Contentful Paint)

Value23.9 s

0/100

25%

SI (Speed Index)

Value20.5 s

0/100

10%

TBT (Total Blocking Time)

Value2,750 ms

3/100

30%

CLS (Cumulative Layout Shift)

Value0.216

58/100

15%

TTI (Time to Interactive)

Value22.5 s

1/100

10%

Network Requests Diagram

swim.org

2900 ms

main.css

629 ms

AC_RunActiveContent.js

870 ms

ga.js

66 ms

search_bt.gif

202 ms

Our browser made a total of 102 requests to load all elements on the main page. We found that 84% of them (86 requests) were addressed to the original Swim.org, 9% (9 requests) were made to Ai.esmplus.com and 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (18 sec) belongs to the original domain Swim.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 205.1 kB (31%)

Content Size

654.6 kB

After Optimization

449.4 kB

In fact, the total size of Swim.org main page is 654.6 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. 20% of websites need less resources to load. Images take 473.5 kB which makes up the majority of the site volume.

HTML Optimization

-92%

Potential reduce by 103.5 kB

  • Original 112.8 kB
  • After minification 63.0 kB
  • After compression 9.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 49.8 kB, which is 44% 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 103.5 kB or 92% of the original size.

Image Optimization

-12%

Potential reduce by 57.8 kB

  • Original 473.5 kB
  • After minification 415.7 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, SWIM needs image optimization as it can save up to 57.8 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-27%

Potential reduce by 6.8 kB

  • Original 25.5 kB
  • After minification 22.3 kB
  • After compression 18.7 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 6.8 kB or 27% of the original size.

CSS Optimization

-87%

Potential reduce by 37.1 kB

  • Original 42.8 kB
  • After minification 35.7 kB
  • After compression 5.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. Swim.org needs all CSS files to be minified and compressed as it can save up to 37.1 kB or 87% of the original size.

Requests Breakdown

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

Requests Now

96

After Optimization

66

The browser has sent 96 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 and as a result speed up the page load time.

Accessibility Review

swim.org accessibility score

69

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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.

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

swim.org best practices score

67

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

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

swim.org SEO score

83

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

    KO

  • Language Claimed

    N/A

  • Encoding

    EUC-KR

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Swim.org can be misinterpreted by Google and other search engines. Our service has detected that Korean is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Swim.org main page’s claimed encoding is euc-kr. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

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