Tools & Wizards About Us
gustav.ws screenshot

Report Summary

  • 0

    Performance

  • 68

    Accessibility

    Visual factors better than
    that of 33% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

gustav.ws

WEBSITE.WS - Your Internet Address For Life™

Page Load Speed

1.1 sec in total

First Response

222 ms

Resources Loaded

832 ms

Page Rendered

60 ms

gustav.ws screenshot

About Website

Visit gustav.ws now to see the best up-to-date Gustav content and also check out these interesting facts you probably never knew about gustav.ws

Visit gustav.ws

Key Findings

We analyzed Gustav.ws page load time and found that the first response time was 222 ms and then it took 892 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

gustav.ws performance score

0

Network Requests Diagram

gustav.ws

222 ms

wc_landing.dhtml

542 ms

layout.css

66 ms

jquery-3.5.0.min.js

70 ms

jquery-migrate-3.0.0.js

70 ms

Our browser made a total of 21 requests to load all elements on the main page. We found that 5% of them (1 request) were addressed to the original Gustav.ws, 95% (20 requests) were made to Website.ws. The less responsive or slowest element that took the longest time to load (542 ms) relates to the external source Website.ws.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.5 kB (17%)

Content Size

8.8 kB

After Optimization

7.3 kB

  • HTML
  • CSS

In fact, the total size of Gustav.ws main page is 8.8 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. CSS take 8.2 kB which makes up the majority of the site volume.

HTML Optimization

-46%

Potential reduce by 264 B

  • Original 570 B
  • After minification 563 B
  • After compression 306 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 264 B or 46% of the original size.

CSS Optimization

-15%

Potential reduce by 1.2 kB

  • Original 8.2 kB
  • After minification 8.2 kB
  • After compression 7.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. Gustav.ws needs all CSS files to be minified and compressed as it can save up to 1.2 kB or 15% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

2

After Optimization

2

  • AJAX
  • CSS

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

Network Requests Diagram

gustav.ws

gustav.ws

222 ms

wc_landing.dhtml

wc_landing.dhtml

542 ms

layout.css

layout.css

66 ms

jquery-3.5.0.min.js

jquery-3.5.0.min.js

70 ms

jquery-migrate-3.0.0.js

jquery-migrate-3.0.0.js

70 ms

cufon-yui.js

cufon-yui.js

70 ms

Rockwell_400.font.js

Rockwell_400.font.js

69 ms

roboto.cufonfonts.js

roboto.cufonfonts.js

69 ms

iepngfix_tilebg.js

iepngfix_tilebg.js

69 ms

thickbox.js

thickbox.js

69 ms

emoji.css

emoji.css

68 ms

emoji.min.js

emoji.min.js

70 ms

emoji.js

emoji.js

68 ms

jquery.md5.js

jquery.md5.js

68 ms

menu.js

menu.js

68 ms

js-loader.js

js-loader.js

68 ms

jquery.emojipicker.css

jquery.emojipicker.css

68 ms

jquery.emojipicker.js

jquery.emojipicker.js

67 ms

jquery.emojipicker.a.css

jquery.emojipicker.a.css

68 ms

jquery.emojis.js

jquery.emojis.js

67 ms

cookie-alert.js

cookie-alert.js

67 ms

Accessibility Review

gustav.ws accessibility score

68

Accessibility Issues

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

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

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

Best Practices

gustav.ws best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

High

Browser errors were logged to the console

SEO Factors

gustav.ws SEO score

83

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

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Gustav.ws 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 Gustav.ws 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

gustav.ws

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