2.3 sec in total
75 ms
1.5 sec
683 ms
Visit zipcar.be now to see the best up-to-date Zipcar content for Belgium and also check out these interesting facts you probably never knew about zipcar.be
Zipcar is the world’s leading car sharing alternative to car rental & ownership. Book cars on demand by the hour or day. Join instantly, drive in minutes.
Visit zipcar.beWe analyzed Zipcar.be page load time and found that the first response time was 75 ms and then it took 2.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
zipcar.be performance score
name
value
score
weighting
Value7.7 s
0/100
10%
Value10.7 s
0/100
25%
Value25.3 s
0/100
10%
Value105,410 ms
0/100
30%
Value0.172
69/100
15%
Value148.3 s
0/100
10%
75 ms
179 ms
123 ms
175 ms
225 ms
Our browser made a total of 45 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Zipcar.be, 44% (20 requests) were made to Media2.zipcar.com and 11% (5 requests) were made to Zipcar.com. The less responsive or slowest element that took the longest time to load (606 ms) relates to the external source Media2.zipcar.com.
Page size can be reduced by 107.0 kB (35%)
305.0 kB
198.0 kB
In fact, the total size of Zipcar.be main page is 305.0 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 70% of websites need less resources to load. Images take 146.3 kB which makes up the majority of the site volume.
Potential reduce by 61.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. This page needs HTML code to be minified as it can gain 12.1 kB, which is 16% 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 61.8 kB or 80% of the original size.
Potential reduce by 45.1 kB
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, Zipcar needs image optimization as it can save up to 45.1 kB or 31% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 50 B
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.
Potential reduce by 24 B
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. Zipcar.be has all CSS files already compressed.
Number of requests can be reduced by 16 (40%)
40
24
The browser has sent 40 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Zipcar. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 14 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
zipcar.be
75 ms
www.zipcar.com
179 ms
js
123 ms
css_yuwk_m_GpzORxylUPXXxy7t6vFgo1glStXY3jUrI11M.css
175 ms
css_17EhS9cXfz7R3UFt20oeeakV2zR0JKdsIVnNAbTTd1Q.css
225 ms
css
111 ms
css_alw_L_H-YnD2PW7jFPP4J0I-gh5j08XRnQ85pW50TlQ.css
249 ms
js
146 ms
271989291.js
181 ms
js_0UhVCau9xz2lmErKM7KJzUiTy_uObsdUoIyO0H69PWE.js
605 ms
page.js
115 ms
js_Y-uz3MjO79Zx2utFjtATps_YIsNh8hUl-OHcZxO7YnQ.js
606 ms
geoip2.js
113 ms
axios.min.js
109 ms
polyline.min.js
143 ms
js_AJSKhwR1O0L9716Rxqgn304ehfhxwmIkW-VcnggmIQc.js
605 ms
v652eace1692a40cfa3763df669d7439c1639079717194
193 ms
axios.min.js
32 ms
gen_204
29 ms
js
527 ms
logo.svg
413 ms
ic-faq-divider-down.svg
375 ms
app-store.svg
382 ms
google-play.svg
380 ms
Q2-homepage_desktop%20%281%29.png
374 ms
Q2-homepage_mobile.png
371 ms
ic-unlock-mobile_2_0.svg
367 ms
ic-drive-wheel_0_0.svg
369 ms
ic-parking_0_0.svg
371 ms
calculator-bkgd-2x.png
438 ms
ic-saving_0.svg
421 ms
ic-map_0.svg
423 ms
ic-24-7-access_0.svg
466 ms
ic-public-transit_1.svg
426 ms
ic-students.svg
419 ms
ic-business.svg
469 ms
zipcar-footer-car.svg
476 ms
accessibility.js
284 ms
fontawesome-webfont.woff
196 ms
eso.e18d3993.js
77 ms
sm.23.html
99 ms
analytics.js
19 ms
collect
23 ms
collect
51 ms
ga-audiences
34 ms
zipcar.be accessibility score
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
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Some elements have a [tabindex] value greater than 0
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
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
zipcar.be best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
zipcar.be SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
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
Document uses legible font sizes
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Zipcar.be can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Zipcar.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.
zipcar.be
Open Graph description is not detected on the main page of Zipcar. 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: