1.9 sec in total
15 ms
1.8 sec
171 ms
Welcome to community.pbspro.org homepage info - get ready to check Community Pbspro best content right away, or after learning these important things about community.pbspro.org
OpenPBS Open Source Project Forum - Sign up to get announcements, read and reply to questions, or participate in technical discussions.
Visit community.pbspro.orgWe analyzed Community.pbspro.org page load time and found that the first response time was 15 ms and then it took 1.9 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.
community.pbspro.org performance score
name
value
score
weighting
Value4.2 s
19/100
10%
Value4.4 s
39/100
25%
Value4.2 s
77/100
10%
Value0 ms
100/100
30%
Value0
100/100
15%
Value4.2 s
85/100
10%
15 ms
442 ms
41 ms
105 ms
151 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 Community.pbspro.org, 33% (36 requests) were made to Avatars.discourse-cdn.com and 28% (31 requests) were made to Sjc6.discourse-cdn.com. The less responsive or slowest element that took the longest time to load (956 ms) relates to the external source Avatars.discourse-cdn.com.
Page size can be reduced by 266.3 kB (15%)
1.8 MB
1.5 MB
In fact, the total size of Community.pbspro.org main page is 1.8 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. 85% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 1.4 MB which makes up the majority of the site volume.
Potential reduce by 258.0 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 258.0 kB or 89% of the original size.
Potential reduce by 32 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. Community Pbspro images are well optimized though.
Potential reduce by 2.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. This website has mostly compressed JavaScripts.
Potential reduce by 6.2 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. Community.pbspro.org has all CSS files already compressed.
Number of requests can be reduced by 92 (95%)
97
5
The browser has sent 97 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Community Pbspro. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 29 to 1 for JavaScripts and from 20 to 1 for CSS and as a result speed up the page load time.
community.pbspro.org
15 ms
community.openpbs.org
442 ms
browser-detect-99f42f91bffa8ca1606d62b70bb92f981d83921e78ccdbd3d9538f07007f27ac.gz.js
41 ms
vendor.f196a698a6a811ae0583c1ea5284644b-53642a3b547b78e34800ab2eeb101f12b39be8c27ec85e9ad359a095161fad6b.gz.js
105 ms
chunk.960be39199b4da8d9453.d41d8cd9.gz.js
151 ms
chunk.d54ab16d74bb903d8221.d41d8cd9.gz.js
175 ms
checklist-3906dc3e28aec1eab0467fd63c79e7db9ee32438162f1c95180102088f8e179f.gz.js
111 ms
discourse-adplugin-27fd32c9528eb521ebffdd3be9dd9c18ffe150c0e8248038856ab0827131beac.gz.js
108 ms
discourse-adplugin_admin-42777d881f7108a2c5f33ba5ca3e5ca7a44bad97a47ed36c747ae2b2cd52f339.gz.js
112 ms
discourse-ai-61f1ef46563fc6a11822e99f44cb17cc9c4974946e00276852dd01378c373ab7.gz.js
176 ms
discourse-akismet-7a9c3c786f220e0b2a361580075231abe2282ef59c27d650b40ec7b7d88f8222.gz.js
115 ms
discourse-cakeday-4a6934fa9246e7ca5e4adb867505cfefb9af2bc963a2fac6f282ae6ef01bf64b.gz.js
118 ms
discourse-deprecation-collector-bd396b619c29d494f5290be1e6f9379d5809f028d81810db1c39c39c58780e8c.gz.js
120 ms
discourse-details-48148ec534a4c5e9614302186b345123ba1358787c41bc31cbd17231f794fe42.gz.js
125 ms
discourse-lazy-videos-ce6495e897b851c47c569a614c6b96df285331ed0f0ac4137bcc28526b1285b7.gz.js
128 ms
discourse-local-dates-a1b9590bc8f26e3bcd3d4cf00594250816149a8c4f00c75ffed0bfcf3e409d74.gz.js
137 ms
discourse-narrative-bot-643f10339e287d380f81413fde738a8ad3a6e2a5ee4d7e30f2e841f92c78e5eb.gz.js
138 ms
discourse-presence-fc08c21eda4e026fe0e91d04f30a77cd839e6e0c9e443bc9bd9817cb6eddf0d4.gz.js
139 ms
discourse-solved-bb7db4a510e5480a85dabd68df1be46d166f138377605217a9de8769eebe0ce0.gz.js
140 ms
footnote-e4283bf95e4bdcc5062c1bde5e8962932a35f35298b193181cda8d1c97d3a555.gz.js
145 ms
footnote_extra-7f7bb8e0891106317fe6883ba187d239709a385df2c386a4d9ab105732204444.gz.js
161 ms
hosted-site-d2bb0c308f09f70e5804f0de1d24a6f9962b2cd58a1a9db73550e38601958a59.gz.js
162 ms
hosted-site_admin-182bc74a8ca0a413b0aaf128749f459651aa76867dad4676f6ef28aaca66c785.gz.js
163 ms
poll-8e67add6a25a5e82f6af6b742df1215a0f1c2b45bd9a0c6f1fd675cf876d43f8.gz.js
162 ms
spoiler-alert-3b3eeb323f466d4eb21a0c807b9a40506ff4d4ca4afc89f4e4c2da1d4a856d83.gz.js
164 ms
en-5788ecdeab1ffa920032ba88ad02b79e10c9ba8a2196c84135a8d62714937d9a.gz.js
164 ms
google-tag-manager-78e83b8ae984b564b9745ad42fff40e8e544d5f805befd1f8265e859205f96b4.gz.js
167 ms
discourse-client-performance.js
169 ms
color_definitions_altair-pbs-styles_1_1_bc09b4547d5d27b80c775f202968f85934c4cad2.css
30 ms
desktop_5e51bd3d59f983053f5aa24289ef63cf80f8296d.css
50 ms
checklist_5e51bd3d59f983053f5aa24289ef63cf80f8296d.css
47 ms
discourse-adplugin_5e51bd3d59f983053f5aa24289ef63cf80f8296d.css
98 ms
discourse-ai_5e51bd3d59f983053f5aa24289ef63cf80f8296d.css
97 ms
discourse-akismet_5e51bd3d59f983053f5aa24289ef63cf80f8296d.css
95 ms
discourse-cakeday_5e51bd3d59f983053f5aa24289ef63cf80f8296d.css
100 ms
discourse-details_5e51bd3d59f983053f5aa24289ef63cf80f8296d.css
101 ms
discourse-lazy-videos_5e51bd3d59f983053f5aa24289ef63cf80f8296d.css
103 ms
discourse-local-dates_5e51bd3d59f983053f5aa24289ef63cf80f8296d.css
103 ms
discourse-narrative-bot_5e51bd3d59f983053f5aa24289ef63cf80f8296d.css
100 ms
discourse-presence_5e51bd3d59f983053f5aa24289ef63cf80f8296d.css
108 ms
discourse-solved_5e51bd3d59f983053f5aa24289ef63cf80f8296d.css
105 ms
footnote_5e51bd3d59f983053f5aa24289ef63cf80f8296d.css
107 ms
hosted-site_5e51bd3d59f983053f5aa24289ef63cf80f8296d.css
108 ms
poll_5e51bd3d59f983053f5aa24289ef63cf80f8296d.css
109 ms
spoiler-alert_5e51bd3d59f983053f5aa24289ef63cf80f8296d.css
109 ms
discourse-ai_desktop_5e51bd3d59f983053f5aa24289ef63cf80f8296d.css
112 ms
poll_desktop_5e51bd3d59f983053f5aa24289ef63cf80f8296d.css
114 ms
desktop_theme_1_7ed95d5388f28b4184b59d9aa2ec9fbf07e24e32.css
113 ms
start-discourse-7c0f5f4daf3c942b7b6ecfe8e62e2e5a0f6555924859cf055314c0df3d617353.gz.js
118 ms
browser-update-9070f07226d022f68c06506e046ae33f8fe725302ff53955cd3d483f2fc47ff6.gz.js
116 ms
gtm.js
113 ms
25.png
192 ms
410_2.png
81 ms
ns.html
85 ms
626_2.png
106 ms
676_2.png
105 ms
265_2.png
173 ms
250_2.png
172 ms
675_2.png
211 ms
674_2.png
209 ms
466_2.png
217 ms
85_2.png
214 ms
93_2.png
241 ms
672_2.png
243 ms
25.png
165 ms
25.png
319 ms
25.png
355 ms
25.png
354 ms
25.png
230 ms
25.png
229 ms
25.png
230 ms
25.png
386 ms
25.png
385 ms
25.png
410 ms
25.png
496 ms
25.png
507 ms
25.png
453 ms
25.png
489 ms
25.png
416 ms
25.png
590 ms
25.png
575 ms
25.png
484 ms
25.png
516 ms
25.png
591 ms
25.png
649 ms
25.png
608 ms
25.png
678 ms
25.png
735 ms
25.png
746 ms
25.png
692 ms
25.png
789 ms
25.png
802 ms
25.png
841 ms
25.png
724 ms
25.png
878 ms
25.png
892 ms
25.png
847 ms
25.png
942 ms
25.png
956 ms
410_2.png
83 ms
676_2.png
5 ms
626_2.png
70 ms
250_2.png
78 ms
265_2.png
72 ms
674_2.png
76 ms
675_2.png
302 ms
85_2.png
74 ms
466_2.png
342 ms
93_2.png
76 ms
672_2.png
257 ms
community.pbspro.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.
community.pbspro.org best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
community.pbspro.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
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 Community.pbspro.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 Community.pbspro.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.
community.pbspro.org
Open Graph data is detected on the main page of Community Pbspro. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: