Report Summary

  • 100

    Performance

    Renders faster than
    97% of other websites

  • 90

    Accessibility

    Visual factors better than
    that of 74% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

htmlpurifier.org

HTML Purifier - Filter your HTML the standards-compliant way!

Page Load Speed

410 ms in total

First Response

61 ms

Resources Loaded

185 ms

Page Rendered

164 ms

About Website

Click here to check amazing HTML Purifier content for United States. Otherwise, check out these important facts you probably never knew about htmlpurifier.org

HTML filter that guards against XSS and ensures standards-compliant output.

Visit htmlpurifier.org

Key Findings

We analyzed Htmlpurifier.org page load time and found that the first response time was 61 ms and then it took 349 ms to load all DOM resources and completely render a web page. This is an excellent result, as only 5% of websites can load faster.

Performance Metrics

htmlpurifier.org performance score

100

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.0 s

100/100

10%

LCP (Largest Contentful Paint)

Value1.5 s

100/100

25%

SI (Speed Index)

Value1.0 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.0 s

100/100

10%

Network Requests Diagram

htmlpurifier.org

61 ms

common.css

29 ms

del.icio.us.js

46 ms

index.css

35 ms

powered.png

43 ms

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

Page Optimization Overview & Recommendations

Page size can be reduced by 16.7 kB (56%)

Content Size

29.5 kB

After Optimization

12.9 kB

In fact, the total size of Htmlpurifier.org main page is 29.5 kB. This result falls within a vast category (top 1 000 000) of heavyweight, probably not optimized, and thus slow loading web pages. Only 5% of websites need less resources to load. HTML takes 12.8 kB which makes up the majority of the site volume.

HTML Optimization

-64%

Potential reduce by 8.3 kB

  • Original 12.8 kB
  • After minification 12.1 kB
  • After compression 4.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 8.3 kB or 64% of the original size.

Image Optimization

-22%

Potential reduce by 1.6 kB

  • Original 7.3 kB
  • After minification 5.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, HTML Purifier needs image optimization as it can save up to 1.6 kB or 22% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-52%

Potential reduce by 299 B

  • Original 576 B
  • After minification 489 B
  • After compression 277 B

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

CSS Optimization

-74%

Potential reduce by 6.5 kB

  • Original 8.8 kB
  • After minification 6.2 kB
  • After compression 2.3 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. Htmlpurifier.org needs all CSS files to be minified and compressed as it can save up to 6.5 kB or 74% 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 HTML Purifier. According to our analytics all requests are already optimized.

Accessibility Review

htmlpurifier.org 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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

htmlpurifier.org best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

SEO Factors

htmlpurifier.org SEO score

75

Search Engine Optimization Advices

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 Htmlpurifier.org 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 Htmlpurifier.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.

Social Sharing Optimization

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