Tools & Wizards About Us
teamster670.org screenshot

Report Summary

  • 69

    Performance

    Renders faster than
    80% of other websites

  • 46

    Accessibility

    Visual factors better than
    that of 20% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

teamster670.org

Teamsters Local Union No. 670

Page Load Speed

2 sec in total

First Response

511 ms

Resources Loaded

1.3 sec

Page Rendered

194 ms

teamster670.org screenshot

About Website

Visit teamster670.org now to see the best up-to-date Teamster 670 content and also check out these interesting facts you probably never knew about teamster670.org

UnionActive

Visit teamster670.org

Key Findings

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

Performance Metrics

teamster670.org performance score

69

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.8 s

55/100

10%

LCP (Largest Contentful Paint)

Value5.8 s

15/100

25%

SI (Speed Index)

Value3.7 s

85/100

10%

TBT (Total Blocking Time)

Value80 ms

99/100

30%

CLS (Cumulative Layout Shift)

Value0.004

100/100

15%

TTI (Time to Interactive)

Value6.1 s

63/100

10%

Network Requests Diagram

teamster670.org

511 ms

cfform.js

168 ms

masks.js

158 ms

tundra.css

18 ms

site.css

298 ms

Our browser made a total of 130 requests to load all elements on the main page. We found that 24% of them (31 requests) were addressed to the original Teamster670.org, 75% (98 requests) were made to Ajax.googleapis.com and 1% (1 request) were made to Server5.unionactive.com. The less responsive or slowest element that took the longest time to load (586 ms) belongs to the original domain Teamster670.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 937.6 kB (35%)

Content Size

2.7 MB

After Optimization

1.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Teamster670.org main page is 2.7 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. 35% of websites need less resources to load. Images take 2.2 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 68.5 kB

  • Original 80.2 kB
  • After minification 66.5 kB
  • After compression 11.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 13.7 kB, which is 17% 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 68.5 kB or 85% of the original size.

Image Optimization

-30%

Potential reduce by 668.1 kB

  • Original 2.2 MB
  • After minification 1.5 MB

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, Teamster 670 needs image optimization as it can save up to 668.1 kB or 30% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-54%

Potential reduce by 187.4 kB

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

CSS Optimization

-66%

Potential reduce by 13.5 kB

  • Original 20.4 kB
  • After minification 16.2 kB
  • After compression 6.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. Teamster670.org needs all CSS files to be minified and compressed as it can save up to 13.5 kB or 66% of the original size.

Requests Breakdown

Number of requests can be reduced by 116 (90%)

Requests Now

129

After Optimization

13

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

teamster670.org

teamster670.org

511 ms

cfform.js

cfform.js

168 ms

masks.js

masks.js

158 ms

tundra.css

tundra.css

18 ms

site.css

site.css

298 ms

adminsite.css

adminsite.css

176 ms

dojo.js

dojo.js

23 ms

site.js

site.js

215 ms

nodefire.js

nodefire.js

266 ms

styles.css

styles.css

167 ms

nodefire.js

nodefire.js

193 ms

styles.css

styles.css

112 ms

css3-mediaqueries.js

css3-mediaqueries.js

146 ms

TooltipDialog.js

TooltipDialog.js

13 ms

DropDownButton.js

DropDownButton.js

61 ms

ContentPane.js

ContentPane.js

61 ms

ContentPane.js

ContentPane.js

62 ms

TabContainer.js

TabContainer.js

63 ms

scroll.js

scroll.js

63 ms

parser.js

parser.js

61 ms

voteicon.gif

voteicon.gif

269 ms

w_logo_Teamsters.png

w_logo_Teamsters.png

228 ms

home.png

home.png

88 ms

menu.png

menu.png

88 ms

hb1_0430.png

hb1_0430.png

517 ms

hb2_0430.png

hb2_0430.png

586 ms

spacer.png

spacer.png

88 ms

lock.png

lock.png

158 ms

user.png

user.png

158 ms

sitemap.png

sitemap.png

158 ms

rss2.png

rss2.png

220 ms

Search.png

Search.png

220 ms

rss-icon.png

rss-icon.png

219 ms

UALOGO.jpg

UALOGO.jpg

306 ms

footer_anchor.png

footer_anchor.png

293 ms

site.css

site.css

296 ms

Rotator.js

Rotator.js

51 ms

AutoRotator.js

AutoRotator.js

51 ms

Controller.js

Controller.js

52 ms

Fade.js

Fade.js

52 ms

focus.js

focus.js

72 ms

_DialogMixin.js

_DialogMixin.js

75 ms

_FormMixin.js

_FormMixin.js

74 ms

_TemplatedMixin.js

_TemplatedMixin.js

74 ms

main.js

main.js

72 ms

flex-direction-nav.png

flex-direction-nav.png

285 ms

32.png

32.png

439 ms

arrow1_right.gif

arrow1_right.gif

356 ms

arrow1_right.gif

arrow1_right.gif

321 ms

arrow1_right.gif

arrow1_right.gif

330 ms

registry.js

registry.js

18 ms

popup.js

popup.js

17 ms

Button.js

Button.js

17 ms

_Container.js

_Container.js

18 ms

_HasDropDown.js

_HasDropDown.js

18 ms

a11yclick.js

a11yclick.js

18 ms

_Widget.js

_Widget.js

18 ms

_ContentPaneResizeMixin.js

_ContentPaneResizeMixin.js

19 ms

string.js

string.js

18 ms

html.js

html.js

19 ms

loading.js

loading.js

19 ms

_base.js

_base.js

32 ms

url.js

url.js

17 ms

all.js

all.js

33 ms

stamp.js

stamp.js

30 ms

_TabContainerBase.js

_TabContainerBase.js

31 ms

TabController.js

TabController.js

33 ms

ScrollingTabController.js

ScrollingTabController.js

32 ms

_base.js

_base.js

33 ms

_core.js

_core.js

32 ms

easing.js

easing.js

32 ms

fx.js

fx.js

29 ms

Stateful.js

Stateful.js

16 ms

window.js

window.js

15 ms

a11y.js

a11y.js

16 ms

cache.js

cache.js

16 ms

_AttachMixin.js

_AttachMixin.js

16 ms

_FormWidget.js

_FormWidget.js

16 ms

_ButtonMixin.js

_ButtonMixin.js

17 ms

place.js

place.js

16 ms

BackgroundIframe.js

BackgroundIframe.js

27 ms

Viewport.js

Viewport.js

15 ms

touch.js

touch.js

28 ms

_FocusMixin.js

_FocusMixin.js

27 ms

_WidgetBase.js

_WidgetBase.js

27 ms

_OnDijitClickMixin.js

_OnDijitClickMixin.js

26 ms

uacss.js

uacss.js

27 ms

hccss.js

hccss.js

28 ms

utils.js

utils.js

27 ms

StackContainer.js

StackContainer.js

15 ms

_WidgetsInTemplateMixin.js

_WidgetsInTemplateMixin.js

14 ms

Menu.js

Menu.js

14 ms

MenuItem.js

MenuItem.js

13 ms

StackController.js

StackController.js

14 ms

common.js

common.js

14 ms

_CssStateMixin.js

_CssStateMixin.js

18 ms

_FormWidgetMixin.js

_FormWidgetMixin.js

16 ms

Destroyable.js

Destroyable.js

6 ms

hccss.js

hccss.js

7 ms

cookie.js

cookie.js

16 ms

_LayoutWidget.js

_LayoutWidget.js

15 ms

_Contained.js

_Contained.js

16 ms

DropDownMenu.js

DropDownMenu.js

15 ms

ToggleButton.js

ToggleButton.js

16 ms

blank.gif

blank.gif

7 ms

regexp.js

regexp.js

7 ms

_MenuBase.js

_MenuBase.js

5 ms

_ToggleButtonMixin.js

_ToggleButtonMixin.js

8 ms

_KeyNavContainer.js

_KeyNavContainer.js

5 ms

_KeyNavMixin.js

_KeyNavMixin.js

6 ms

Toggler.js

Toggler.js

4 ms

manager.js

manager.js

4 ms

_base.js

_base.js

5 ms

WidgetSet.js

WidgetSet.js

4 ms

focus.js

focus.js

5 ms

place.js

place.js

5 ms

popup.js

popup.js

7 ms

scroll.js

scroll.js

6 ms

sniff.js

sniff.js

6 ms

typematic.js

typematic.js

7 ms

wai.js

wai.js

10 ms

window.js

window.js

8 ms

selection.js

selection.js

5 ms

typematic.js

typematic.js

6 ms

_FormValueWidget.js

_FormValueWidget.js

6 ms

_FormValueMixin.js

_FormValueMixin.js

5 ms

ComboButton.js

ComboButton.js

4 ms

PopupMenuItem.js

PopupMenuItem.js

9 ms

CheckedMenuItem.js

CheckedMenuItem.js

5 ms

MenuSeparator.js

MenuSeparator.js

5 ms

Accessibility Review

teamster670.org accessibility score

46

Accessibility Issues

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

Form elements do not have associated labels

High

Links do not have a discernible name

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

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

teamster670.org SEO score

82

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Teamster670.org can be misinterpreted by Google and other search engines. Our service has detected that English 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 Teamster670.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

teamster670.org

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