Tools & Wizards About Us
bigmouth.nl screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

bigmouth.nl

BigMouth Music

Page Load Speed

3.4 sec in total

First Response

453 ms

Resources Loaded

2.7 sec

Page Rendered

283 ms

bigmouth.nl screenshot

About Website

Visit bigmouth.nl now to see the best up-to-date Big Mouth content and also check out these interesting facts you probably never knew about bigmouth.nl

Visit bigmouth.nl

Key Findings

We analyzed Bigmouth.nl page load time and found that the first response time was 453 ms and then it took 3 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

bigmouth.nl performance score

0

Network Requests Diagram

bigmouth.nl

453 ms

www.bigmouth.nl

781 ms

style.css

183 ms

jquery.min.js

9 ms

fullwidthAudioPlayer-tracks.css

203 ms

Our browser made a total of 28 requests to load all elements on the main page. We found that 75% of them (21 requests) were addressed to the original Bigmouth.nl, 7% (2 requests) were made to Connect.soundcloud.com and 7% (2 requests) were made to Mobile.twitter.com. The less responsive or slowest element that took the longest time to load (781 ms) belongs to the original domain Bigmouth.nl.

Page Optimization Overview & Recommendations

Page size can be reduced by 250.7 kB (29%)

Content Size

874.1 kB

After Optimization

623.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Bigmouth.nl main page is 874.1 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. Images take 520.3 kB which makes up the majority of the site volume.

HTML Optimization

-72%

Potential reduce by 11.0 kB

  • Original 15.4 kB
  • After minification 14.3 kB
  • After compression 4.4 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 11.0 kB or 72% of the original size.

Image Optimization

-2%

Potential reduce by 8.8 kB

  • Original 520.3 kB
  • After minification 511.6 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. Big Mouth images are well optimized though.

JavaScript Optimization

-68%

Potential reduce by 222.3 kB

  • Original 326.7 kB
  • After minification 326.6 kB
  • After compression 104.4 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 222.3 kB or 68% of the original size.

CSS Optimization

-74%

Potential reduce by 8.7 kB

  • Original 11.7 kB
  • After minification 9.3 kB
  • After compression 3.0 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. Bigmouth.nl needs all CSS files to be minified and compressed as it can save up to 8.7 kB or 74% of the original size.

Requests Breakdown

Number of requests can be reduced by 12 (50%)

Requests Now

24

After Optimization

12

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

bigmouth.nl

bigmouth.nl

453 ms

www.bigmouth.nl

www.bigmouth.nl

781 ms

style.css

style.css

183 ms

jquery.min.js

jquery.min.js

9 ms

fullwidthAudioPlayer-tracks.css

fullwidthAudioPlayer-tracks.css

203 ms

jquery.fullwidthAudioPlayer.css

jquery.fullwidthAudioPlayer.css

241 ms

sdk.js

sdk.js

137 ms

jquery.js

jquery.js

496 ms

jquery.ui.core.min.js

jquery.ui.core.min.js

212 ms

jquery.ui.widget.min.js

jquery.ui.widget.min.js

210 ms

jquery.ui.mouse.min.js

jquery.ui.mouse.min.js

354 ms

jquery.ui.draggable.min.js

jquery.ui.draggable.min.js

452 ms

jquery.ui.sortable.min.js

jquery.ui.sortable.min.js

475 ms

jquery.fullwidthAudioPlayer.min.js

jquery.fullwidthAudioPlayer.min.js

691 ms

ytprefs.min.js

ytprefs.min.js

428 ms

blogger.js

blogger.js

125 ms

Bigmouthmusic.json

Bigmouthmusic.json

114 ms

iframe_api

iframe_api

30 ms

background.jpg

background.jpg

778 ms

header.png

header.png

390 ms

top_content.png

top_content.png

210 ms

studio.jpg

studio.jpg

392 ms

bottom_content.png

bottom_content.png

213 ms

audio.png

audio.png

211 ms

sidebar_bottom.png

sidebar_bottom.png

388 ms

news.png

news.png

397 ms

www-widgetapi.js

www-widgetapi.js

15 ms

soundmanager2.js

soundmanager2.js

57 ms

SEO Factors

bigmouth.nl SEO score

0

Language and Encoding

  • Language Detected

    NL

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

bigmouth.nl

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