Report Summary

  • 34

    Performance

    Renders faster than
    54% of other websites

  • 67

    Accessibility

    Visual factors better than
    that of 32% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 85

    SEO

    Google-friendlier than
    56% of websites

rockfon.be

Akoestische plafond- en wandoplossingen | Rockfon

Page Load Speed

3.1 sec in total

First Response

246 ms

Resources Loaded

2.7 sec

Page Rendered

151 ms

rockfon.be screenshot

About Website

Visit rockfon.be now to see the best up-to-date Rockfon content and also check out these interesting facts you probably never knew about rockfon.be

Creëer prachtige en comfortabele ruimtes met een optimaal binnenklimaat dankzij het ruime assortiment akoestische plafond- en wandpanelen van Rockfon.

Visit rockfon.be

Key Findings

We analyzed Rockfon.be page load time and found that the first response time was 246 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 50% of websites can load faster. This domain responded with an error, which can significantly jeopardize Rockfon.be rating and web reputation

Performance Metrics

rockfon.be performance score

34

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.1 s

22/100

10%

LCP (Largest Contentful Paint)

Value7.0 s

6/100

25%

SI (Speed Index)

Value10.0 s

9/100

10%

TBT (Total Blocking Time)

Value710 ms

42/100

30%

CLS (Cumulative Layout Shift)

Value0.019

100/100

15%

TTI (Time to Interactive)

Value12.4 s

15/100

10%

Network Requests Diagram

rockfon.be

246 ms

www.rockfon.be

420 ms

bootstrap.css

369 ms

bootstrap-responsive.css

367 ms

jquery.fancybox.css

306 ms

Our browser made a total of 33 requests to load all elements on the main page. We found that 88% of them (29 requests) were addressed to the original Rockfon.be, 6% (2 requests) were made to Rockfon.eu and 6% (2 requests) were made to Rfn-gmcdb.inforce.dk. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Rockfon.be.

Page Optimization Overview & Recommendations

Page size can be reduced by 584.5 kB (79%)

Content Size

737.1 kB

After Optimization

152.7 kB

In fact, the total size of Rockfon.be main page is 737.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. 20% of websites need less resources to load. CSS take 371.3 kB which makes up the majority of the site volume.

HTML Optimization

-72%

Potential reduce by 13.8 kB

  • Original 19.1 kB
  • After minification 16.9 kB
  • After compression 5.3 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 2.2 kB, which is 11% 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 13.8 kB or 72% of the original size.

Image Optimization

-39%

Potential reduce by 7.5 kB

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

JavaScript Optimization

-75%

Potential reduce by 246.4 kB

  • Original 327.7 kB
  • After minification 276.5 kB
  • After compression 81.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 246.4 kB or 75% of the original size.

CSS Optimization

-85%

Potential reduce by 316.8 kB

  • Original 371.3 kB
  • After minification 291.8 kB
  • After compression 54.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. Rockfon.be needs all CSS files to be minified and compressed as it can save up to 316.8 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 15 (58%)

Requests Now

26

After Optimization

11

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

Accessibility Review

rockfon.be accessibility score

67

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

ARIA input fields do not have accessible names

High

ARIA IDs are not unique

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

Form elements do not have associated labels

High

Links do not have a discernible name

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

rockfon.be best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

rockfon.be SEO score

85

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

    NL

  • Language Claimed

    BE

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Rockfon.be 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 Byelorussian language. Our system also found out that Rockfon.be 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

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