1.5 sec in total
24 ms
1.3 sec
206 ms
Welcome to community.lsst.org homepage info - get ready to check Community LSST best content for United States right away, or after learning these important things about community.lsst.org
Online community for the Vera C. Rubin Observatory Legacy Survey of Space and Time.
Visit community.lsst.orgWe analyzed Community.lsst.org page load time and found that the first response time was 24 ms and then it took 1.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.
community.lsst.org performance score
name
value
score
weighting
Value1.8 s
89/100
10%
Value3.2 s
73/100
25%
Value1.8 s
100/100
10%
Value50 ms
100/100
30%
Value0.054
98/100
15%
Value3.3 s
94/100
10%
24 ms
162 ms
37 ms
57 ms
30 ms
Our browser made a total of 48 requests to load all elements on the main page. We found that 96% of them (46 requests) were addressed to the original Community.lsst.org, 4% (2 requests) were made to Cdn.mathjax.org. The less responsive or slowest element that took the longest time to load (465 ms) relates to the external source Cdn.mathjax.org.
Page size can be reduced by 2.8 MB (79%)
3.5 MB
750.0 kB
In fact, the total size of Community.lsst.org main page is 3.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. 80% 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 3.2 MB which makes up the majority of the site volume.
Potential reduce by 106.7 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 106.7 kB or 84% of the original size.
Potential reduce by 0 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 LSST images are well optimized though.
Potential reduce by 2.5 MB
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 2.5 MB or 80% of the original size.
Potential reduce by 150.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. Community.lsst.org needs all CSS files to be minified and compressed as it can save up to 150.7 kB or 79% of the original size.
Number of requests can be reduced by 22 (49%)
45
23
The browser has sent 45 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Community LSST. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 8 to 1 for JavaScripts and as a result speed up the page load time.
community.lsst.org
24 ms
community.lsst.org
162 ms
desktop_35c6fa7df36bd03e99cf2e65491b1a57909526a6.css
37 ms
7e202ef2-56d7-47d5-98d8-a9c8d15e57dd.css
57 ms
preload_store-d16a3675434b5a0043157cfc2b850471.js
30 ms
en-401858fddda085eb0a54a4c57eb6f8e3.js
53 ms
ember_jquery-37c15254b70c40ceb7888cb7248c79d6.js
80 ms
vendor-17831e059f10b3b31503434a43f32398.js
78 ms
application-d73e1e27b35431da93cd41e6429d26d2.js
179 ms
browser-update-1b088c371e098d02d2b87570660d5d68.js
52 ms
MathJax.js
465 ms
aeaeebda6f0363b2e5772499382f4fbcb35f9c56.png
322 ms
1_1.png
36 ms
4_1.png
73 ms
47_1.png
73 ms
37_1.png
74 ms
31_1.png
74 ms
25.png
29 ms
125_1.png
94 ms
3_1.png
93 ms
25.png
73 ms
24_1.png
100 ms
12_1.png
101 ms
25.png
92 ms
25.png
94 ms
28_1.png
111 ms
29_1.png
114 ms
10_1.png
122 ms
25.png
103 ms
44_1.png
127 ms
118_1.png
134 ms
25.png
118 ms
25.png
131 ms
52_1.png
140 ms
63_1.png
146 ms
82_1.png
154 ms
25.png
142 ms
25_1.png
163 ms
25.png
157 ms
9_1.png
173 ms
124_1.png
174 ms
138_1.png
187 ms
65_1.png
186 ms
25.png
173 ms
217_1.png
210 ms
grippie-d28a6f65e22c0033dcf0d63883bcc590.png
180 ms
fontawesome-webfont-90e687312466f7a4993c85399c116f2f.woff
194 ms
TeX-AMS-MML_HTMLorMML.js
12 ms
community.lsst.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
Heading elements are not in a sequentially-descending order
community.lsst.org best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
community.lsst.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 Community.lsst.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.lsst.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.lsst.org
Open Graph description is not detected on the main page of Community LSST. 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: