6.5 sec in total
1.5 sec
4.7 sec
359 ms
Click here to check amazing Raoule content. Otherwise, check out these important facts you probably never knew about raoule.com
Trotinettes et vélos pliants électriques ou nons sur Raoule, une boutique spécialisée dans les déplacements urbains alternatifs pour citadins malins
Visit raoule.comWe analyzed Raoule.com page load time and found that the first response time was 1.5 sec and then it took 5 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
raoule.com performance score
name
value
score
weighting
Value2.7 s
59/100
10%
Value9.3 s
1/100
25%
Value7.8 s
24/100
10%
Value1,610 ms
12/100
30%
Value0.497
16/100
15%
Value13.6 s
11/100
10%
1468 ms
355 ms
24 ms
519 ms
176 ms
Our browser made a total of 91 requests to load all elements on the main page. We found that 47% of them (43 requests) were addressed to the original Raoule.com, 11% (10 requests) were made to Apis.google.com and 7% (6 requests) were made to Static.iadvize.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Raoule.com.
Page size can be reduced by 1.4 MB (54%)
2.6 MB
1.2 MB
In fact, the total size of Raoule.com main page is 2.6 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. 65% of websites need less resources to load. Javascripts take 1.5 MB which makes up the majority of the site volume.
Potential reduce by 143.4 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 143.4 kB or 76% of the original size.
Potential reduce by 21.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. Raoule images are well optimized though.
Potential reduce by 1.0 MB
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 1.0 MB or 68% of the original size.
Potential reduce by 173.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. Raoule.com needs all CSS files to be minified and compressed as it can save up to 173.9 kB or 83% of the original size.
Number of requests can be reduced by 44 (51%)
87
43
The browser has sent 87 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Raoule. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 30 to 1 for JavaScripts and as a result speed up the page load time.
www.raoule.com
1468 ms
7964f79c91fd7ffc87d17eccba232c5a_all.css
355 ms
css
24 ms
d4705c2b73b401540e41b42264daaff4.js
519 ms
bootstrap.min.js
176 ms
addthis_widget.js
12 ms
ga.js
28 ms
trame-fond.png
85 ms
bout-merappeler.png
87 ms
bout-chatenligne.png
85 ms
url_on.gif
158 ms
url_off.gif
159 ms
logo-8.jpg
238 ms
picto_satisfaction.png
161 ms
picto_livraison.png
166 ms
4-2.jpg
686 ms
5-2.jpg
936 ms
6-2.jpg
476 ms
mini-micro-jaune-evolutive.jpg
238 ms
mini-micro-bleu.jpg
246 ms
mini-micro-bleu-kit.jpg
406 ms
mini-micro-rouge-evolutive.jpg
402 ms
mini-micro-aqua.jpg
402 ms
picto-footer-puce-prev.png
422 ms
picto-footer-puce-next.png
447 ms
qaDmg_CNIuBGdKmH4z3spA.ttf
51 ms
fdSK0BiCsJzg1JgCoZQLEaCWcynf_cDxXwCLxiixG1c.ttf
56 ms
__utm.gif
20 ms
picto_panier.png
437 ms
bg_menu.png
437 ms
sep-menu.png
494 ms
picto-home.png
539 ms
fleche_titre_home.png
541 ms
trame-fond-bas.jpg
541 ms
trame-footer.jpg
573 ms
picto-footer-tel.png
615 ms
picto-footer-satisfait.png
617 ms
picto-footer-colis.png
617 ms
picto-footer-paiementligne.png
655 ms
picto-footer-temoignage1.png
683 ms
picto-footer-temoignage2.png
704 ms
picto-footer-temoignage2.png
703 ms
notation.png
700 ms
picto-footer-puce.png
732 ms
ajax-loader-small.gif
755 ms
pictos-footer-cartes.png
763 ms
pictos-footer-livraison.png
756 ms
chat_init.js
190 ms
index.php
617 ms
300lo.json
76 ms
fr.js
29 ms
all.js&version=v2.0
735 ms
widgets.js
24 ms
plusone.js
68 ms
counter.5524cceca805eb4b9b2b.js
14 ms
bouton-radio-diaporama.png
491 ms
storage.local.php
495 ms
sh.8e5f85691f9aaa082472a194.html
28 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
36 ms
shares.json
59 ms
cb=gapi.loaded_0
117 ms
cb=gapi.loaded_1
145 ms
fastbutton
174 ms
fastbutton
212 ms
layers.e5ea973510bf60b3db41.js
32 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.fr.html
87 ms
postmessageRelay
54 ms
rs=AGLTcCMZQMkD3nQb9neyXrDGlfp1IpCqrw
7 ms
cb=gapi.loaded_0
41 ms
cb=gapi.loaded_1
40 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
56 ms
3193398744-postmessagerelay.js
38 ms
rpc:shindig_random.js
68 ms
jot
98 ms
cb=gapi.loaded_0
3 ms
init.php
261 ms
jquery-1.8.1.min-noconflict.js
297 ms
mirror.min.0aba518c.js
340 ms
template.c501bb0b.js
187 ms
livechat.fc88d189.js
473 ms
mini.10dd7690.js
193 ms
widgetFloating.4a402c33.js
192 ms
62 ms
xd_arbiter.php
249 ms
xd_arbiter.php
456 ms
referrer.php
110 ms
poll
196 ms
ping
40 ms
like.php
79 ms
tEnfyhc8XtK.js
483 ms
LVx-xkvaJ0b.png
545 ms
raoule.com accessibility score
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
[id] attributes on active, focusable elements 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
Image elements do not have [alt] attributes
Links do not have a discernible name
raoule.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
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
raoule.com 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
FR
FR
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Raoule.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 Raoule.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.
raoule.com
Open Graph description is not detected on the main page of Raoule. 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: