Tools & Wizards About Us
plani.fr screenshot

Report Summary

  • 21

    Performance

    Renders faster than
    39% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 68% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

plani.fr

Plani - Plani.fr | Atelier Plani, PlaniMonteur, PlaniPresse et PlaniCorp

Page Load Speed

2.6 sec in total

First Response

243 ms

Resources Loaded

2.2 sec

Page Rendered

121 ms

plani.fr screenshot

About Website

Welcome to plani.fr homepage info - get ready to check Plani best content for France right away, or after learning these important things about plani.fr

PLANI | À vos côtés, du tournage à la diffusion ! Situé à Paris, de part et d'autre de la Seine, à deux pas des grands pôles audiovisuels français.

Visit plani.fr

Key Findings

We analyzed Plani.fr page load time and found that the first response time was 243 ms and then it took 2.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

plani.fr performance score

21

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.3 s

7/100

10%

LCP (Largest Contentful Paint)

Value15.6 s

0/100

25%

SI (Speed Index)

Value13.5 s

2/100

10%

TBT (Total Blocking Time)

Value1,400 ms

16/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value17.8 s

4/100

10%

Network Requests Diagram

plani.fr

243 ms

plani.studio

477 ms

style.min.css

167 ms

sr7.css

241 ms

js_composer.min.css

405 ms

Our browser made a total of 91 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Plani.fr, 88% (80 requests) were made to Plani.studio and 4% (4 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (838 ms) relates to the external source Plani.studio.

Page Optimization Overview & Recommendations

Page size can be reduced by 423.2 kB (33%)

Content Size

1.3 MB

After Optimization

856.4 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Plani.fr main page is 1.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. 50% of websites need less resources to load. Images take 616.9 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 90.7 kB

  • Original 115.8 kB
  • After minification 114.2 kB
  • After compression 25.1 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 90.7 kB or 78% of the original size.

Image Optimization

-0%

Potential reduce by 817 B

  • Original 616.9 kB
  • After minification 616.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. Plani images are well optimized though.

JavaScript Optimization

-61%

Potential reduce by 331.7 kB

  • Original 546.9 kB
  • After minification 546.9 kB
  • After compression 215.2 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 331.7 kB or 61% of the original size.

Requests Breakdown

Number of requests can be reduced by 73 (88%)

Requests Now

83

After Optimization

10

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

plani.fr

plani.fr

243 ms

plani.studio

plani.studio

477 ms

style.min.css

style.min.css

167 ms

sr7.css

sr7.css

241 ms

js_composer.min.css

js_composer.min.css

405 ms

bootstrap-light.min.css

bootstrap-light.min.css

240 ms

base.min.css

base.min.css

245 ms

widget-wd-recent-posts.min.css

widget-wd-recent-posts.min.css

248 ms

footer-sticky.min.css

footer-sticky.min.css

257 ms

wp-gutenberg.min.css

wp-gutenberg.min.css

320 ms

int-wpcf7.min.css

int-wpcf7.min.css

318 ms

int-rev-slider.min.css

int-rev-slider.min.css

325 ms

int-wpb-base.min.css

int-wpb-base.min.css

331 ms

int-wpb-base-deprecated.min.css

int-wpb-base-deprecated.min.css

340 ms

woo-opt-sticky-notices.min.css

woo-opt-sticky-notices.min.css

397 ms

woocommerce-base.min.css

woocommerce-base.min.css

398 ms

mod-star-rating.min.css

mod-star-rating.min.css

416 ms

woo-el-track-order.min.css

woo-el-track-order.min.css

416 ms

woo-mod-block-notices.min.css

woo-mod-block-notices.min.css

425 ms

woo-gutenberg.min.css

woo-gutenberg.min.css

475 ms

style.css

style.css

477 ms

header-base.min.css

header-base.min.css

479 ms

mod-tools.min.css

mod-tools.min.css

484 ms

header-el-base.min.css

header-el-base.min.css

495 ms

header-el-mobile-nav-dropdown.min.css

header-el-mobile-nav-dropdown.min.css

508 ms

int-wbp-el-animations.min.css

int-wbp-el-animations.min.css

553 ms

footer-base.min.css

footer-base.min.css

555 ms

opt-scrolltotop.min.css

opt-scrolltotop.min.css

557 ms

wd-search-form.min.css

wd-search-form.min.css

564 ms

opt-cookies.min.css

opt-cookies.min.css

578 ms

css

css

36 ms

tptools.js

tptools.js

788 ms

sr7.js

sr7.js

838 ms

jquery.min.js

jquery.min.js

716 ms

jquery-migrate.min.js

jquery-migrate.min.js

635 ms

jquery.blockUI.min.js

jquery.blockUI.min.js

643 ms

add-to-cart.min.js

add-to-cart.min.js

659 ms

js.cookie.min.js

js.cookie.min.js

715 ms

js

js

70 ms

api.js

api.js

36 ms

wc-blocks.css

wc-blocks.css

714 ms

animate.min.css

animate.min.css

625 ms

owl.min.css

owl.min.css

606 ms

v4-shims.min.css

v4-shims.min.css

607 ms

all.min.css

all.min.css

603 ms

woocommerce.min.js

woocommerce.min.js

613 ms

woocommerce-add-to-cart.js

woocommerce-add-to-cart.js

623 ms

device.min.js

device.min.js

575 ms

scrollBar.min.js

scrollBar.min.js

575 ms

updateCartFragmentsFix.js

updateCartFragmentsFix.js

568 ms

sourcebuster.min.js

sourcebuster.min.js

570 ms

order-attribution.min.js

order-attribution.min.js

593 ms

inspector.js

inspector.js

592 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

591 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

574 ms

wp-polyfill.min.js

wp-polyfill.min.js

573 ms

index.js

index.js

595 ms

js_composer_front.min.js

js_composer_front.min.js

595 ms

helpers.min.js

helpers.min.js

573 ms

woocommerceNotices.min.js

woocommerceNotices.min.js

574 ms

imagesloaded.min.js

imagesloaded.min.js

571 ms

stickyFooter.min.js

stickyFooter.min.js

567 ms

headerBuilder.min.js

headerBuilder.min.js

566 ms

menuOffsets.min.js

menuOffsets.min.js

582 ms

menuSetUp.min.js

menuSetUp.min.js

579 ms

vc-waypoints.min.js

vc-waypoints.min.js

573 ms

masonry.pkgd.min.js

masonry.pkgd.min.js

573 ms

owl.carousel.min.js

owl.carousel.min.js

566 ms

imagesloaded.pkgd.min.js

imagesloaded.pkgd.min.js

560 ms

underscore.min.js

underscore.min.js

536 ms

vc_grid.min.js

vc_grid.min.js

563 ms

scrollTop.min.js

scrollTop.min.js

549 ms

mobileNavigation.min.js

mobileNavigation.min.js

493 ms

cookiesPopup.min.js

cookiesPopup.min.js

430 ms

lazyload.min.js

lazyload.min.js

466 ms

uk-35x20-1.jpg

uk-35x20-1.jpg

474 ms

be.js

be.js

67 ms

fr-35x20-1.jpg

fr-35x20-1.jpg

451 ms

logo.jpg

logo.jpg

451 ms

planipresse.jpg

planipresse.jpg

618 ms

planimonteur-1.jpg

planimonteur-1.jpg

618 ms

planicorp.jpg

planicorp.jpg

616 ms

pxiByp8kv8JHgFVrLEj6Z1xlEA.ttf

pxiByp8kv8JHgFVrLEj6Z1xlEA.ttf

45 ms

pxiByp8kv8JHgFVrLCz7Z1xlEA.ttf

pxiByp8kv8JHgFVrLCz7Z1xlEA.ttf

54 ms

pxiByp8kv8JHgFVrLGT9Z1xlEA.ttf

pxiByp8kv8JHgFVrLGT9Z1xlEA.ttf

71 ms

pxiEyp8kv8JHgFVrJJfedw.ttf

pxiEyp8kv8JHgFVrJJfedw.ttf

70 ms

atelierplani.jpg

atelierplani.jpg

733 ms

recaptcha__en.js

recaptcha__en.js

57 ms

fa-solid-900.woff

fa-solid-900.woff

577 ms

fa-regular-400.woff

fa-regular-400.woff

484 ms

c3po.jpg

c3po.jpg

129 ms

Accessibility Review

plani.fr accessibility score

88

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.

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

plani.fr best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

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

SEO Factors

plani.fr SEO score

100

Search Engine Optimization Advices

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 Plani.fr 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 Plani.fr 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

plani.fr

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