Tools & Wizards About Us
dinamo.fm screenshot

Report Summary

  • 34

    Performance

    Renders faster than
    54% of other websites

  • 32

    Accessibility

    Visual factors better than
    that of 18% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 80

    SEO

    Google-friendlier than
    42% of websites

dinamo.fm

dinamo.fm

Page Load Speed

3.1 sec in total

First Response

180 ms

Resources Loaded

2.7 sec

Page Rendered

159 ms

dinamo.fm screenshot

About Website

Visit dinamo.fm now to see the best up-to-date Dinamo content for Turkey and also check out these interesting facts you probably never knew about dinamo.fm

Official website of Istanbul's premier electronic/indie radio station.

Visit dinamo.fm

Key Findings

We analyzed Dinamo.fm page load time and found that the first response time was 180 ms and then it took 2.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

dinamo.fm performance score

34

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value9.6 s

0/100

10%

LCP (Largest Contentful Paint)

Value20.1 s

0/100

25%

SI (Speed Index)

Value14.6 s

1/100

10%

TBT (Total Blocking Time)

Value440 ms

64/100

30%

CLS (Cumulative Layout Shift)

Value0.052

98/100

15%

TTI (Time to Interactive)

Value19.1 s

3/100

10%

Network Requests Diagram

dinamo.fm

180 ms

default.aspx

570 ms

css

41 ms

css

58 ms

css

61 ms

Our browser made a total of 74 requests to load all elements on the main page. We found that 78% of them (58 requests) were addressed to the original Dinamo.fm, 4% (3 requests) were made to Fonts.googleapis.com and 4% (3 requests) were made to Connect.facebook.net. The less responsive or slowest element that took the longest time to load (813 ms) belongs to the original domain Dinamo.fm.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.2 MB (47%)

Content Size

2.5 MB

After Optimization

1.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Dinamo.fm main page is 2.5 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 65% of websites need less resources to load. Javascripts take 1.0 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 43.5 kB

  • Original 53.4 kB
  • After minification 40.0 kB
  • After compression 9.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. This page needs HTML code to be minified as it can gain 13.4 kB, which is 25% 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 43.5 kB or 81% of the original size.

Image Optimization

-7%

Potential reduce by 70.9 kB

  • Original 1.0 MB
  • After minification 941.0 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. Dinamo images are well optimized though.

JavaScript Optimization

-69%

Potential reduce by 726.0 kB

  • Original 1.0 MB
  • After minification 894.5 kB
  • After compression 318.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 726.0 kB or 69% of the original size.

CSS Optimization

-87%

Potential reduce by 319.9 kB

  • Original 369.6 kB
  • After minification 273.7 kB
  • After compression 49.6 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. Dinamo.fm needs all CSS files to be minified and compressed as it can save up to 319.9 kB or 87% of the original size.

Requests Breakdown

Number of requests can be reduced by 26 (39%)

Requests Now

67

After Optimization

41

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

dinamo.fm

dinamo.fm

180 ms

default.aspx

default.aspx

570 ms

css

css

41 ms

css

css

58 ms

css

css

61 ms

animate.css

animate.css

246 ms

style-opensansm.css

style-opensansm.css

626 ms

main.css

main.css

407 ms

font-icons.css

font-icons.css

561 ms

magnific-popup.css

magnific-popup.css

334 ms

responsive.css

responsive.css

500 ms

jquery.js

jquery.js

613 ms

plugins.js

plugins.js

813 ms

jquery.lava.js

jquery.lava.js

487 ms

plugins.js

plugins.js

728 ms

js

js

58 ms

jquery.gmap.js

jquery.gmap.js

578 ms

js

js

58 ms

custom.js

custom.js

572 ms

main_ssl.js

main_ssl.js

584 ms

register.js

register.js

624 ms

widgets.js

widgets.js

90 ms

fp.js

fp.js

100 ms

analytics.js

analytics.js

229 ms

logo.png

logo.png

208 ms

logo-text.png

logo-text.png

206 ms

logo@2x.png

logo@2x.png

209 ms

logo-text@2x.png

logo-text@2x.png

207 ms

preloader.gif

preloader.gif

207 ms

slider5.jpg

slider5.jpg

212 ms

slider1.png

slider1.png

348 ms

itunes-big.png

itunes-big.png

210 ms

right-arrow.png

right-arrow.png

210 ms

legacy.jpg

legacy.jpg

211 ms

pop-icon.png

pop-icon.png

213 ms

amazon.png

amazon.png

295 ms

apple.png

apple.png

295 ms

lastfm.png

lastfm.png

295 ms

facebook-icon.png

facebook-icon.png

296 ms

twitter-icon.png

twitter-icon.png

298 ms

player-sprite.png

player-sprite.png

347 ms

201427102436_dinamofm_bluelogo.jpg

201427102436_dinamofm_bluelogo.jpg

348 ms

201427102732_caffe.jpg

201427102732_caffe.jpg

348 ms

201427102642_deep.jpg

201427102642_deep.jpg

349 ms

201417718320_disco.jpg

201417718320_disco.jpg

384 ms

202023715431_dinamofm_fluentweb.jpg

202023715431_dinamofm_fluentweb.jpg

414 ms

201417718242_loco.jpg

201417718242_loco.jpg

413 ms

2016151021421_mm_radyo.jpg

2016151021421_mm_radyo.jpg

488 ms

20142710269_sleep.jpg

20142710269_sleep.jpg

417 ms

20142710278_smog.jpg

20142710278_smog.jpg

417 ms

widget.js

widget.js

396 ms

all.js

all.js

124 ms

trackdisplay.html

trackdisplay.html

299 ms

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

94 ms

volume-drag.png

volume-drag.png

288 ms

player-sprite2.png

player-sprite2.png

295 ms

font

font

44 ms

font

font

49 ms

helveticaneue-webfont.woff

helveticaneue-webfont.woff

234 ms

icomoon.woff

icomoon.woff

562 ms

helveticaneueltcombd.woff

helveticaneueltcombd.woff

300 ms

collect

collect

72 ms

all.js

all.js

33 ms

settings

settings

118 ms

js

js

42 ms

cryptodonate.css

cryptodonate.css

88 ms

cryptodonate.js

cryptodonate.js

104 ms

timthumb.php

timthumb.php

558 ms

helveticaneue-light-webfont.woff

helveticaneue-light-webfont.woff

90 ms

right-arrow-filled.png

right-arrow-filled.png

81 ms

icon_bitcoin.png

icon_bitcoin.png

78 ms

wallet.png

wallet.png

79 ms

retina.css

retina.css

83 ms

flex-arrow.png

flex-arrow.png

81 ms

Accessibility Review

dinamo.fm accessibility score

32

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

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

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.

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

dinamo.fm best practices score

67

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

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

dinamo.fm SEO score

80

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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

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 Dinamo.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 Dinamo.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

dinamo.fm

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