6.4 sec in total
244 ms
5.3 sec
900 ms
Welcome to wee-bot.com homepage info - get ready to check Weebot best content for France right away, or after learning these important things about wee-bot.com
Weebot est la Marque Trottinette Électrique et Vélo Électrique N°1 en France. Batterie Samsung et de la Norme CE. Trottinette Meilleur Prix. Garantie 2 ans et SAV France. Livraison Gratuite Rapide par...
Visit wee-bot.comWe analyzed Wee-bot.com page load time and found that the first response time was 244 ms and then it took 6.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
wee-bot.com performance score
name
value
score
weighting
Value5.4 s
6/100
10%
Value33.4 s
0/100
25%
Value45.7 s
0/100
10%
Value79,640 ms
0/100
30%
Value0.063
97/100
15%
Value102.6 s
0/100
10%
244 ms
298 ms
107 ms
103 ms
98 ms
Our browser made a total of 149 requests to load all elements on the main page. We found that 1% of them (2 requests) were addressed to the original Wee-bot.com, 26% (39 requests) were made to Cdn.shopify.com and 11% (16 requests) were made to Herowelcomebar.appspot.com. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Scontent.cdninstagram.com.
Page size can be reduced by 883.3 kB (38%)
2.3 MB
1.4 MB
In fact, the total size of Wee-bot.com main page is 2.3 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 1.0 MB which makes up the majority of the site volume.
Potential reduce by 60.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 10.8 kB, which is 14% 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 60.8 kB or 81% of the original size.
Potential reduce by 24.0 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. Weebot images are well optimized though.
Potential reduce by 574.0 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 574.0 kB or 64% of the original size.
Potential reduce by 224.4 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. Wee-bot.com needs all CSS files to be minified and compressed as it can save up to 224.4 kB or 70% of the original size.
Number of requests can be reduced by 80 (58%)
137
57
The browser has sent 137 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Weebot. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 51 to 1 for JavaScripts and from 15 to 1 for CSS and as a result speed up the page load time.
www.wee-bot.com
244 ms
fbevents.js
298 ms
timber.scss.css
107 ms
theme.scss.css
103 ms
css
98 ms
css
99 ms
ga_urchin_forms-0826cdefee6590321eb5c0c435eeebf7a8425a5493a9e95059c40e07e069ad52.js
100 ms
jquery.min.js
11 ms
modernizr.min.js
125 ms
fastclick.min.js
152 ms
timber.js
102 ms
theme.js
154 ms
slick.min.js
159 ms
slick-theme.js
158 ms
handlebars.min.js
160 ms
ajax-cart.js
156 ms
conversion.js
151 ms
4mkapps.insta.min.js
171 ms
widget_v2.134.js
21 ms
shopify_stats.js
233 ms
trekkie.storefront.min.js
272 ms
shop_events_listener-dabe00038c134ebede3c66ef50bfdcedb847ac379226dfb9a22bbf438ac8dbef.js
234 ms
logo.png
201 ms
logo-inverted.png
202 ms
hero_slide_1.jpg
214 ms
hhh6_1024x1024.png
202 ms
45_1024x1024.png
203 ms
4587_1024x1024.jpg
229 ms
1478_36ce2d27-30ef-41ca-8d96-730cf1421fd7_1024x1024.jpg
290 ms
458_1024x1024.jpg
334 ms
geeko_3186ef89-9bac-456d-8a51-b1e18e87ec6d_large.png
228 ms
Ms921pUt_400x400_03003f20-39ae-405c-96af-cd2c84a230e5_large.png
228 ms
hoverboard_paris_weebot_self_balancing_large.png
229 ms
IMAGE_53_79e723eb-d006-41db-95ed-037c976144e6_large.png
274 ms
logo10451_1_2_large.jpg
275 ms
tf1_0e6f49c9-dbad-4b03-bb26-951df10ad24a_large.png
275 ms
blue_large.jpg
274 ms
b_large.jpg
333 ms
r_large.jpg
363 ms
bl_large.jpg
331 ms
insta_bg_image.png
331 ms
378 ms
images
670 ms
ajax-loader.gif
196 ms
5-AYViExptypIdFoLKAxTA.woff
133 ms
cJZKeOuBrn4kERxqtaUH3T8E0i7KZn-EPnyo3HZu7kw.woff
145 ms
icons.woff
220 ms
icons.woff
219 ms
156959106
144 ms
__$$__stringtable_lang_fr.js
66 ms
315 ms
435 ms
identify
357 ms
player.js
220 ms
player.css
328 ms
ga.js
159 ms
vuid.min.js
341 ms
record.gif
208 ms
analytics.js
104 ms
269 ms
collect
22 ms
collect
248 ms
page
237 ms
__utm.gif
147 ms
proxy.html
120 ms
558114272.jpg
210 ms
11199745_60x60.jpg
136 ms
12784109_1746401112256096_1050126101_n.jpg
434 ms
slider-left.png
47 ms
12747674_1660225294245046_1192249264_n.jpg
899 ms
12716693_1697988717111899_144812077_n.jpg
1097 ms
12479166_586726521481258_831164655_n.jpg
1033 ms
12534087_1551017381889330_1976220245_n.jpg
1033 ms
12383296_1737041033196857_98130450_n.jpg
1071 ms
12547599_1643131069283601_1924632282_n.jpg
1183 ms
12519205_1644020519191960_318337907_n.jpg
1031 ms
10632197_1491116401195939_668942542_n.jpg
1181 ms
12394001_1044124085640580_1939481789_n.jpg
1142 ms
12346209_1674075669472597_1872058952_n.jpg
1242 ms
slider-right.png
22 ms
nr-885.min.js
55 ms
689d5b4562
102 ms
avatar_simple_visitor.png
109 ms
aL63HcygAAVYuCCsAAA==
1 ms
loader.js
376 ms
spr.js
42 ms
1458392773.js
798 ms
spr.css
26 ms
jquery.min.js
10 ms
badges
83 ms
5vUXXlOlpHicY2BigAAuBuyAlYGBkZmRhZGVkY01syQ114CluCSxiAtE6KbmFpRUcoKZGYk5abxwlm5iTgkDAwCe8RByAABLuADIUlixAQGOWbkIAAgAYyCwASNEsAMjcLIEKAlFUkSyCgIHKrEGAUSxJAGIUViwQIhYsQYDRLEmAYhRWLgEAIhYsQYBRFlZWVm4Af+FsASNsQUARAAA
1 ms
font-awesome-stars.svg
96 ms
inffuse.js
119 ms
script.js
117 ms
widget.html
76 ms
css
91 ms
css
98 ms
css
114 ms
ui-lib.min.css
82 ms
jquery-latest.min.js
49 ms
jquery-ui.js
77 ms
angular.js
78 ms
jquery.jrumble.1.3.js
69 ms
widget.js
185 ms
notify.js
67 ms
jquery.fontselector.js
60 ms
fontselector.css
181 ms
widget.css
78 ms
animate.css
195 ms
jquery.fittext.js
85 ms
jquery.lettering.js
86 ms
jquery.textillate.js
85 ms
jquery.marquee.min.js
195 ms
sca-pp.css
75 ms
css
77 ms
sca-pp.min.js
88 ms
inffuse.js
887 ms
json2.min.js
95 ms
cart.js
106 ms
gift.png
14 ms
mega-close.png
14 ms
xgzbb53t8j-Mo-vYa23n5nhCUOGz7vYGh680lGh-uXM.woff
13 ms
widgets.js
41 ms
mixpanel-2-latest.min.js
146 ms
white_logo2.png
21 ms
close.png
25 ms
sdk.js
264 ms
cJZKeOuBrn4kERxqtaUH3T8E0i7KZn-EPnyo3HZu7kw.woff
51 ms
k3k702ZOKiLJc3WVjuplzHhCUOGz7vYGh680lGh-uXM.woff
52 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
4 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.en.html
30 ms
38 ms
32 ms
19 ms
jot
98 ms
57 ms
xd_arbiter.php
353 ms
n73m7muf
103 ms
12 ms
like.php
101 ms
intercom.21a35ffd.js
88 ms
TY3MhkXpWJ-.js
347 ms
LVx-xkvaJ0b.png
427 ms
ping
203 ms
echo.515e8809.js
12 ms
icon-preview-close.ec1a68fc.png
15 ms
client-test
128 ms
client-test
108 ms
TY3MhkXpWJ-.js
122 ms
wee-bot.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
[aria-*] attributes do not match their roles
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
wee-bot.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
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
wee-bot.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
Tap targets are not sized appropriately
FR
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Wee-bot.com can be misinterpreted by Google and other search engines. Our service has detected that French is used on the page, and it does not match the claimed English language. Our system also found out that Wee-bot.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.
wee-bot.com
Open Graph data is detected on the main page of Weebot. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: