Tools & Wizards About Us
webwhiteblue.org screenshot

Report Summary

  • 23

    Performance

    Renders faster than
    42% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 93

    SEO

    Google-friendlier than
    84% of websites

webwhiteblue.org

Web White & Blue 2000 Evaluation Summary | Markle | Advancing America's Future

Page Load Speed

2.8 sec in total

First Response

72 ms

Resources Loaded

2 sec

Page Rendered

721 ms

webwhiteblue.org screenshot

About Website

Click here to check amazing Web White Blue content. Otherwise, check out these important facts you probably never knew about webwhiteblue.org

This is a summary of the evaluation results of Web White and Blue 2000, a Markle initiative organized around the 2000 national elections to help voter

Visit webwhiteblue.org

Key Findings

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

Performance Metrics

webwhiteblue.org performance score

23

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.1 s

3/100

10%

LCP (Largest Contentful Paint)

Value7.9 s

3/100

25%

SI (Speed Index)

Value9.7 s

11/100

10%

TBT (Total Blocking Time)

Value2,150 ms

6/100

30%

CLS (Cumulative Layout Shift)

Value0.007

100/100

15%

TTI (Time to Interactive)

Value8.7 s

37/100

10%

Network Requests Diagram

webwhiteblue.org

72 ms

393 ms

wp-emoji-release.min.js

21 ms

style.min.css

29 ms

font-awesome.css

219 ms

Our browser made a total of 29 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Webwhiteblue.org, 52% (15 requests) were made to Markle.org and 17% (5 requests) were made to Tfaforms.com. The less responsive or slowest element that took the longest time to load (393 ms) relates to the external source Markle.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 43.8 kB (28%)

Content Size

157.0 kB

After Optimization

113.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Webwhiteblue.org main page is 157.0 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. 55% of websites need less resources to load. CSS take 56.4 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 37.8 kB

  • Original 47.3 kB
  • After minification 47.3 kB
  • After compression 9.6 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 37.8 kB or 80% of the original size.

Image Optimization

-0%

Potential reduce by 1 B

  • Original 10.0 kB
  • After minification 10.0 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. Web White Blue images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 431 B

  • Original 43.3 kB
  • After minification 43.3 kB
  • After compression 42.9 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.

CSS Optimization

-10%

Potential reduce by 5.6 kB

  • Original 56.4 kB
  • After minification 56.4 kB
  • After compression 50.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. Webwhiteblue.org has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 13 (76%)

Requests Now

17

After Optimization

4

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

webwhiteblue.org

webwhiteblue.org

72 ms

393 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

21 ms

style.min.css

style.min.css

29 ms

font-awesome.css

font-awesome.css

219 ms

style.css

style.css

37 ms

jquery.min.js

jquery.min.js

34 ms

jquery-migrate.min.js

jquery-migrate.min.js

34 ms

main.js

main.js

247 ms

wforms-layout.css

wforms-layout.css

188 ms

theme-70589.css

theme-70589.css

191 ms

wforms.js

wforms.js

212 ms

localization-en_US.js

localization-en_US.js

187 ms

email-decode.min.js

email-decode.min.js

66 ms

p.css

p.css

213 ms

css

css

84 ms

css

css

97 ms

wforms-jsonly.css

wforms-jsonly.css

59 ms

Markle-Logo-min.png

Markle-Logo-min.png

200 ms

Markle-Logo-White@2x-1-min.png

Markle-Logo-White@2x-1-min.png

141 ms

d

d

109 ms

d

d

198 ms

d

d

196 ms

d

d

220 ms

d

d

218 ms

fa-solid-900.woff

fa-solid-900.woff

366 ms

fa-regular-400.woff

fa-regular-400.woff

363 ms

fa-light-300.woff

fa-light-300.woff

296 ms

fa-brands-400.woff

fa-brands-400.woff

290 ms

Accessibility Review

webwhiteblue.org accessibility score

100

Accessibility Issues

Best Practices

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

SEO Factors

webwhiteblue.org SEO score

93

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

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

webwhiteblue.org

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