Report Summary

  • 51

    Performance

    Renders faster than
    69% of other websites

  • 90

    Accessibility

    Visual factors better than
    that of 74% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 67

    SEO

    Google-friendlier than
    26% of websites

debuggex.com

Debuggex: Online visual regex tester. JavaScript, Python, and PCRE.

Page Load Speed

2.1 sec in total

First Response

138 ms

Resources Loaded

1.9 sec

Page Rendered

81 ms

About Website

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.com

Key Findings

We analyzed Debuggex.com page load time and found that the first response time was 138 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.

Performance Metrics

debuggex.com performance score

51

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.8 s

4/100

10%

LCP (Largest Contentful Paint)

Value5.8 s

15/100

25%

SI (Speed Index)

Value6.3 s

42/100

10%

TBT (Total Blocking Time)

Value350 ms

73/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value7.0 s

53/100

10%

Network Requests Diagram

debuggex.com

138 ms

debuggex.com

269 ms

www.debuggex.com

299 ms

main.css

142 ms

main.js

532 ms

Our browser made a total of 12 requests to load all elements on the main page. We found that 83% of them (10 requests) were addressed to the original Debuggex.com, 17% (2 requests) were made to Ssl.google-analytics.com. The less responsive or slowest element that took the longest time to load (532 ms) belongs to the original domain Debuggex.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 91.7 kB (73%)

Content Size

125.2 kB

After Optimization

33.5 kB

In fact, the total size of Debuggex.com main page is 125.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 78.9 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 62.5 kB

  • Original 78.9 kB
  • After minification 73.6 kB
  • After compression 16.3 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.5 kB or 79% of the original size.

JavaScript Optimization

-63%

Potential reduce by 29.1 kB

  • Original 46.3 kB
  • After minification 46.3 kB
  • After compression 17.1 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 29.1 kB or 63% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

8

After Optimization

8

The browser has sent 8 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Debuggex. According to our analytics all requests are already optimized.

Accessibility Review

debuggex.com accessibility score

90

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

High

Form elements do not have associated labels

Best Practices

debuggex.com best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

debuggex.com SEO score

67

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    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.

Social Sharing Optimization

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: