Tools & Wizards About Us
dot.fm screenshot

Report Summary

  • 76

    Performance

    Renders faster than
    84% of other websites

  • 60

    Accessibility

    Visual factors better than
    that of 26% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

dot.fm

dotFM - Official .FM Top-Level Domain Registry

Page Load Speed

1.9 sec in total

First Response

300 ms

Resources Loaded

1.5 sec

Page Rendered

130 ms

dot.fm screenshot

About Website

Click here to check amazing Dot content for United States. Otherwise, check out these important facts you probably never knew about dot.fm

Imagining, the Next Big Thing? Get a .FM Top-Level Domain!

Visit dot.fm

Key Findings

We analyzed Dot.fm page load time and found that the first response time was 300 ms and then it took 1.6 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

dot.fm performance score

76

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

40/100

10%

LCP (Largest Contentful Paint)

Value4.4 s

40/100

25%

SI (Speed Index)

Value3.3 s

90/100

10%

TBT (Total Blocking Time)

Value100 ms

98/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value4.4 s

84/100

10%

Network Requests Diagram

dot.fm

300 ms

sdk.js

63 ms

style.css

114 ms

jquery.js

227 ms

styles.css

218 ms

Our browser made a total of 49 requests to load all elements on the main page. We found that 53% of them (26 requests) were addressed to the original Dot.fm, 6% (3 requests) were made to Connect.facebook.net and 6% (3 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (618 ms) belongs to the original domain Dot.fm.

Page Optimization Overview & Recommendations

Page size can be reduced by 291.9 kB (57%)

Content Size

515.9 kB

After Optimization

224.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Dot.fm main page is 515.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 292.5 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 38.5 kB

  • Original 48.6 kB
  • After minification 47.6 kB
  • After compression 10.0 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 38.5 kB or 79% of the original size.

Image Optimization

-27%

Potential reduce by 39.7 kB

  • Original 145.8 kB
  • After minification 106.2 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. Obviously, Dot needs image optimization as it can save up to 39.7 kB or 27% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-65%

Potential reduce by 190.2 kB

  • Original 292.5 kB
  • After minification 249.9 kB
  • After compression 102.3 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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 190.2 kB or 65% of the original size.

CSS Optimization

-81%

Potential reduce by 23.5 kB

  • Original 29.0 kB
  • After minification 23.0 kB
  • After compression 5.5 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. Dot.fm needs all CSS files to be minified and compressed as it can save up to 23.5 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 24 (52%)

Requests Now

46

After Optimization

22

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

dot.fm

dot.fm

300 ms

sdk.js

sdk.js

63 ms

style.css

style.css

114 ms

jquery.js

jquery.js

227 ms

styles.css

styles.css

218 ms

jquery.min.js

jquery.min.js

49 ms

js

js

111 ms

js

js

126 ms

element.js

element.js

108 ms

bootstrap.min.css

bootstrap.min.css

68 ms

font-awesome.min.css

font-awesome.min.css

108 ms

emoji.css

emoji.css

217 ms

dotfmlogo25yrs.png

dotfmlogo25yrs.png

287 ms

ib_facebook.png

ib_facebook.png

245 ms

ib_instagram.png

ib_instagram.png

246 ms

ib_x.png

ib_x.png

284 ms

ib_tiktok.png

ib_tiktok.png

285 ms

ib_pinterest.png

ib_pinterest.png

286 ms

ib_linkedin.png

ib_linkedin.png

463 ms

ib_youtube.png

ib_youtube.png

462 ms

ib_tumblr.png

ib_tumblr.png

464 ms

ib_lastfm.png

ib_lastfm.png

464 ms

ib_paypal.png

ib_paypal.png

465 ms

hp_imagining.png

hp_imagining.png

465 ms

jquery-1.11.3.min.js

jquery-1.11.3.min.js

59 ms

config.js

config.js

618 ms

util.js

util.js

419 ms

jquery.emojiarea.js

jquery.emojiarea.js

421 ms

emoji-picker.js

emoji-picker.js

420 ms

HPPreOrder2022.png

HPPreOrder2022.png

423 ms

cc_bitpay2022.png

cc_bitpay2022.png

420 ms

sdk.js

sdk.js

18 ms

css

css

42 ms

oct.js

oct.js

30 ms

css

css

19 ms

css

css

24 ms

gtm.js

gtm.js

186 ms

fbevents.js

fbevents.js

9 ms

uwt.js

uwt.js

8 ms

searchD.cfm

searchD.cfm

157 ms

ajax_framework.js

ajax_framework.js

187 ms

h0GsssGg9FxgDgCjLeAd7hjYx-s.ttf

h0GsssGg9FxgDgCjLeAd7hjYx-s.ttf

313 ms

530423000000319069

530423000000319069

430 ms

blank.gif

blank.gif

74 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

29 ms

adsct

adsct

152 ms

adsct

adsct

92 ms

adsct

adsct

112 ms

adsct

adsct

170 ms

Accessibility Review

dot.fm accessibility score

60

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

dot.fm 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

dot.fm SEO score

92

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

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

    UTF-8

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

dot.fm

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