Access hotdoom.com. collection of axel nordin, hot doom .com by rafaël rozendaal, 2009

hotdoom.com

167 ms

swfobject.js

70 ms

ga.js

11 ms

Our browser made a total of 3 requests to load all elements on the main page. We found that 33% of them (1 request) were addressed to the original Hotdoom.com, 33% (1 request) were made to Rafaelrozendaal.com and 33% (1 request) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (167 ms) belongs to the original domain Hotdoom.com.

Content Size

31.7 kB

After Optimization

22.5 kB

In fact, the total size of Hotdoom.com main page is 31.7 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. Javascripts take 27.2 kB which makes up the majority of the site volume.

HTML Optimization

-67%

Potential reduce by 3.0 kB

Original 4.4 kB
After minification 3.6 kB
After compression 1.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. This page needs HTML code to be minified as it can gain 896 B, which is 20% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 3.0 kB or 67% of the original size.

JavaScript Optimization

-23%

Potential reduce by 6.3 kB

Original 27.2 kB
After minification 27.2 kB
After compression 21.0 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 6.3 kB or 23% of the original size.

Requests Now

After Optimization

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

Accessibility Issues

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.

High

<frame> or <iframe> elements do not have a title

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

High

<html> element does not have a [lang] attribute

These items highlight common accessibility best practices.

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Areas of Improvement

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

High

Missing source maps for large first-party JavaScript

Search Engine Optimization Advices

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

High

robots.txt is not valid

Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).

High

Document doesn't use legible font sizes

Language and Encoding

Language Detected

EN
Language Claimed

N/A
Encoding

UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Hotdoom.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Hotdoom.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 data is detected on the main page of Hot Doom. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: