Tools & Wizards About Us
webikeamsterdam.com screenshot

Report Summary

  • 8

    Performance

    Renders faster than
    22% of other websites

  • 98

    Accessibility

    Visual factors better than
    that of 94% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

webikeamsterdam.com

We Bike Amsterdam - City and Countryside Bike Tours

Page Load Speed

1.9 sec in total

First Response

209 ms

Resources Loaded

1.5 sec

Page Rendered

197 ms

webikeamsterdam.com screenshot

About Website

Visit webikeamsterdam.com now to see the best up-to-date We Bike Amsterdam content and also check out these interesting facts you probably never knew about webikeamsterdam.com

We Bike Amsterdam offers City Bike Tours of Amsterdam's hidden gems, Countryside Bike Tours of Holland and Private Bike Tours.

Visit webikeamsterdam.com

Key Findings

We analyzed Webikeamsterdam.com page load time and found that the first response time was 209 ms and then it took 1.7 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

webikeamsterdam.com performance score

8

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.7 s

29/100

10%

LCP (Largest Contentful Paint)

Value35.2 s

0/100

25%

SI (Speed Index)

Value13.0 s

2/100

10%

TBT (Total Blocking Time)

Value1,340 ms

17/100

30%

CLS (Cumulative Layout Shift)

Value1.944

0/100

15%

TTI (Time to Interactive)

Value20.3 s

2/100

10%

Network Requests Diagram

webikeamsterdam.com

209 ms

www.webikeamsterdam.com

328 ms

style.min.css

33 ms

mediaelementplayer-legacy.min.css

24 ms

wp-mediaelement.min.css

30 ms

Our browser made a total of 43 requests to load all elements on the main page. We found that 53% of them (23 requests) were addressed to the original Webikeamsterdam.com, 19% (8 requests) were made to I0.wp.com and 9% (4 requests) were made to Dipr2nuwo661l.cloudfront.net. The less responsive or slowest element that took the longest time to load (437 ms) belongs to the original domain Webikeamsterdam.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 42.8 kB (1%)

Content Size

5.9 MB

After Optimization

5.8 MB

  • Images
  • JavaScript
  • CSS

In fact, the total size of Webikeamsterdam.com main page is 5.9 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. 30% of websites need less resources to load. Images take 4.9 MB which makes up the majority of the site volume.

HTML Optimization

-0%

Potential reduce by -8 B

  • Original 0 B

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 web page is already compressed.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 4.9 MB
  • After minification 4.9 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. We Bike Amsterdam images are well optimized though.

JavaScript Optimization

-5%

Potential reduce by 40.0 kB

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

-8%

Potential reduce by 2.8 kB

  • Original 33.7 kB
  • After minification 33.7 kB
  • After compression 30.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. Webikeamsterdam.com has all CSS files already compressed.

Requests Breakdown

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

Requests Now

37

After Optimization

14

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

webikeamsterdam.com

webikeamsterdam.com

209 ms

www.webikeamsterdam.com

www.webikeamsterdam.com

328 ms

style.min.css

style.min.css

33 ms

mediaelementplayer-legacy.min.css

mediaelementplayer-legacy.min.css

24 ms

wp-mediaelement.min.css

wp-mediaelement.min.css

30 ms

styles.css

styles.css

28 ms

style.min.css

style.min.css

34 ms

7cd4c9bf4ef6c62f204dde2cc2f217af.min.css

7cd4c9bf4ef6c62f204dde2cc2f217af.min.css

54 ms

jetpack.css

jetpack.css

39 ms

language-cookie.js

language-cookie.js

37 ms

breeze-prefetch-links.min.js

breeze-prefetch-links.min.js

44 ms

jquery.min.js

jquery.min.js

19 ms

jquery-migrate.min.js

jquery-migrate.min.js

45 ms

js

js

111 ms

platform.js

platform.js

46 ms

749415217a.js

749415217a.js

110 ms

platform.js

platform.js

50 ms

image-cdn.js

image-cdn.js

32 ms

e-202437.js

e-202437.js

38 ms

c570c52bfa85f1a7885971b67754c31c.min.js

c570c52bfa85f1a7885971b67754c31c.min.js

37 ms

lazyload.min.js

lazyload.min.js

33 ms

tripadvisor-logo-tripadvisor-still-flying-high-its-journey-instant-bookings-digital-innovation-and-6.png

tripadvisor-logo-tripadvisor-still-flying-high-its-journey-instant-bookings-digital-innovation-and-6.png

31 ms

nl.svg

nl.svg

16 ms

en.svg

en.svg

17 ms

We-bike-Amsterdam.svg

We-bike-Amsterdam.svg

17 ms

hidden-gems-of-Amsterdam-2.webp

hidden-gems-of-Amsterdam-2.webp

44 ms

Amsterdam-Windmill.webp

Amsterdam-Windmill.webp

37 ms

Private-Family-Tour-at-Prinseneiland.webp

Private-Family-Tour-at-Prinseneiland.webp

37 ms

hidden-gems-of-Amsterdam-2-1.webp

hidden-gems-of-Amsterdam-2-1.webp

34 ms

Countryside-bike-tour.webp

Countryside-bike-tour.webp

33 ms

Private-Family-Tour-at-Prinseneiland-1.webp

Private-Family-Tour-at-Prinseneiland-1.webp

34 ms

amsterdam-s-hidden-gems.jpg

amsterdam-s-hidden-gems.jpg

39 ms

fa-solid-900.woff

fa-solid-900.woff

437 ms

AmericanTypewriterStd-Bold.woff

AmericanTypewriterStd-Bold.woff

268 ms

awb-icons.woff

awb-icons.woff

17 ms

integration-kit-bundle.js

integration-kit-bundle.js

152 ms

278 ms

style-cart.a02642c318da0638f31a.css

style-cart.a02642c318da0638f31a.css

92 ms

fonts.eacdf4961de415ddab83.css

fonts.eacdf4961de415ddab83.css

109 ms

output.018d63fa1f96.js

output.018d63fa1f96.js

92 ms

js

js

21 ms

djangojs.js

djangojs.js

83 ms

output.577d4a9fd616.js

output.577d4a9fd616.js

81 ms

Accessibility Review

webikeamsterdam.com accessibility score

98

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.

Best Practices

webikeamsterdam.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

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

webikeamsterdam.com SEO score

93

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

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

    EN

  • Language Claimed

    N/A

  • Encoding

    N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Webikeamsterdam.com can be misinterpreted by Google and other search engines. Our service has detected that English 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 Webikeamsterdam.com main page’s claimed encoding is . Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

webikeamsterdam.com

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