Report Summary

  • 12

    Performance

    Renders faster than
    25% of other websites

  • 50

    Accessibility

    Visual factors better than
    that of 20% of websites

  • 69

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 81

    SEO

    Google-friendlier than
    43% of websites

auto5.be

AUTO 5 - Pneus, pièces & équipement auto

Page Load Speed

3.7 sec in total

First Response

296 ms

Resources Loaded

3.2 sec

Page Rendered

277 ms

auto5.be screenshot

About Website

Welcome to auto5.be homepage info - get ready to check AUTO 5 best content for Belgium right away, or after learning these important things about auto5.be

Le spécialiste de l’entretien et l’équipement automobile en Belgique. Retrait gratuit en 1h en centre, 90 jours pour changer d’avis.

Visit auto5.be

Key Findings

We analyzed Auto5.be page load time and found that the first response time was 296 ms and then it took 3.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

auto5.be performance score

12

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.8 s

58/100

10%

LCP (Largest Contentful Paint)

Value10.3 s

0/100

25%

SI (Speed Index)

Value7.4 s

28/100

10%

TBT (Total Blocking Time)

Value3,860 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.744

6/100

15%

TTI (Time to Interactive)

Value10.9 s

22/100

10%

Network Requests Diagram

auto5.be

296 ms

www.auto5.be

1005 ms

base.min.css

167 ms

branding_min.css

368 ms

norauto.css

179 ms

Our browser made a total of 94 requests to load all elements on the main page. We found that 84% of them (79 requests) were addressed to the original Auto5.be, 4% (4 requests) were made to Cdn.tagcommander.com and 4% (4 requests) were made to Medias-auto5.be. The less responsive or slowest element that took the longest time to load (1 sec) belongs to the original domain Auto5.be.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.0 MB (57%)

Content Size

1.8 MB

After Optimization

763.3 kB

In fact, the total size of Auto5.be main page is 1.8 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. 55% of websites need less resources to load. Javascripts take 579.1 kB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 238.2 kB

  • Original 273.4 kB
  • After minification 270.5 kB
  • After compression 35.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 238.2 kB or 87% of the original size.

Image Optimization

-4%

Potential reduce by 17.4 kB

  • Original 495.8 kB
  • After minification 478.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. AUTO 5 images are well optimized though.

JavaScript Optimization

-70%

Potential reduce by 403.4 kB

  • Original 579.1 kB
  • After minification 577.0 kB
  • After compression 175.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 403.4 kB or 70% of the original size.

CSS Optimization

-83%

Potential reduce by 350.5 kB

  • Original 424.4 kB
  • After minification 424.2 kB
  • After compression 73.9 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. Auto5.be needs all CSS files to be minified and compressed as it can save up to 350.5 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 20 (22%)

Requests Now

92

After Optimization

72

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

Accessibility Review

auto5.be accessibility score

50

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

[role]s are not contained by their required parent element

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

High

Image elements do not have [alt] attributes

High

Links do not have a discernible 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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

Tables and lists

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

Impact

Issue

High

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

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

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

Best Practices

auto5.be best practices score

69

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

General

Impact

Issue

High

Registers an unload listener

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

auto5.be SEO score

81

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

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

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 uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    FR

  • Language Claimed

    FR

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Auto5.be 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 Auto5.be main page’s claimed encoding is iso-8859-1. 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

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