Tools & Wizards About Us
chronopost.com screenshot

Report Summary

  • 15

    Performance

    Renders faster than
    27% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 50

    Best Practices

    More advanced features
    available than in
    18% of websites

  • 76

    SEO

    Google-friendlier than
    35% of websites

chronopost.com

Accueil EN - Chronopost | Chronopost

Page Load Speed

2.4 sec in total

First Response

274 ms

Resources Loaded

1.9 sec

Page Rendered

190 ms

chronopost.com screenshot

About Website

Welcome to chronopost.com homepage info - get ready to check Chronopost best content for Egypt right away, or after learning these important things about chronopost.com

Envoyez vos colis en express en France et à l'international, suivez vos envois et découvrez tous les services de Chronopost.

Visit chronopost.com

Key Findings

We analyzed Chronopost.com page load time and found that the first response time was 274 ms and then it took 2.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.

Performance Metrics

chronopost.com performance score

15

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value8.3 s

0/100

10%

LCP (Largest Contentful Paint)

Value10.9 s

0/100

25%

SI (Speed Index)

Value13.5 s

2/100

10%

TBT (Total Blocking Time)

Value16,390 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.021

100/100

15%

TTI (Time to Interactive)

Value34.8 s

0/100

10%

Network Requests Diagram

en

274 ms

css__2V-O98JOWSIQ2a1GTvJR69Q63ho2BIZRwBHFk0fZvhg__YrH45CFWEzd9UXurJicL479FSXW01NoV_HBXtmSATOE__RMammJN8ZY3ds3TWCYIqbrwqh387OsexRitLTV7vynE.css

95 ms

css__ztLC7_77sWzO-fb7cU92zEKzYg-TPfQkk2lwTzqGPhk__fW_BDnRVH99F94rnYOT7OZ9NaEvhbh39O6NfpHoqgW4__RMammJN8ZY3ds3TWCYIqbrwqh387OsexRitLTV7vynE.css

270 ms

css__jQR_WDgdVau-mkV7XoqA89zCg9Bxf54CKWTXklCH-YU__5cV4kt7rWe67S9PutO25aJCi1q3n7hioszkVsIQdafE__RMammJN8ZY3ds3TWCYIqbrwqh387OsexRitLTV7vynE.css

282 ms

css__MMNpFwVGe9Q_ZjuXqJqyEhAz1raxizVJffoA9LJ8SjA__J-7q0OhWgk3ojKJFMupVR4KCaNmQAssaI6Tt0Hrgu7w__RMammJN8ZY3ds3TWCYIqbrwqh387OsexRitLTV7vynE.css

294 ms

Our browser made a total of 30 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Chronopost.com, 3% (1 request) were made to Googletagmanager.com and 3% (1 request) were made to Logc406.xiti.com. The less responsive or slowest element that took the longest time to load (533 ms) relates to the external source Chronopost.fr.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.1 MB (71%)

Content Size

1.5 MB

After Optimization

426.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Chronopost.com main page is 1.5 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. 40% of websites need less resources to load. CSS take 683.9 kB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 35.5 kB

  • Original 46.7 kB
  • After minification 42.0 kB
  • After compression 11.2 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 35.5 kB or 76% of the original size.

Image Optimization

-4%

Potential reduce by 8.8 kB

  • Original 229.5 kB
  • After minification 220.7 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. Chronopost images are well optimized though.

JavaScript Optimization

-83%

Potential reduce by 441.7 kB

  • Original 534.9 kB
  • After minification 331.3 kB
  • After compression 93.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 441.7 kB or 83% of the original size.

CSS Optimization

-85%

Potential reduce by 582.7 kB

  • Original 683.9 kB
  • After minification 668.0 kB
  • After compression 101.2 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. Chronopost.com needs all CSS files to be minified and compressed as it can save up to 582.7 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 8 (28%)

Requests Now

29

After Optimization

21

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

en

en

274 ms

css__2V-O98JOWSIQ2a1GTvJR69Q63ho2BIZRwBHFk0fZvhg__YrH45CFWEzd9UXurJicL479FSXW01NoV_HBXtmSATOE__RMammJN8ZY3ds3TWCYIqbrwqh387OsexRitLTV7vynE.css

css__2V-O98JOWSIQ2a1GTvJR69Q63ho2BIZRwBHFk0fZvhg__YrH45CFWEzd9UXurJicL479FSXW01NoV_HBXtmSATOE__RMammJN8ZY3ds3TWCYIqbrwqh387OsexRitLTV7vynE.css

95 ms

css__ztLC7_77sWzO-fb7cU92zEKzYg-TPfQkk2lwTzqGPhk__fW_BDnRVH99F94rnYOT7OZ9NaEvhbh39O6NfpHoqgW4__RMammJN8ZY3ds3TWCYIqbrwqh387OsexRitLTV7vynE.css

css__ztLC7_77sWzO-fb7cU92zEKzYg-TPfQkk2lwTzqGPhk__fW_BDnRVH99F94rnYOT7OZ9NaEvhbh39O6NfpHoqgW4__RMammJN8ZY3ds3TWCYIqbrwqh387OsexRitLTV7vynE.css

270 ms

css__jQR_WDgdVau-mkV7XoqA89zCg9Bxf54CKWTXklCH-YU__5cV4kt7rWe67S9PutO25aJCi1q3n7hioszkVsIQdafE__RMammJN8ZY3ds3TWCYIqbrwqh387OsexRitLTV7vynE.css

css__jQR_WDgdVau-mkV7XoqA89zCg9Bxf54CKWTXklCH-YU__5cV4kt7rWe67S9PutO25aJCi1q3n7hioszkVsIQdafE__RMammJN8ZY3ds3TWCYIqbrwqh387OsexRitLTV7vynE.css

282 ms

css__MMNpFwVGe9Q_ZjuXqJqyEhAz1raxizVJffoA9LJ8SjA__J-7q0OhWgk3ojKJFMupVR4KCaNmQAssaI6Tt0Hrgu7w__RMammJN8ZY3ds3TWCYIqbrwqh387OsexRitLTV7vynE.css

css__MMNpFwVGe9Q_ZjuXqJqyEhAz1raxizVJffoA9LJ8SjA__J-7q0OhWgk3ojKJFMupVR4KCaNmQAssaI6Tt0Hrgu7w__RMammJN8ZY3ds3TWCYIqbrwqh387OsexRitLTV7vynE.css

294 ms

js__j6xA2v62wDcRGF-wHf-K49v5QZMaI9VIICiFASAy2ls__uB2x17QpzKNVxcj-Tslc29Kx6kGAIf0tfw3ZzCc_aqU__RMammJN8ZY3ds3TWCYIqbrwqh387OsexRitLTV7vynE.js

js__j6xA2v62wDcRGF-wHf-K49v5QZMaI9VIICiFASAy2ls__uB2x17QpzKNVxcj-Tslc29Kx6kGAIf0tfw3ZzCc_aqU__RMammJN8ZY3ds3TWCYIqbrwqh387OsexRitLTV7vynE.js

450 ms

js__FpqD_lxCKykdzZwp0Wamaenlp7zkZqDJve3JgQBFB-U__rmJ4TVsXXxFWpN9w0IKSf5TxomDtmgFiA7Aqk_0srx0__RMammJN8ZY3ds3TWCYIqbrwqh387OsexRitLTV7vynE.js

js__FpqD_lxCKykdzZwp0Wamaenlp7zkZqDJve3JgQBFB-U__rmJ4TVsXXxFWpN9w0IKSf5TxomDtmgFiA7Aqk_0srx0__RMammJN8ZY3ds3TWCYIqbrwqh387OsexRitLTV7vynE.js

309 ms

js__WcTpt-w0y1FyXrxZNriX8Ts1KjsFTDpdvZaw9yhRn24__w5t7T5sSQWZqyRBRSI1jPKVo3qJ6imXeUlk0giATltQ__RMammJN8ZY3ds3TWCYIqbrwqh387OsexRitLTV7vynE.js

js__WcTpt-w0y1FyXrxZNriX8Ts1KjsFTDpdvZaw9yhRn24__w5t7T5sSQWZqyRBRSI1jPKVo3qJ6imXeUlk0giATltQ__RMammJN8ZY3ds3TWCYIqbrwqh387OsexRitLTV7vynE.js

184 ms

js__i11V-7AETPhfL9YzRpXBpECwVkYyQ_ahu2eHxES_mK0__Tgy2Gm7LmUJY8GXZeWxVbS51f3txED35LX1ul4UiOfk__RMammJN8ZY3ds3TWCYIqbrwqh387OsexRitLTV7vynE.js

js__i11V-7AETPhfL9YzRpXBpECwVkYyQ_ahu2eHxES_mK0__Tgy2Gm7LmUJY8GXZeWxVbS51f3txED35LX1ul4UiOfk__RMammJN8ZY3ds3TWCYIqbrwqh387OsexRitLTV7vynE.js

308 ms

xtcore.js

xtcore.js

359 ms

en.png

en.png

134 ms

fr.png

fr.png

135 ms

chronopost_logo.png

chronopost_logo.png

183 ms

045_femme_ban_940x350.jpg

045_femme_ban_940x350.jpg

184 ms

arrow.png

arrow.png

135 ms

106_chronokdo_ban_940x350_0.jpg

106_chronokdo_ban_940x350_0.jpg

182 ms

103_shanghai_ban_940x350.jpg

103_shanghai_ban_940x350.jpg

448 ms

arrow-gray.png

arrow-gray.png

182 ms

001_vehiculedos_bloc480x290.jpg

001_vehiculedos_bloc480x290.jpg

185 ms

003_fillecolis_bloc480x290.jpg

003_fillecolis_bloc480x290.jpg

363 ms

drop_down.png

drop_down.png

277 ms

logo_facebook.png

logo_facebook.png

274 ms

logo_twitter.png

logo_twitter.png

275 ms

dpd-logo.png

dpd-logo.png

278 ms

chronopost_logo_small.png

chronopost_logo_small.png

364 ms

PlutoSansDPDRegular-Web.woff

PlutoSansDPDRegular-Web.woff

533 ms

PlutoSansDPDLight-Web.woff

PlutoSansDPDLight-Web.woff

520 ms

glyphicons-halflings-regular.woff

glyphicons-halflings-regular.woff

347 ms

gtm.js

gtm.js

95 ms

hit.xiti

hit.xiti

197 ms

Accessibility Review

chronopost.com accessibility score

83

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 input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

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

Buttons do not have an accessible name

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.

Best Practices

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

Missing source maps for large first-party JavaScript

SEO Factors

chronopost.com SEO score

76

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

High

robots.txt is not valid

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 doesn't use legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

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

chronopost.com

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