8.4 sec in total
317 ms
7.6 sec
431 ms
Visit cityroul.com now to see the best up-to-date Cityroul content and also check out these interesting facts you probably never knew about cityroul.com
Rennes Autopartage : une voiture à partager en plein coeur de Rennes. Location de voitures en libre-service, pour une heure ou plus, dans des stations de proximité.
Visit cityroul.comWe analyzed Cityroul.com page load time and found that the first response time was 317 ms and then it took 8.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
cityroul.com performance score
name
value
score
weighting
Value4.0 s
23/100
10%
Value4.3 s
41/100
25%
Value7.7 s
24/100
10%
Value1,120 ms
23/100
30%
Value0.023
100/100
15%
Value16.3 s
5/100
10%
317 ms
1053 ms
288 ms
185 ms
187 ms
Our browser made a total of 100 requests to load all elements on the main page. We found that 79% of them (79 requests) were addressed to the original Cityroul.com, 4% (4 requests) were made to Use.typekit.net and 4% (4 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (5.1 sec) belongs to the original domain Cityroul.com.
Page size can be reduced by 871.5 kB (51%)
1.7 MB
844.6 kB
In fact, the total size of Cityroul.com 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. 60% of websites need less resources to load. Images take 630.6 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. 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 35.5 kB or 76% of the original size.
Potential reduce by 54.7 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. Cityroul images are well optimized though.
Potential reduce by 430.7 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 430.7 kB or 70% of the original size.
Potential reduce by 350.7 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. Cityroul.com needs all CSS files to be minified and compressed as it can save up to 350.7 kB or 83% of the original size.
Number of requests can be reduced by 65 (68%)
95
30
The browser has sent 95 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Cityroul. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 39 to 1 for JavaScripts and from 28 to 1 for CSS and as a result speed up the page load time.
cityroul.com
317 ms
www.cityroul.com
1053 ms
gabarit.css
288 ms
flexslider.css
185 ms
organic-shortcodes.css
187 ms
font-awesome.css
13 ms
dashicons.min.css
366 ms
thickbox.css
187 ms
validationEngine.jquery.css
187 ms
farbtastic.css
272 ms
organic-shortcodes.css
275 ms
organic-shortcodes-ie8.css
277 ms
pretty-photo.css
278 ms
style_shortcodes_esm.css
361 ms
tipTip.css
365 ms
style_shortcodes_ultimate.css
367 ms
style_accordeon_slider.css
367 ms
nivo-slider.css
371 ms
nivoslider.css
451 ms
jcarousel.css
451 ms
font-awesome.css
453 ms
font-awesome-ie7.css
459 ms
public.css
459 ms
public.css
460 ms
intermediaire_chaine_btt_tiny_mce.js
539 ms
jquery.js
654 ms
jquery-migrate.min.js
544 ms
jquery.custom.js
549 ms
jquery.fitVids.js
550 ms
jquery.modal.min.js
550 ms
retina.js
630 ms
superfish.js
559 ms
hoverIntent.js
563 ms
jquery.prettyPhoto.js
566 ms
actions.shortcodes.esm.js
565 ms
jquery.tipTip.minified.js
649 ms
init.js
652 ms
jcarousel.js
652 ms
widgets.js
25 ms
plusone.js
90 ms
pinit.js
71 ms
alr5fdp.js
164 ms
css
37 ms
css
48 ms
css
58 ms
style.css
751 ms
jquery.nivo.slider.pack.js
560 ms
nivoslider.js
568 ms
jwplayer.js
826 ms
jquery.tinysort.min.js
639 ms
public.js
560 ms
public.js
559 ms
selectivizr.min.js
561 ms
modernizr-2.6.2-respond-1.1.0.min.js
648 ms
css
13 ms
thickbox.js
635 ms
jquery.ui.core.min.js
564 ms
jquery.ui.widget.min.js
566 ms
jquery.ui.tabs.min.js
566 ms
jquery.ui.accordion.min.js
5074 ms
foundation.min.js
5077 ms
fastclick.js
5071 ms
jquery.flexslider-min.js
4991 ms
init_gabarit.js
4991 ms
cb=gapi.loaded_0
22 ms
3
86 ms
bg-3000.jpg
540 ms
p.gif
189 ms
pinit_main.js
191 ms
bg-1200.jpg
364 ms
sdk.js
135 ms
masthead.jpg
368 ms
logo-header.png
186 ms
site-description.png
130 ms
sprite.png
362 ms
bg-accueil-1200.jpg
535 ms
accueil-deco1.jpg
449 ms
Paque_CityRoul_Freepik-01-242x245.png
503 ms
Paque_CityRoul_Freepik-01.png
543 ms
201601_7stations-242x245.png
546 ms
201601_7stations.png
636 ms
201601_NouveauxVehicules-242x245.png
558 ms
201601_NouveauxVehicules.png
680 ms
20151012_NouvelEspace-DAccueil-01-242x245.png
626 ms
20151012_NouvelEspace-DAccueil-01.png
636 ms
voiture_intelligente-242x245.png
637 ms
voiture_intelligente.png
640 ms
accueil-deco2.jpg
719 ms
bg-footer-accueil-1200.jpg
725 ms
frise.png
726 ms
btn-dispo-smartphone.png
726 ms
analytics.js
83 ms
loadingAnimation.gif
611 ms
G4PSYQ8t_45C5CJXgAURpGLK9XhXKM_6y8PdPv_WnW9ff5zfggM9eMI6MK6f5Mb.eot
38 ms
fontawesome-webfont.woff
10 ms
XYor-FzfFtK55_a2_5-R50DuZKlJEbZ17SvO5YwOhjSff5DfggM9eMI6MK6f5Mt.eot
86 ms
233 ms
logo-header-large.png
604 ms
xd_arbiter.php
34 ms
xd_arbiter.php
60 ms
cityroul.com 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.
cityroul.com 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
cityroul.com 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 Cityroul.com 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 Cityroul.com 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.
cityroul.com
Open Graph description is not detected on the main page of Cityroul. 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: