2.5 sec in total
374 ms
1.9 sec
158 ms
Click here to check amazing Autocool content. Otherwise, check out these important facts you probably never knew about autocool.fr
Location de voitures partagées en libre-service 24h/24 à Bordeaux
Visit autocool.frWe analyzed Autocool.fr page load time and found that the first response time was 374 ms and then it took 2.1 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.
autocool.fr performance score
name
value
score
weighting
Value4.0 s
22/100
10%
Value9.3 s
1/100
25%
Value8.2 s
20/100
10%
Value460 ms
62/100
30%
Value0.002
100/100
15%
Value14.8 s
8/100
10%
374 ms
261 ms
89 ms
249 ms
174 ms
Our browser made a total of 57 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Autocool.fr, 86% (49 requests) were made to Bordeaux.citiz.coop and 5% (3 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Bordeaux.citiz.coop.
Page size can be reduced by 1.1 MB (53%)
2.2 MB
1.0 MB
In fact, the total size of Autocool.fr main page is 2.2 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. 50% of websites need less resources to load. Images take 936.3 kB which makes up the majority of the site volume.
Potential reduce by 35.5 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 9.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 35.5 kB or 86% of the original size.
Potential reduce by 151.2 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, Autocool needs image optimization as it can save up to 151.2 kB or 16% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 743.6 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 743.6 kB or 80% of the original size.
Potential reduce by 218.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. Autocool.fr needs all CSS files to be minified and compressed as it can save up to 218.5 kB or 86% of the original size.
Number of requests can be reduced by 11 (22%)
50
39
The browser has sent 50 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Autocool. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
autocool.fr
374 ms
bordeaux.citiz.coop
261 ms
90c608b.css
89 ms
53cec58.css
249 ms
55983cc.css
174 ms
7abe7da.js
685 ms
4e09e58.js
177 ms
config
185 ms
routing
187 ms
js
78 ms
ffbec06.js
427 ms
6e5a12a.js
350 ms
analytics.js
292 ms
header-bordeaux.png
370 ms
header-punchline.png
329 ms
car-s.jpg
367 ms
car-m.jpg
405 ms
car-l.jpg
427 ms
jeunes3.jpeg
956 ms
jardinier2.jpeg
878 ms
pros1.jpeg
878 ms
pmr2.jpeg
880 ms
bordeaux.jpg
596 ms
nouveaux-tarifs.png
941 ms
flotte-citiz.jpeg
872 ms
map-small.png
879 ms
manuel-1.png
927 ms
manuel-2.png
928 ms
manuel-3.png
938 ms
manuel-4.png
939 ms
clock.png
1020 ms
twitter.png
1008 ms
facebook.png
1023 ms
print.png
1024 ms
email.png
1025 ms
citiz-decli.png
1043 ms
ajax-loader.gif
1087 ms
css
24 ms
circle-arrow-grey.png
858 ms
circle-arrow-yellow.png
855 ms
circle-more-yellow.png
856 ms
stations.png
857 ms
glyphicons-halflings-white.png
882 ms
VistaSansOTCE-Book.otf
965 ms
VistaSansOTCE-Light.otf
995 ms
7XUFZ5tgS-tD6QamInJTcU3KvHLhcNjEHFQzwNtdMQY.ttf
23 ms
anMUvcNT0H1YN4FII8wpr4e2tK5W43RXgBRKkM4A5Qg.ttf
37 ms
anMUvcNT0H1YN4FII8wprzsSLeNQG2cy_mKit6iEdYs.ttf
48 ms
analytics.js
91 ms
pointer-v2.png
327 ms
pointer-active-v2.png
328 ms
datepicker.png
335 ms
ui-bg_flat_75_ffffff_40x100.png
357 ms
car-s.png
417 ms
car-m.png
418 ms
car-l.png
427 ms
collect
23 ms
autocool.fr accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
ARIA IDs are not unique
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
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
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
List items (<li>) are not contained within <ul> or <ol> parent elements.
autocool.fr 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
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
autocool.fr SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
FR
FR
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Autocool.fr can be misinterpreted by Google and other search engines. Our service has detected that French is used on the page, and it matches the claimed language. Our system also found out that Autocool.fr 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.
autocool.fr
Open Graph description is not detected on the main page of Autocool. 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: