Report Summary

  • 12

    Performance

    Renders faster than
    25% of other websites

  • 73

    Accessibility

    Visual factors better than
    that of 39% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 79

    SEO

    Google-friendlier than
    40% of websites

airtahiti.pf

Air Tahiti, the airline connecting the islands of Tahiti - Official website - AIR TAHITI

Page Load Speed

6.8 sec in total

First Response

353 ms

Resources Loaded

6.1 sec

Page Rendered

365 ms

airtahiti.pf screenshot

About Website

Visit airtahiti.pf now to see the best up-to-date Air Tahiti content for French Polynesia and also check out these interesting facts you probably never knew about airtahiti.pf

Air Tahiti Official website – Book airline tickets for your inter-island travel in French Polynesia, browse our offers and discover our beautiful islands.

Visit airtahiti.pf

Key Findings

We analyzed Airtahiti.pf page load time and found that the first response time was 353 ms and then it took 6.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

airtahiti.pf performance score

12

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.1 s

1/100

10%

LCP (Largest Contentful Paint)

Value11.6 s

0/100

25%

SI (Speed Index)

Value12.2 s

3/100

10%

TBT (Total Blocking Time)

Value3,100 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0.158

74/100

15%

TTI (Time to Interactive)

Value25.4 s

0/100

10%

Network Requests Diagram

airtahiti.pf

353 ms

www.airtahiti.pf

649 ms

www.airtahiti.fr

900 ms

main.css

244 ms

main.css

293 ms

Our browser made a total of 76 requests to load all elements on the main page. We found that 3% of them (2 requests) were addressed to the original Airtahiti.pf, 95% (72 requests) were made to Airtahiti.fr and 3% (2 requests) were made to Ssl.google-analytics.com. The less responsive or slowest element that took the longest time to load (3.1 sec) relates to the external source Airtahiti.fr.

Page Optimization Overview & Recommendations

Page size can be reduced by 909.6 kB (41%)

Content Size

2.2 MB

After Optimization

1.3 MB

In fact, the total size of Airtahiti.pf main page is 2.2 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. 30% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 61.2 kB

  • Original 76.1 kB
  • After minification 75.0 kB
  • After compression 14.9 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 61.2 kB or 80% of the original size.

Image Optimization

-9%

Potential reduce by 94.9 kB

  • Original 1.1 MB
  • After minification 999.1 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. Air Tahiti images are well optimized though.

JavaScript Optimization

-67%

Potential reduce by 483.0 kB

  • Original 716.7 kB
  • After minification 706.5 kB
  • After compression 233.7 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 483.0 kB or 67% of the original size.

CSS Optimization

-84%

Potential reduce by 270.6 kB

  • Original 323.3 kB
  • After minification 315.1 kB
  • After compression 52.7 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. Airtahiti.pf needs all CSS files to be minified and compressed as it can save up to 270.6 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 43 (60%)

Requests Now

72

After Optimization

29

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

Accessibility Review

airtahiti.pf accessibility score

73

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

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.

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

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

airtahiti.pf best practices score

75

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

airtahiti.pf SEO score

79

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

High

Image elements do not have [alt] attributes

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    FR

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Airtahiti.pf can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed French language. Our system also found out that Airtahiti.pf 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

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