Access restom.net. Restom : Technologies pour la restauration des véhicules anciens

name

value

score

weighting

FCP (First Contentful Paint)

Value7.2 s

1/100

10%

LCP (Largest Contentful Paint)

Value20.5 s

0/100

25%

SI (Speed Index)

Value16.7 s

0/100

10%

TBT (Total Blocking Time)

Value1,350 ms

17/100

30%

CLS (Cumulative Layout Shift)

Value0.597

11/100

15%

TTI (Time to Interactive)

Value26.5 s

0/100

10%

restom.net

576 ms

distinct_env.css

81 ms

global.css

244 ms

highdpi.css

160 ms

responsive-tables.css

168 ms

Our browser made a total of 96 requests to load all elements on the main page. We found that 84% of them (81 requests) were addressed to the original Restom.net, 7% (7 requests) were made to Fonts.gstatic.com and 3% (3 requests) were made to S.ytimg.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Restom.net.

Content Size

4.0 MB

After Optimization

3.0 MB

In fact, the total size of Restom.net main page is 4.0 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 2.8 MB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 72.7 kB

Original 82.9 kB
After minification 53.5 kB
After compression 10.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. This page needs HTML code to be minified as it can gain 29.4 kB, which is 35% 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 72.7 kB or 88% of the original size.

Image Optimization

-1%

Potential reduce by 38.4 kB

Original 2.8 MB
After minification 2.7 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. Restom images are well optimized though.

JavaScript Optimization

-71%

Potential reduce by 449.7 kB

Original 630.1 kB
After minification 553.6 kB
After compression 180.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 449.7 kB or 71% of the original size.

CSS Optimization

-84%

Potential reduce by 475.5 kB

Original 566.3 kB
After minification 494.3 kB
After compression 90.8 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. Restom.net needs all CSS files to be minified and compressed as it can save up to 475.5 kB or 84% of the original size.

Requests Now

After Optimization

The browser has sent 86 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Restom. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 27 to 1 for JavaScripts and from 22 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 keyboard navigation in your application.

High

Heading elements are not in a sequentially-descending order

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

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

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

Displays images with incorrect aspect ratio

Low

Detected JavaScript libraries

High

Page has valid source maps

Search Engine Optimization Advices

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

High

Links are not crawlable

High

robots.txt is not valid

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

High

Tap targets are not sized appropriately

Language and Encoding

Language Detected

FR
Language Claimed

FR
Encoding

UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Restom.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 Restom.net 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

restom.net

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

Report Summary

Performance

Accessibility

Best Practices

SEO

Restom : Technologies pour la restauration des véhicules anciens

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

restom.net

distinct_env.css

global.css

highdpi.css

responsive-tables.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

restom.net

distinct_env.css

global.css

highdpi.css

responsive-tables.css

uniform.default.css

jquery.fancybox.css

product_list.css

blockcategories.css

blockmyaccount.css

blocksearch.css

jquery.autocomplete.css

blocktags.css

blockviewed.css

homeslider.css

jquery.bxslider.css

blocktopmenu.css

superfish-modified.css

blockcart.css

zorel.css

blocknewsletter.css

jquery-1.11.0.min.js

jquery-migrate-1.2.1.min.js

jquery.easing.js

tools.js

global.js

10-bootstrap.min.js

15-jquery.total-storage.min.js

15-jquery.uniform-modified.js

jquery.fancybox.js

treeManagement.js

jquery.autocomplete.js

blocksearch.js

homeslider.js

jquery.bxslider.js

hoverIntent.js

css

superfish-modified.js

blocktopmenu.js

ajax-cart.js

jquery.scrollTo.js

jquery.serialScroll.js

jquery-ui.min.js