Tools & Wizards About Us
containerinfo.net screenshot

Report Summary

  • 54

    Performance

    Renders faster than
    72% of other websites

  • 63

    Accessibility

    Visual factors better than
    that of 28% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 67

    SEO

    Google-friendlier than
    25% of websites

containerinfo.net

Le container ou conteneur

Page Load Speed

22 sec in total

First Response

446 ms

Resources Loaded

21.4 sec

Page Rendered

206 ms

containerinfo.net screenshot

About Website

Click here to check amazing Container Info content for France. Otherwise, check out these important facts you probably never knew about containerinfo.net

Tout savoir sur les containers ou conteneurs maritimes de transport ainsi que sur leur usage terrestre et où acheter un container d'occasion

Visit containerinfo.net

Key Findings

We analyzed Containerinfo.net page load time and found that the first response time was 446 ms and then it took 21.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster. Unfortunately, there were 2 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

containerinfo.net performance score

54

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.6 s

94/100

10%

LCP (Largest Contentful Paint)

Value5.2 s

23/100

25%

SI (Speed Index)

Value3.5 s

88/100

10%

TBT (Total Blocking Time)

Value770 ms

38/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value8.2 s

41/100

10%

Network Requests Diagram

containerinfo.net

446 ms

acasrule.gif

329 ms

home_cmp_cascade110_vbtn_p.gif

105 ms

home_cmp_cascade110_vbtn_a.gif

198 ms

le_container.htm_cmp_cascade110_vbtn.gif

203 ms

Our browser made a total of 44 requests to load all elements on the main page. We found that 75% of them (33 requests) were addressed to the original Containerinfo.net, 7% (3 requests) were made to Perso.estat.com and 7% (3 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (19.7 sec) relates to the external source Hades.bubblestat.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 115.0 kB (70%)

Content Size

165.3 kB

After Optimization

50.4 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Containerinfo.net main page is 165.3 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 15% of websites need less resources to load. Javascripts take 139.7 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 12.6 kB

  • Original 16.1 kB
  • After minification 15.5 kB
  • After compression 3.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 12.6 kB or 78% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 9.5 kB
  • After minification 9.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. Container Info images are well optimized though.

JavaScript Optimization

-73%

Potential reduce by 102.4 kB

  • Original 139.7 kB
  • After minification 131.3 kB
  • After compression 37.4 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 102.4 kB or 73% of the original size.

Requests Breakdown

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

Requests Now

40

After Optimization

5

  • AJAX
  • Images
  • JavaScript

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

Network Requests Diagram

containerinfo.net

containerinfo.net

446 ms

acasrule.gif

acasrule.gif

329 ms

home_cmp_cascade110_vbtn_p.gif

home_cmp_cascade110_vbtn_p.gif

105 ms

home_cmp_cascade110_vbtn_a.gif

home_cmp_cascade110_vbtn_a.gif

198 ms

le_container.htm_cmp_cascade110_vbtn.gif

le_container.htm_cmp_cascade110_vbtn.gif

203 ms

le_container.htm_cmp_cascade110_vbtn_a.gif

le_container.htm_cmp_cascade110_vbtn_a.gif

203 ms

avantages.htm_cmp_cascade110_vbtn.gif

avantages.htm_cmp_cascade110_vbtn.gif

200 ms

avantages.htm_cmp_cascade110_vbtn_a.gif

avantages.htm_cmp_cascade110_vbtn_a.gif

202 ms

mini-container.htm_cmp_cascade110_vbtn.gif

mini-container.htm_cmp_cascade110_vbtn.gif

198 ms

mini-container.htm_cmp_cascade110_vbtn_a.gif

mini-container.htm_cmp_cascade110_vbtn_a.gif

292 ms

container-marine.htm_cmp_cascade110_vbtn.gif

container-marine.htm_cmp_cascade110_vbtn.gif

300 ms

container-marine.htm_cmp_cascade110_vbtn_a.gif

container-marine.htm_cmp_cascade110_vbtn_a.gif

300 ms

construction.htm_cmp_cascade110_vbtn.gif

construction.htm_cmp_cascade110_vbtn.gif

300 ms

construction.htm_cmp_cascade110_vbtn_a.gif

construction.htm_cmp_cascade110_vbtn_a.gif

300 ms

norme.htm_cmp_cascade110_vbtn.gif

norme.htm_cmp_cascade110_vbtn.gif

298 ms

norme.htm_cmp_cascade110_vbtn_a.gif

norme.htm_cmp_cascade110_vbtn_a.gif

386 ms

galerie_photos.htm_cmp_cascade110_vbtn.gif

galerie_photos.htm_cmp_cascade110_vbtn.gif

405 ms

galerie_photos.htm_cmp_cascade110_vbtn_a.gif

galerie_photos.htm_cmp_cascade110_vbtn_a.gif

405 ms

conform.htm_cmp_cascade110_vbtn.gif

conform.htm_cmp_cascade110_vbtn.gif

399 ms

conform.htm_cmp_cascade110_vbtn_a.gif

conform.htm_cmp_cascade110_vbtn_a.gif

402 ms

trafic.htm_cmp_cascade110_vbtn.gif

trafic.htm_cmp_cascade110_vbtn.gif

405 ms

trafic.htm_cmp_cascade110_vbtn_a.gif

trafic.htm_cmp_cascade110_vbtn_a.gif

485 ms

gestion.htm_cmp_cascade110_vbtn.gif

gestion.htm_cmp_cascade110_vbtn.gif

498 ms

gestion.htm_cmp_cascade110_vbtn_a.gif

gestion.htm_cmp_cascade110_vbtn_a.gif

501 ms

m.js

m.js

537 ms

show_ads.js

show_ads.js

48 ms

usage.htm_cmp_cascade110_vbtn.gif

usage.htm_cmp_cascade110_vbtn.gif

496 ms

usage.htm_cmp_cascade110_vbtn_a.gif

usage.htm_cmp_cascade110_vbtn_a.gif

495 ms

nous.htm_cmp_cascade110_vbtn.gif

nous.htm_cmp_cascade110_vbtn.gif

495 ms

nous.htm_cmp_cascade110_vbtn_a.gif

nous.htm_cmp_cascade110_vbtn_a.gif

570 ms

ou.htm_cmp_cascade110_vbtn.gif

ou.htm_cmp_cascade110_vbtn.gif

584 ms

ou.htm_cmp_cascade110_vbtn_a.gif

ou.htm_cmp_cascade110_vbtn_a.gif

590 ms

sources.htm_cmp_cascade110_vbtn.gif

sources.htm_cmp_cascade110_vbtn.gif

595 ms

sources.htm_cmp_cascade110_vbtn_a.gif

sources.htm_cmp_cascade110_vbtn_a.gif

594 ms

CT%20occ3.JPG

CT%20occ3.JPG

644 ms

251051176356

251051176356

228 ms

202002208824

202002208824

381 ms

ad.bub

ad.bub

19719 ms

ad.bub

ad.bub

19719 ms

markV3.gif

markV3.gif

286 ms

ca-pub-2995451242287099.js

ca-pub-2995451242287099.js

426 ms

zrt_lookup.html

zrt_lookup.html

417 ms

show_ads_impl.js

show_ads_impl.js

287 ms

ads

ads

252 ms

Accessibility Review

containerinfo.net accessibility score

63

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-*] attributes do not match their roles

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

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

containerinfo.net best practices score

67

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

Displays images with incorrect aspect ratio

High

Serves images with low resolution

SEO Factors

containerinfo.net SEO score

67

Search Engine Optimization Advices

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

Language and Encoding

  • Language Detected

    FR

  • Language Claimed

    FR

  • Encoding

    WINDOWS-1252

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Containerinfo.net 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 Containerinfo.net main page’s claimed encoding is windows-1252. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

containerinfo.net

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