2.6 sec in total
111 ms
1.7 sec
750 ms
Click here to check amazing JWST Docs Stsci content for United States. Otherwise, check out these important facts you probably never knew about jwst-docs.stsci.edu
Welcome to the JWST User Documentation Homepage This website holds a comprehensive collection of documentation (known as JDox) on the JWST spacecraft and instru
Visit jwst-docs.stsci.eduWe analyzed Jwst-docs.stsci.edu page load time and found that the first response time was 111 ms and then it took 2.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
jwst-docs.stsci.edu performance score
name
value
score
weighting
Value7.9 s
0/100
10%
Value9.0 s
1/100
25%
Value7.9 s
22/100
10%
Value2,120 ms
7/100
30%
Value0.004
100/100
15%
Value10.2 s
25/100
10%
111 ms
557 ms
281 ms
249 ms
247 ms
Our browser made a total of 78 requests to load all elements on the main page. We found that 85% of them (66 requests) were addressed to the original Jwst-docs.stsci.edu, 8% (6 requests) were made to Fonts.gstatic.com and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (557 ms) belongs to the original domain Jwst-docs.stsci.edu.
Page size can be reduced by 471.1 kB (60%)
783.3 kB
312.3 kB
In fact, the total size of Jwst-docs.stsci.edu main page is 783.3 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. 70% of websites need less resources to load. HTML takes 354.0 kB which makes up the majority of the site volume.
Potential reduce by 330.2 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 142.6 kB, which is 40% 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 330.2 kB or 93% of the original size.
Potential reduce by 113.6 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, JWST Docs Stsci needs image optimization as it can save up to 113.6 kB or 67% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 7.2 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 20.1 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. Jwst-docs.stsci.edu needs all CSS files to be minified and compressed as it can save up to 20.1 kB or 13% of the original size.
Number of requests can be reduced by 61 (87%)
70
9
The browser has sent 70 CSS, Javascripts, AJAX and image requests in order to completely render the main page of JWST Docs Stsci. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 36 to 1 for JavaScripts and from 20 to 1 for CSS and as a result speed up the page load time.
jwst-docs.stsci.edu
111 ms
jwst-docs.stsci.edu
557 ms
js
281 ms
batch.js
249 ms
batch.js
247 ms
com.atlassian.auiplugin:split_aui.component.form.select2.js
169 ms
com.atlassian.confluence.editor:page-editor-soy.js
168 ms
com.atlassian.confluence.plugins.drag-and-drop:files-upload-analytics.js
169 ms
com.atlassian.confluence.editor:panel-components.js
168 ms
confluence.web.resources:dictionary.js
294 ms
confluence.web.resources:macro-js-overrides.js
295 ms
com.atlassian.confluence.plugins.confluence-ui-components:space-picker.js
295 ms
com.atlassian.auiplugin:split_aui.splitchunk.vendors--02a4084a95.js
296 ms
com.atlassian.auiplugin:split_aui.splitchunk.vendors--ec56cc9135.js
325 ms
com.atlassian.auiplugin:split_aui.component.form.date-select.js
327 ms
confluence.web.resources:date-picker.js
327 ms
com.atlassian.confluence.plugins.confluence-ui-components:space-page-picker.js
323 ms
com.atlassian.confluence.plugins.confluence-ui-components:page-picker.js
321 ms
com.atlassian.confluence.plugins.confluence-ui-components:label-picker.js
327 ms
com.atlassian.confluence.plugins.confluence-ui-components:include-exclude-picker.js
330 ms
com.atlassian.confluence.plugins.confluence-ui-components:user-group-select2.js
333 ms
com.atlassian.confluence.plugins.confluence-ui-components:cql.js
360 ms
com.atlassian.confluence.plugins.confluence-create-content-plugin:user-select2.js
331 ms
com.atlassian.confluence.plugins.confluence-macro-browser:macro-browser-js.js
359 ms
com.atlassian.confluence.plugins.confluence-frontend:split_vendors~moment.js
333 ms
com.atlassian.confluence.plugins.confluence-frontend:split_moment.js
353 ms
com.atlassian.confluence.editor:collaborative-helper.js
387 ms
com.atlassian.confluence.editor:page-editor-js.js
398 ms
com.atlassian.auiplugin:split_aui.component.progressbar.js
398 ms
confluence.web.resources:draft-changes-js.js
403 ms
edu.stsci.confluence.jdox.macros.JDoxMacros:JDoxMacros-resources.js
402 ms
com.atlassian.auiplugin:split_aui.pattern.forms.js
401 ms
edu.stsci.confluence.jdox.CustomPageTree:CustomPageTree-resources.js
401 ms
com.k15t.scroll.scroll-viewport:resource-editor-resource-omitter.js
422 ms
com.k15t.scroll.scroll-viewport:resource-quick-reload-manager-disabler.js
421 ms
batch.css
440 ms
batch.css
427 ms
com.atlassian.auiplugin:split_aui.component.form.select2.css
419 ms
vue
274 ms
font-awesome.min.css
266 ms
com.atlassian.confluence.plugins.confluence-ui-components:space-picker.css
368 ms
com.atlassian.auiplugin:split_aui.component.form.date-select.css
337 ms
com.atlassian.confluence.plugins.confluence-ui-components:space-page-picker.css
337 ms
com.atlassian.confluence.plugins.confluence-ui-components:user-group-select2.css
338 ms
com.atlassian.confluence.plugins.confluence-ui-components:cql.css
329 ms
com.atlassian.confluence.plugins.confluence-create-content-plugin:user-select2.css
261 ms
com.atlassian.confluence.plugins.confluence-macro-browser:macro-browser-css.css
223 ms
confluence.web.resources:macro-browser-sprites.css
238 ms
com.atlassian.auiplugin:split_aui.component.progressbar.css
205 ms
com.atlassian.confluence.editor:page-editor-css.css
209 ms
analytics.js
182 ms
confluence.web.resources:draft-changes-css.css
186 ms
edu.stsci.confluence.jdox.macros.JDoxMacros:JDoxMacros-resources.css
178 ms
com.atlassian.confluence.plugins.confluence-inline-tasks:inline-tasks-styles.css
208 ms
edu.stsci.confluence.jdox.CustomPageTree:CustomPageTree-resources.css
209 ms
main.css
218 ms
main.js
203 ms
css
83 ms
collect
28 ms
webb-logo.png
327 ms
jdox-updates.svg
107 ms
youtube-tutorials.svg
104 ms
pdf-documentation_1.svg
109 ms
observatory.svg
110 ms
instruments.svg
112 ms
proposing-tools.svg
114 ms
for-proposers.svg
117 ms
data.svg
115 ms
stsci_pri_combo_mark_horizonal_dark_bkgd.png
125 ms
facebook.svg
119 ms
twitter.svg
119 ms
youtube.svg
121 ms
S6uyw4BMUTPHvxk.ttf
72 ms
S6uyw4BMUTPHjx4wWw.ttf
82 ms
S6u9w4BMUTPHh7USew8.ttf
85 ms
S6u8w4BMUTPHh30wWw.ttf
82 ms
S6u9w4BMUTPHh6UVew8.ttf
84 ms
S6u9w4BMUTPHh50Xew8.ttf
78 ms
jwst-docs.stsci.edu 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.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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.
jwst-docs.stsci.edu 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
Missing source maps for large first-party JavaScript
jwst-docs.stsci.edu 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
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Jwst-docs.stsci.edu can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Jwst-docs.stsci.edu 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.
jwst-docs.stsci.edu
Open Graph description is not detected on the main page of JWST Docs Stsci. 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: