Tools & Wizards About Us
future3000.eu screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

future3000.eu

B-Line - kompletní sortiment podlahových krytin

Page Load Speed

2.5 sec in total

First Response

265 ms

Resources Loaded

2 sec

Page Rendered

277 ms

future3000.eu screenshot

About Website

Visit future3000.eu now to see the best up-to-date Future 3000 content and also check out these interesting facts you probably never knew about future3000.eu

B - line značka kvalitních podlahových krytin, kterou naleznete v široké síťi prodejen po celé České republice

Visit future3000.eu

Key Findings

We analyzed Future3000.eu page load time and found that the first response time was 265 ms and then it took 2.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

future3000.eu performance score

0

Network Requests Diagram

future3000.eu

265 ms

bootstrap.css

222 ms

font-awesome.css

218 ms

flexslider.css

220 ms

prettyPhoto.css

236 ms

Our browser made a total of 58 requests to load all elements on the main page. We found that 91% of them (53 requests) were addressed to the original Future3000.eu, 5% (3 requests) were made to Fonts.googleapis.com and 2% (1 request) were made to Maps.google.com. The less responsive or slowest element that took the longest time to load (776 ms) belongs to the original domain Future3000.eu.

Page Optimization Overview & Recommendations

Page size can be reduced by 712.3 kB (42%)

Content Size

1.7 MB

After Optimization

980.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Future3000.eu main page is 1.7 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. 55% of websites need less resources to load. Images take 852.1 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 32.2 kB

  • Original 40.3 kB
  • After minification 33.7 kB
  • After compression 8.1 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 6.7 kB, which is 16% 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 32.2 kB or 80% of the original size.

Image Optimization

-5%

Potential reduce by 42.3 kB

  • Original 852.1 kB
  • After minification 809.8 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. Future 3000 images are well optimized though.

JavaScript Optimization

-75%

Potential reduce by 320.1 kB

  • Original 426.6 kB
  • After minification 340.8 kB
  • After compression 106.5 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 320.1 kB or 75% of the original size.

CSS Optimization

-85%

Potential reduce by 317.7 kB

  • Original 374.1 kB
  • After minification 322.6 kB
  • After compression 56.4 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. Future3000.eu needs all CSS files to be minified and compressed as it can save up to 317.7 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 27 (49%)

Requests Now

55

After Optimization

28

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

future3000.eu

future3000.eu

265 ms

bootstrap.css

bootstrap.css

222 ms

font-awesome.css

font-awesome.css

218 ms

flexslider.css

flexslider.css

220 ms

prettyPhoto.css

prettyPhoto.css

236 ms

component.css

component.css

233 ms

magnific-popup.css

magnific-popup.css

236 ms

jquery.isotope.css

jquery.isotope.css

324 ms

theme.css

theme.css

325 ms

drupal-styles.css

drupal-styles.css

330 ms

theme-elements.css

theme-elements.css

332 ms

theme-animate.css

theme-animate.css

336 ms

theme-blog.css

theme-blog.css

337 ms

bootstrap-responsive.css

bootstrap-responsive.css

433 ms

theme-responsive.css

theme-responsive.css

436 ms

css_pbm0lsQQJ7A7WCCIMgxLho6mI_kBNgznNUWmTWcnfoE.css

css_pbm0lsQQJ7A7WCCIMgxLho6mI_kBNgznNUWmTWcnfoE.css

436 ms

css_TsVRTbLFUpEZAfw-_bWPJu840QT523CPjUVJ5MRWfyk.css

css_TsVRTbLFUpEZAfw-_bWPJu840QT523CPjUVJ5MRWfyk.css

439 ms

css_6OD8o33e-znEI6roxfGV6FLFzfEPjjBBAB_1DPchIW4.css

css_6OD8o33e-znEI6roxfGV6FLFzfEPjjBBAB_1DPchIW4.css

441 ms

css

css

26 ms

css_RoMI2lxDG6i5LtH6x7Bkvz2CW8Ux8fIzDF78XHjYj2k.css

css_RoMI2lxDG6i5LtH6x7Bkvz2CW8Ux8fIzDF78XHjYj2k.css

444 ms

css

css

38 ms

css_AbpHGcgLb-kRsJGnwFEktk7uzpZOCcBY74-YBdrKVGs.css

css_AbpHGcgLb-kRsJGnwFEktk7uzpZOCcBY74-YBdrKVGs.css

537 ms

skin.less

skin.less

556 ms

js_YG98FuAkznGpfUVD7la3EObWLhNr4zOIqZcdXzZxHVI.js

js_YG98FuAkznGpfUVD7la3EObWLhNr4zOIqZcdXzZxHVI.js

651 ms

js_x3gIHn41cMHAjzm8Jp9wCcn8sJkqEhvRUG3vJnJH2Dc.js

js_x3gIHn41cMHAjzm8Jp9wCcn8sJkqEhvRUG3vJnJH2Dc.js

548 ms

js_AUkbGY-9JqbVUmeK4EcleSENFcMzfZXgEnxNqXgeN-A.js

js_AUkbGY-9JqbVUmeK4EcleSENFcMzfZXgEnxNqXgeN-A.js

672 ms

js_NQ837YE39AlUfIC4c0RYGa5uvLXSyiY4xXKaXU16rPo.js

js_NQ837YE39AlUfIC4c0RYGa5uvLXSyiY4xXKaXU16rPo.js

769 ms

css

css

44 ms

js

js

22 ms

sticky.js

sticky.js

644 ms

modernizr.js

modernizr.js

670 ms

index_0.png

index_0.png

117 ms

slide-bg.jpg

slide-bg.jpg

429 ms

png-1_0.png

png-1_0.png

111 ms

slide-concept-2-1.png

slide-concept-2-1.png

219 ms

slide-concept-2-2.png

slide-concept-2-2.png

117 ms

slide-concept-2-3.png

slide-concept-2-3.png

121 ms

slide-concept-2-4.png

slide-concept-2-4.png

125 ms

slide-concept-2-5.png

slide-concept-2-5.png

329 ms

slide-concept.png

slide-concept.png

442 ms

logo-1-slide.png

logo-1-slide.png

229 ms

home-concept.png

home-concept.png

236 ms

home-concept-icons.png

home-concept-icons.png

328 ms

home-concept-item.png

home-concept-item.png

339 ms

home-concept-item-1.png

home-concept-item-1.png

452 ms

home-concept-item-2.png

home-concept-item-2.png

541 ms

home-concept-item-3.png

home-concept-item-3.png

441 ms

project-home-3.jpg

project-home-3.jpg

557 ms

project-home-1.jpg

project-home-1.jpg

640 ms

project-home-2.jpg

project-home-2.jpg

692 ms

project-home-4.jpg

project-home-4.jpg

659 ms

project-home-6.jpg

project-home-6.jpg

670 ms

project-home-5.jpg

project-home-5.jpg

755 ms

divider.png

divider.png

665 ms

logo-footer.png

logo-footer.png

750 ms

md-arrow.png

md-arrow.png

768 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

776 ms

clhLqOv7MXn459PTh0gXYBayoCksK7A5ZWkzVNukUdQ.ttf

clhLqOv7MXn459PTh0gXYBayoCksK7A5ZWkzVNukUdQ.ttf

4 ms

SEO Factors

future3000.eu SEO score

0

Language and Encoding

  • Language Detected

    CS

  • Language Claimed

    CS

  • Encoding

    UTF-8

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

future3000.eu

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