Tools & Wizards About Us
next-level-berlin.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

next-level-berlin.com

Page Load Speed

5.4 sec in total

First Response

1.6 sec

Resources Loaded

3.6 sec

Page Rendered

174 ms

next-level-berlin.com screenshot

About Website

Click here to check amazing Next Level Berlin content. Otherwise, check out these important facts you probably never knew about next-level-berlin.com

Visit next-level-berlin.com

Key Findings

We analyzed Next-level-berlin.com page load time and found that the first response time was 1.6 sec and then it took 3.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

next-level-berlin.com performance score

0

Network Requests Diagram

www.next-level-berlin.com

1582 ms

style.css

324 ms

fancybox-1.3.4.css

244 ms

css

23 ms

styles.css

232 ms

Our browser made a total of 39 requests to load all elements on the main page. We found that 74% of them (29 requests) were addressed to the original Next-level-berlin.com, 10% (4 requests) were made to Google-analytics.com and 5% (2 requests) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Next-level-berlin.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 322.8 kB (56%)

Content Size

572.5 kB

After Optimization

249.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Next-level-berlin.com main page is 572.5 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. 30% of websites need less resources to load. Javascripts take 346.3 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 36.0 kB

  • Original 44.7 kB
  • After minification 37.2 kB
  • After compression 8.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. This page needs HTML code to be minified as it can gain 7.4 kB, which is 17% 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 36.0 kB or 81% of the original size.

Image Optimization

-24%

Potential reduce by 35.1 kB

  • Original 146.1 kB
  • After minification 111.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. Obviously, Next Level Berlin needs image optimization as it can save up to 35.1 kB or 24% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-64%

Potential reduce by 222.6 kB

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

CSS Optimization

-82%

Potential reduce by 29.1 kB

  • Original 35.4 kB
  • After minification 28.4 kB
  • After compression 6.3 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. Next-level-berlin.com needs all CSS files to be minified and compressed as it can save up to 29.1 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 29 (76%)

Requests Now

38

After Optimization

9

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.next-level-berlin.com

www.next-level-berlin.com

1582 ms

style.css

style.css

324 ms

fancybox-1.3.4.css

fancybox-1.3.4.css

244 ms

css

css

23 ms

styles.css

styles.css

232 ms

jquery-ui.min.css

jquery-ui.min.css

18 ms

jquery-ui-timepicker-addon.min.css

jquery-ui-timepicker-addon.min.css

235 ms

jquery.js

jquery.js

612 ms

jquery-migrate.min.js

jquery-migrate.min.js

347 ms

jquery.fancybox-1.3.4.js

jquery.fancybox-1.3.4.js

347 ms

theme.js

theme.js

346 ms

comment-reply.min.js

comment-reply.min.js

212 ms

jquery.form.min.js

jquery.form.min.js

282 ms

scripts.js

scripts.js

290 ms

jquery.ui.core.min.js

jquery.ui.core.min.js

296 ms

jquery.ui.datepicker.min.js

jquery.ui.datepicker.min.js

394 ms

jquery.ui.datepicker-de.min.js

jquery.ui.datepicker-de.min.js

10 ms

jquery-ui-timepicker-addon.min.js

jquery-ui-timepicker-addon.min.js

415 ms

jquery-ui-timepicker-de.js

jquery-ui-timepicker-de.js

389 ms

jquery.ui.widget.min.js

jquery.ui.widget.min.js

394 ms

jquery.ui.mouse.min.js

jquery.ui.mouse.min.js

400 ms

jquery.ui.slider.min.js

jquery.ui.slider.min.js

502 ms

jquery.ui.button.min.js

jquery.ui.button.min.js

504 ms

jquery-ui-sliderAccess.js

jquery-ui-sliderAccess.js

505 ms

analytics.js

analytics.js

17 ms

collect

collect

45 ms

ga.js

ga.js

28 ms

bg.jpg

bg.jpg

323 ms

logo.png

logo.png

119 ms

icon-phone-white.png

icon-phone-white.png

121 ms

logos.png

logos.png

210 ms

icon-facebook.png

icon-facebook.png

121 ms

icon-twitter.png

icon-twitter.png

124 ms

icon-soundcloud.png

icon-soundcloud.png

228 ms

ajax-loader.gif

ajax-loader.gif

176 ms

__utm.gif

__utm.gif

13 ms

like.php

like.php

140 ms

qeKvIRsJabD.js

qeKvIRsJabD.js

140 ms

LVx-xkvaJ0b.png

LVx-xkvaJ0b.png

155 ms

SEO Factors

next-level-berlin.com SEO score

0

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    DE

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Next-level-berlin.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is German. Our system also found out that Next-level-berlin.com 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

next-level-berlin.com

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