Report Summary

  • 13

    Performance

    Renders faster than
    25% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 62% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

ora.pf

Ora - Forfait Mobile - Internet 4G - Internet Fibre

Page Load Speed

46.2 sec in total

First Response

1 sec

Resources Loaded

34 sec

Page Rendered

11.2 sec

ora.pf screenshot

About Website

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

Offres et abonnements Internet à Tahiti. Internet 4G à la maison sans attendre et sans ligne téléphonique. Internet fibre optique en haut débit et illimité.

Visit ora.pf

Key Findings

We analyzed Ora.pf page load time and found that the first response time was 1 sec and then it took 45.1 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.

Performance Metrics

ora.pf performance score

13

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value15.2 s

0/100

10%

LCP (Largest Contentful Paint)

Value21.4 s

0/100

25%

SI (Speed Index)

Value37.0 s

0/100

10%

TBT (Total Blocking Time)

Value15,250 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.106

88/100

15%

TTI (Time to Interactive)

Value40.5 s

0/100

10%

Network Requests Diagram

www.ora.pf

1034 ms

wp-emoji-release.min.js

571 ms

bk7p1.css

561 ms

css

60 ms

bk7p1.css

607 ms

Our browser made a total of 218 requests to load all elements on the main page. We found that 94% of them (205 requests) were addressed to the original Ora.pf, 2% (4 requests) were made to Code.jquery.com and 2% (4 requests) were made to Maps.googleapis.com. The less responsive or slowest element that took the longest time to load (8 sec) belongs to the original domain Ora.pf.

Page Optimization Overview & Recommendations

Page size can be reduced by 207.6 kB (10%)

Content Size

2.0 MB

After Optimization

1.8 MB

In fact, the total size of Ora.pf 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. 75% 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 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 168.9 kB

  • Original 208.0 kB
  • After minification 205.2 kB
  • After compression 39.0 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 168.9 kB or 81% of the original size.

Image Optimization

-2%

Potential reduce by 25.6 kB

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

JavaScript Optimization

-2%

Potential reduce by 8.8 kB

  • Original 445.1 kB
  • After minification 445.1 kB
  • After compression 436.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. This website has mostly compressed JavaScripts.

CSS Optimization

-2%

Potential reduce by 4.2 kB

  • Original 257.7 kB
  • After minification 257.7 kB
  • After compression 253.5 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. Ora.pf has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 172 (83%)

Requests Now

208

After Optimization

36

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

Accessibility Review

ora.pf accessibility score

86

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-hidden="true"] elements contain focusable descendents

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

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

ora.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

ora.pf 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

    FR

  • Language Claimed

    FR

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ora.pf 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 Ora.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 data is detected on the main page of Ora. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: