3.5 sec in total
169 ms
2.9 sec
442 ms
Click here to check amazing Thuasne content for France. Otherwise, check out these important facts you probably never knew about thuasne.fr
Thuasne crée et distribue des dispositifs médicaux. Spécialisés dans les orthèses, nous en proposons une large gamme pour chaque partie du corps (dos…
Visit thuasne.frWe analyzed Thuasne.fr page load time and found that the first response time was 169 ms and then it took 3.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
thuasne.fr performance score
name
value
score
weighting
Value3.7 s
31/100
10%
Value6.8 s
7/100
25%
Value5.8 s
49/100
10%
Value530 ms
55/100
30%
Value0.035
100/100
15%
Value6.7 s
56/100
10%
169 ms
359 ms
516 ms
79 ms
247 ms
Our browser made a total of 118 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Thuasne.fr, 94% (111 requests) were made to Fr.thuasne.com and 3% (3 requests) were made to Cdn.cookielaw.org. The less responsive or slowest element that took the longest time to load (633 ms) relates to the external source Fr.thuasne.com.
Page size can be reduced by 227.6 kB (11%)
2.0 MB
1.8 MB
In fact, the total size of Thuasne.fr main page is 2.0 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. 55% of websites need less resources to load. Images take 1.6 MB which makes up the majority of the site volume.
Potential reduce by 114.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. This page needs HTML code to be minified as it can gain 37.3 kB, which is 29% 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 114.4 kB or 89% of the original size.
Potential reduce by 83.8 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. Thuasne images are well optimized though.
Potential reduce by 16.1 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. This website has mostly compressed JavaScripts.
Potential reduce by 13.3 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. Thuasne.fr needs all CSS files to be minified and compressed as it can save up to 13.3 kB or 27% of the original size.
Number of requests can be reduced by 99 (88%)
113
14
The browser has sent 113 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Thuasne. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 53 to 1 for JavaScripts and from 48 to 1 for CSS and as a result speed up the page load time.
thuasne.fr
169 ms
fr.thuasne.com
359 ms
fr
516 ms
gtm.js
79 ms
vk_viewport.css
247 ms
wysiwyg.css
246 ms
clearfix.module.css
309 ms
hidden.module.css
313 ms
vk_video.css
313 ms
calendar.css
316 ms
calendar_multiday.css
316 ms
vk_lazy-load.css
316 ms
paragraphs.unpublished.css
376 ms
normalize.css
380 ms
normalize-fixes.css
382 ms
base.css
382 ms
grid.css
385 ms
viewport.css
383 ms
slick.css
443 ms
component--modal-search--layout.css
447 ms
component--mega-menu--layout.css
447 ms
component--language-switcher--layout.css
449 ms
component--country-switcher--layout.css
450 ms
component--header--layout.css
451 ms
component--footer--layout.css
510 ms
component--cta--layout.css
516 ms
component--breadcrumb--layout.css
516 ms
main.css
517 ms
additional.css
519 ms
component--slick-carousel--layout.css
519 ms
component--read-more--layout.css
577 ms
progress.css
584 ms
node.css
584 ms
base.css
528 ms
component--modal-search--state.css
531 ms
component--mega-menu--state.css
533 ms
component--language-switcher--state.css
590 ms
component--country-switcher--state.css
595 ms
component--read-more--state.css
597 ms
css
110 ms
otSDKStub.js
120 ms
component--read-more--state.css
419 ms
component--header--theme.css
418 ms
component--footer--theme.css
421 ms
component--cta--theme.css
416 ms
component--text-formatted--theme.css
415 ms
fonts.fr.css
415 ms
component--scroll-animations--theme.css
415 ms
component--paragraph--theme.css
416 ms
component--slider--theme.css
417 ms
component--reassurance--theme.css
415 ms
component--read-more--theme.css
413 ms
page--homepage--theme.css
414 ms
vk_console.js
418 ms
vk_request-animation-frame.js
420 ms
vk_url-search.js
419 ms
vk_in-array.js
415 ms
vk_throttle-debounce.js
413 ms
vk_pubsub.js
413 ms
vk_viewport.js
414 ms
jquery.min.js
633 ms
once.min.js
479 ms
fr_cEWfEQcaFnS0rY17f9BPM8Fv8Kzr7JumMEnQ9eqW02c.js
433 ms
util.js
427 ms
modal.js
431 ms
drupalSettingsLoader.js
432 ms
drupal.js
564 ms
drupal.init.js
606 ms
intersection-observer.js
548 ms
index.umd.min.js
542 ms
vk_get-body.js
540 ms
component--forms.js
541 ms
component--modal-search.js
539 ms
vk_transition-helper.js
589 ms
vk_transition-event.js
531 ms
vk_aria-toggle.js
524 ms
component--main-menu.js
526 ms
component--language-switcher.js
523 ms
component--country-switcher.js
520 ms
main-menu.js
564 ms
scroll.js
507 ms
progress.js
502 ms
loadjs.min.js
503 ms
debounce.js
503 ms
announce.js
500 ms
message.js
565 ms
ajax.js
576 ms
ajax.js
505 ms
vk_gtm.js
498 ms
vk_scroll-actions.js
497 ms
vk_lazy-load.js
496 ms
vk_scroll-animations.js
560 ms
vk_smooth-scroll.js
509 ms
vk_video.js
509 ms
wysiwyg.js
508 ms
6ed7f4dc-3c4b-4627-9160-47b659ad9f1d.json
59 ms
slick.js
438 ms
component--slider.js
498 ms
location
191 ms
component--reassurance.js
488 ms
text-clipper.js
488 ms
component--read-more.js
483 ms
component--read-more.js
351 ms
page--homepage.js
351 ms
roihu-regular.woff2
443 ms
logo.svg
374 ms
otBannerSdk.js
46 ms
bg-header_2.jpg
145 ms
roihu-regular.woff
203 ms
dos_push.png
296 ms
ortho_push.png
343 ms
compression_push.png
424 ms
lympho2_push_0.png
423 ms
Maintien_DOM_push.jpg
341 ms
product-lombastab2-lombastab2-106655461e61a65.jpg
295 ms
product-genustaice-genustart-ice-dsc-0916665545fd05505.png
297 ms
product-fastairc3-fastairc3-10665545ee81b79.jpg
341 ms
product-actionrel-actionrel-10665545af2836f.jpg
353 ms
thuasne.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
[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
Links do not have a discernible name
thuasne.fr 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
Page has valid source maps
thuasne.fr SEO score
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 Thuasne.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 Thuasne.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.
thuasne.fr
Open Graph description is not detected on the main page of Thuasne. 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: