Report Summary

  • 100

    Performance

    Renders faster than
    97% of other websites

  • 66

    Accessibility

    Visual factors better than
    that of 31% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 62

    SEO

    Google-friendlier than
    22% of websites

vuln.xssed.net

XSSed - XSS (cross-site scripting) information and vulnerable websites archive

Page Load Speed

1.3 sec in total

First Response

304 ms

Resources Loaded

842 ms

Page Rendered

104 ms

vuln.xssed.net screenshot

About Website

Visit vuln.xssed.net now to see the best up-to-date Vuln XSSed content and also check out these interesting facts you probably never knew about vuln.xssed.net

Providing the latest information on XSS (cross-site scripting) vulnerabilities. Advisories, news articles, tutorials and an archive of XSS vulnerable websites.

Visit vuln.xssed.net

Key Findings

We analyzed Vuln.xssed.net page load time and found that the first response time was 304 ms and then it took 946 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.

Performance Metrics

vuln.xssed.net performance score

100

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.1 s

99/100

10%

LCP (Largest Contentful Paint)

Value1.1 s

100/100

25%

SI (Speed Index)

Value1.3 s

100/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value1.1 s

100/100

10%

Network Requests Diagram

vuln.xssed.net

304 ms

xssed.css

187 ms

xssed.gif

188 ms

b.gif

180 ms

print.css

186 ms

Our browser made a total of 5 requests to load all elements on the main page. We found that all of those requests were addressed to Vuln.xssed.net and no external sources were called. The less responsive or slowest element that took the longest time to load (304 ms) belongs to the original domain Vuln.xssed.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 759 B (33%)

Content Size

2.3 kB

After Optimization

1.5 kB

In fact, the total size of Vuln.xssed.net main page is 2.3 kB. This result falls within a vast category (top 1 000 000) of heavyweight, probably not optimized, and thus slow loading web pages. Only a small number of websites need less resources to load. CSS take 1.2 kB which makes up the majority of the site volume.

HTML Optimization

-50%

Potential reduce by 537 B

  • Original 1.1 kB
  • After minification 1.1 kB
  • After compression 545 B

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 537 B or 50% of the original size.

CSS Optimization

-18%

Potential reduce by 222 B

  • Original 1.2 kB
  • After minification 1.2 kB
  • After compression 979 B

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. Vuln.xssed.net needs all CSS files to be minified and compressed as it can save up to 222 B or 18% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

2

After Optimization

2

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

Accessibility Review

vuln.xssed.net accessibility score

66

Accessibility Issues

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<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

High

Image elements do not have [alt] attributes

Best Practices

vuln.xssed.net best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

High

Browser errors were logged to the console

SEO Factors

vuln.xssed.net SEO score

62

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Page is blocked from indexing

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

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Vuln.xssed.net 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 Vuln.xssed.net main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

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