8.8 sec in total
2.2 sec
6.5 sec
82 ms
Click here to check amazing JIRA EWORX content for Greece. Otherwise, check out these important facts you probably never knew about jira.eworx.gr
Visit jira.eworx.grWe analyzed Jira.eworx.gr page load time and found that the first response time was 2.2 sec and then it took 6.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
jira.eworx.gr performance score
name
value
score
weighting
Value5.3 s
7/100
10%
Value5.4 s
20/100
25%
Value9.2 s
13/100
10%
Value10 ms
100/100
30%
Value0
100/100
15%
Value5.3 s
72/100
10%
2177 ms
396 ms
695 ms
664 ms
624 ms
Our browser made a total of 36 requests to load all elements on the main page. We found that all of those requests were addressed to Jira.eworx.gr and no external sources were called. The less responsive or slowest element that took the longest time to load (2.2 sec) belongs to the original domain Jira.eworx.gr.
Page size can be reduced by 28.4 kB (78%)
36.2 kB
7.8 kB
In fact, the total size of Jira.eworx.gr main page is 36.2 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. 15% of websites need less resources to load. HTML takes 36.2 kB which makes up the majority of the site volume.
Potential reduce by 28.4 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 28.4 kB or 78% of the original size.
Number of requests can be reduced by 24 (71%)
34
10
The browser has sent 34 CSS, Javascripts, AJAX and image requests in order to completely render the main page of JIRA EWORX. 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 from 8 to 1 for CSS and as a result speed up the page load time.
jira.eworx.gr
2177 ms
Dashboard.jspa
396 ms
combined.css
695 ms
global.css
664 ms
com.atlassian.auiplugin:ajs.css
624 ms
com.atlassian.auiplugin:ajs.js
2068 ms
com.atlassian.gadgets.dashboard:dashboard.css
773 ms
com.atlassian.gadgets.dashboard:dashboard.js
1480 ms
com.atlassian.gadgets.embedded:gadget-core-resources.js
961 ms
com.atlassian.gadgets.embedded:gadget-container-resources.js
825 ms
com.atlassian.gadgets.dashboard:gadget-dashboard-resources.js
880 ms
com.atlassian.gadgets.dashboard:gadget-dashboard-resources.css
939 ms
jira.webresources:jira-global.js
1339 ms
jira.webresources:jira-global.css
1066 ms
jira.webresources:header.js
1141 ms
header-separator
152 ms
dropdowns
153 ms
header-separator
152 ms
menu_indicator_for_light_backgrounds.gif
154 ms
ifr
343 ms
ifr
515 ms
dashboard-diagnostics
420 ms
lt.png
236 ms
rt.png
237 ms
l.png
245 ms
r.png
382 ms
lb.png
384 ms
rb.png
401 ms
b.png
472 ms
com.atlassian.jira.gadgets:common.js
392 ms
com.atlassian.jira.gadgets:common.css
412 ms
intro
152 ms
login
149 ms
loading.gif
177 ms
intro-gadget.png
159 ms
combined-printable.css
151 ms
jira.eworx.gr accessibility score
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.
jira.eworx.gr 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
Missing source maps for large first-party JavaScript
jira.eworx.gr 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
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Jira.eworx.gr 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 Jira.eworx.gr 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.
jira.eworx.gr
Open Graph description is not detected on the main page of JIRA EWORX. 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: