4 sec in total
152 ms
3.8 sec
125 ms
Click here to check amazing Issues Jboss content for India. Otherwise, check out these important facts you probably never knew about issues.jboss.org
Visit issues.jboss.orgWe analyzed Issues.jboss.org page load time and found that the first response time was 152 ms and then it took 3.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
issues.jboss.org performance score
name
value
score
weighting
Value5.1 s
8/100
10%
Value9.1 s
1/100
25%
Value5.6 s
53/100
10%
Value490 ms
59/100
30%
Value0.036
100/100
15%
Value10.2 s
25/100
10%
152 ms
321 ms
558 ms
392 ms
458 ms
Our browser made a total of 53 requests to load all elements on the main page. We found that 53% of them (28 requests) were addressed to the original Issues.jboss.org, 6% (3 requests) were made to Google-analytics.com and 6% (3 requests) were made to Redhat.com. The less responsive or slowest element that took the longest time to load (969 ms) belongs to the original domain Issues.jboss.org.
Page size can be reduced by 147.8 kB (39%)
377.3 kB
229.5 kB
In fact, the total size of Issues.jboss.org main page is 377.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. 35% of websites need less resources to load. Javascripts take 206.8 kB which makes up the majority of the site volume.
Potential reduce by 36.6 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 36.6 kB or 76% of the original size.
Potential reduce by 11 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. Issues Jboss images are well optimized though.
Potential reduce by 111.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 111.1 kB or 54% of the original size.
Number of requests can be reduced by 38 (78%)
49
11
The browser has sent 49 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Issues Jboss. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 26 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
Dashboard.jspa
152 ms
batch.css
321 ms
batch.css
558 ms
batch.css
392 ms
batch.css
458 ms
batch.css
341 ms
batch.js
820 ms
batch.js
591 ms
batch.js
755 ms
batch.js
469 ms
batch.js
587 ms
batch.js
718 ms
batch.js
656 ms
jira.webresources:calendar-en.js
654 ms
jira.webresources:calendar-localisation-moment.js
756 ms
shortcuts.js
969 ms
jira-logo-scaled.png
180 ms
appswitcher
132 ms
atlassian-icons.woff
228 ms
gtm.js
86 ms
jira-login.png
476 ms
filter
201 ms
tools_20.png
158 ms
dashboard-diagnostics
297 ms
ifr
211 ms
analytics.js
63 ms
conversion_async.js
85 ms
s_code.js
166 ms
elqCfg.js
177 ms
aquant.js
97 ms
fbevents.js
79 ms
9c3a9c2a-4031-4809-b0b5-3d51ca785f3b.js
84 ms
insight.min.js
90 ms
collect
16 ms
collect
68 ms
48 ms
58 ms
pixel;r=181511330;a=p-6FvuVnRbT9rdD;ezt=1;orderid=;revenue=;labels=_fp.event.JBoss;fpan=1;fpa=P0-435289497-1458490989385;ns=0;ce=1;cm=;je=0;sr=1024x768x32;enc=n;dst=0;et=1458490989385;tzo=-180;ref=;url=https%3A%2F%2Fissues.jboss.org%2Fsecure%2FDashboard.jspa;ogl=
46 ms
auth-refresh.js
85 ms
53 ms
rh_omni_footer.js
6 ms
eloqua-1.0.13.min.js
14 ms
batch.css
83 ms
batch.js
270 ms
ip.js
58 ms
elqCfg.min.js
130 ms
svrGP
740 ms
quicklinks
178 ms
loading.gif
133 ms
s52959332047030
42 ms
svrGP.aspx
79 ms
collect
13 ms
17 ms
issues.jboss.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
Some elements have a [tabindex] value greater than 0
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
Form elements do not have associated labels
issues.jboss.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
Page has valid source maps
issues.jboss.org SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Page is blocked from indexing
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 Issues.jboss.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 Issues.jboss.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.
issues.jboss.org
Open Graph description is not detected on the main page of Issues Jboss. 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: