Tools & Wizards About Us
tui.fr screenshot

Report Summary

  • 27

    Performance

    Renders faster than
    46% of other websites

  • 61

    Accessibility

    Visual factors better than
    that of 27% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 97

    SEO

    Google-friendlier than
    91% of websites

tui.fr

Réservez vos voyages TUI séjour, clubs vacances ou circuit en ligne ou en agence de voyage

Page Load Speed

2.3 sec in total

First Response

422 ms

Resources Loaded

1.5 sec

Page Rendered

362 ms

tui.fr screenshot

About Website

Welcome to tui.fr homepage info - get ready to check TUI best content for France right away, or after learning these important things about tui.fr

TUI conçoit des voyages pour toutes vos envies : clubs vacances, circuits, séjours. 200 agences de voyages. Bons Plans Voyage. Départs de régions. Meilleur Prix Garanti.

Visit tui.fr

Key Findings

We analyzed Tui.fr page load time and found that the first response time was 422 ms and then it took 1.9 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.

Performance Metrics

tui.fr performance score

27

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.6 s

65/100

10%

LCP (Largest Contentful Paint)

Value4.7 s

33/100

25%

SI (Speed Index)

Value5.5 s

55/100

10%

TBT (Total Blocking Time)

Value1,840 ms

9/100

30%

CLS (Cumulative Layout Shift)

Value0.511

15/100

15%

TTI (Time to Interactive)

Value12.0 s

16/100

10%

Network Requests Diagram

tui.fr

422 ms

jquery.fancybox.css

158 ms

global.css

248 ms

jquery-2.1.4.js

411 ms

jquery.fancybox.pack.js

246 ms

Our browser made a total of 23 requests to load all elements on the main page. We found that 22% of them (5 requests) were addressed to the original Tui.fr, 65% (15 requests) were made to Images.marmara.com and 9% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (920 ms) relates to the external source Images.marmara.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 293.4 kB (42%)

Content Size

698.5 kB

After Optimization

405.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Tui.fr main page is 698.5 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 25% of websites need less resources to load. Images take 328.4 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 25.2 kB

  • Original 30.7 kB
  • After minification 21.3 kB
  • After compression 5.5 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 9.4 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 25.2 kB or 82% of the original size.

Image Optimization

-0%

Potential reduce by 914 B

  • Original 328.4 kB
  • After minification 327.5 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. TUI images are well optimized though.

JavaScript Optimization

-78%

Potential reduce by 236.5 kB

  • Original 303.9 kB
  • After minification 177.1 kB
  • After compression 67.3 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 236.5 kB or 78% of the original size.

CSS Optimization

-87%

Potential reduce by 30.8 kB

  • Original 35.5 kB
  • After minification 22.2 kB
  • After compression 4.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. Tui.fr needs all CSS files to be minified and compressed as it can save up to 30.8 kB or 87% of the original size.

Requests Breakdown

Number of requests can be reduced by 11 (50%)

Requests Now

22

After Optimization

11

  • Images
  • JavaScript
  • CSS

The browser has sent 22 CSS, Javascripts, AJAX and image requests in order to completely render the main page of TUI. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 4 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

tui.fr

tui.fr

422 ms

jquery.fancybox.css

jquery.fancybox.css

158 ms

global.css

global.css

248 ms

jquery-2.1.4.js

jquery-2.1.4.js

411 ms

jquery.fancybox.pack.js

jquery.fancybox.pack.js

246 ms

gtm.js

gtm.js

63 ms

sprite-icones.png

sprite-icones.png

235 ms

loader.gif

loader.gif

135 ms

sprite-photos.jpg

sprite-photos.jpg

920 ms

uk.svg

uk.svg

131 ms

ch.svg

ch.svg

355 ms

at.svg

at.svg

133 ms

nl.svg

nl.svg

136 ms

pl.svg

pl.svg

138 ms

es.svg

es.svg

182 ms

de.svg

de.svg

353 ms

dk.svg

dk.svg

150 ms

be.svg

be.svg

154 ms

no.svg

no.svg

159 ms

se.svg

se.svg

465 ms

fi.svg

fi.svg

473 ms

analytics.js

analytics.js

22 ms

collect

collect

13 ms

Accessibility Review

tui.fr accessibility score

61

Accessibility Issues

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

High

[aria-*] attributes do not match their roles

High

[aria-hidden="true"] elements contain focusable descendents

High

ARIA input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

High

[aria-*] attributes do not have valid values

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

High

Buttons do not have an accessible name

High

Links do not have a discernible name

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

tui.fr best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

tui.fr SEO score

97

Search Engine Optimization Advices

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    FR

  • Language Claimed

    FR

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Tui.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 Tui.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.

Social Sharing Optimization

tui.fr

Open Graph description is not detected on the main page of TUI. 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: