2.5 sec in total
256 ms
2 sec
242 ms
Visit nakamura.fr now to see the best up-to-date Nakamura content for France and also check out these interesting facts you probably never knew about nakamura.fr
Tous les vélos NAKAMURA, du vélo enfant au VTT downhill en passant par les vélos de course et les vélos électriques.
Visit nakamura.frWe analyzed Nakamura.fr page load time and found that the first response time was 256 ms and then it took 2.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
nakamura.fr performance score
name
value
score
weighting
Value5.6 s
5/100
10%
Value14.3 s
0/100
25%
Value10.8 s
6/100
10%
Value5,350 ms
0/100
30%
Value0.013
100/100
15%
Value20.3 s
2/100
10%
256 ms
299 ms
250 ms
244 ms
253 ms
Our browser made a total of 75 requests to load all elements on the main page. We found that 17% of them (13 requests) were addressed to the original Nakamura.fr, 23% (17 requests) were made to Css.ressource.nakamura.fr and 8% (6 requests) were made to Ressource.nakamura.fr. The less responsive or slowest element that took the longest time to load (518 ms) relates to the external source Media.nakamura.fr.
Page size can be reduced by 709.5 kB (44%)
1.6 MB
886.8 kB
In fact, the total size of Nakamura.fr main page is 1.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. 50% of websites need less resources to load. Javascripts take 725.2 kB which makes up the majority of the site volume.
Potential reduce by 52.7 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 52.7 kB or 83% of the original size.
Potential reduce by 32.3 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. Nakamura images are well optimized though.
Potential reduce by 528.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 528.6 kB or 73% of the original size.
Potential reduce by 95.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. Nakamura.fr needs all CSS files to be minified and compressed as it can save up to 95.9 kB or 81% of the original size.
Number of requests can be reduced by 20 (28%)
71
51
The browser has sent 71 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Nakamura. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
nakamura.fr
256 ms
www.nakamura.fr
299 ms
common.min.css
250 ms
nakamura.min.css
244 ms
minbrowseraddon.css
253 ms
print.css
256 ms
gigya.js
104 ms
jquery-1.7.2.min.js
366 ms
jquery.query-2.1.7.js
253 ms
analyticsmediator.js
251 ms
opentag-105234-1384119.js
14 ms
common.min.js
467 ms
newsletteraddon52.js
234 ms
minbrowseraddon.js
261 ms
nakamura.min.js
95 ms
8807346012190.png
84 ms
Guide04_470x300.jpg
304 ms
btn-moar.png
207 ms
Guide07_470x300.jpg
392 ms
8809541894174.jpg
361 ms
Guide12_220x220.jpg
251 ms
Guide17_220x220.jpg
251 ms
Guide19_220x220.jpg
361 ms
nakamurafb.jpg
339 ms
analytics.js
13 ms
t2s.min.js
233 ms
curves.png
82 ms
sprite-nakamura.png
193 ms
storesFacetSearchIcon.png
87 ms
header-comp-gradient.png
88 ms
header-comp-border.png
188 ms
btn-more-0.png
194 ms
intersport-logo-small.png
195 ms
smartserve-3374.js
184 ms
feedback-min.js
11 ms
collect
11 ms
frutiger_lt_std_roman.woff
252 ms
frutiger_lt_std_bold.woff
252 ms
spinner.gif
109 ms
json
148 ms
8807565787166.jpg
501 ms
8807565819934.jpg
323 ms
8807565852702.jpg
402 ms
overlay.png
101 ms
loading_background.png
101 ms
loading.gif
101 ms
controls.png
102 ms
PostData.js
4 ms
consent-widget-1.1.0.min.js
27 ms
gigya.services.plugins.base.min.js
40 ms
gigya.services.socialize.plugins.followbar.min.js
39 ms
gigya.services.socialize.plugins.login.min.js
34 ms
t
318 ms
q
310 ms
scrollingarrowl_left.gif
151 ms
scrollingarrowl_left.gif
43 ms
scrollingarrowl_left.gif
39 ms
scrollingarrowl_left.gif
141 ms
scrollingarrowl_disable_left.gif
60 ms
scrollingarrowl_right.gif
36 ms
scrollingarrowl_disable_right.gif
31 ms
icon-facebook.png
88 ms
scrollingarrowl_disable_left.gif
34 ms
scrollingarrowl_right.gif
37 ms
scrollingarrowl_disable_right.gif
32 ms
scrollingarrowl_disable_left.gif
58 ms
scrollingarrowl_right.gif
91 ms
scrollingarrowl_disable_right.gif
144 ms
scrollingarrowl_disable_left.gif
35 ms
scrollingarrowl_right.gif
90 ms
scrollingarrowl_disable_right.gif
143 ms
2252978AIA_Q1
324 ms
prod-curve.png
83 ms
2252946AKU_Q1
518 ms
5000827NN5_Q1
491 ms
nakamura.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
[aria-*] attributes do not match their roles
[aria-hidden="true"] elements contain focusable descendents
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
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
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.
nakamura.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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
nakamura.fr 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
![]()
FR
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Nakamura.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 Nakamura.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.
nakamura.fr
Open Graph description is not detected on the main page of Nakamura. 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: