Report Summary

  • 25

    Performance

    Renders faster than
    44% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 57% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 84

    SEO

    Google-friendlier than
    53% of websites

izegem.be

Stad Izegem

Page Load Speed

5.6 sec in total

First Response

1.1 sec

Resources Loaded

4.2 sec

Page Rendered

236 ms

izegem.be screenshot

About Website

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

Visit izegem.be

Key Findings

We analyzed Izegem.be page load time and found that the first response time was 1.1 sec and then it took 4.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

izegem.be performance score

25

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.6 s

14/100

10%

LCP (Largest Contentful Paint)

Value19.2 s

0/100

25%

SI (Speed Index)

Value13.8 s

1/100

10%

TBT (Total Blocking Time)

Value970 ms

28/100

30%

CLS (Cumulative Layout Shift)

Value0.028

100/100

15%

TTI (Time to Interactive)

Value27.5 s

0/100

10%

Network Requests Diagram

izegem.be

1128 ms

www.izegem.be

379 ms

start.izegem.be

647 ms

main.css

120 ms

font-awesome.min.css

5 ms

Our browser made a total of 21 requests to load all elements on the main page. We found that 10% of them (2 requests) were addressed to the original Izegem.be, 71% (15 requests) were made to Start.izegem.be and 10% (2 requests) were made to Maxcdn.bootstrapcdn.com. The less responsive or slowest element that took the longest time to load (1.8 sec) relates to the external source Start.izegem.be.

Page Optimization Overview & Recommendations

Page size can be reduced by 148.2 kB (10%)

Content Size

1.4 MB

After Optimization

1.3 MB

In fact, the total size of Izegem.be main page is 1.4 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. 25% of websites need less resources to load. Images take 1.2 MB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 6.6 kB

  • Original 8.9 kB
  • After minification 8.4 kB
  • After compression 2.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. 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 6.6 kB or 74% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 1.2 MB
  • After minification 1.2 MB

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. Izegem images are well optimized though.

JavaScript Optimization

-60%

Potential reduce by 121.3 kB

  • Original 202.2 kB
  • After minification 199.4 kB
  • After compression 80.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 121.3 kB or 60% of the original size.

CSS Optimization

-76%

Potential reduce by 20.3 kB

  • Original 26.8 kB
  • After minification 26.8 kB
  • After compression 6.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. Izegem.be needs all CSS files to be minified and compressed as it can save up to 20.3 kB or 76% of the original size.

Requests Breakdown

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

Requests Now

17

After Optimization

12

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

Accessibility Review

izegem.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

izegem.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

High

Page has valid source maps

SEO Factors

izegem.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 Izegem.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 Izegem.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 Izegem. 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: