Tools & Wizards About Us
aligro.ch screenshot

Report Summary

  • 17

    Performance

    Renders faster than
    32% of other websites

  • 74

    Accessibility

    Visual factors better than
    that of 40% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 99

    SEO

    Google-friendlier than
    93% of websites

aligro.ch

Le spécialiste de la gastronomie au service des gros consommateurs - ALIGRO

Page Load Speed

9.8 sec in total

First Response

362 ms

Resources Loaded

8.1 sec

Page Rendered

1.4 sec

aligro.ch screenshot

About Website

Click here to check amazing ALIGRO content for Switzerland. Otherwise, check out these important facts you probably never knew about aligro.ch

Offre pour les gros consommateurs, avec prix TTC. 2000 actions sur l'alimentation, vins et boissons, produits frais, et non-food.

Visit aligro.ch

Key Findings

We analyzed Aligro.ch page load time and found that the first response time was 362 ms and then it took 9.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

aligro.ch performance score

17

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.7 s

2/100

10%

LCP (Largest Contentful Paint)

Value36.9 s

0/100

25%

SI (Speed Index)

Value11.3 s

5/100

10%

TBT (Total Blocking Time)

Value2,550 ms

4/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value25.6 s

0/100

10%

Network Requests Diagram

aligro.ch

362 ms

www.aligro.ch

914 ms

css2

153 ms

918.fc0ef1d0.css

130 ms

app.57e1eac8.css

339 ms

Our browser made a total of 132 requests to load all elements on the main page. We found that 23% of them (30 requests) were addressed to the original Aligro.ch, 9% (12 requests) were made to Track.adform.net and 8% (10 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (2.9 sec) relates to the external source Global.ib-ibi.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 246.7 kB (6%)

Content Size

4.1 MB

After Optimization

3.9 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Aligro.ch main page is 4.1 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.7 MB which makes up the majority of the site volume.

HTML Optimization

-92%

Potential reduce by 241.0 kB

  • Original 262.2 kB
  • After minification 255.7 kB
  • After compression 21.1 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 241.0 kB or 92% of the original size.

Image Optimization

-0%

Potential reduce by 133 B

  • Original 3.7 MB
  • After minification 3.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. ALIGRO images are well optimized though.

JavaScript Optimization

-9%

Potential reduce by 5.4 kB

  • Original 57.7 kB
  • After minification 57.7 kB
  • After compression 52.2 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. This website has mostly compressed JavaScripts.

CSS Optimization

-0%

Potential reduce by 77 B

  • Original 55.6 kB
  • After minification 55.6 kB
  • After compression 55.5 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. Aligro.ch has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 82 (83%)

Requests Now

99

After Optimization

17

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

aligro.ch

aligro.ch

362 ms

www.aligro.ch

www.aligro.ch

914 ms

css2

css2

153 ms

918.fc0ef1d0.css

918.fc0ef1d0.css

130 ms

app.57e1eac8.css

app.57e1eac8.css

339 ms

vue.cd5825e1.css

vue.cd5825e1.css

335 ms

js

js

166 ms

polyfill.min.js

polyfill.min.js

150 ms

router.js

router.js

860 ms

routing

routing

1150 ms

runtime.280916f0.js

runtime.280916f0.js

859 ms

946.e67b2380.js

946.e67b2380.js

1181 ms

918.b1e13c10.js

918.b1e13c10.js

1237 ms

162.135610b5.js

162.135610b5.js

1132 ms

app.62b81247.js

app.62b81247.js

1131 ms

840.a6129484.js

840.a6129484.js

1132 ms

960.59b4b22a.js

960.59b4b22a.js

1277 ms

756.e435daa5.js

756.e435daa5.js

1140 ms

vue.0d64b1d0.js

vue.0d64b1d0.js

1155 ms

analytics.js

analytics.js

1016 ms

hotjar-3025112.js

hotjar-3025112.js

1140 ms

logo_2018_spaceless.f28474ce.svg

logo_2018_spaceless.f28474ce.svg

656 ms

62fa5fdfabebf025570498.jpg

62fa5fdfabebf025570498.jpg

784 ms

5fd20131a4723659144462.jpg

5fd20131a4723659144462.jpg

891 ms

6033a7a1e5f02491872313.jpg

6033a7a1e5f02491872313.jpg

802 ms

6033a82c85d0e715924389.jpg

6033a82c85d0e715924389.jpg

671 ms

6033a8e1a7fd1337513414.jpg

6033a8e1a7fd1337513414.jpg

1081 ms

S6uyw4BMUTPHvxk.ttf

S6uyw4BMUTPHvxk.ttf

470 ms

S6u9w4BMUTPHh7USew8.ttf

S6u9w4BMUTPHh7USew8.ttf

550 ms

S6u9w4BMUTPHh6UVew8.ttf

S6u9w4BMUTPHh6UVew8.ttf

607 ms

icomoon.3e6b99ea.woff

icomoon.3e6b99ea.woff

858 ms

1328 ms

trackpoint-async.js

trackpoint-async.js

778 ms

601955e292c9f607643140.jpg

601955e292c9f607643140.jpg

1040 ms

6033a82c85d0e715924389.jpg

6033a82c85d0e715924389.jpg

2106 ms

collect

collect

110 ms

62fa5fdfabebf025570498.jpg

62fa5fdfabebf025570498.jpg

822 ms

6033a7a1e5f02491872313.jpg

6033a7a1e5f02491872313.jpg

895 ms

modules.2be88a2123e5e486752f.js

modules.2be88a2123e5e486752f.js

393 ms

5fd20131a4723659144462.jpg

5fd20131a4723659144462.jpg

745 ms

collect

collect

714 ms

6033a8980c25e664243387.jpg

6033a8980c25e664243387.jpg

739 ms

box-69edcc3187336f9b0a3fbb4c73be9fe6.html

box-69edcc3187336f9b0a3fbb4c73be9fe6.html

690 ms

6033a8e1a7fd1337513414.jpg

6033a8e1a7fd1337513414.jpg

821 ms

440 ms

508 ms

581 ms

592 ms

186 ms

ga-audiences

ga-audiences

110 ms

trackpoint-async.js

trackpoint-async.js

25 ms

176 ms

90 ms

142 ms

114 ms

pixels

pixels

169 ms

2718 ms

168 ms

244 ms

inv

inv

239 ms

1318 ms

2817 ms

user-registering

user-registering

2264 ms

29729

29729

2258 ms

click

click

2783 ms

pixel

pixel

2241 ms

Pug

Pug

2180 ms

cs

cs

2635 ms

image.sbmx

image.sbmx

2933 ms

0.gif

0.gif

2497 ms

um

um

2090 ms

pixel.gif

pixel.gif

2619 ms

2717 ms

put

put

2194 ms

33302

33302

2166 ms

1201 ms

js

js

1760 ms

js

js

2075 ms

fbevents.js

fbevents.js

2074 ms

teads-fellow.js

teads-fellow.js

2008 ms

conversion_async.js

conversion_async.js

1245 ms

js

js

258 ms

match

match

156 ms

gdpr_consent=

gdpr_consent=

522 ms

rum

rum

584 ms

sd

sd

487 ms

match

match

417 ms

415 ms

generic

generic

402 ms

pixel

pixel

768 ms

pixel

pixel

1078 ms

1445 ms

xuid

xuid

729 ms

match

match

738 ms

813297449168756

813297449168756

690 ms

1132 ms

pixel.gif

pixel.gif

1197 ms

info2

info2

538 ms

xuid

xuid

539 ms

617 ms

790 ms

match

match

687 ms

match

match

722 ms

generic

generic

681 ms

match

match

473 ms

472 ms

498 ms

304 ms

560 ms

376 ms

487 ms

393 ms

314 ms

358 ms

324 ms

p

p

104 ms

setuid

setuid

114 ms

289 ms

match

match

103 ms

104 ms

134 ms

dcm

dcm

36 ms

27 ms

65 ms

36 ms

60 ms

58 ms

28 ms

34 ms

33 ms

28 ms

25 ms

Accessibility Review

aligro.ch accessibility score

74

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

High

ARIA IDs are not unique

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

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

Heading elements are not in a sequentially-descending order

Best Practices

aligro.ch best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

aligro.ch SEO score

99

Search Engine Optimization Advices

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

    UTF-8

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

aligro.ch

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