Tools & Wizards About Us
habbo.st screenshot

Report Summary

  • 49

    Performance

    Renders faster than
    67% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 51% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 97

    SEO

    Google-friendlier than
    91% of websites

habbo.st

Habbo.st - Dein Retro Hotel seit 2004.

Page Load Speed

2.5 sec in total

First Response

33 ms

Resources Loaded

2.2 sec

Page Rendered

321 ms

habbo.st screenshot

About Website

Click here to check amazing Habbo content for Germany. Otherwise, check out these important facts you probably never knew about habbo.st

Habbo ist eine virtuelle Welt für Kinder und Jugendliche. Hier bei uns kannst du eigene Räume erstellen, Freunde finden und berühmt werden!

Visit habbo.st

Key Findings

We analyzed Habbo.st page load time and found that the first response time was 33 ms and then it took 2.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

habbo.st performance score

49

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.9 s

52/100

10%

LCP (Largest Contentful Paint)

Value3.1 s

75/100

25%

SI (Speed Index)

Value4.9 s

65/100

10%

TBT (Total Blocking Time)

Value2,380 ms

5/100

30%

CLS (Cumulative Layout Shift)

Value0.044

99/100

15%

TTI (Time to Interactive)

Value11.1 s

20/100

10%

Network Requests Diagram

habbo.st

33 ms

index

232 ms

app.css

194 ms

adsbygoogle.js

110 ms

jquery_sel.js

223 ms

Our browser made a total of 69 requests to load all elements on the main page. We found that 23% of them (16 requests) were addressed to the original Habbo.st, 16% (11 requests) were made to Avatar.habbo.st and 16% (11 requests) were made to Images.habbo.st. The less responsive or slowest element that took the longest time to load (783 ms) relates to the external source Avatar.habbo.st.

Page Optimization Overview & Recommendations

Page size can be reduced by 271.0 kB (19%)

Content Size

1.4 MB

After Optimization

1.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Habbo.st main page is 1.4 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 50% of websites need less resources to load. Javascripts take 679.8 kB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 91.3 kB

  • Original 104.7 kB
  • After minification 97.1 kB
  • After compression 13.4 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 91.3 kB or 87% of the original size.

Image Optimization

-24%

Potential reduce by 150.1 kB

  • Original 634.2 kB
  • After minification 484.0 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, Habbo needs image optimization as it can save up to 150.1 kB or 24% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-4%

Potential reduce by 28.3 kB

  • Original 679.8 kB
  • After minification 679.8 kB
  • After compression 651.5 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

-31%

Potential reduce by 1.3 kB

  • Original 4.3 kB
  • After minification 4.3 kB
  • After compression 3.0 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. Habbo.st needs all CSS files to be minified and compressed as it can save up to 1.3 kB or 31% of the original size.

Requests Breakdown

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

Requests Now

61

After Optimization

28

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 61 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Habbo. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

habbo.st

habbo.st

33 ms

index

index

232 ms

app.css

app.css

194 ms

adsbygoogle.js

adsbygoogle.js

110 ms

jquery_sel.js

jquery_sel.js

223 ms

api.js

api.js

59 ms

email-decode.min.js

email-decode.min.js

19 ms

cookieconsent.min.css

cookieconsent.min.css

29 ms

cookieconsent.min.js

cookieconsent.min.js

38 ms

snowstorm.js

snowstorm.js

304 ms

show_ads_impl.js

show_ads_impl.js

276 ms

css

css

36 ms

recaptcha__en.js

recaptcha__en.js

96 ms

b3U5hRt.png

b3U5hRt.png

74 ms

avatar.habbo.st

avatar.habbo.st

374 ms

3d8cc6778292a6b640fc2a6a2dc5b432.png

3d8cc6778292a6b640fc2a6a2dc5b432.png

454 ms

avatar.habbo.st

avatar.habbo.st

478 ms

avatar.habbo.st

avatar.habbo.st

675 ms

avatar.habbo.st

avatar.habbo.st

595 ms

avatar.habbo.st

avatar.habbo.st

652 ms

avatar.habbo.st

avatar.habbo.st

687 ms

avatar.habbo.st

avatar.habbo.st

595 ms

