Access aznavour-paris.com. aznavour

name

value

score

weighting

FCP (First Contentful Paint)

Value7.5 s

1/100

10%

LCP (Largest Contentful Paint)

Value61.3 s

0/100

25%

SI (Speed Index)

Value40.2 s

0/100

10%

TBT (Total Blocking Time)

Value1,260 ms

19/100

30%

CLS (Cumulative Layout Shift)

Value0.712

7/100

15%

TTI (Time to Interactive)

Value64.1 s

0/100

10%

www.aznavour-paris.com

1657 ms

reset.css

561 ms

common.css

566 ms

layer.css

579 ms

layout.css

583 ms

Our browser made a total of 121 requests to load all elements on the main page. We found that 47% of them (57 requests) were addressed to the original Aznavour-paris.com, 18% (22 requests) were made to Cdn-saas-web-217-134.cdn-nhncommerce.com and 15% (18 requests) were made to Godomall.speedycdn.net. The less responsive or slowest element that took the longest time to load (3.6 sec) belongs to the original domain Aznavour-paris.com.

Content Size

3.9 MB

After Optimization

3.6 MB

In fact, the total size of Aznavour-paris.com main page is 3.9 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. Only a small number of websites need less resources to load. Images take 3.5 MB which makes up the majority of the site volume.

HTML Optimization

-89%

Potential reduce by 147.0 kB

Original 165.6 kB
After minification 121.5 kB
After compression 18.6 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 44.1 kB, which is 27% 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 147.0 kB or 89% of the original size.

Image Optimization

-3%

Potential reduce by 102.2 kB

Original 3.5 MB
After minification 3.4 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. Aznavour Paris images are well optimized though.

JavaScript Optimization

-12%

Potential reduce by 20.5 kB

Original 173.2 kB
After minification 173.0 kB
After compression 152.7 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 20.5 kB or 12% of the original size.

CSS Optimization

-19%

Potential reduce by 11.7 kB

Original 62.2 kB
After minification 62.2 kB
After compression 50.4 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. Aznavour-paris.com needs all CSS files to be minified and compressed as it can save up to 11.7 kB or 19% of the original size.

Requests Now

After Optimization

The browser has sent 85 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Aznavour Paris. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 30 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-*] attributes do not match their roles

High

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

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.

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

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

High

Image elements do not have [alt] attributes

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

These items highlight common accessibility best practices.

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Areas of Improvement

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

High

Serves images with low resolution

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

Search Engine Optimization Advices

Format your HTML in a way that enables crawlers to better understand your app’s content.

High

Links do not have descriptive text

High

Image elements do not have [alt] attributes

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

High

Links are not crawlable

High

Page is blocked from indexing

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

High

Tap targets are not sized appropriately

Language and Encoding

Language Detected

N/A
Language Claimed

N/A
Encoding

UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Aznavour-paris.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Aznavour-paris.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

aznavour-paris.com

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

Report Summary

Performance

Accessibility

Best Practices

SEO

aznavour

Page Load Speed

First Response

Resources Loaded

Page Rendered

About Website

Key Findings

Performance Metrics

Measured Metrics

FCP (First Contentful Paint)

LCP (Largest Contentful Paint)

SI (Speed Index)

TBT (Total Blocking Time)

CLS (Cumulative Layout Shift)

TTI (Time to Interactive)

Network Requests Diagram

www.aznavour-paris.com

reset.css

common.css

layer.css

layout.css

Page Optimization Overview & Recommendations

Content Size

After Optimization

HTML Optimization

Image Optimization

JavaScript Optimization

CSS Optimization

Requests Breakdown

Requests Now

After Optimization

Network Requests Diagram

www.aznavour-paris.com

reset.css

common.css

layer.css

layout.css

main.css

list.css

button.css

chosen.css

aos.css

jquery.bxslider.css

swiper-bundle.min.css

custom.css

cus_common.css

cus_font.css

cus_list.css

cus_view.css

cus_others.css

cus_main.css

brandstory.css

gd_gettext.js

jquery.min.js

underscore-min.js

jquery.validate.min.js

additional-methods.min.js

numeral.min.js

accounting.min.js

money.min.js

chosen.jquery.min.js

placeholders.jquery.min.js

aos.js

jquery.bxslider.min.js

swiper-bundle.min.js

cus_common.js

cus_list.js

cus_main.js

ld.js

js

mobile-detect.min.js

clipboard.min.js

jquery.vticker.js

gd_ui.js

gd_common.js