Tools & Wizards About Us
api.nextbike.net screenshot

Report Summary

  • 19

    Performance

    Renders faster than
    36% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 61% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 99

    SEO

    Google-friendlier than
    93% of websites

api.nextbike.net

nextbike - europäischer Bike-Sharing Marktführer

Page Load Speed

4.5 sec in total

First Response

211 ms

Resources Loaded

3.5 sec

Page Rendered

814 ms

api.nextbike.net screenshot

About Website

Visit api.nextbike.net now to see the best up-to-date Api Next Bike content for Germany and also check out these interesting facts you probably never knew about api.nextbike.net

Passgenaue Mobilitätslösungen im Bike-Sharing mit nextbike. Stationsbasiert oder stationslos: Wir stellen maßgeschneiderte Systeme bereit.

Visit api.nextbike.net

Key Findings

We analyzed Api.nextbike.net page load time and found that the first response time was 211 ms and then it took 4.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

api.nextbike.net performance score

19

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.8 s

12/100

10%

LCP (Largest Contentful Paint)

Value8.2 s

2/100

25%

SI (Speed Index)

Value8.0 s

21/100

10%

TBT (Total Blocking Time)

Value4,430 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.018

100/100

15%

TTI (Time to Interactive)

Value15.9 s

6/100

10%

Network Requests Diagram

api.nextbike.net

211 ms

api.nextbike.net

412 ms

www.nextbike.net

628 ms

style.min.css

207 ms

styles.css

293 ms

Our browser made a total of 73 requests to load all elements on the main page. We found that 3% of them (2 requests) were addressed to the original Api.nextbike.net, 97% (71 requests) were made to Nextbike.net. The less responsive or slowest element that took the longest time to load (960 ms) relates to the external source Nextbike.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 938.6 kB (33%)

Content Size

2.9 MB

After Optimization

1.9 MB

  • HTML
  • Images

In fact, the total size of Api.nextbike.net main page is 2.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. 55% of websites need less resources to load. Images take 2.5 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 336.9 kB

  • Original 401.7 kB
  • After minification 399.3 kB
  • After compression 64.8 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 336.9 kB or 84% of the original size.

Image Optimization

-24%

Potential reduce by 601.7 kB

  • Original 2.5 MB
  • After minification 1.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. Obviously, Api Next Bike needs image optimization as it can save up to 601.7 kB or 24% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

Requests Breakdown

Number of requests can be reduced by 47 (76%)

Requests Now

62

After Optimization

15

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

api.nextbike.net

api.nextbike.net

211 ms

api.nextbike.net

api.nextbike.net

412 ms

www.nextbike.net

www.nextbike.net

628 ms

style.min.css

style.min.css

207 ms

styles.css

styles.css

293 ms

styles.css

styles.css

298 ms

style.min.css

style.min.css

292 ms

font-awesome-legacy.min.css

font-awesome-legacy.min.css

308 ms

grid-system.css

grid-system.css

305 ms

style.css

style.css

314 ms

element-testimonial.css

element-testimonial.css

391 ms

element-fancy-box.css

element-fancy-box.css

392 ms

element-highlighted-text.css

element-highlighted-text.css

389 ms

element-interactive-map.css

element-interactive-map.css

406 ms

element-milestone.css

element-milestone.css

408 ms

cf7.css

cf7.css

415 ms

responsive.css

responsive.css

488 ms

select2.css

select2.css

493 ms

skin-original.css

skin-original.css

492 ms

borlabs-cookie_1_de.css

borlabs-cookie_1_de.css

407 ms

js_composer.min.css

js_composer.min.css

409 ms

style.css

style.css

413 ms

index.css

index.css

485 ms

redux-google-fonts-salient_redux.css

redux-google-fonts-salient_redux.css

484 ms

jquery.min.js

jquery.min.js

586 ms

jquery-migrate.min.js

jquery-migrate.min.js

509 ms

borlabs-cookie-prioritize.min.js

borlabs-cookie-prioritize.min.js

510 ms

index.js

index.js

514 ms

style-non-critical.css

style-non-critical.css

580 ms

magnific.css

magnific.css

581 ms

core.css

core.css

652 ms

index.js

index.js

651 ms

index.js

index.js

652 ms

jquery.easing.min.js

jquery.easing.min.js

759 ms

jquery.mousewheel.min.js

jquery.mousewheel.min.js

759 ms

priority.js

priority.js

759 ms

transit.min.js

transit.min.js

760 ms

waypoints.js

waypoints.js

760 ms

imagesLoaded.min.js

imagesLoaded.min.js

760 ms

hoverintent.min.js

hoverintent.min.js

711 ms

magnific.js

magnific.js

626 ms

touchswipe.min.js

touchswipe.min.js

625 ms

nectar-testimonial-slider.js

nectar-testimonial-slider.js

639 ms

anime.min.js

anime.min.js

628 ms

superfish.js

superfish.js

623 ms

init.js

init.js

912 ms

select2.min.js

select2.min.js

598 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

597 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

637 ms

wp-polyfill.min.js

wp-polyfill.min.js

623 ms

js_composer_front.min.js

js_composer_front.min.js

623 ms

borlabs-cookie.min.js

borlabs-cookie.min.js

673 ms

nextbike-Combi-Mark-Negative.png

nextbike-Combi-Mark-Negative.png

380 ms

de.png

de.png

422 ms

en.png

en.png

423 ms

it.png

it.png

424 ms

es.png

es.png

476 ms

fr.png

fr.png

477 ms

LOGO_COLOR_CMYK-scaled.jpg

LOGO_COLOR_CMYK-scaled.jpg

626 ms

Ohne-Zusatz-scaled.jpg

Ohne-Zusatz-scaled.jpg

727 ms

UITP_With_baseline_Horizontal_RGB_screen.jpg

UITP_With_baseline_Horizontal_RGB_screen.jpg

827 ms

Main-logo-colourPNG.png

Main-logo-colourPNG.png

669 ms

Smartbike_2.0_QF_DACH_2.jpg

Smartbike_2.0_QF_DACH_2.jpg

822 ms

Background_map_grey-1.png

Background_map_grey-1.png

868 ms

noto-sans-normal-400.woff

noto-sans-normal-400.woff

521 ms

noto-sans-normal-700.woff

noto-sans-normal-700.woff

561 ms

OpenSans-SemiBold.woff

OpenSans-SemiBold.woff

622 ms

OpenSans-Bold.woff

OpenSans-Bold.woff

637 ms

OpenSans-Regular.woff

OpenSans-Regular.woff

661 ms

OpenSans-Light.woff

OpenSans-Light.woff

721 ms

fontawesome-webfont.svg

fontawesome-webfont.svg

960 ms

icomoon.woff

icomoon.woff

736 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

202 ms

Accessibility Review

api.nextbike.net accessibility score

86

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

Links do not have a discernible name

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

api.nextbike.net best practices score

83

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

Browser errors were logged to the console

SEO Factors

api.nextbike.net SEO score

99

Search Engine Optimization Advices

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

    DE

  • Language Claimed

    DE

  • Encoding

    UTF-8

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

api.nextbike.net

Open Graph data is detected on the main page of Api Next Bike. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: