2.6 sec in total
168 ms
2.2 sec
173 ms
Welcome to issues.freepbx.org homepage info - get ready to check Issue S Freepbx best content for India right away, or after learning these important things about issues.freepbx.org
Visit issues.freepbx.orgWe analyzed Issues.freepbx.org page load time and found that the first response time was 168 ms and then it took 2.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
issues.freepbx.org performance score
name
value
score
weighting
Value5.0 s
9/100
10%
Value5.2 s
23/100
25%
Value7.0 s
33/100
10%
Value80 ms
99/100
30%
Value0
100/100
15%
Value5.1 s
75/100
10%
168 ms
286 ms
577 ms
531 ms
87 ms
Our browser made a total of 110 requests to load all elements on the main page. We found that all of those requests were addressed to Issues.freepbx.org and no external sources were called. The less responsive or slowest element that took the longest time to load (670 ms) belongs to the original domain Issues.freepbx.org.
Page size can be reduced by 127.1 kB (84%)
151.9 kB
24.8 kB
In fact, the total size of Issues.freepbx.org main page is 151.9 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. 40% of websites need less resources to load. HTML takes 148.8 kB which makes up the majority of the site volume.
Potential reduce by 127.1 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 127.1 kB or 85% of the original size.
Potential reduce by 44 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. Issue S Freepbx images are well optimized though.
Number of requests can be reduced by 83 (79%)
105
22
The browser has sent 105 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Issue S Freepbx. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 57 to 1 for JavaScripts and from 28 to 1 for CSS and as a result speed up the page load time.
Dashboard.jspa
168 ms
batch.css
286 ms
batch.css
577 ms
batch.js
531 ms
batch.js
87 ms
batch.js
670 ms
jira.webresources:calendar-en.js
111 ms
jira.webresources:calendar-localisation-moment.js
133 ms
shortcuts.js
207 ms
license
123 ms
122 ms
jira-logo-scaled.png
115 ms
appswitcher
99 ms
atlassian-icons.woff
97 ms
filter
124 ms
tools_20.png
52 ms
dateCountInPeriod
256 ms
dateCountInPeriod
168 ms
dashboard-diagnostics
289 ms
com.spartez.jira.plugins.commenttemplates-key
116 ms
ifr
283 ms
resources
269 ms
viewavatar
175 ms
minor.svg
185 ms
viewavatar
186 ms
viewavatar
188 ms
viewavatar
191 ms
batch.css
81 ms
batch.js
107 ms
auth-refresh.js
96 ms
com.atlassian.auiplugin:aui-reset.css
48 ms
com.atlassian.auiplugin:aui-page-typography.css
53 ms
com.atlassian.auiplugin:aui-avatars.css
52 ms
com.atlassian.auiplugin:aui-page-layout.css
139 ms
com.atlassian.auiplugin:ajs-gadgets-base.css
114 ms
com.atlassian.auiplugin:aui-navigation.css
112 ms
com.atlassian.auiplugin:aui-experimental-iconfont.css
115 ms
com.atlassian.auiplugin:aui-header-unresponsive.css
135 ms
com.atlassian.auiplugin:aui-header.css
138 ms
com.atlassian.auiplugin:aui-page-header.css
151 ms
com.atlassian.auiplugin:aui-dropdown2.css
153 ms
com.atlassian.auiplugin:aui-buttons.css
160 ms
com.atlassian.auiplugin:aui-toolbar2.css
172 ms
com.atlassian.auiplugin:fancy-file-input.css
172 ms
com.atlassian.auiplugin:layer.css
173 ms
com.atlassian.auiplugin:dialog.css
188 ms
com.atlassian.auiplugin:internal-inline-dialog-common.css
191 ms
com.atlassian.auiplugin:internal-ajs-no-context-path.css
194 ms
com.atlassian.gadgets.publisher:ajax.css
213 ms
com.atlassian.gadgets.publisher:ajs-gadgets.css
214 ms
jira.webresources:icons.css
234 ms
com.atlassian.jira.gadgets:core-gadget-resources.css
231 ms
com.atlassian.streams:datepicker.css
238 ms
com.atlassian.streams.actions:commentActionHandlers.css
237 ms
com.atlassian.streams:streamsWebResources.css
250 ms
com.atlassian.plugins.atlassian-plugins-webresource-plugin:data.js
258 ms
com.atlassian.plugins.atlassian-plugins-webresource-plugin:context-path.js
279 ms
com.atlassian.plugins.jquery:jquery.js
352 ms
com.atlassian.auiplugin:jquery-compatibility.js
275 ms
com.atlassian.auiplugin:aui-deprecation.js
272 ms
com.atlassian.auiplugin:aui-core.js
279 ms
com.atlassian.auiplugin:ajs-gadgets-base.js
291 ms
com.atlassian.soy.soy-template-plugin:soy-deps.js
306 ms
com.atlassian.auiplugin:internal-aui-widget.js
278 ms
com.atlassian.auiplugin:aui-navigation.js
280 ms
com.atlassian.auiplugin:aui-header.js
258 ms
com.atlassian.auiplugin:aui-dropdown2.js
277 ms
com.atlassian.auiplugin:fancy-file-input.js
270 ms
com.atlassian.auiplugin:hotkeys.js
270 ms
com.atlassian.auiplugin:aui-focus-manager.js
269 ms
com.atlassian.auiplugin:aui-layer-manager.js
281 ms
com.atlassian.auiplugin:layer.js
262 ms
com.atlassian.auiplugin:dialog.js
266 ms
com.atlassian.auiplugin:internal-aui-animation.js
269 ms
com.atlassian.auiplugin:internal-ajs-no-context-path.js
287 ms
com.atlassian.gadgets.publisher:templates.js
288 ms
com.atlassian.gadgets.publisher:util.js
263 ms
com.atlassian.gadgets.publisher:ajax.js
280 ms
com.atlassian.gadgets.publisher:ajs-gadgets.js
329 ms
jira.webresources:almond.js
270 ms
jira.webresources:aui-core-amd-shim.js
282 ms
jira.webresources:legacy-namespacing.js
281 ms
jira.webresources:jira-metadata.js
264 ms
jira.webresources:aui-extensions.js
271 ms
jira.webresources:jira-events.js
265 ms
com.atlassian.auiplugin:ajs-underscorejs.js
275 ms
jira.webresources:ajs-underscorejs-amd-shim.js
277 ms
jira.webresources:browser-properties.js
278 ms
jira.webresources:util-lite.js
269 ms
com.atlassian.jira.gadgets:core-gadget-resources.js
290 ms
com.atlassian.streams:date-default.js
273 ms
com.atlassian.streams:date-js.js
282 ms
com.atlassian.streams:datepicker.js
290 ms
com.atlassian.streams:streams-parent-js.js
275 ms
com.atlassian.streams.actions:inlineActionsJs.js
277 ms
com.atlassian.streams.actions:commentActionHandlers.js
274 ms
com.atlassian.streams.jira.inlineactions:actionHandlers.js
266 ms
com.atlassian.streams:streamsWebResources.js
305 ms
com.atlassian.streams:streamsGadgetResources.js
269 ms
jira.webresources:aui-extensions-experimental.js
256 ms
com.atlassian.plugin.jslibs:moment-2.6.0.js
242 ms
jira.webresources:momentjs.js
257 ms
jira.webresources:jquery-livestamp.js
275 ms
com.atlassian.streams.streams-jira-plugin:moment-i18n.js
276 ms
preferences
81 ms
gadget-loading.gif
48 ms
throbber.gif
46 ms
feed-icon.png
47 ms
full-view-icon.png
48 ms
list-view-icon.png
87 ms
issues.freepbx.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.
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.
issues.freepbx.org 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
issues.freepbx.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
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.freepbx.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.freepbx.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.freepbx.org
Open Graph description is not detected on the main page of Issue S Freepbx. 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: