Tools & Wizards About Us
domxss.com screenshot

Report Summary

  • 88

    Performance

    Renders faster than
    90% of other websites

  • 65

    Accessibility

    Visual factors better than
    that of 30% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 54

    SEO

    Google-friendlier than
    19% of websites

domxss.com

DOMXSS.com: interactive DOM XSS vulnerable website

Page Load Speed

546 ms in total

First Response

76 ms

Resources Loaded

358 ms

Page Rendered

112 ms

domxss.com screenshot

About Website

Click here to check amazing DOM XSS content. Otherwise, check out these important facts you probably never knew about domxss.com

DOM XSS security Page

Visit domxss.com

Key Findings

We analyzed Domxss.com page load time and found that the first response time was 76 ms and then it took 470 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 10% of websites can load faster.

Performance Metrics

domxss.com performance score

88

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.7 s

92/100

10%

LCP (Largest Contentful Paint)

Value3.2 s

72/100

25%

SI (Speed Index)

Value1.7 s

100/100

10%

TBT (Total Blocking Time)

Value170 ms

92/100

30%

CLS (Cumulative Layout Shift)

Value0.011

100/100

15%

TTI (Time to Interactive)

Value4.2 s

85/100

10%

Network Requests Diagram

domxss.com

76 ms

72 ms

global.css

34 ms

custom.css

65 ms

jquery-1.4.4.min.js

114 ms

Our browser made a total of 14 requests to load all elements on the main page. We found that 79% of them (11 requests) were addressed to the original Domxss.com, 14% (2 requests) were made to Google-analytics.com and 7% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (114 ms) belongs to the original domain Domxss.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 32.8 kB (23%)

Content Size

143.0 kB

After Optimization

110.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Domxss.com main page is 143.0 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. Images take 73.5 kB which makes up the majority of the site volume.

HTML Optimization

-63%

Potential reduce by 4.3 kB

  • Original 6.8 kB
  • After minification 6.1 kB
  • After compression 2.5 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 4.3 kB or 63% of the original size.

Image Optimization

-38%

Potential reduce by 27.8 kB

  • Original 73.5 kB
  • After minification 45.7 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. Obviously, DOM XSS needs image optimization as it can save up to 27.8 kB or 38% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-0%

Potential reduce by 139 B

  • Original 56.0 kB
  • After minification 56.0 kB
  • After compression 55.9 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. This website has mostly compressed JavaScripts.

CSS Optimization

-9%

Potential reduce by 615 B

  • Original 6.7 kB
  • After minification 6.7 kB
  • After compression 6.1 kB

CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Domxss.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 4 (33%)

Requests Now

12

After Optimization

8

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 12 CSS, Javascripts, AJAX and image requests in order to completely render the main page of DOM XSS. 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.

Network Requests Diagram

domxss.com

domxss.com

76 ms

72 ms

global.css

global.css

34 ms

custom.css

custom.css

65 ms

jquery-1.4.4.min.js

jquery-1.4.4.min.js

114 ms

jquery.parallax-0.2-min.js

jquery.parallax-0.2-min.js

70 ms

cufon-yui.js

cufon-yui.js

72 ms

analytics.js

analytics.js

9 ms

logo.png

logo.png

38 ms

start.png

start.png

67 ms

1460733933_logo-bcdet.png

1460733933_logo-bcdet.png

58 ms

background.jpg

background.jpg

102 ms

collect

collect

32 ms

js

js

59 ms

Accessibility Review

domxss.com accessibility score

65

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

domxss.com best practices score

75

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

SEO Factors

domxss.com SEO score

54

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

High

robots.txt is not valid

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

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

domxss.com

Open Graph description is not detected on the main page of DOM XSS. 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: