Report Summary

  • 33

    Performance

    Renders faster than
    53% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 71% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

brunner.nl

HOME - BRUNNER - Brunner - Brunner Projektmeubelen B.V. - Brunner

Page Load Speed

2.9 sec in total

First Response

383 ms

Resources Loaded

2.4 sec

Page Rendered

138 ms

About Website

Click here to check amazing Brunner content. Otherwise, check out these important facts you probably never knew about brunner.nl

Bij Brunner ligt de focus op projectmeubelen voor Zakelijke Ondernemingen en Hospitality, Beurs- & Congrescentra, maar ook voor de vakgebieden (Ouderen) Zorg, Onderwijs en Publieke Sector.

Visit brunner.nl

Key Findings

We analyzed Brunner.nl page load time and found that the first response time was 383 ms and then it took 2.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

brunner.nl performance score

33

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.7 s

5/100

10%

LCP (Largest Contentful Paint)

Value10.5 s

0/100

25%

SI (Speed Index)

Value7.4 s

28/100

10%

TBT (Total Blocking Time)

Value740 ms

40/100

30%

CLS (Cumulative Layout Shift)

Value0.003

100/100

15%

TTI (Time to Interactive)

Value10.2 s

25/100

10%

Network Requests Diagram

brunner.nl

383 ms

brunner.nl

391 ms

www.brunner.nl

691 ms

bootstrap.css

198 ms

style.css

284 ms

Our browser made a total of 39 requests to load all elements on the main page. We found that 90% of them (35 requests) were addressed to the original Brunner.nl, 3% (1 request) were made to Google.com and 3% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (691 ms) belongs to the original domain Brunner.nl.

Page Optimization Overview & Recommendations

Page size can be reduced by 22.5 kB (4%)

Content Size

564.1 kB

After Optimization

541.6 kB

In fact, the total size of Brunner.nl main page is 564.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. Javascripts take 291.9 kB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 12.0 kB

  • Original 16.1 kB
  • After minification 14.3 kB
  • After compression 4.2 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 1.8 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 12.0 kB or 74% of the original size.

Image Optimization

-2%

Potential reduce by 4.1 kB

  • Original 213.5 kB
  • After minification 209.4 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. Brunner images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 1.3 kB

  • Original 291.9 kB
  • After minification 291.9 kB
  • After compression 290.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. This website has mostly compressed JavaScripts.

CSS Optimization

-12%

Potential reduce by 5.2 kB

  • Original 42.5 kB
  • After minification 42.5 kB
  • After compression 37.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. Brunner.nl needs all CSS files to be minified and compressed as it can save up to 5.2 kB or 12% of the original size.

Requests Breakdown

Number of requests can be reduced by 17 (53%)

Requests Now

32

After Optimization

15

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

Accessibility Review

brunner.nl accessibility score

89

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Best Practices

brunner.nl 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

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

brunner.nl SEO score

92

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

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

Language and Encoding

  • Language Detected

    NL

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Brunner.nl can be misinterpreted by Google and other search engines. Our service has detected that Dutch 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 Brunner.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

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