1.5 sec in total
97 ms
1.3 sec
103 ms
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.orgWe analyzed Webwhiteblue.org page load time and found that the first response time was 97 ms and then it took 1.4 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.
webwhiteblue.org performance score
name
value
score
weighting
Value6.3 s
3/100
10%
Value7.4 s
4/100
25%
Value6.3 s
42/100
10%
Value130 ms
96/100
30%
Value0.001
100/100
15%
Value7.0 s
53/100
10%
97 ms
66 ms
471 ms
50 ms
8 ms
Our browser made a total of 110 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Webwhiteblue.org, 78% (86 requests) were made to Ka-p.fontawesome.com and 9% (10 requests) were made to Markle.org. The less responsive or slowest element that took the longest time to load (471 ms) relates to the external source Markle.org.
Page size can be reduced by 94.4 kB (18%)
523.4 kB
429.0 kB
In fact, the total size of Webwhiteblue.org main page is 523.4 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. Only a small number of websites need less resources to load. CSS take 249.5 kB which makes up the majority of the site volume.
Potential reduce by 44.5 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 44.5 kB or 80% of the original size.
Potential reduce by 18 B
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.
Potential reduce by 34.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 34.9 kB or 17% of the original size.
Potential reduce by 15.0 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.
Number of requests can be reduced by 15 (79%)
19
4
The browser has sent 19 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 6 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
webwhiteblue.org
97 ms
231-web-white-blue-2000-evaluation-summary
66 ms
471 ms
gtm.js
50 ms
style.min.css
8 ms
font-awesome.css
17 ms
style.css
21 ms
jquery.min.js
26 ms
jquery-migrate.min.js
20 ms
main.js
26 ms
wforms-layout.css
66 ms
theme-70589.css
69 ms
wforms.js
70 ms
localization-en_US.js
66 ms
Markle-Logo-min.png
24 ms
Markle-Logo-White@2x-1-min.png
26 ms
pro.min.css
73 ms
pro-v4-shims.min.css
103 ms
pro-v5-font-face.min.css
128 ms
pro-v4-font-face.min.css
127 ms
css
33 ms
css
45 ms
wforms-jsonly.css
5 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf
59 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aX8.ttf
59 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aX8.ttf
68 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aX8.ttf
71 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf
76 ms
pro-fa-regular-400-06a6e9.ttf
46 ms
pro-fa-regular-400-e633e8.ttf
47 ms
pro-fa-regular-400-ea8718.ttf
47 ms
pro-fa-regular-400-e5c668.ttf
44 ms
pro-fa-regular-400-2a5ebc.ttf
70 ms
pro-fa-regular-400-a9f9c5.ttf
69 ms
pro-fa-regular-400-9326ac.ttf
68 ms
pro-fa-regular-400-4adefe.ttf
75 ms
pro-fa-regular-400-764e6a.ttf
68 ms
pro-fa-regular-400-6b8b58.ttf
91 ms
pro-fa-regular-400-1722b2.ttf
92 ms
pro-fa-regular-400-b909c1.ttf
92 ms
pro-fa-regular-400-bddfaa.ttf
90 ms
pro-fa-regular-400-e3907a.ttf
89 ms
pro-fa-regular-400-043e6a.ttf
104 ms
pro-fa-regular-400-9a7529.ttf
104 ms
pro-fa-regular-400-90d968.ttf
102 ms
pro-fa-regular-400-e41116.ttf
103 ms
pro-fa-regular-400-d5bbe9.ttf
126 ms
pro-fa-light-300-06a6e9.ttf
107 ms
pro-fa-light-300-e633e8.ttf
117 ms
pro-fa-light-300-ea8718.ttf
117 ms
pro-fa-light-300-e5c668.ttf
127 ms
pro-fa-light-300-2a5ebc.ttf
141 ms
pro-fa-light-300-a9f9c5.ttf
126 ms
pro-fa-light-300-9326ac.ttf
129 ms
pro-fa-light-300-4adefe.ttf
139 ms
pro-fa-light-300-764e6a.ttf
150 ms
pro-fa-light-300-6b8b58.ttf
148 ms
pro-fa-light-300-1722b2.ttf
151 ms
pro-fa-light-300-b909c1.ttf
150 ms
pro-fa-light-300-bddfaa.ttf
148 ms
pro-fa-light-300-e3907a.ttf
153 ms
pro-fa-light-300-043e6a.ttf
167 ms
pro-fa-light-300-9a7529.ttf
172 ms
pro-fa-light-300-90d968.ttf
168 ms
pro-fa-light-300-e41116.ttf
130 ms
pro-fa-light-300-d5bbe9.ttf
125 ms
pro-fa-thin-100-06a6e9.ttf
126 ms
pro-fa-thin-100-e633e8.ttf
132 ms
pro-fa-thin-100-ea8718.ttf
121 ms
pro-fa-thin-100-e5c668.ttf
122 ms
pro-fa-thin-100-2a5ebc.ttf
120 ms
pro-fa-thin-100-a9f9c5.ttf
135 ms
pro-fa-thin-100-9326ac.ttf
104 ms
pro-fa-thin-100-4adefe.ttf
120 ms
pro-fa-thin-100-764e6a.ttf
116 ms
pro-fa-thin-100-6b8b58.ttf
114 ms
pro-fa-thin-100-1722b2.ttf
113 ms
pro-fa-thin-100-b909c1.ttf
116 ms
pro-fa-thin-100-bddfaa.ttf
119 ms
pro-fa-thin-100-e3907a.ttf
118 ms
pro-fa-thin-100-043e6a.ttf
133 ms
pro-fa-thin-100-9a7529.ttf
130 ms
pro-fa-thin-100-90d968.ttf
106 ms
pro-fa-thin-100-e41116.ttf
108 ms
pro-fa-thin-100-d5bbe9.ttf
117 ms
pro-fa-solid-900-06a6e9.ttf
110 ms
pro-fa-solid-900-e633e8.ttf
110 ms
pro-fa-solid-900-ea8718.ttf
110 ms
pro-fa-solid-900-e5c668.ttf
116 ms
pro-fa-solid-900-2a5ebc.ttf
113 ms
pro-fa-solid-900-a9f9c5.ttf
112 ms
pro-fa-solid-900-9326ac.ttf
135 ms
pro-fa-solid-900-4adefe.ttf
108 ms
pro-fa-solid-900-764e6a.ttf
104 ms
pro-fa-solid-900-6b8b58.ttf
119 ms
pro-fa-solid-900-1722b2.ttf
117 ms
pro-fa-solid-900-b909c1.ttf
117 ms
pro-fa-solid-900-bddfaa.ttf
104 ms
pro-fa-solid-900-e3907a.ttf
102 ms
pro-fa-solid-900-043e6a.ttf
115 ms
pro-fa-solid-900-9a7529.ttf
129 ms
pro-fa-solid-900-90d968.ttf
116 ms
pro-fa-solid-900-e41116.ttf
104 ms
pro-fa-solid-900-d5bbe9.ttf
116 ms
pro-fa-brands-400-2a5ebc.ttf
118 ms
pro-fa-brands-400-764e6a.ttf
115 ms
pro-fa-brands-400-6b8b58.ttf
112 ms
pro-fa-brands-400-9a7529.ttf
120 ms
pro-fa-brands-400-90d968.ttf
118 ms
pro-fa-brands-400-f6b769.ttf
132 ms
webwhiteblue.org accessibility score
webwhiteblue.org best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
webwhiteblue.org SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
EN
EN
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.
webwhiteblue.org
Open Graph data is detected on the main page of PARSED_DOMAIN, but there is no image specified in description. It would be a good idea for the website admin to select a nice image that can properly represent the website in Open Graph data, otherwise the first found image will be taken for this purpose and social media information block will look like this: