Report Summary

  • 6

    Performance

    Renders faster than
    21% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 60% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

huahine.com

Huahine Guide - Resorts, Activities and Vacations | Tahiti.com

Page Load Speed

7.5 sec in total

First Response

291 ms

Resources Loaded

5.9 sec

Page Rendered

1.2 sec

huahine.com screenshot

About Website

Click here to check amazing Huahine content. Otherwise, check out these important facts you probably never knew about huahine.com

Huahine is an immense tropical jungle thriving with coconut plantations and vanilla. Huahine is also a culturally preserved sanctuary with sacred temples.

Visit huahine.com

Key Findings

We analyzed Huahine.com page load time and found that the first response time was 291 ms and then it took 7.2 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

huahine.com performance score

6

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value8.5 s

0/100

10%

LCP (Largest Contentful Paint)

Value22.0 s

0/100

25%

SI (Speed Index)

Value47.1 s

0/100

10%

TBT (Total Blocking Time)

Value49,190 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.279

43/100

15%

TTI (Time to Interactive)

Value77.4 s

0/100

10%

Network Requests Diagram

huahine.com

291 ms

huahine

237 ms

huahine

312 ms

jqueryBase

182 ms

angular

244 ms

Our browser made a total of 207 requests to load all elements on the main page. We found that 0% of them (1 request) were addressed to the original Huahine.com, 49% (101 requests) were made to Juicer.io and 28% (57 requests) were made to Tahiti.com. The less responsive or slowest element that took the longest time to load (1.9 sec) relates to the external source Tahiti.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 913.3 kB (6%)

Content Size

15.3 MB

After Optimization

14.4 MB

In fact, the total size of Huahine.com main page is 15.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. 85% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 14.6 MB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 289.7 kB

  • Original 331.4 kB
  • After minification 296.3 kB
  • After compression 41.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. This page needs HTML code to be minified as it can gain 35.1 kB, which is 11% 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 289.7 kB or 87% of the original size.

Image Optimization

-3%

Potential reduce by 474.9 kB

  • Original 14.6 MB
  • After minification 14.1 MB

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. Huahine images are well optimized though.

JavaScript Optimization

-34%

Potential reduce by 148.7 kB

  • Original 440.4 kB
  • After minification 424.2 kB
  • After compression 291.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 148.7 kB or 34% of the original size.

CSS Optimization

-0%

Potential reduce by 13 B

  • Original 17.7 kB
  • After minification 17.7 kB
  • After compression 17.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. Huahine.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 28 (15%)

Requests Now

183

After Optimization

155

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

Accessibility Review

huahine.com accessibility score

85

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 input fields do not have accessible names

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.

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

<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.

High

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

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

huahine.com 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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

huahine.com SEO score

86

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

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

High

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

Social Sharing Optimization

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