Tools & Wizards About Us
swapa.org screenshot

Report Summary

  • 19

    Performance

    Renders faster than
    36% of other websites

  • 74

    Accessibility

    Visual factors better than
    that of 40% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 79

    SEO

    Google-friendlier than
    40% of websites

swapa.org

Southwest Airlines Pilots Association

Page Load Speed

2.3 sec in total

First Response

322 ms

Resources Loaded

1.8 sec

Page Rendered

162 ms

swapa.org screenshot

About Website

Click here to check amazing Swapa content for United States. Otherwise, check out these important facts you probably never knew about swapa.org

Southwest Airlines Pilots Association (SWAPA) is the sole bargaining unit for the almost 11,000 Pilots of Southwest Airlines.

Visit swapa.org

Key Findings

We analyzed Swapa.org page load time and found that the first response time was 322 ms and then it took 2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.

Performance Metrics

swapa.org performance score

19

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.5 s

14/100

10%

LCP (Largest Contentful Paint)

Value7.5 s

4/100

25%

SI (Speed Index)

Value9.2 s

13/100

10%

TBT (Total Blocking Time)

Value3,590 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.075

95/100

15%

TTI (Time to Interactive)

Value17.1 s

4/100

10%

Network Requests Diagram

www.swapa.org

322 ms

styles.css

44 ms

jquery

131 ms

jqueryval

348 ms

js

84 ms

Our browser made a total of 60 requests to load all elements on the main page. We found that 43% of them (26 requests) were addressed to the original Swapa.org, 20% (12 requests) were made to Static.xx.fbcdn.net and 18% (11 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (621 ms) relates to the external source 1759130d8be94095bf2b4d3e7fa17e43.svc.dynamics.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 149.7 kB (23%)

Content Size

659.7 kB

After Optimization

510.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Swapa.org main page is 659.7 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 338.3 kB which makes up the majority of the site volume.

HTML Optimization

-66%

Potential reduce by 51.6 kB

  • Original 78.3 kB
  • After minification 75.6 kB
  • After compression 26.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 51.6 kB or 66% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 139.1 kB
  • After minification 139.1 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. Swapa images are well optimized though.

JavaScript Optimization

-17%

Potential reduce by 56.0 kB

  • Original 338.3 kB
  • After minification 338.3 kB
  • After compression 282.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 56.0 kB or 17% of the original size.

CSS Optimization

-41%

Potential reduce by 42.2 kB

  • Original 104.0 kB
  • After minification 104.0 kB
  • After compression 61.8 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. Swapa.org needs all CSS files to be minified and compressed as it can save up to 42.2 kB or 41% of the original size.

Requests Breakdown

Number of requests can be reduced by 32 (57%)

Requests Now

56

After Optimization

24

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.swapa.org

www.swapa.org

322 ms

styles.css

styles.css

44 ms

jquery

jquery

131 ms

jqueryval

jqueryval

348 ms

js

js

84 ms

ws-tracking.js

ws-tracking.js

72 ms

form-loader.js

form-loader.js

81 ms

widgets.js

widgets.js

129 ms

find.js

find.js

85 ms

scripts.js

scripts.js

85 ms

swapa_logo.png

swapa_logo.png

178 ms

swapa_logo.png

swapa_logo.png

180 ms

mdw_picket_0453_web.jpg

mdw_picket_0453_web.jpg

179 ms

microsoftteams-image-81.png

microsoftteams-image-81.png

181 ms

press-release_swapa-carousel.jpg

press-release_swapa-carousel.jpg

176 ms

inthenews_1_thumbnails_350x200.png

inthenews_1_thumbnails_350x200.png

177 ms

press-release_swapa-carousel.jpg

press-release_swapa-carousel.jpg

204 ms

in-the-news-4-thumbnail.jpg

in-the-news-4-thumbnail.jpg

203 ms

facebook.svg

facebook.svg

204 ms

twitter.svg

twitter.svg

201 ms

about.svg

about.svg

202 ms

advocacy.svg

advocacy.svg

202 ms

news.svg

news.svg

224 ms

family.svg

family.svg

226 ms

resources.svg

resources.svg

227 ms

page.php

page.php

195 ms

search.97e496b3.svg

search.97e496b3.svg

219 ms

previous.731131d7.svg

previous.731131d7.svg

222 ms

next.68d53825.svg

next.68d53825.svg

217 ms

ai.0.js

ai.0.js

180 ms

nimbus-sans-bold.f2ed5ea8.woff

nimbus-sans-bold.f2ed5ea8.woff

230 ms

nimbus-sans-medium.d19e46a9.woff

nimbus-sans-medium.d19e46a9.woff

366 ms

urw-din-condensed-bold.c7d4188d.woff

urw-din-condensed-bold.c7d4188d.woff

230 ms

cBZaLPhN

cBZaLPhN

621 ms

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

91 ms

jB7wh023WSF.css

jB7wh023WSF.css

74 ms

SHojUHmeyWm.js

SHojUHmeyWm.js

98 ms

teTZ2tZqwkq.js

teTZ2tZqwkq.js

96 ms

D0hW5UcG2V4.js

D0hW5UcG2V4.js

129 ms

qnn7MVQZYOT.js

qnn7MVQZYOT.js

127 ms

7CmGfGBVS6H.js

7CmGfGBVS6H.js

128 ms

p55HfXW__mM.js

p55HfXW__mM.js

128 ms

G95XClHFDrT.js

G95XClHFDrT.js

138 ms

OWkNLphO4cA.js

OWkNLphO4cA.js

141 ms

settings

settings

160 ms

247165809_296185365842183_412576002242122332_n.jpg

247165809_296185365842183_412576002242122332_n.jpg

64 ms

554t-O9EjCU.js

554t-O9EjCU.js

16 ms

4Za9TE_Wiy4.js

4Za9TE_Wiy4.js

13 ms

UXtr_j2Fwe-.png

UXtr_j2Fwe-.png

14 ms

timeline.e108540dddc96e4b707f5cf259a582d7.js

timeline.e108540dddc96e4b707f5cf259a582d7.js

25 ms

swapapilots

swapapilots

375 ms

polyfills-3b821eda8863adcc4a4b.js

polyfills-3b821eda8863adcc4a4b.js

25 ms

runtime-a697c5a1ae32bd7e4d42.js

runtime-a697c5a1ae32bd7e4d42.js

49 ms

modules.20f98d7498a59035a762.js

modules.20f98d7498a59035a762.js

95 ms

main-fd9ef5eb169057cda26d.js

main-fd9ef5eb169057cda26d.js

75 ms

_app-88bf420a57d49e33be53.js

_app-88bf420a57d49e33be53.js

86 ms

%5BscreenName%5D-c33f0b02841cffc3e9b4.js

%5BscreenName%5D-c33f0b02841cffc3e9b4.js

88 ms

_buildManifest.js

_buildManifest.js

88 ms

_ssgManifest.js

_ssgManifest.js

90 ms

track

track

75 ms

Accessibility Review

swapa.org accessibility score

74

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

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

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

User Experience

Impact

Issue

High

Serves images with low resolution

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

swapa.org SEO score

79

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

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 Swapa.org 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 Swapa.org 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

swapa.org

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