2.2 sec in total
227 ms
1.9 sec
162 ms
Visit bugs.xdebug.org now to see the best up-to-date Bugs Xdebug content for United States and also check out these interesting facts you probably never knew about bugs.xdebug.org
Visit bugs.xdebug.orgWe analyzed Bugs.xdebug.org page load time and found that the first response time was 227 ms and then it took 2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
bugs.xdebug.org performance score
name
value
score
weighting
Value2.6 s
63/100
10%
Value5.7 s
16/100
25%
Value4.3 s
76/100
10%
Value130 ms
96/100
30%
Value0.043
99/100
15%
Value5.8 s
67/100
10%
227 ms
81 ms
226 ms
234 ms
311 ms
Our browser made a total of 33 requests to load all elements on the main page. We found that all of those requests were addressed to Bugs.xdebug.org and no external sources were called. The less responsive or slowest element that took the longest time to load (981 ms) belongs to the original domain Bugs.xdebug.org.
Page size can be reduced by 559.1 kB (74%)
755.5 kB
196.4 kB
In fact, the total size of Bugs.xdebug.org main page is 755.5 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. Javascripts take 695.0 kB which makes up the majority of the site volume.
Potential reduce by 36.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 36.0 kB or 87% of the original size.
Potential reduce by 1.9 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. Bugs Xdebug images are well optimized though.
Potential reduce by 521.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 521.2 kB or 75% of the original size.
Number of requests can be reduced by 20 (87%)
23
3
The browser has sent 23 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Bugs Xdebug. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
my_view_page.php
227 ms
default.css
81 ms
status_config.php
226 ms
dropzone-5.5.0.min.css
234 ms
bootstrap-3.4.1.min.css
311 ms
font-awesome-4.7.0.min.css
237 ms
fonts.css
238 ms
bootstrap-datetimepicker-4.17.47.min.css
242 ms
ace.min.css
386 ms
ace-mantis.css
321 ms
ace-skins.min.css
323 ms
javascript_config.php
412 ms
javascript_translations.php
420 ms
jquery-2.2.4.min.js
467 ms
dropzone-5.5.0.min.js
466 ms
common.js
483 ms
plugin_file.php
531 ms
bootstrap-3.4.1.min.js
600 ms
moment-with-locales-2.29.4.min.js
981 ms
bootstrap-datetimepicker-4.17.47.min.js
598 ms
typeahead.jquery-1.3.0.min.js
599 ms
list-2.3.1.min.js
599 ms
ace.min.js
611 ms
mantis_logo.png
133 ms
open-sans-v35-latin-regular.woff
105 ms
open-sans-v35-latin-ext-regular.woff
88 ms
open-sans-v35-vietnamese-regular.woff
103 ms
open-sans-v35-hebrew-regular.woff
104 ms
open-sans-v35-greek-regular.woff
104 ms
open-sans-v35-greek-ext-regular.woff
168 ms
open-sans-v35-cyrillic-regular.woff
183 ms
open-sans-v35-cyrillic-ext-regular.woff
183 ms
fontawesome-webfont.woff
250 ms
bugs.xdebug.org accessibility score
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
Links do not have a discernible name
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>).
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.
bugs.xdebug.org best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
bugs.xdebug.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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Bugs.xdebug.org 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 Bugs.xdebug.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.
bugs.xdebug.org
Open Graph description is not detected on the main page of Bugs Xdebug. 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: