Tools & Wizards About Us
metaldating.dk screenshot

Report Summary

  • 14

    Performance

    Renders faster than
    26% of other websites

  • 82

    Accessibility

    Visual factors better than
    that of 52% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

metaldating.dk

Metaldating

Page Load Speed

6.4 sec in total

First Response

371 ms

Resources Loaded

5.8 sec

Page Rendered

178 ms

metaldating.dk screenshot

About Website

Visit metaldating.dk now to see the best up-to-date Metaldating content and also check out these interesting facts you probably never knew about metaldating.dk

Metaldating.com is the largest dating site in the world for metalheads. 100% free with thousands of real metalheads!

Visit metaldating.dk

Key Findings

We analyzed Metaldating.dk page load time and found that the first response time was 371 ms and then it took 6 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

metaldating.dk performance score

14

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.6 s

33/100

10%

LCP (Largest Contentful Paint)

Value8.0 s

2/100

25%

SI (Speed Index)

Value13.7 s

2/100

10%

TBT (Total Blocking Time)

Value2,520 ms

4/100

30%

CLS (Cumulative Layout Shift)

Value0.238

52/100

15%

TTI (Time to Interactive)

Value15.3 s

7/100

10%

Network Requests Diagram

metaldating.dk

371 ms

metaldating.com

436 ms

www.metaldating.com

2470 ms

font-awesome.min.css

110 ms

bootstrap.min.css

219 ms

Our browser made a total of 84 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Metaldating.dk, 37% (31 requests) were made to Metaldating.com and 11% (9 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (2.5 sec) relates to the external source Metaldating.com.

Page Optimization Overview & Recommendations

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

Content Size

838.9 kB

After Optimization

678.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Metaldating.dk main page is 838.9 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. 55% of websites need less resources to load. Javascripts take 519.4 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 46.6 kB

  • Original 59.0 kB
  • After minification 57.9 kB
  • After compression 12.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. 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 46.6 kB or 79% of the original size.

Image Optimization

-0%

Potential reduce by 98 B

  • Original 130.6 kB
  • After minification 130.5 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. Metaldating images are well optimized though.

JavaScript Optimization

-5%

Potential reduce by 24.7 kB

  • Original 519.4 kB
  • After minification 519.4 kB
  • After compression 494.7 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

-68%

Potential reduce by 88.8 kB

  • Original 129.8 kB
  • After minification 111.5 kB
  • After compression 41.1 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. Metaldating.dk needs all CSS files to be minified and compressed as it can save up to 88.8 kB or 68% of the original size.

Requests Breakdown

Number of requests can be reduced by 42 (56%)

Requests Now

75

After Optimization

33

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

metaldating.dk

metaldating.dk

371 ms

metaldating.com

metaldating.com

436 ms

www.metaldating.com

www.metaldating.com

2470 ms

font-awesome.min.css

font-awesome.min.css

110 ms

bootstrap.min.css

bootstrap.min.css

219 ms

style_blue.css

style_blue.css

400 ms

epoch_new.css

epoch_new.css

303 ms

css

css

37 ms

functions.js

functions.js

302 ms

validate.js

validate.js

294 ms

float-panel.js

float-panel.js

299 ms

shoutbox.js

shoutbox.js

314 ms

adsbygoogle.js

adsbygoogle.js

161 ms

jquery.min.js

jquery.min.js

508 ms

bootstrap.min.js

bootstrap.min.js

438 ms

fblogin.php

fblogin.php

115 ms

Metalheart_tranparant.png

Metalheart_tranparant.png

110 ms

Metaldating.jpg

Metaldating.jpg

110 ms

Concert.jpg

Concert.jpg

420 ms

getsnap.php

getsnap.php

122 ms

getsnap.php

getsnap.php

197 ms

getsnap.php

getsnap.php

210 ms

getsnap.php

getsnap.php

233 ms

getsnap.php

getsnap.php

243 ms

getsnap.php

getsnap.php

233 ms

getsnap.php

getsnap.php

368 ms

getsnap.php

getsnap.php

368 ms

getsnap.php

getsnap.php

419 ms

getsnap.php

getsnap.php

369 ms

getsnap.php

getsnap.php

410 ms

getsnap.php

getsnap.php

459 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

532 ms

show_ads_impl.js

show_ads_impl.js

243 ms

WBLnrEXKYFlGHrOKmGDFXEXI.ttf

WBLnrEXKYFlGHrOKmGDFXEXI.ttf

64 ms

updateonlinetime.php

updateonlinetime.php

0 ms

updateonlinecount.php

updateonlinecount.php

1042 ms

sdk.js

sdk.js

16 ms

sdk.js

sdk.js

5 ms

login_button.php

login_button.php

68 ms

VSqDVBWWUii.js

VSqDVBWWUii.js

21 ms

teE39sffXW8.png

teE39sffXW8.png

12 ms

iqVGY7gYXlg.gif

iqVGY7gYXlg.gif

14 ms

zrt_lookup.html

zrt_lookup.html

49 ms

ads

ads

622 ms

ads

ads

408 ms

17e840dcfb558e6e2f54294b33a53192.js

17e840dcfb558e6e2f54294b33a53192.js

33 ms

2c467cbcaed741394c4076d97cdce7d0.js

2c467cbcaed741394c4076d97cdce7d0.js

32 ms

load_preloaded_resource.js

load_preloaded_resource.js

27 ms

bbe3fbefe89164063f731512d72e756f.js

bbe3fbefe89164063f731512d72e756f.js

31 ms

ff6b8413ccec2e2686fe44d6d4a2e9d1.js

ff6b8413ccec2e2686fe44d6d4a2e9d1.js

55 ms

abg_lite.js

abg_lite.js

54 ms

window_focus.js

window_focus.js

198 ms

qs_click_protection.js

qs_click_protection.js

99 ms

ufs_web_display.js

ufs_web_display.js

22 ms

b8bba7bdb82ef259240353901c7e809d.js

b8bba7bdb82ef259240353901c7e809d.js

90 ms

icon.png

icon.png

146 ms

s

s

109 ms

css

css

40 ms

reactive_library.js

reactive_library.js

224 ms

ads

ads

401 ms

ads

ads

785 ms

ads

ads

259 ms

4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrw2IJllpyw.ttf

4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrw2IJllpyw.ttf

15 ms

4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrwEIJllpyw.ttf

4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrwEIJllpyw.ttf

22 ms

activeview

activeview

72 ms

KV3D6fBnFTiXbIv-4-1-itQxPECiOLE_JpSNKJs5lP8.js

KV3D6fBnFTiXbIv-4-1-itQxPECiOLE_JpSNKJs5lP8.js

5 ms

feedback_grey600_24dp.png

feedback_grey600_24dp.png

22 ms

fullscreen_api_adapter.js

fullscreen_api_adapter.js

11 ms

interstitial_ad_frame.js

interstitial_ad_frame.js

57 ms

settings_grey600_24dp.png

settings_grey600_24dp.png

56 ms

ff6b8413ccec2e2686fe44d6d4a2e9d1.js

ff6b8413ccec2e2686fe44d6d4a2e9d1.js

15 ms

cookie_push_onload.html

cookie_push_onload.html

134 ms

sn.ashx

sn.ashx

44 ms

pixel

pixel

36 ms

pixel

pixel

34 ms

pixel

pixel

33 ms

pixel

pixel

33 ms

activeview

activeview

87 ms

pixel

pixel

15 ms

sodar

sodar

70 ms

sodar2.js

sodar2.js

5 ms

runner.html

runner.html

5 ms

aframe

aframe

28 ms

pixel

pixel

32 ms

Accessibility Review

metaldating.dk accessibility score

82

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

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

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

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

metaldating.dk SEO score

82

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

Links do not have descriptive text

High

Image elements do not have [alt] attributes

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

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

metaldating.dk

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