Report Summary

  • 90

    Performance

    Renders faster than
    91% of other websites

  • 76

    Accessibility

    Visual factors better than
    that of 43% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 58

    SEO

    Google-friendlier than
    20% of websites

dirty-date.net

Dirty-Date

Page Load Speed

1.6 sec in total

First Response

388 ms

Resources Loaded

896 ms

Page Rendered

278 ms

dirty-date.net screenshot

About Website

Visit dirty-date.net now to see the best up-to-date Dirty Date content for Germany and also check out these interesting facts you probably never knew about dirty-date.net

Visit dirty-date.net

Key Findings

We analyzed Dirty-date.net page load time and found that the first response time was 388 ms and then it took 1.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.

Performance Metrics

dirty-date.net performance score

90

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.8 s

56/100

10%

LCP (Largest Contentful Paint)

Value2.8 s

83/100

25%

SI (Speed Index)

Value3.4 s

89/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value2.8 s

97/100

10%

Network Requests Diagram

dirty-date.net

388 ms

jquery.min.js

31 ms

chat_background.jpg

473 ms

70_black.png

199 ms

Our browser made a total of 4 requests to load all elements on the main page. We found that 75% of them (3 requests) were addressed to the original Dirty-date.net, 25% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (473 ms) belongs to the original domain Dirty-date.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 4.0 kB (2%)

Content Size

171.7 kB

After Optimization

167.7 kB

In fact, the total size of Dirty-date.net main page is 171.7 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 166.3 kB which makes up the majority of the site volume.

HTML Optimization

-65%

Potential reduce by 3.5 kB

  • Original 5.4 kB
  • After minification 5.4 kB
  • After compression 1.9 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 3.5 kB or 65% of the original size.

Image Optimization

-0%

Potential reduce by 539 B

  • Original 166.3 kB
  • After minification 165.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. Dirty Date images are well optimized though.

Requests Breakdown

We found no issues to fix!

Requests Now

3

After Optimization

3

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

Accessibility Review

dirty-date.net accessibility score

76

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.

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

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Some elements have a [tabindex] value greater than 0

Best Practices

dirty-date.net best practices score

75

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

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

dirty-date.net SEO score

58

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Page is blocked from indexing

Language and Encoding

  • Language Detected

    DE

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Dirty-date.net can be misinterpreted by Google and other search engines. Our service has detected that German 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 Dirty-date.net 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 Dirty Date. 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: