1 sec in total
35 ms
602 ms
376 ms
Visit thepublicdiscourse.com now to see the best up-to-date The Public Discourse content for United States and also check out these interesting facts you probably never knew about thepublicdiscourse.com
The online journal of The Witherspoon Institute
Visit thepublicdiscourse.comWe analyzed Thepublicdiscourse.com page load time and found that the first response time was 35 ms and then it took 978 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.
thepublicdiscourse.com performance score
name
value
score
weighting
Value6.2 s
3/100
10%
Value15.3 s
0/100
25%
Value10.5 s
8/100
10%
Value2,580 ms
4/100
30%
Value0.042
99/100
15%
Value20.7 s
2/100
10%
35 ms
24 ms
9 ms
11 ms
21 ms
Our browser made a total of 39 requests to load all elements on the main page. We found that 74% of them (29 requests) were addressed to the original Thepublicdiscourse.com, 10% (4 requests) were made to Fonts.gstatic.com and 5% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (116 ms) belongs to the original domain Thepublicdiscourse.com.
Page size can be reduced by 303.7 kB (56%)
538.9 kB
235.2 kB
In fact, the total size of Thepublicdiscourse.com main page is 538.9 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. 50% of websites need less resources to load. Javascripts take 335.5 kB which makes up the majority of the site volume.
Potential reduce by 25.9 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 5.3 kB, which is 15% 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 25.9 kB or 75% of the original size.
Potential reduce by 11.2 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. The Public Discourse images are well optimized though.
Potential reduce by 232.6 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 232.6 kB or 69% of the original size.
Potential reduce by 33.9 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. Thepublicdiscourse.com needs all CSS files to be minified and compressed as it can save up to 33.9 kB or 83% of the original size.
Number of requests can be reduced by 18 (58%)
31
13
The browser has sent 31 CSS, Javascripts, AJAX and image requests in order to completely render the main page of The Public Discourse. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
www.thepublicdiscourse.com
35 ms
css
24 ms
base.css
9 ms
skeleton.css
11 ms
layout.css
21 ms
widget.css
12 ms
style.css
13 ms
jquery.js
18 ms
jquery-migrate.min.js
13 ms
script.js
14 ms
open_in_new_window_no.js
13 ms
open_in_new_window.js
13 ms
buttons.js
15 ms
jquery.js
86 ms
app.js
12 ms
wp-embed.min.js
13 ms
print.css
66 ms
wp-emoji-release.min.js
49 ms
fluid-header.jpg
30 ms
logo-hor-left_424x140.gif
26 ms
line.gif
27 ms
thriving-society-ad.jpg
37 ms
icon_facebook.png
28 ms
icon_twitter.png
29 ms
icon_rss.png
32 ms
support-button.gif
31 ms
PD-logo-fourth-try.jpg
32 ms
subscribe-button.jpg
32 ms
ga.js
25 ms
style.css
116 ms
getAllAppDefault.esi
64 ms
__utm.gif
44 ms
3IFMwfRa07i-auYR-B-zNYnF5uFdDttMLvmWuJdhhgs.ttf
43 ms
rEy5tGc5HdXy56Xvd4f3I1FZMcfX2SbzQ69I7OWmkGo.ttf
43 ms
a5QZnvmn5amyNI-t2BMkWCtfYakCkPqOMDce0h_3gD8.ttf
60 ms
4j4TR-EfnvCt43InYpUNDDolfeppZzFSKvLyJNPKLMk.ttf
60 ms
FontinSans-SmallCaps.otf
16 ms
FontinSans-Bold.otf
16 ms
FontinSans-Roman.otf
16 ms
thepublicdiscourse.com 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.
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
Image elements do not have [alt] attributes
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
thepublicdiscourse.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
thepublicdiscourse.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
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
Document uses legible font sizes
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Thepublicdiscourse.com 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 Thepublicdiscourse.com 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.
thepublicdiscourse.com
Open Graph data is detected on the main page of The Public Discourse. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: