2.4 sec in total
236 ms
2.1 sec
106 ms
Click here to check amazing Debuggex content for United States. Otherwise, check out these important facts you probably never knew about debuggex.com
Test your regex by visualizing it with a live editor. JavaScript, Python, and PCRE.
Visit debuggex.comWe analyzed Debuggex.com page load time and found that the first response time was 236 ms and then it took 2.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.
debuggex.com performance score
name
value
score
weighting
Value6.5 s
2/100
10%
Value6.5 s
9/100
25%
Value7.3 s
29/100
10%
Value260 ms
84/100
30%
Value0
100/100
15%
Value7.5 s
48/100
10%
236 ms
456 ms
158 ms
653 ms
58 ms
Our browser made a total of 27 requests to load all elements on the main page. We found that 33% of them (9 requests) were addressed to the original Debuggex.com, 48% (13 requests) were made to Static.login.persona.org and 11% (3 requests) were made to Login.persona.org. The less responsive or slowest element that took the longest time to load (653 ms) belongs to the original domain Debuggex.com.
Page size can be reduced by 272.2 kB (66%)
413.9 kB
141.7 kB
In fact, the total size of Debuggex.com main page is 413.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. 20% of websites need less resources to load. Javascripts take 321.4 kB which makes up the majority of the site volume.
Potential reduce by 62.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 62.6 kB or 79% of the original size.
Potential reduce by 426 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. Debuggex images are well optimized though.
Potential reduce by 209.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 209.2 kB or 65% of the original size.
Number of requests can be reduced by 10 (42%)
24
14
The browser has sent 24 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Debuggex. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 5 to 1 for JavaScripts and as a result speed up the page load time.
debuggex.com
236 ms
www.debuggex.com
456 ms
main.css
158 ms
main.js
653 ms
include.js
58 ms
ga.js
214 ms
global_regex
242 ms
logo.png
84 ms
startslider.png
156 ms
slider.png
230 ms
fontawesome-webfont.woff
361 ms
communication_iframe
22 ms
communication_iframe.js
29 ms
__utm.gif
23 ms
dialog.js
32 ms
session_context
9 ms
dialog.css
12 ms
grain.png
13 ms
persona-logo-transparent.png
20 ms
arrow_grey.png
6 ms
button-loader.gif
13 ms
button-arrow.png
8 ms
button-arrow-hover.png
7 ms
button-arrow-active.png
6 ms
persona_watermark.png
44 ms
persona_watermark_sm.png
21 ms
persona_watermark_dark_sm.png
7 ms
debuggex.com 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.
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
debuggex.com 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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
debuggex.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Debuggex.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 Debuggex.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.
debuggex.com
Open Graph description is not detected on the main page of Debuggex. 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: