Tools & Wizards About Us
workingfamilies.org screenshot

Report Summary

  • 24

    Performance

    Renders faster than
    43% of other websites

  • 98

    Accessibility

    Visual factors better than
    that of 94% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

workingfamilies.org

Working Families Party - Fighting for an America that works for the many, not the few.

Page Load Speed

4.1 sec in total

First Response

595 ms

Resources Loaded

3.2 sec

Page Rendered

318 ms

workingfamilies.org screenshot

About Website

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

WFP is building a political home for all of us who see bigotry, bailouts, and business as usual in our political system and ask, "Is that the best we can do?"

Visit workingfamilies.org

Key Findings

We analyzed Workingfamilies.org page load time and found that the first response time was 595 ms and then it took 3.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

workingfamilies.org performance score

24

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.8 s

57/100

10%

LCP (Largest Contentful Paint)

Value9.3 s

1/100

25%

SI (Speed Index)

Value8.7 s

16/100

10%

TBT (Total Blocking Time)

Value1,090 ms

24/100

30%

CLS (Cumulative Layout Shift)

Value0.24

52/100

15%

TTI (Time to Interactive)

Value13.6 s

11/100

10%

Network Requests Diagram

workingfamilies.org

595 ms

style.css

73 ms

wf_icons.css

84 ms

ie.css

78 ms

stylesheet.css

97 ms

Our browser made a total of 70 requests to load all elements on the main page. We found that 50% of them (35 requests) were addressed to the original Workingfamilies.org, 17% (12 requests) were made to Scontent.xx.fbcdn.net and 14% (10 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (839 ms) relates to the external source Scontent.xx.fbcdn.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 309.0 kB (43%)

Content Size

720.5 kB

After Optimization

411.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Workingfamilies.org main page is 720.5 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. 40% of websites need less resources to load. Javascripts take 311.7 kB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 30.9 kB

  • Original 41.3 kB
  • After minification 39.1 kB
  • After compression 10.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. 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 30.9 kB or 75% of the original size.

Image Optimization

-5%

Potential reduce by 13.8 kB

  • Original 294.3 kB
  • After minification 280.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. Working Families images are well optimized though.

JavaScript Optimization

-65%

Potential reduce by 203.7 kB

  • Original 311.7 kB
  • After minification 289.9 kB
  • After compression 108.0 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 203.7 kB or 65% of the original size.

CSS Optimization

-83%

Potential reduce by 60.6 kB

  • Original 73.3 kB
  • After minification 42.9 kB
  • After compression 12.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. Workingfamilies.org needs all CSS files to be minified and compressed as it can save up to 60.6 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 38 (56%)

Requests Now

68

After Optimization

30

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

workingfamilies.org

workingfamilies.org

595 ms

style.css

style.css

73 ms

wf_icons.css

wf_icons.css

84 ms

ie.css

ie.css

78 ms

stylesheet.css

stylesheet.css

97 ms

jquery.fancybox.css

jquery.fancybox.css

99 ms

flexslider.css

flexslider.css

107 ms

styles.css

styles.css

111 ms

wpgform.css

wpgform.css

124 ms

jquery.js

jquery.js

194 ms

jquery-migrate.min.js

jquery-migrate.min.js

147 ms

vao3xjz.js

vao3xjz.js

215 ms

comment-reply.min.js

comment-reply.min.js

115 ms

jquery.form.min.js

jquery.form.min.js

119 ms

scripts.js

scripts.js

141 ms

SalsaPress.js

SalsaPress.js

150 ms

wp-embed.min.js

wp-embed.min.js

155 ms

modernizr-2.6.2.min.js

modernizr-2.6.2.min.js

174 ms

jquery.flexslider-min.js

jquery.flexslider-min.js

184 ms

jquery.infinitescroll.js

jquery.infinitescroll.js

219 ms

jquery.placeholder.js

jquery.placeholder.js

191 ms

widgets.js

widgets.js

7 ms

jquery.fancybox.pack.js

jquery.fancybox.pack.js

216 ms

main.js

main.js

220 ms

reset.css

reset.css

185 ms

normalize.css

normalize.css

187 ms

wp.basic.css

wp.basic.css

224 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

77 ms

ga.js

ga.js

75 ms

fbevents.js

fbevents.js

311 ms

logo.png

logo.png

117 ms

all.js

all.js

370 ms

wfp4berniefrontpage-960x345.jpg

wfp4berniefrontpage-960x345.jpg

296 ms

atlanticarticleimg-300x200.jpg

atlanticarticleimg-300x200.jpg

91 ms

WFP_Creative-Brief-300x200.jpg

WFP_Creative-Brief-300x200.jpg

264 ms

medium-173x300.jpg

medium-173x300.jpg

90 ms

footer_shadow.png

footer_shadow.png

88 ms

__utm.gif

__utm.gif

189 ms

wf_icons.woff

wf_icons.woff

141 ms

26 ms

responsive_768max.css

responsive_768max.css

76 ms

collect

collect

97 ms

36 ms

responsive_540max.css

responsive_540max.css

37 ms

xd_arbiter.php

xd_arbiter.php

211 ms

xd_arbiter.php

xd_arbiter.php

416 ms

ping

ping

44 ms

like_box.php

like_box.php

91 ms

lL2b34Z7dj7.css

lL2b34Z7dj7.css

286 ms

guHxiHaOfJH.css

guHxiHaOfJH.css

355 ms

_rx8naC75Dy.js

_rx8naC75Dy.js

489 ms

b94UUzHjapV.js

b94UUzHjapV.js

620 ms

0wM5s1Khldu.js

0wM5s1Khldu.js

522 ms

TTCre3391I0.js

TTCre3391I0.js

522 ms

12643018_10153737743946418_1120879980909996725_n.jpg

12643018_10153737743946418_1120879980909996725_n.jpg

415 ms

12311291_10153623681801418_699279833093240308_n.png

12311291_10153623681801418_699279833093240308_n.png

479 ms

200356_163626643692497_6524276_n.jpg

200356_163626643692497_6524276_n.jpg

547 ms

12003878_106371433063445_4889451117351177915_n.jpg

12003878_106371433063445_4889451117351177915_n.jpg

612 ms

11022555_10205979128027627_8475140903246106113_n.jpg

11022555_10205979128027627_8475140903246106113_n.jpg

615 ms

10613078_803775519715858_6306746815538943622_n.jpg

10613078_803775519715858_6306746815538943622_n.jpg

616 ms

12140637_404863049712758_3640338160554385170_n.jpg

12140637_404863049712758_3640338160554385170_n.jpg

675 ms

12705560_475855342603404_8830184197897937390_n.jpg

12705560_475855342603404_8830184197897937390_n.jpg

613 ms

535491_220459671392630_1585815409_n.jpg

535491_220459671392630_1585815409_n.jpg

686 ms

409056_299345710114478_211575099_n.jpg

409056_299345710114478_211575099_n.jpg

678 ms

1440_10101265979304230_7210782694182860318_n.jpg

1440_10101265979304230_7210782694182860318_n.jpg

839 ms

12417957_118366455209585_2646451305434131662_n.jpg

12417957_118366455209585_2646451305434131662_n.jpg

680 ms

wL6VQj7Ab77.png

wL6VQj7Ab77.png

68 ms

s7jcwEQH7Sx.png

s7jcwEQH7Sx.png

69 ms

I6-MnjEovm5.js

I6-MnjEovm5.js

71 ms

f6T91Deal_q.js

f6T91Deal_q.js

136 ms

Accessibility Review

workingfamilies.org accessibility score

98

Accessibility Issues

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

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

workingfamilies.org SEO score

100

Search Engine Optimization Advices

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

workingfamilies.org

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