Tools & Wizards About Us
fiets.be screenshot

Report Summary

  • 23

    Performance

    Renders faster than
    42% of other websites

  • 77

    Accessibility

    Visual factors better than
    that of 45% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 85

    SEO

    Google-friendlier than
    56% of websites

fiets.be

Bike Republic

Page Load Speed

5.7 sec in total

First Response

407 ms

Resources Loaded

4.8 sec

Page Rendered

445 ms

fiets.be screenshot

About Website

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

Bike Republic biedt een uitgebreid aanbod aan (elektrische) fietsen, fietsaccessoires, -onderdelen en advies. Ontdek ons assortiment of kom langs in een Bike Republic winkel.

Visit fiets.be

Key Findings

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

Performance Metrics

fiets.be performance score

23

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.1 s

22/100

10%

LCP (Largest Contentful Paint)

Value15.2 s

0/100

25%

SI (Speed Index)

Value8.6 s

17/100

10%

TBT (Total Blocking Time)

Value1,870 ms

9/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value13.9 s

10/100

10%

Network Requests Diagram

fiets.be

407 ms

www.fiets.be

909 ms

www.fiets.be

742 ms

ffa24b5b3014a6dd232247fd4518d372.css

87 ms

83e36456d67a65e53e2e93c4b8e3b03f.css

517 ms

Our browser made a total of 70 requests to load all elements on the main page. We found that 63% of them (44 requests) were addressed to the original Fiets.be, 13% (9 requests) were made to Google-analytics.com and 6% (4 requests) were made to Portal.hansstruijkfietsen.nl. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Fiets.be.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.6 MB (43%)

Content Size

3.7 MB

After Optimization

2.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Fiets.be main page is 3.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 2.0 MB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 104.3 kB

  • Original 121.5 kB
  • After minification 94.4 kB
  • After compression 17.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 27.1 kB, which is 22% 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 104.3 kB or 86% of the original size.

Image Optimization

-6%

Potential reduce by 122.0 kB

  • Original 2.0 MB
  • After minification 1.8 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. Fiets images are well optimized though.

JavaScript Optimization

-76%

Potential reduce by 683.4 kB

  • Original 901.5 kB
  • After minification 699.3 kB
  • After compression 218.1 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 683.4 kB or 76% of the original size.

CSS Optimization

-90%

Potential reduce by 682.6 kB

  • Original 760.1 kB
  • After minification 622.7 kB
  • After compression 77.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. Fiets.be needs all CSS files to be minified and compressed as it can save up to 682.6 kB or 90% of the original size.

Requests Breakdown

Number of requests can be reduced by 21 (34%)

Requests Now

61

After Optimization

40

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

fiets.be

fiets.be

407 ms

www.fiets.be

www.fiets.be

909 ms

www.fiets.be

www.fiets.be

742 ms

ffa24b5b3014a6dd232247fd4518d372.css

ffa24b5b3014a6dd232247fd4518d372.css

87 ms

83e36456d67a65e53e2e93c4b8e3b03f.css

83e36456d67a65e53e2e93c4b8e3b03f.css

517 ms

ed811db2206d4dd9e3946d2d32dc6db4.js

ed811db2206d4dd9e3946d2d32dc6db4.js

842 ms

css

css

61 ms

css

css

74 ms

options.css.php

options.css.php

305 ms

logo.png

logo.png

95 ms

banner1-vroegevogel.png

banner1-vroegevogel.png

1175 ms

banner-stads.png

banner-stads.png

587 ms

banner1-fietswandel.png

banner1-fietswandel.png

635 ms

banner3-sportief.png

banner3-sportief.png

521 ms

banner2-merksem.png

banner2-merksem.png

740 ms

16_000046-2.jpg

16_000046-2.jpg

427 ms

16_000528-1.jpg

16_000528-1.jpg

512 ms

16_000529-1.jpg

16_000529-1.jpg

594 ms

16_000054-2.jpg

16_000054-2.jpg

704 ms

4054571119889-2.jpg

4054571119889-2.jpg

675 ms

4054571119957-2.jpg

4054571119957-2.jpg

843 ms

15_000010-1.jpg

15_000010-1.jpg

750 ms

16_000176-1.jpg

16_000176-1.jpg

812 ms

8717185960563-1.jpg

8717185960563-1.jpg

981 ms

8717185960549-1.jpg

8717185960549-1.jpg

970 ms

16_000177-1.jpg

16_000177-1.jpg

970 ms

16_000178-1.jpg

16_000178-1.jpg

973 ms

8717185960730-1.jpg

8717185960730-1.jpg

987 ms

8717185960716-1.jpg

8717185960716-1.jpg

1051 ms

banner1-woonwerk.png

banner1-woonwerk.png

1631 ms

banner2-stromer.png

banner2-stromer.png

1229 ms

fietsmag3.png

fietsmag3.png

1176 ms

tantekaat2.png

tantekaat2.png

1629 ms

voorzelfdegeld2.jpg

voorzelfdegeld2.jpg

1132 ms

betaalkaarten.png

betaalkaarten.png

1219 ms

logoPostNL.png

logoPostNL.png

1627 ms

Flevobird.jpg

Flevobird.jpg

1625 ms

pattern.jpg

pattern.jpg

1604 ms

loader.gif

loader.gif

1604 ms

cat_favoriet.png

cat_favoriet.png

375 ms

icomoon.ttf

icomoon.ttf

1584 ms

icomoon.woff

icomoon.woff

1584 ms

century-gothic.woff

century-gothic.woff

1578 ms

cat_tip_philip.png

cat_tip_philip.png

370 ms

cat_outlet.png

cat_outlet.png

363 ms

cat_prijs_topper.png

cat_prijs_topper.png

361 ms

gtm.js

gtm.js

113 ms

arrow_totop.png

arrow_totop.png

1481 ms

arrow_footer.png

arrow_footer.png

1483 ms

bx_loader.gif

bx_loader.gif

1484 ms

6390.js

6390.js

31 ms

analytics.js

analytics.js

201 ms

conversion_async.js

conversion_async.js

195 ms

widget_v2.132.js

widget_v2.132.js

44 ms

__$$__stringtable_lang_nl.js

__$$__stringtable_lang_nl.js

46 ms

45 ms

ec.js

ec.js

17 ms

collect

collect

20 ms

collect

collect

74 ms

collect

collect

38 ms

collect

collect

44 ms

collect

collect

50 ms

collect

collect

54 ms

collect

collect

56 ms

collect

collect

56 ms

56 ms

ga-audiences

ga-audiences

15 ms

avatar_simple_visitor.png

avatar_simple_visitor.png

134 ms

aL63HcygAAVYuCCsAAA==

aL63HcygAAVYuCCsAAA==

48 ms

aea57fd1bcf402c95e84a68e24dc7243.css

aea57fd1bcf402c95e84a68e24dc7243.css

97 ms

Accessibility Review

fiets.be accessibility score

77

Accessibility Issues

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

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

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

Missing source maps for large first-party JavaScript

SEO Factors

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

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

fiets.be

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