Tools & Wizards About Us
plan.nc screenshot

Report Summary

  • 38

    Performance

    Renders faster than
    57% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 68% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

plan.nc

Annuaire des entreprises Plan.nc

Page Load Speed

785 ms in total

First Response

81 ms

Resources Loaded

625 ms

Page Rendered

79 ms

plan.nc screenshot

About Website

Welcome to plan.nc homepage info - get ready to check Plan best content for New Caledonia right away, or after learning these important things about plan.nc

Retrouvez toutes les entreprises en Nouvelle-Calédonie sur l'annuaire plan nc – PLAN.NC

Visit plan.nc

Key Findings

We analyzed Plan.nc page load time and found that the first response time was 81 ms and then it took 704 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.

Performance Metrics

plan.nc performance score

38

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.0 s

85/100

10%

LCP (Largest Contentful Paint)

Value5.3 s

22/100

25%

SI (Speed Index)

Value5.3 s

58/100

10%

TBT (Total Blocking Time)

Value2,200 ms

6/100

30%

CLS (Cumulative Layout Shift)

Value0.009

100/100

15%

TTI (Time to Interactive)

Value13.5 s

11/100

10%

Network Requests Diagram

plan.nc

81 ms

plan.nc

45 ms

piwik.js

492 ms

polyfill.min.js

204 ms

polyfill.js

203 ms

Our browser made a total of 21 requests to load all elements on the main page. We found that 90% of them (19 requests) were addressed to the original Plan.nc, 5% (1 request) were made to Plannc.matomo.cloud and 5% (1 request) were made to Cdn.polyfill.io. The less responsive or slowest element that took the longest time to load (492 ms) relates to the external source Plannc.matomo.cloud.

Page Optimization Overview & Recommendations

Page size can be reduced by 2.2 MB (78%)

Content Size

2.8 MB

After Optimization

622.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Plan.nc main page is 2.8 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. Javascripts take 2.1 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 151.0 kB

  • Original 184.5 kB
  • After minification 184.5 kB
  • After compression 33.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. 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 151.0 kB or 82% of the original size.

Image Optimization

-28%

Potential reduce by 66.2 kB

  • Original 232.7 kB
  • After minification 166.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. Obviously, Plan needs image optimization as it can save up to 66.2 kB or 28% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-82%

Potential reduce by 1.7 MB

  • Original 2.1 MB
  • After minification 1.4 MB
  • After compression 376.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 1.7 MB or 82% of the original size.

CSS Optimization

-85%

Potential reduce by 257.1 kB

  • Original 303.6 kB
  • After minification 220.3 kB
  • After compression 46.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. Plan.nc needs all CSS files to be minified and compressed as it can save up to 257.1 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 12 (80%)

Requests Now

15

After Optimization

3

  • Images
  • JavaScript

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

Network Requests Diagram

plan.nc

plan.nc

81 ms

plan.nc

plan.nc

45 ms

piwik.js

piwik.js

492 ms

polyfill.min.js

polyfill.min.js

204 ms

polyfill.js

polyfill.js

203 ms

component---src-pages-index-js.js

component---src-pages-index-js.js

231 ms

6034c53ecfc8d39796442ea01ee021fecfc730db.js

6034c53ecfc8d39796442ea01ee021fecfc730db.js

11 ms

49f6d0fdfb9f161b7902797113928b67c6bad6e5.js

49f6d0fdfb9f161b7902797113928b67c6bad6e5.js

11 ms

045760064478403115e3873c04ebb5ffb43e038d.js

045760064478403115e3873c04ebb5ffb43e038d.js

11 ms

b26c7e4b28abcb049839a02707aa37a3d2b111f0.js

b26c7e4b28abcb049839a02707aa37a3d2b111f0.js

11 ms

05d954cf.js

05d954cf.js

18 ms

styles.js

styles.js

15 ms

app.js

app.js

131 ms

framework.js

framework.js

25 ms

webpack-runtime.js

webpack-runtime.js

18 ms

logo-head.svg

logo-head.svg

130 ms

logo-mobile.svg

logo-mobile.svg

121 ms

4iCs6KVjbNBYlgoKfw7w.woff

4iCs6KVjbNBYlgoKfw7w.woff

130 ms

4iCv6KVjbNBYlgoC1CzjsGyL.woff

4iCv6KVjbNBYlgoC1CzjsGyL.woff

276 ms

plan_icon-71e65bca525516a6dfe0a73347556b72.ttf

plan_icon-71e65bca525516a6dfe0a73347556b72.ttf

4 ms

plan_categories-52fa5680547ca0f69dac77e10c8d5f9e.ttf

plan_categories-52fa5680547ca0f69dac77e10c8d5f9e.ttf

12 ms

Accessibility Review

plan.nc accessibility score

88

Accessibility Issues

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best Practices

plan.nc best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Requests the geolocation permission on page load

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

plan.nc SEO score

92

Search Engine Optimization Advices

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 Plan.nc 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 Plan.nc 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

plan.nc

Open Graph data is detected on the main page of Plan. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: