5.4 sec in total
2.1 sec
3.1 sec
174 ms
Welcome to centerforplainlanguage.org homepage info - get ready to check Center For Plain Language best content for United States right away, or after learning these important things about centerforplainlanguage.org
The Center for Plain Language is a 501(c)(3), non-profit organization. We help organizations create information that's easier to understand, which makes it easier to take action.
Visit centerforplainlanguage.orgWe analyzed Centerforplainlanguage.org page load time and found that the first response time was 2.1 sec and then it took 3.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
centerforplainlanguage.org performance score
name
value
score
weighting
Value8.2 s
0/100
10%
Value17.1 s
0/100
25%
Value11.6 s
4/100
10%
Value190 ms
90/100
30%
Value0.026
100/100
15%
Value15.6 s
7/100
10%
2050 ms
24 ms
39 ms
46 ms
49 ms
Our browser made a total of 124 requests to load all elements on the main page. We found that 83% of them (103 requests) were addressed to the original Centerforplainlanguage.org, 6% (8 requests) were made to Fonts.gstatic.com and 4% (5 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain Centerforplainlanguage.org.
Page size can be reduced by 1.1 MB (72%)
1.5 MB
438.7 kB
In fact, the total size of Centerforplainlanguage.org main page is 1.5 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. 60% of websites need less resources to load. Javascripts take 890.5 kB which makes up the majority of the site volume.
Potential reduce by 76.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 76.3 kB or 82% of the original size.
Potential reduce by 5.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. Center For Plain Language images are well optimized though.
Potential reduce by 627.1 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 627.1 kB or 70% of the original size.
Potential reduce by 402.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. Centerforplainlanguage.org needs all CSS files to be minified and compressed as it can save up to 402.7 kB or 83% of the original size.
Number of requests can be reduced by 93 (81%)
115
22
The browser has sent 115 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Center For Plain Language. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 42 to 1 for JavaScripts and from 43 to 1 for CSS and as a result speed up the page load time.
centerforplainlanguage.org
2050 ms
css
24 ms
css
39 ms
css
46 ms
css
49 ms
style.css
90 ms
mobile.nav.frontend.css
133 ms
overlays.css
93 ms
custom.css
92 ms
otw-grid.css
95 ms
general_foundicons.css
134 ms
social_foundicons.css
136 ms
otw_shortcode.css
136 ms
bootstrap.custom.min.css
227 ms
public.css
169 ms
cvpro.min.css
176 ms
style.css
178 ms
style.css
179 ms
styles.css
180 ms
custom-404-pro-public.css
212 ms
cff-style.css
220 ms
font-awesome.min.css
25 ms
font-awesome.min.css
221 ms
social_widget.css
223 ms
logos.css
225 ms
easy-twitter-feed-widget.css
254 ms
superfish.css
264 ms
flexslider.css
264 ms
responsive.dataTables.min.css
265 ms
tablepress-combined.min.css
267 ms
masterslider.main.css
354 ms
tablepress-responsive-flip.min.css
297 ms
jquery.js
393 ms
jquery-migrate.min.js
307 ms
jquery.transit.min.js
308 ms
jquery.touchwipe.min.js
310 ms
jquery.sidr.js
341 ms
mobile.nav.frontend.js
349 ms
main.js
350 ms
jquery.mobile.min.js
354 ms
responsiveslides.js
383 ms
buttons.js
19 ms
style.css
318 ms
main.js
365 ms
custom-404-pro-public.js
364 ms
front.js
364 ms
font-awesome.min.css
336 ms
content-protector.css
331 ms
global.css
330 ms
normal.css
328 ms
box-shortcodes.css
328 ms
content-shortcodes.css
315 ms
altimage.js
307 ms
jquery.carouFredSel-6.2.1.js
356 ms
logos.js
315 ms
jscripts.php
382 ms
overlays.js
283 ms
frontend.js
371 ms
comment-reply.min.js
306 ms
jquery.form.min.js
313 ms
scripts.js
315 ms
bootstrap.custom.min.js
346 ms
public.js
321 ms
cvpro.min.js
359 ms
cff-scripts.js
320 ms
logout.js
337 ms
superfish.js
347 ms
jquery.fitvids.js
321 ms
jquery.fittext.js
319 ms
jquery.flexslider-min.js
324 ms
theme_trust.js
335 ms
widget-easy-twitter-feed-widget.js
315 ms
jscripts-ftr-min.js
310 ms
wp-embed.min.js
315 ms
jquery.easing.min.js
320 ms
masterslider.min.js
412 ms
ga.js
48 ms
wp-emoji-release.min.js
351 ms
css
28 ms
frontend.css
277 ms
frontend.css
259 ms
galleria.lcweb.css
264 ms
jplayer.media.grid.css
269 ms
__utm.gif
10 ms
analytics.js
9 ms
CPL_logo_new-300x64.png
51 ms
blank.gif
52 ms
facebook.png
52 ms
twitter.png
52 ms
slideshare.png
51 ms
rss.png
52 ms
ic_award.png
140 ms
ic_expose.png
140 ms
ic_reportcard.png
140 ms
ic_blog.png
142 ms
ic_connect.png
141 ms
ic_advocacy.png
140 ms
ic_writebetter_w.png
278 ms
ic_member_w.png
141 ms
ic_complain_w.png
142 ms
ic_support_w.png
142 ms
ic_workshop_w.png
143 ms
logo01_usability.jpg
142 ms
logo03_aetna.jpg
297 ms
logo08_zuula.jpg
297 ms
logo02_kleiman.jpg
298 ms
logo05_gf.jpg
297 ms
clogo_plainlanguage.jpg
296 ms
Siegel_Big.jpg
296 ms
clogo_presshere.png
340 ms
linkedin.png
327 ms
googleplus.png
328 ms
collect
22 ms
line.gif
282 ms
k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf
17 ms
MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf
17 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
19 ms
DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf
19 ms
7XUFZ5tgS-tD6QamInJTcU3KvHLhcNjEHFQzwNtdMQY.ttf
18 ms
anMUvcNT0H1YN4FII8wpr4e2tK5W43RXgBRKkM4A5Qg.ttf
18 ms
xjAJXh38I15wypJXxuGMBp0EAVxt0G0biEntp43Qt6E.ttf
18 ms
PRmiXeptR36kaC0GEAetxp_TkvowlIOtbR7ePgFOpF4.ttf
18 ms
widgets.js
155 ms
getAllAppDefault.esi
134 ms
centerforplainlanguage.org accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
Heading elements are not in a sequentially-descending order
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
Links do not have a discernible name
centerforplainlanguage.org best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
centerforplainlanguage.org SEO score
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
Document uses legible font sizes
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Centerforplainlanguage.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 Centerforplainlanguage.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.
centerforplainlanguage.org
Open Graph description is not detected on the main page of Center For Plain Language. 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: