Tools & Wizards About Us
vanity.dk screenshot

Report Summary

  • 97

    Performance

    Renders faster than
    94% of other websites

  • 62

    Accessibility

    Visual factors better than
    that of 28% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 67

    SEO

    Google-friendlier than
    26% of websites

vanity.dk

vanity.dk - playground for the 4th sin

Page Load Speed

1.2 sec in total

First Response

450 ms

Resources Loaded

653 ms

Page Rendered

56 ms

vanity.dk screenshot

About Website

Click here to check amazing Vanity content for United States. Otherwise, check out these important facts you probably never knew about vanity.dk

Playground for the 4th sin

Visit vanity.dk

Key Findings

We analyzed Vanity.dk page load time and found that the first response time was 450 ms and then it took 709 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

vanity.dk performance score

97

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.6 s

94/100

10%

LCP (Largest Contentful Paint)

Value2.5 s

89/100

25%

SI (Speed Index)

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

100/100

10%

Network Requests Diagram

vanity.dk

450 ms

styles.css

87 ms

vanity_logo_01.jpg

172 ms

css

24 ms

ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyVVpcBO5Xo.woff

10 ms

Our browser made a total of 7 requests to load all elements on the main page. We found that 43% of them (3 requests) were addressed to the original Vanity.dk, 43% (3 requests) were made to Fonts.gstatic.com and 14% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (450 ms) belongs to the original domain Vanity.dk.

Page Optimization Overview & Recommendations

Page size can be reduced by 862 B (6%)

Content Size

15.4 kB

After Optimization

14.6 kB

  • HTML
  • Images
  • CSS

In fact, the total size of Vanity.dk main page is 15.4 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. Only 10% of websites need less resources to load. Images take 13.8 kB which makes up the majority of the site volume.

HTML Optimization

-62%

Potential reduce by 685 B

  • Original 1.1 kB
  • After minification 860 B
  • After compression 419 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. This page needs HTML code to be minified as it can gain 244 B, which is 22% 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 685 B or 62% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 13.8 kB
  • After minification 13.8 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. Vanity images are well optimized though.

CSS Optimization

-34%

Potential reduce by 177 B

  • Original 515 B
  • After minification 515 B
  • After compression 338 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. Vanity.dk needs all CSS files to be minified and compressed as it can save up to 177 B or 34% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

3

After Optimization

3

  • Images
  • CSS

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

Network Requests Diagram

vanity.dk

vanity.dk

450 ms

styles.css

styles.css

87 ms

vanity_logo_01.jpg

vanity_logo_01.jpg

172 ms

css

css

24 ms

ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyVVpcBO5Xo.woff

ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyVVpcBO5Xo.woff

10 ms

ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyWyosBO5Xo.woff

ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyWyosBO5Xo.woff

15 ms

ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyXsosBO5Xo.woff

ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyXsosBO5Xo.woff

18 ms

Accessibility Review

vanity.dk accessibility score

62

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

vanity.dk 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

User Experience

Impact

Issue

High

Serves images with low resolution

SEO Factors

vanity.dk SEO score

67

Search Engine Optimization Advices

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

    N/A

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Vanity.dk can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Vanity.dk 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

vanity.dk

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