avatar.habbo.st

avatar.habbo.st

667 ms

avatar.habbo.st

avatar.habbo.st

783 ms

avatar.habbo.st

avatar.habbo.st

782 ms

avatar.habbo.st

avatar.habbo.st

749 ms

5fde590d95d39f3c402765d9b8f79893.png

5fde590d95d39f3c402765d9b8f79893.png

268 ms

b90284a2571374ba894ada854a44749f.png

b90284a2571374ba894ada854a44749f.png

355 ms

35967a5e8f736c6d7b97c9fd068748da.png

35967a5e8f736c6d7b97c9fd068748da.png

347 ms

51f89ea26d4722f4ba1990c3429795ff.png

51f89ea26d4722f4ba1990c3429795ff.png

446 ms

0b03ae9bea82192bb8c0b38980c187a9.png

0b03ae9bea82192bb8c0b38980c187a9.png

277 ms

293aa3948c3f1bef6e804f940d313e2e.png

293aa3948c3f1bef6e804f940d313e2e.png

625 ms

1155810603056cce6cf6a851507daa20.png

1155810603056cce6cf6a851507daa20.png

380 ms

b50a97a223e4f7ff8a08f9715efc7ad9.png

b50a97a223e4f7ff8a08f9715efc7ad9.png

445 ms

bb8eeeed88501121d8d57b403339f60c.png

bb8eeeed88501121d8d57b403339f60c.png

543 ms

cebdd6309c066727a534d026210cb7ed.png

cebdd6309c066727a534d026210cb7ed.png

483 ms

habbos_2.png

habbos_2.png

240 ms

arrow.png

arrow.png

248 ms

logo_ch.png

logo_ch.png

239 ms

head.png

head.png

264 ms

lock.png

lock.png

261 ms

clock.png

clock.png

262 ms

logo.png

logo.png

438 ms

larg_hotel.png

larg_hotel.png

698 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

81 ms

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

87 ms

pxiEyp8kv8JHgFVrJJfedw.ttf

pxiEyp8kv8JHgFVrJJfedw.ttf

92 ms

pxiByp8kv8JHgFVrLGT9Z1xlEA.ttf

pxiByp8kv8JHgFVrLGT9Z1xlEA.ttf

95 ms

pxiByp8kv8JHgFVrLEj6Z1xlEA.ttf

pxiByp8kv8JHgFVrLEj6Z1xlEA.ttf

101 ms

pxiByp8kv8JHgFVrLCz7Z1xlEA.ttf

pxiByp8kv8JHgFVrLCz7Z1xlEA.ttf

100 ms

default

default

491 ms

zrt_lookup.html

zrt_lookup.html

42 ms

ads

ads

89 ms

mail.png

mail.png

235 ms

main.js

main.js

9 ms

sodar

sodar

71 ms

twk-event-polyfill.js

twk-event-polyfill.js

531 ms

twk-main.js

twk-main.js

59 ms

twk-vendor.js

twk-vendor.js

152 ms

twk-chunk-vendors.js

twk-chunk-vendors.js

183 ms

twk-chunk-common.js

twk-chunk-common.js

195 ms

twk-runtime.js

twk-runtime.js

106 ms

twk-app.js

twk-app.js

61 ms

sodar2.js

sodar2.js

19 ms

runner.html

runner.html

6 ms

aframe

aframe

20 ms

q3_ozqIbHCwHEmDedgzG-D6UnUyzi2L496FFdqoLokA.js

q3_ozqIbHCwHEmDedgzG-D6UnUyzi2L496FFdqoLokA.js

6 ms

widget-settings

widget-settings

216 ms

de.js

de.js

14 ms

Accessibility Review

habbo.st accessibility score

81

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

High

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

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

Best Practices

habbo.st 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

Page has valid source maps

SEO Factors

habbo.st SEO score

97

Search Engine Optimization Advices

Mobile Friendly

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/).

Impact

Issue

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    DE

  • Language Claimed

    DE

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Habbo.st can be misinterpreted by Google and other search engines. Our service has detected that German is used on the page, and it matches the claimed language. Our system also found out that Habbo.st 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

habbo.st

Open Graph data is detected on the main page of Habbo. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: