Tools & Wizards About Us
wml.link screenshot

Report Summary

  • 38

    Performance

    Renders faster than
    57% of other websites

  • 95

    Accessibility

    Visual factors better than
    that of 86% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

wml.link

Smart links for music marketing, artist promotion, and fan engagement | Linkfire

Page Load Speed

2 sec in total

First Response

31 ms

Resources Loaded

1.5 sec

Page Rendered

490 ms

wml.link screenshot

About Website

Visit wml.link now to see the best up-to-date Wml content and also check out these interesting facts you probably never knew about wml.link

Smart links for music marketing. From your first single to your first world tour, Linkfire simplifies your artist promotion every step of the way. Trusted by major labels and over 50k artists.

Visit wml.link

Key Findings

We analyzed Wml.link page load time and found that the first response time was 31 ms and then it took 2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.

Performance Metrics

wml.link performance score

38

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.5 s

35/100

10%

LCP (Largest Contentful Paint)

Value5.6 s

18/100

25%

SI (Speed Index)

Value5.3 s

58/100

10%

TBT (Total Blocking Time)

Value900 ms

31/100

30%

CLS (Cumulative Layout Shift)

Value0.161

72/100

15%

TTI (Time to Interactive)

Value7.9 s

44/100

10%

Network Requests Diagram

wml.link

31 ms

www.linkfire.com

488 ms

pwr.min.css

137 ms

pwr-burger.min.css

242 ms

scroll-shadow.min.css

340 ms

Our browser made a total of 36 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Wml.link, 61% (22 requests) were made to Linkfire.com and 8% (3 requests) were made to Cdn.cookielaw.org. The less responsive or slowest element that took the longest time to load (585 ms) relates to the external source Linkfire.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 144.2 kB (33%)

Content Size

432.8 kB

After Optimization

288.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Wml.link main page is 432.8 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. 25% of websites need less resources to load. Javascripts take 242.8 kB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 129.8 kB

  • Original 151.5 kB
  • After minification 143.0 kB
  • After compression 21.6 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 129.8 kB or 86% of the original size.

Image Optimization

-4%

Potential reduce by 343 B

  • Original 9.7 kB
  • After minification 9.3 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. Wml images are well optimized though.

JavaScript Optimization

-3%

Potential reduce by 7.2 kB

  • Original 242.8 kB
  • After minification 242.8 kB
  • After compression 235.6 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

-24%

Potential reduce by 6.8 kB

  • Original 28.9 kB
  • After minification 28.9 kB
  • After compression 22.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. Wml.link needs all CSS files to be minified and compressed as it can save up to 6.8 kB or 24% of the original size.

Requests Breakdown

Number of requests can be reduced by 23 (77%)

Requests Now

30

After Optimization

7

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

wml.link

wml.link

31 ms

www.linkfire.com

www.linkfire.com

488 ms

pwr.min.css

pwr.min.css

137 ms

pwr-burger.min.css

pwr-burger.min.css

242 ms

scroll-shadow.min.css

scroll-shadow.min.css

340 ms

module_50162273254_CTA_Section_2022_Custom.min.css

module_50162273254_CTA_Section_2022_Custom.min.css

347 ms

otSDKStub.js

otSDKStub.js

30 ms

jquery-1.11.2.js

jquery-1.11.2.js

412 ms

embed.js

embed.js

31 ms

pwr.min.js

pwr.min.js

410 ms

child.min.js

child.min.js

411 ms

project.js

project.js

422 ms

pwr-burger.min.js

pwr-burger.min.js

428 ms

scroll-shadow.min.js

scroll-shadow.min.js

437 ms

project.js

project.js

453 ms

Typewriter.min.js

Typewriter.min.js

516 ms

pwr-heights.min.js

pwr-heights.min.js

511 ms

_swiper-bundle.min.js

_swiper-bundle.min.js

553 ms

pwr-swiper.min.js

pwr-swiper.min.js

526 ms

25446013.js

25446013.js

432 ms

index.js

index.js

547 ms

js.cookie.js

js.cookie.js

585 ms

6730c662-ee4e-4224-b51d-0768adc92afe.json

6730c662-ee4e-4224-b51d-0768adc92afe.json

86 ms

gtm.js

gtm.js

91 ms

stat.js

stat.js

94 ms

Linkfire%20smart%20links%20home%20page%20hero.png

Linkfire%20smart%20links%20home%20page%20hero.png

502 ms

linkfire-logo-dark.svg

linkfire-logo-dark.svg

283 ms

arrow-right-black.svg

arrow-right-black.svg

564 ms

regular.woff

regular.woff

256 ms

500.woff

500.woff

302 ms

700.woff

700.woff

302 ms

location

location

36 ms

collectedforms.js

collectedforms.js

453 ms

banner.js

banner.js

454 ms

25446013.js

25446013.js

476 ms

otBannerSdk.js

otBannerSdk.js

16 ms

Accessibility Review

wml.link accessibility score

95

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Links do not have a discernible name

Best Practices

wml.link 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

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

wml.link SEO score

93

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

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

    EN

  • Encoding

    UTF-8

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

wml.link

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