9.3 sec in total
1.6 sec
7.7 sec
77 ms
Click here to check amazing Flaneurz content for France. Otherwise, check out these important facts you probably never knew about flaneurz.com
Flaneurz offers the possibility to roll and walk with the same pair of shoes. Clip-on your sneakers to your rolling part and own the city.
Visit flaneurz.comWe analyzed Flaneurz.com page load time and found that the first response time was 1.6 sec and then it took 7.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
flaneurz.com performance score
name
value
score
weighting
Value4.2 s
20/100
10%
Value7.7 s
3/100
25%
Value11.6 s
4/100
10%
Value1,440 ms
15/100
30%
Value0.341
33/100
15%
Value33.3 s
0/100
10%
1564 ms
427 ms
272 ms
302 ms
6 ms
Our browser made a total of 73 requests to load all elements on the main page. We found that 97% of them (71 requests) were addressed to the original Flaneurz.com, 3% (2 requests) were made to Code.jquery.com. The less responsive or slowest element that took the longest time to load (4.2 sec) belongs to the original domain Flaneurz.com.
Page size can be reduced by 445.4 kB (34%)
1.3 MB
866.0 kB
In fact, the total size of Flaneurz.com main page is 1.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. 40% of websites need less resources to load. Images take 846.7 kB which makes up the majority of the site volume.
Potential reduce by 54.0 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 20.5 kB, which is 31% 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 54.0 kB or 83% of the original size.
Potential reduce by 61.6 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. Flaneurz images are well optimized though.
Potential reduce by 179.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 179.0 kB or 75% of the original size.
Potential reduce by 150.8 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. Flaneurz.com needs all CSS files to be minified and compressed as it can save up to 150.8 kB or 94% of the original size.
Number of requests can be reduced by 6 (10%)
61
55
The browser has sent 61 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Flaneurz. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 7 to 1 for JavaScripts and as a result speed up the page load time.
flaneurz.com
1564 ms
www.flaneurz.com
427 ms
app.css
272 ms
modernizr.js
302 ms
jquery-1.11.0.min.js
6 ms
jquery-migrate-1.2.1.min.js
8 ms
jquery.min.js
290 ms
foundation.min.js
386 ms
app.js
721 ms
flaneurzApp.js
189 ms
flaneurz.jpg
94 ms
kickstarter-badge-funded.png
156 ms
logoFlaneurzMobile.png
113 ms
iconFbMobile.png
156 ms
iconTwitterMobile.png
235 ms
iconTumblrMobile.png
770 ms
iconInstagramMobile.png
312 ms
iconYoutubeMobile.png
291 ms
imgVideo3.png
261 ms
top_ten.png
2600 ms
nike_blazer.png
3274 ms
reebok_exo_fit.png
657 ms
nike_force.png
669 ms
pantanal.png
955 ms
5sec.jpg
893 ms
bfm.jpg
2311 ms
bigumigu.jpg
1027 ms
stylist.jpg
1006 ms
jpeux-pas-j'ai-piscine.jpg
1049 ms
lci.jpg
2849 ms
chasseursdecool.jpg
1259 ms
futurascience.jpg
1167 ms
highsnobiety.jpg
1257 ms
konbini.jpg
1373 ms
Idesignme.jpg
1371 ms
leparisien.jpg
1709 ms
les-echos.jpg
1505 ms
G.jpg
1619 ms
lhm.jpg
1715 ms
intersection.jpg
1811 ms
M6.jpg
1806 ms
luckybird.jpg
3598 ms
RQ.jpg
1903 ms
FuturaStd-Light.svg
1960 ms
FuturaStd-Light.otf
2426 ms
FuturaStd-Light.woff
2289 ms
FuturaStd-Medium.svg
2350 ms
FuturaStd-Medium.woff
2423 ms
FuturaStd-Medium.otf
2633 ms
maddyness.jpg
2446 ms
madmoizelle.jpg
2463 ms
makerfaire.jpg
2485 ms
masculin.jpg
2516 ms
rel.jpg
2378 ms
pepsnews.jpg
2256 ms
lsdmag.jpg
2264 ms
gizmag.jpg
2261 ms
rtl2.jpg
2086 ms
stupiddope.jpg
2056 ms
thebergerie.jpg
2045 ms
thecornerlounge.jpg
2270 ms
W.jpg
2528 ms
free.jpg
2038 ms
huffingtonpost.jpg
4182 ms
theriderpost.jpg
2052 ms
wad.jpg
2018 ms
yahoo.jpg
2098 ms
minutebuzz.jpg
1913 ms
logoFlaneurz.png
1877 ms
kickstarterLogo.png
1827 ms
boursorama.jpg
1845 ms
FuturaStd-Light.ttf
1184 ms
FuturaStd-Medium.ttf
1040 ms
flaneurz.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
[role]s do not have all required [aria-*] attributes
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
<frame> or <iframe> elements do not have a title
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.
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>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
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.
flaneurz.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
Browser errors were logged to the console
Page has valid source maps
Issues were logged in the Issues panel in Chrome Devtools
flaneurz.com SEO score
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 doesn't use 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 Flaneurz.com 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 Flaneurz.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.
flaneurz.com
Open Graph description is not detected on the main page of Flaneurz. 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: