Tools & Wizards About Us
izibike.nl screenshot

Report Summary

  • 45

    Performance

    Renders faster than
    64% of other websites

  • 65

    Accessibility

    Visual factors better than
    that of 30% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

izibike.nl

Mantel - De fietsenwinkel waar je in één keer slaagt

Page Load Speed

3 sec in total

First Response

355 ms

Resources Loaded

2.2 sec

Page Rendered

451 ms

izibike.nl screenshot

About Website

Click here to check amazing Izibike content for Netherlands. Otherwise, check out these important facts you probably never knew about izibike.nl

Groot assortiment aan e-bikes, elektrische fietsen, racefietsen en mountainbikes ✓ 4 fietsenwinkels voor extra service ✓ Voor 22:00 besteld, morgen in huis.

Visit izibike.nl

Key Findings

We analyzed Izibike.nl page load time and found that the first response time was 355 ms and then it took 2.6 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

izibike.nl performance score

45

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.9 s

24/100

10%

LCP (Largest Contentful Paint)

Value8.8 s

1/100

25%

SI (Speed Index)

Value5.8 s

49/100

10%

TBT (Total Blocking Time)

Value470 ms

61/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value8.3 s

40/100

10%

Network Requests Diagram

izibike.nl

355 ms

mantel.com

367 ms

www.mantel.com

674 ms

mantel-webshop.min.css

30 ms

js

80 ms

Our browser made a total of 66 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Izibike.nl, 82% (54 requests) were made to Cdn.mantel.com and 5% (3 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (769 ms) relates to the external source Checkoutshopper-live.adyen.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 532.3 kB (31%)

Content Size

1.7 MB

After Optimization

1.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Izibike.nl main page is 1.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. 65% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-93%

Potential reduce by 498.9 kB

  • Original 534.3 kB
  • After minification 378.3 kB
  • After compression 35.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 155.9 kB, which is 29% 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 498.9 kB or 93% of the original size.

Image Optimization

-3%

Potential reduce by 33.1 kB

  • Original 1.1 MB
  • After minification 1.1 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. Izibike images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 26 B

  • Original 39.8 kB
  • After minification 39.8 kB
  • After compression 39.8 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

-0%

Potential reduce by 197 B

  • Original 43.2 kB
  • After minification 43.2 kB
  • After compression 43.0 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. Izibike.nl has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 23 (39%)

Requests Now

59

After Optimization

36

  • Images
  • JavaScript
  • CSS

The browser has sent 59 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Izibike. 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 as a result speed up the page load time.

Network Requests Diagram

izibike.nl

izibike.nl

355 ms

mantel.com

mantel.com

367 ms

www.mantel.com

www.mantel.com

674 ms

mantel-webshop.min.css

mantel-webshop.min.css

30 ms

js

js

80 ms

gtm.js

gtm.js

141 ms

flag-NL.svg

flag-NL.svg

37 ms

flag-BE.svg

flag-BE.svg

119 ms

flag-DE.svg

flag-DE.svg

148 ms

flag-GB.svg

flag-GB.svg

149 ms

flag-FI.svg

flag-FI.svg

167 ms

flag-IE.svg

flag-IE.svg

165 ms

flag-LU.svg

flag-LU.svg

177 ms

flag-PT.svg

flag-PT.svg

169 ms

flag-PL.svg

flag-PL.svg

176 ms

flag-AT.svg

flag-AT.svg

174 ms

flag-FR.svg

flag-FR.svg

174 ms

flag-ES.svg

flag-ES.svg

311 ms

flag-IT.svg

flag-IT.svg

179 ms

flag-SE.svg

flag-SE.svg

180 ms

flag-DK.svg

flag-DK.svg

309 ms

product.php

product.php

176 ms

landing

landing

412 ms

js

js

261 ms

product.php

product.php

68 ms

product.php

product.php

200 ms

product.php

product.php

200 ms

product.php

product.php

200 ms

product.php

product.php

207 ms

product.php

product.php

208 ms

content.php

content.php

341 ms

content.php

content.php

341 ms

product.php

product.php

200 ms

product.php

product.php

201 ms

product.php

product.php

206 ms

product.php

product.php

206 ms

product.php

product.php

338 ms

product.php

product.php

338 ms

content.php

content.php

339 ms

content.php

content.php

338 ms

content.php

content.php

341 ms

content.php

content.php

352 ms

product.php

product.php

351 ms

product.php

product.php

351 ms

product.php

product.php

351 ms

ideal.svg

ideal.svg

768 ms

hammer.min.js

hammer.min.js

653 ms

popper.min.js

popper.min.js

655 ms

polyfills.min.js

polyfills.min.js

303 ms

webshop.min.js

webshop.min.js

302 ms

address-lookup-by-zipcode.min.js

address-lookup-by-zipcode.min.js

304 ms

mc.svg

mc.svg

769 ms

visa.svg

visa.svg

768 ms

product.php

product.php

304 ms

product.php

product.php

297 ms

product.php

product.php

297 ms

product.php

product.php

295 ms

product.php

product.php

295 ms

mantel-stores.jpg

mantel-stores.jpg

295 ms

working-at-mantel.jpg

working-at-mantel.jpg

463 ms

trustpilot-logo.svg

trustpilot-logo.svg

460 ms

widget-postnl.svg

widget-postnl.svg

460 ms

fa-solid-900.woff

fa-solid-900.woff

158 ms

fa-regular-400.woff

fa-regular-400.woff

323 ms

fa-light-300.woff

fa-light-300.woff

326 ms

fa-brands-400.woff

fa-brands-400.woff

323 ms

Accessibility Review

izibike.nl accessibility score

65

Accessibility Issues

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

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

[id] attributes on active, focusable elements are not unique

High

Heading elements are not in a sequentially-descending order

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

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

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

izibike.nl best practices score

92

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

Page has valid source maps

SEO Factors

izibike.nl SEO score

86

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

izibike.nl

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