2 sec in total
16 ms
1.9 sec
94 ms
Click here to check amazing Dev Kayako content for United States. Otherwise, check out these important facts you probably never knew about dev.kayako.com
Log in to Jira, Confluence, and all other Atlassian Cloud products here. Not an Atlassian user? Sign up for free.
Visit dev.kayako.comWe analyzed Dev.kayako.com page load time and found that the first response time was 16 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.
dev.kayako.com performance score
name
value
score
weighting
Value6.5 s
2/100
10%
Value7.6 s
3/100
25%
Value6.5 s
39/100
10%
Value360 ms
72/100
30%
Value0
100/100
15%
Value7.9 s
44/100
10%
16 ms
153 ms
822 ms
59 ms
309 ms
Our browser made a total of 85 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Dev.kayako.com, 69% (59 requests) were made to D1ixbz5qgnvms3.cloudfront.net and 25% (21 requests) were made to Kayako.atlassian.net. The less responsive or slowest element that took the longest time to load (822 ms) relates to the external source Kayako.atlassian.net.
Page size can be reduced by 171.7 kB (67%)
258.1 kB
86.4 kB
In fact, the total size of Dev.kayako.com main page is 258.1 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. 55% of websites need less resources to load. Javascripts take 190.7 kB which makes up the majority of the site volume.
Potential reduce by 52.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 52.0 kB or 80% of the original size.
Potential reduce by 5 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. Dev Kayako images are well optimized though.
Potential reduce by 119.7 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 119.7 kB or 63% of the original size.
Number of requests can be reduced by 59 (76%)
78
19
The browser has sent 78 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Dev Kayako. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 47 to 1 for JavaScripts and from 14 to 1 for CSS and as a result speed up the page load time.
dev.kayako.com
16 ms
kayako.atlassian.net
153 ms
kayako.atlassian.net
822 ms
batch.css
59 ms
batch.css
309 ms
jira.webresources:calendar.css
52 ms
jira.webresources:groupbrowser.css
56 ms
jira.webresources:group-pickers.css
55 ms
batch.js
105 ms
batch.js
399 ms
batch.js
114 ms
batch.js
71 ms
batch.js
71 ms
jira.webresources:calendar.js
84 ms
jira.webresources:group-label-lozenge.js
83 ms
jira.webresources:groupbrowser.js
93 ms
jira.webresources:group-pickers.js
96 ms
jira.webresources:ie-imitation-placeholder.js
101 ms
jira.webresources:jira-project-issuetype-fields.js
100 ms
jira.webresources:jira-fields.js
108 ms
jira.webresources:calendar-en.js
105 ms
jira.webresources:calendar-localisation-moment.js
106 ms
shortcuts.js
246 ms
main.js
82 ms
main.js
78 ms
resources
301 ms
resources
357 ms
jira-logo-scaled.png
115 ms
appswitcher
208 ms
tools_20.png
45 ms
filter
178 ms
dashboard-diagnostics
484 ms
atlassian-icons.woff
55 ms
ifr
242 ms
ga.js
62 ms
admin
189 ms
announcement
209 ms
session
208 ms
user
215 ms
mypermissions
435 ms
resources
418 ms
__utm.gif
14 ms
batch.js
4 ms
batch.js
296 ms
auth-refresh.js
181 ms
com.atlassian.auiplugin:ajs-gadgets-base.css
15 ms
com.atlassian.gadgets.publisher:ajax.css
14 ms
com.atlassian.gadgets.publisher:ajs-gadgets-lite.css
17 ms
jira.webresources:icons.css
14 ms
com.atlassian.jira.gadgets:core-gadget-resources.css
15 ms
jira.webresources:list-styles.css
14 ms
jira.webresources:inline-layer.css
16 ms
jira.webresources:dropdown.css
15 ms
jira.webresources:almond.js
15 ms
com.atlassian.plugins.jquery:jquery.js
17 ms
com.atlassian.auiplugin:jquery-compatibility.js
15 ms
com.atlassian.auiplugin:aui-deprecation.js
16 ms
com.atlassian.auiplugin:aui-core.js
15 ms
com.atlassian.auiplugin:ajs-gadgets-base.js
15 ms
com.atlassian.gadgets.publisher:templates.js
19 ms
com.atlassian.gadgets.publisher:util.js
19 ms
com.atlassian.gadgets.publisher:ajax.js
18 ms
com.atlassian.gadgets.publisher:ajs-gadgets-lite.js
20 ms
jira.webresources:aui-core-amd-shim.js
20 ms
jira.webresources:legacy-namespacing.js
19 ms
com.atlassian.auiplugin:ajs-underscorejs.js
19 ms
jira.webresources:ajs-underscorejs-amd-shim.js
20 ms
jira.webresources:jira-metadata.js
21 ms
jira.webresources:aui-extensions.js
22 ms
jira.webresources:jira-events.js
23 ms
jira.webresources:browser-properties.js
22 ms
jira.webresources:top-same-origin-window.js
23 ms
jira.webresources:util-lite.js
23 ms
com.atlassian.jira.gadgets:core-gadget-resources.js
23 ms
jira.webresources:content-retrievers.js
23 ms
jira.webresources:inline-layer.js
25 ms
jira.webresources:list.js
24 ms
jira.webresources:dropdown.js
23 ms
generate
83 ms
loading.gif
16 ms
batch.css
84 ms
batch.js
151 ms
ico_reports.png
8 ms
menu_indicator_for_light_backgrounds.gif
12 ms
ico_filters.png
3 ms
dev.kayako.com accessibility score
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
dev.kayako.com 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
Browser errors were logged to the console
Page has valid source maps
dev.kayako.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
robots.txt is not valid
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 Dev.kayako.com 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 Dev.kayako.com 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.
dev.kayako.com
Open Graph description is not detected on the main page of Dev Kayako. 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: