Tools & Wizards About Us

Report Summary

  • 66

    Performance

    Renders faster than
    79% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 89% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 89

    SEO

    Google-friendlier than
    67% of websites

ifrecor.org

Page Load Speed

10.5 sec in total

First Response

246 ms

Resources Loaded

9.8 sec

Page Rendered

452 ms

About Website

Visit ifrecor.org now to see the best up-to-date Ifrecor content and also check out these interesting facts you probably never knew about ifrecor.org

L’Initiative Française sur les Récifs Coralliens (IFRECOR) est une action nationale en faveur des récifs coralliens des collectivités de l’outre-mer français, engagée sur décision du premier ministre....

Visit ifrecor.org

Key Findings

We analyzed Ifrecor.org page load time and found that the first response time was 246 ms and then it took 10.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

ifrecor.org performance score

66

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.0 s

23/100

10%

LCP (Largest Contentful Paint)

Value5.0 s

27/100

25%

SI (Speed Index)

Value6.9 s

33/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value4.0 s

87/100

10%

Network Requests Diagram

ifrecor.org

246 ms

www.ifrecor.org

267 ms

www.ifrecor.com

778 ms

style.css

169 ms

nav.css

171 ms

Our browser made a total of 103 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Ifrecor.org, 62% (64 requests) were made to Ifrecor.com and 17% (18 requests) were made to Maps.googleapis.com. The less responsive or slowest element that took the longest time to load (7.1 sec) relates to the external source Ifrecor.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 979.9 kB (27%)

Content Size

3.7 MB

After Optimization

2.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Ifrecor.org main page is 3.7 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. 65% of websites need less resources to load. Images take 2.4 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 47.9 kB

  • Original 58.8 kB
  • After minification 56.8 kB
  • After compression 10.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 47.9 kB or 82% of the original size.

Image Optimization

-2%

Potential reduce by 55.7 kB

  • Original 2.4 MB
  • After minification 2.4 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. Ifrecor images are well optimized though.

JavaScript Optimization

-74%

Potential reduce by 821.4 kB

  • Original 1.1 MB
  • After minification 983.1 kB
  • After compression 293.0 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 821.4 kB or 74% of the original size.

CSS Optimization

-86%

Potential reduce by 54.9 kB

  • Original 63.7 kB
  • After minification 52.8 kB
  • After compression 8.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. Ifrecor.org needs all CSS files to be minified and compressed as it can save up to 54.9 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 37 (41%)

Requests Now

90

After Optimization

53

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

ifrecor.org accessibility score

96

Accessibility Issues

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

Links do not have a discernible name

Best Practices

ifrecor.org best practices score

67

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

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

ifrecor.org SEO score

89

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

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

    JA

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ifrecor.org can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Ifrecor.org 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 Ifrecor. 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: