Report Summary

  • 24

    Performance

    Renders faster than
    44% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 58% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 84

    SEO

    Google-friendlier than
    53% of websites

kuurne.be

Homepagina

Page Load Speed

2.3 sec in total

First Response

304 ms

Resources Loaded

1.7 sec

Page Rendered

251 ms

kuurne.be screenshot

About Website

Welcome to kuurne.be homepage info - get ready to check Kuurne best content for Belgium right away, or after learning these important things about kuurne.be

Visit kuurne.be

Key Findings

We analyzed Kuurne.be page load time and found that the first response time was 304 ms and then it took 2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.

Performance Metrics

kuurne.be performance score

24

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.3 s

18/100

10%

LCP (Largest Contentful Paint)

Value17.1 s

0/100

25%

SI (Speed Index)

Value12.1 s

3/100

10%

TBT (Total Blocking Time)

Value1,160 ms

22/100

30%

CLS (Cumulative Layout Shift)

Value0.028

100/100

15%

TTI (Time to Interactive)

Value19.5 s

2/100

10%

Network Requests Diagram

kuurne.be

304 ms

www.kuurne.be

503 ms

modernizr.min.js

92 ms

css_GtADxgzpCgxdVoxFmfaqWc59x7lhedAG7CUBV3ZOpI0.css

172 ms

css__S6455Eq1bNp3C3Fx8ikTFFawoLE61SYHyB3rX_xWfQ.css

173 ms

Our browser made a total of 46 requests to load all elements on the main page. We found that 87% of them (40 requests) were addressed to the original Kuurne.be, 9% (4 requests) were made to Google-analytics.com and 2% (1 request) were made to Maps.googleapis.com. The less responsive or slowest element that took the longest time to load (539 ms) belongs to the original domain Kuurne.be.

Page Optimization Overview & Recommendations

Page size can be reduced by 505.3 kB (38%)

Content Size

1.3 MB

After Optimization

825.8 kB

In fact, the total size of Kuurne.be main page is 1.3 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. 45% of websites need less resources to load. Images take 744.3 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 58.5 kB

  • Original 70.4 kB
  • After minification 63.2 kB
  • After compression 11.9 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 58.5 kB or 83% of the original size.

Image Optimization

-10%

Potential reduce by 76.2 kB

  • Original 744.3 kB
  • After minification 668.1 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. Kuurne images are well optimized though.

JavaScript Optimization

-64%

Potential reduce by 211.1 kB

  • Original 328.0 kB
  • After minification 289.7 kB
  • After compression 116.9 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 211.1 kB or 64% of the original size.

CSS Optimization

-85%

Potential reduce by 159.5 kB

  • Original 188.4 kB
  • After minification 185.1 kB
  • After compression 28.9 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. Kuurne.be needs all CSS files to be minified and compressed as it can save up to 159.5 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 19 (45%)

Requests Now

42

After Optimization

23

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

Accessibility Review

kuurne.be accessibility score

84

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-*] attributes do not match their roles

High

[role] values are not valid

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.

Best Practices

kuurne.be best practices score

75

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

kuurne.be SEO score

84

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    NL

  • Language Claimed

    NL

  • Encoding

    UTF-8

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