12.7 sec in total
1.5 sec
11.1 sec
145 ms
Visit plainreason.org now to see the best up-to-date Plain Reason content and also check out these interesting facts you probably never knew about plainreason.org
Plain Reason promotes critical thinking and strategies for moving Australia to a fully secular nation.
Visit plainreason.orgWe analyzed Plainreason.org page load time and found that the first response time was 1.5 sec and then it took 11.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
plainreason.org performance score
name
value
score
weighting
Value10.3 s
0/100
10%
Value16.9 s
0/100
25%
Value20.1 s
0/100
10%
Value6,500 ms
0/100
30%
Value0.004
100/100
15%
Value22.8 s
1/100
10%
1497 ms
209 ms
416 ms
623 ms
632 ms
Our browser made a total of 79 requests to load all elements on the main page. We found that 67% of them (53 requests) were addressed to the original Plainreason.org, 19% (15 requests) were made to Fonts.gstatic.com and 6% (5 requests) were made to Gstatic.com. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Plainreason.org.
Page size can be reduced by 241.4 kB (28%)
862.4 kB
621.1 kB
In fact, the total size of Plainreason.org main page is 862.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. 65% of websites need less resources to load. Javascripts take 404.4 kB which makes up the majority of the site volume.
Potential reduce by 75.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 75.5 kB or 82% of the original size.
Potential reduce by 156.8 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. Obviously, Plain Reason needs image optimization as it can save up to 156.8 kB or 61% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 8.3 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.
Potential reduce by 845 B
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. Plainreason.org has all CSS files already compressed.
Number of requests can be reduced by 53 (88%)
60
7
The browser has sent 60 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Plain Reason. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 28 to 1 for JavaScripts and from 27 to 1 for CSS and as a result speed up the page load time.
www.plainreason.org
1497 ms
a1hoy.css
209 ms
a1hoy.css
416 ms
a1hoy.css
623 ms
a1hoy.css
632 ms
post-3759.css
627 ms
a1hoy.css
634 ms
a1hoy.css
634 ms
a1hoy.css
640 ms
a1hoy.css
829 ms
a1hoy.css
835 ms
a1hoy.css
838 ms
post-308.css
840 ms
a1hoy.css
845 ms
post-3762.css
854 ms
a1hoy.css
1036 ms
a1hoy.css
1044 ms
post-3771.css
1046 ms
style.css
1049 ms
css
37 ms
a1hoy.css
1059 ms
a1hoy.css
1067 ms
a1hoy.css
1244 ms
a1hoy.js
1470 ms
js
74 ms
a1hoy.css
1253 ms
a1hox.css
1267 ms
a1hox.css
1271 ms
a1hox.css
1282 ms
index.js
1450 ms
index.js
1461 ms
hello-frontend.min.js
1568 ms
happy-addons.min.js
1568 ms
happy-addons-pro.js
1716 ms
api.js
52 ms
wp-polyfill-inert.min.js
1662 ms
regenerator-runtime.min.js
1673 ms
wp-polyfill.min.js
1686 ms
index.js
1692 ms
jquery.smartmenus.min.js
1698 ms
webpack-pro.runtime.min.js
1668 ms
webpack.runtime.min.js
1475 ms
frontend-modules.min.js
1287 ms
hooks.min.js
1287 ms
i18n.min.js
1289 ms
frontend.min.js
1306 ms
waypoints.min.js
1445 ms
core.min.js
1457 ms
frontend.min.js
1286 ms
elements-handlers.min.js
1288 ms
pr-logo-22-300x100.png
638 ms
sacred-to-secular-cover-cropped.png
1081 ms
separation-of-religion-chart-v2-768x512.png
1193 ms
KFOmCnqEu92Fr1Mu4mxPKTU1Kg.ttf
29 ms
KFOlCnqEu92Fr1MmEU9fBBc9AMP6lQ.ttf
33 ms
KFOlCnqEu92Fr1MmSU5fBBc9AMP6lQ.ttf
43 ms
KFOkCnqEu92Fr1MmgVxIIzcXKMny.ttf
54 ms
KFOlCnqEu92Fr1MmWUlfBBc9AMP6lQ.ttf
54 ms
KFOlCnqEu92Fr1MmYUtfBBc9AMP6lQ.ttf
54 ms
fa-regular-400.woff
717 ms
fa-solid-900.woff
923 ms
KFOjCnqEu92Fr1Mu51S7ACc6CsHYl4BO.ttf
55 ms
KFOkCnqEu92Fr1Mu51xIIzcXKMny.ttf
54 ms
KFOjCnqEu92Fr1Mu51TjASc6CsHYl4BO.ttf
45 ms
KFOiCnqEu92Fr1Mu51QrEzAdKuvwnYg.ttf
55 ms
KFOjCnqEu92Fr1Mu51TzBic6CsHYl4BO.ttf
56 ms
KFOjCnqEu92Fr1Mu51TLBCc6CsHYl4BO.ttf
56 ms
fa-brands-400.woff
1143 ms
recaptcha__en.js
31 ms
anchor
37 ms
styles__ltr.css
4 ms
recaptcha__en.js
13 ms
Dq4s5fHQ4MqajtxkAI1TQErT3JHnCXhk4JQIHWIJ1B4.js
40 ms
webworker.js
79 ms
logo_48.png
26 ms
KFOmCnqEu92Fr1Mu4mxPKTU1Kg.ttf
35 ms
KFOlCnqEu92Fr1MmEU9fBBc9AMP6lQ.ttf
36 ms
KFOlCnqEu92Fr1MmYUtfBBc9AMP6lQ.ttf
36 ms
recaptcha__en.js
19 ms
plainreason.org accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
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
plainreason.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
plainreason.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 Plainreason.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 Plainreason.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.
plainreason.org
Open Graph data is detected on the main page of Plain Reason. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: