Access history.bnpparibas. BNP Paribas Well of History : 2 centuries of banking archives

name

value

score

weighting

FCP (First Contentful Paint)

Value8.7 s

0/100

10%

LCP (Largest Contentful Paint)

Value22.0 s

0/100

25%

SI (Speed Index)

Value21.6 s

0/100

10%

TBT (Total Blocking Time)

Value700 ms

42/100

30%

CLS (Cumulative Layout Shift)

Value0.029

100/100

15%

TTI (Time to Interactive)

Value22.2 s

1/100

10%

301 ms

twentytwenty.css

138 ms

admin-ajax.php

3651 ms

style.min.css

117 ms

style-index.css

291 ms

Our browser made a total of 94 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original History.bnpparibas, 1% (1 request) were made to Googletagmanager.com and 1% (1 request) were made to Analyticscom.staging.bnpparibas. The less responsive or slowest element that took the longest time to load (4.5 sec) relates to the external source Histoire.bnpparibas.

Content Size

3.2 MB

After Optimization

2.6 MB

In fact, the total size of History.bnpparibas main page is 3.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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 3.0 MB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 200.3 kB

Original 230.2 kB
After minification 187.2 kB
After compression 29.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. This page needs HTML code to be minified as it can gain 43.0 kB, which is 19% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 200.3 kB or 87% of the original size.

Image Optimization

-14%

Potential reduce by 435.1 kB

Original 3.0 MB
After minification 2.6 MB

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, History needs image optimization as it can save up to 435.1 kB or 14% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

Requests Now

After Optimization

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

Accessibility Issues

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.

High

[aria-hidden="true"] elements contain focusable descendents

These are opportunities to improve the legibility of your content.

High

Background and foreground colors do not have a sufficient contrast ratio.

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.

High

Links do not have a discernible name

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Areas of Improvement

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

High

Issues were logged in the Issues panel in Chrome Devtools

Search Engine Optimization Advices

To appear in search results, crawlers need access to your app.

High

Links are not crawlable

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/).

High

Document uses legible font sizes

Language and Encoding

Language Detected

EN
Language Claimed

EN
Encoding

UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise History.bnpparibas can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that History.bnpparibas 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

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