Tools & Wizards About Us
planetoscope.com screenshot

Report Summary

  • 16

    Performance

    Renders faster than
    30% of other websites

  • 60

    Accessibility

    Visual factors better than
    that of 26% of websites

  • 50

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 74

    SEO

    Google-friendlier than
    31% of websites

planetoscope.com

Statistiques mondiales écologiques

Page Load Speed

10.3 sec in total

First Response

634 ms

Resources Loaded

9.2 sec

Page Rendered

415 ms

planetoscope.com screenshot

About Website

Visit planetoscope.com now to see the best up-to-date Planetoscope content for Tunisia and also check out these interesting facts you probably never knew about planetoscope.com

Les statistiques mondiales en temps réel : écologie, pollution, démographie...

Visit planetoscope.com

Key Findings

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

planetoscope.com performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.7 s

5/100

10%

LCP (Largest Contentful Paint)

Value6.9 s

6/100

25%

SI (Speed Index)

Value11.6 s

4/100

10%

TBT (Total Blocking Time)

Value4,370 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.099

90/100

15%

TTI (Time to Interactive)

Value26.7 s

0/100

10%

Network Requests Diagram

planetoscope.com

634 ms

planetoscope.css

422 ms

widget.css

453 ms

stub

292 ms

cmp

795 ms

Our browser made a total of 108 requests to load all elements on the main page. We found that 63% of them (68 requests) were addressed to the original Planetoscope.com, 17% (18 requests) were made to Facebook.com and 6% (7 requests) were made to Encyclo-ecolo.com. The less responsive or slowest element that took the longest time to load (7.9 sec) relates to the external source Facebook.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 270.6 kB (22%)

Content Size

1.2 MB

After Optimization

970.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Planetoscope.com main page is 1.2 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. 60% of websites need less resources to load. Images take 817.1 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 81.1 kB

  • Original 98.0 kB
  • After minification 90.4 kB
  • After compression 16.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 81.1 kB or 83% of the original size.

Image Optimization

-2%

Potential reduce by 13.8 kB

  • Original 817.1 kB
  • After minification 803.3 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. Planetoscope images are well optimized though.

JavaScript Optimization

-50%

Potential reduce by 141.7 kB

  • Original 285.2 kB
  • After minification 268.4 kB
  • After compression 143.5 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 141.7 kB or 50% of the original size.

CSS Optimization

-83%

Potential reduce by 34.0 kB

  • Original 41.0 kB
  • After minification 31.7 kB
  • After compression 7.0 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. Planetoscope.com needs all CSS files to be minified and compressed as it can save up to 34.0 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 25 (27%)

Requests Now

94

After Optimization

69

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

planetoscope.com

planetoscope.com

634 ms

planetoscope.css

planetoscope.css

422 ms

widget.css

widget.css

453 ms

stub

stub

292 ms

cmp

cmp

795 ms

76 ms

planetoscope.js

planetoscope.js

237 ms

AC_RunActiveContent.js

AC_RunActiveContent.js

236 ms

fonctions.js

fonctions.js

239 ms

jquery-1.7.2.min.js

jquery-1.7.2.min.js

241 ms

jquery.plugin.cookie.min.js

jquery.plugin.cookie.min.js

314 ms

init.js

init.js

315 ms

jquery.simplemodal-1.3.min.js

jquery.simplemodal-1.3.min.js

320 ms

AC_RunActiveContent.js

AC_RunActiveContent.js

318 ms

planetoscope.js

planetoscope.js

241 ms

fonctions.js

fonctions.js

332 ms

jquery-1.7.2.min.js

jquery-1.7.2.min.js

461 ms

analytics.js

analytics.js

30 ms

js

js

61 ms

newsletter.css

newsletter.css

88 ms

jquery-plugin.js

jquery-plugin.js

311 ms

jquery.plugin.cookie.min.js

jquery.plugin.cookie.min.js

221 ms

init.js

init.js

325 ms

jquery.simplemodal-1.3.min.js

jquery.simplemodal-1.3.min.js

298 ms

newsletter.css

newsletter.css

294 ms

like.php

like.php

280 ms

like.php

like.php

414 ms

like.php

like.php

388 ms

like.php

like.php

378 ms

like.php

like.php

466 ms

like.php

like.php

393 ms

like.php

like.php

449 ms

like.php

like.php

534 ms

like.php

like.php

527 ms

like.php

like.php

615 ms

like.php

like.php

7926 ms

like.php

like.php

684 ms

like.php

like.php

617 ms

like.php

like.php

729 ms

like.php

like.php

776 ms

like.php

like.php

804 ms

like.php

like.php

761 ms

like.php

like.php

827 ms

accueil.jpg

accueil.jpg

551 ms

170px-Cours2.jpg

170px-Cours2.jpg

657 ms

barometre-entreprise.jpg

barometre-entreprise.jpg

577 ms

header_3.jpg

header_3.jpg

220 ms

btn_search.png

btn_search.png

220 ms

fond_menu.gif

fond_menu.gif

220 ms

rollover_menu_off.png

rollover_menu_off.png

219 ms

puce_fleche.gif

puce_fleche.gif

219 ms

fond_section.gif

fond_section.gif

218 ms

cg_recyclage.png

cg_recyclage.png

335 ms

bt_stat.png

bt_stat.png

335 ms

fond_section_stat.gif

fond_section_stat.gif

333 ms

compteur.gif

compteur.gif

333 ms

cg_dechet.png

cg_dechet.png

334 ms

scg_automobile.png

scg_automobile.png

334 ms

cg_biodiversite.png

cg_biodiversite.png

419 ms

cg_commerce.png

cg_commerce.png

501 ms

scg_elevage.png

scg_elevage.png

518 ms

scg_habitat.png

scg_habitat.png

500 ms

scg_fruit.png

scg_fruit.png

430 ms

scg_pollution.png

scg_pollution.png

434 ms

cg_energie.png

cg_energie.png

500 ms

cg_internet.png

cg_internet.png

516 ms

scg_eau.png

scg_eau.png

518 ms

cg_alimentation.png

cg_alimentation.png

580 ms

scg_mortalite.png

scg_mortalite.png

576 ms

cg_insolite.png

cg_insolite.png

582 ms

cg_demographie.jpg

cg_demographie.jpg

583 ms

sprite-planeto.png

sprite-planeto.png

593 ms

recyclage(1).jpg

recyclage(1).jpg

1329 ms

picto_encyclo-ecolo.gif

picto_encyclo-ecolo.gif

607 ms

logo-conso.png

logo-conso.png

296 ms

add.jpg

add.jpg

296 ms

170px-Bali2.jpg

170px-Bali2.jpg

651 ms

170px-Terre_pollu%C3%A9e2.jpg

170px-Terre_pollu%C3%A9e2.jpg

571 ms

170px-For%C3%AAt2.jpg

170px-For%C3%AAt2.jpg

655 ms

170px-Pollution2.jpg

170px-Pollution2.jpg

576 ms

170px-Ocean2.jpg

170px-Ocean2.jpg

684 ms

Avion2.jpg

Avion2.jpg

648 ms

fond_titre_nav.jpg

fond_titre_nav.jpg

575 ms

icone_facebook.gif

icone_facebook.gif

619 ms

fond_colonne.png

fond_colonne.png

627 ms

overlay.png

overlay.png

608 ms

icone_favori.gif

icone_favori.gif

602 ms

bt_haut.png

bt_haut.png

616 ms

logo_ee_up.png

logo_ee_up.png

351 ms

illustration_cd_roll.png

illustration_cd_roll.png

369 ms

collect

collect

105 ms

logo-planeto.png

logo-planeto.png

474 ms

collect

collect

38 ms

js

js

36 ms

9RkfBY4NJsx.js

9RkfBY4NJsx.js

39 ms

gWpQpSsEGQ-.png

gWpQpSsEGQ-.png

36 ms

ga-audiences

ga-audiences

66 ms

logo-conso.png

logo-conso.png

435 ms

add.jpg

add.jpg

446 ms

logo_cg_up.png

logo_cg_up.png

426 ms

logo_cd_up.png

logo_cd_up.png

426 ms

picto-fr.png

picto-fr.png

442 ms

picto-monde.png

picto-monde.png

443 ms

arrow_up.png

arrow_up.png

402 ms

logo_ee_up.png

logo_ee_up.png

412 ms

illustration_cg_roll.png

illustration_cg_roll.png

407 ms

illustration_ee_roll.png

illustration_ee_roll.png

497 ms

illustration_cd_roll.png

illustration_cd_roll.png

498 ms

Accessibility Review

planetoscope.com accessibility score

60

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

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

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

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

planetoscope.com best practices score

50

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

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

planetoscope.com SEO score

74

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    FR

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Planetoscope.com can be misinterpreted by Google and other search engines. Our service has detected that French 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 Planetoscope.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

planetoscope.com

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