Tools & Wizards About Us
azko.fr screenshot

Report Summary

  • 27

    Performance

    Renders faster than
    46% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 51% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 79

    SEO

    Google-friendlier than
    40% of websites

azko.fr

Septeo Legaltech | Des solutions dédiées aux professionnels du droit

Page Load Speed

4.1 sec in total

First Response

262 ms

Resources Loaded

3.3 sec

Page Rendered

484 ms

azko.fr screenshot

About Website

Click here to check amazing Azko content for France. Otherwise, check out these important facts you probably never knew about azko.fr

Visit azko.fr

Key Findings

We analyzed Azko.fr page load time and found that the first response time was 262 ms and then it took 3.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

azko.fr performance score

27

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.2 s

1/100

10%

LCP (Largest Contentful Paint)

Value17.5 s

0/100

25%

SI (Speed Index)

Value10.0 s

9/100

10%

TBT (Total Blocking Time)

Value830 ms

35/100

30%

CLS (Cumulative Layout Shift)

Value0.014

100/100

15%

TTI (Time to Interactive)

Value19.3 s

2/100

10%

Network Requests Diagram

azko.fr

262 ms

www.azko.fr

266 ms

www.azko.fr

601 ms

jquery-ui.min.css

27 ms

bootstrap.min.css

37 ms

Our browser made a total of 101 requests to load all elements on the main page. We found that 26% of them (26 requests) were addressed to the original Azko.fr, 13% (13 requests) were made to Skins.azko.fr and 10% (10 requests) were made to Static.azko.fr. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Azko.fr.

Page Optimization Overview & Recommendations

Page size can be reduced by 715.4 kB (20%)

Content Size

3.6 MB

After Optimization

2.9 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-89%

Potential reduce by 327.2 kB

  • Original 366.5 kB
  • After minification 351.2 kB
  • After compression 39.3 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 327.2 kB or 89% of the original size.

Image Optimization

-7%

Potential reduce by 195.2 kB

  • Original 2.7 MB
  • After minification 2.5 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. Azko images are well optimized though.

JavaScript Optimization

-4%

Potential reduce by 9.5 kB

  • Original 265.2 kB
  • After minification 265.2 kB
  • After compression 255.6 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

-74%

Potential reduce by 183.5 kB

  • Original 247.1 kB
  • After minification 84.9 kB
  • After compression 63.6 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. Azko.fr needs all CSS files to be minified and compressed as it can save up to 183.5 kB or 74% of the original size.

Requests Breakdown

Number of requests can be reduced by 42 (55%)

Requests Now

77

After Optimization

35

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

azko.fr

azko.fr

262 ms

www.azko.fr

www.azko.fr

266 ms

www.azko.fr

www.azko.fr

601 ms

jquery-ui.min.css

jquery-ui.min.css

27 ms

bootstrap.min.css

bootstrap.min.css

37 ms

font-awesome.min.css

font-awesome.min.css

465 ms

all.min.css

all.min.css

462 ms

commun.css

commun.css

513 ms

jquery.ui.warning.css

jquery.ui.warning.css

434 ms

jquery.sdnotify.css

jquery.sdnotify.css

435 ms

septeo-legaltech-v2.css

septeo-legaltech-v2.css

762 ms

jquery-1.11.0.min.js

jquery-1.11.0.min.js

28 ms

jquery.sdnotify.js

jquery.sdnotify.js

435 ms

output.min.js

output.min.js

452 ms

std.min.js

std.min.js

452 ms

url.min.js

url.min.js

457 ms

i18n.min.js

i18n.min.js

519 ms

message.min.js

message.min.js

518 ms

notice.js

notice.js

519 ms

select2.min.css

select2.min.css

44 ms

slick.min.css

slick.min.css

55 ms

slick-theme.min.css

slick-theme.min.css

56 ms

slick.min.js

slick.min.js

57 ms

js

js

92 ms

main.js.minjs

main.js.minjs

104 ms

espaceprive.js.minjs

espaceprive.js.minjs

199 ms

carte.js.minjs

carte.js.minjs

284 ms

septeo-legaltech-v2.js

septeo-legaltech-v2.js

441 ms

jquery.fancybox.min.css

jquery.fancybox.min.css

98 ms

all.min.css

all.min.css

102 ms

css2

css2

60 ms

css2

css2

80 ms

widgets.js

widgets.js

73 ms

logo.svg

logo.svg

262 ms

azko.png

azko.png

299 ms

picto-search.png

picto-search.png

297 ms

ecostaff.png

ecostaff.png

301 ms

ml.png

ml.png

299 ms

legatus.png

legatus.png

457 ms

header-accueil-min-6130ca8cf27b5-maxw2000-maxh1000.jpg

header-accueil-min-6130ca8cf27b5-maxw2000-maxh1000.jpg

865 ms

987564132.png

987564132.png

458 ms

1564879.png

1564879.png

550 ms

894541215564.png

894541215564.png

552 ms

854.png

854.png

552 ms

56464879.png

56464879.png

551 ms

156564121.png

156564121.png

548 ms

833757515159.png

833757515159.png

629 ms

879564.png

879564.png

627 ms

accueil-img-bloc-1.jpg

accueil-img-bloc-1.jpg

1023 ms

accueil-img-bloc-2.jpg

accueil-img-bloc-2.jpg

867 ms

accueil-img-bloc-3.jpg

accueil-img-bloc-3.jpg

734 ms

vignette-ecostaff.png

vignette-ecostaff.png

867 ms

message-post-rs_plan-de-travail-1.png

message-post-rs_plan-de-travail-1.png

1118 ms

microsoftteams-image--94--maxw2000-maxh1000.png

microsoftteams-image--94--maxw2000-maxh1000.png

1185 ms

642730250

642730250

168 ms

demo.svg

demo.svg

272 ms

devis.svg

devis.svg

271 ms

call.svg

call.svg

436 ms

rdv.svg

rdv.svg

429 ms

pxiEyp8kv8JHgFVrFJA.ttf

pxiEyp8kv8JHgFVrFJA.ttf

224 ms

pxiByp8kv8JHgFVrLGT9V1s.ttf

pxiByp8kv8JHgFVrLGT9V1s.ttf

271 ms

pxiByp8kv8JHgFVrLDz8V1s.ttf

pxiByp8kv8JHgFVrLDz8V1s.ttf

331 ms

pxiByp8kv8JHgFVrLFj_V1s.ttf

pxiByp8kv8JHgFVrLFj_V1s.ttf

331 ms

pxiGyp8kv8JHgFVrLPTedw.ttf

pxiGyp8kv8JHgFVrLPTedw.ttf

378 ms

pxiByp8kv8JHgFVrLEj6V1s.ttf

pxiByp8kv8JHgFVrLEj6V1s.ttf

330 ms

pxiByp8kv8JHgFVrLCz7V1s.ttf

pxiByp8kv8JHgFVrLCz7V1s.ttf

330 ms

pxiByp8kv8JHgFVrLDD4V1s.ttf

pxiByp8kv8JHgFVrLDD4V1s.ttf

330 ms

pxiByp8kv8JHgFVrLBT5V1s.ttf

pxiByp8kv8JHgFVrLBT5V1s.ttf

475 ms

cercle-pointill%C3%A9-bleu.svg

cercle-pointill%C3%A9-bleu.svg

402 ms

fa-brands-400.woff

fa-brands-400.woff

403 ms

fa-brands-400.woff

fa-brands-400.woff

404 ms

piwik.js

piwik.js

651 ms

20410676.js

20410676.js

365 ms

wait_blackalpha.gif

wait_blackalpha.gif

357 ms

642730250

642730250

1 ms

642730250

642730250

0 ms

642730250

642730250

306 ms

ajax-loader.gif

ajax-loader.gif

159 ms

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

110 ms

arrow-left.png

arrow-left.png

297 ms

arrow-right.png

arrow-right.png

296 ms

fa-solid-900.woff

fa-solid-900.woff

360 ms

fa-solid-900.woff

fa-solid-900.woff

375 ms

fa-regular-400.woff

fa-regular-400.woff

456 ms

fa-regular-400.woff

fa-regular-400.woff

457 ms

slick.woff

slick.woff

80 ms

settings

settings

200 ms

20410676.js

20410676.js

123 ms

web-interactives-embed.js

web-interactives-embed.js

62 ms

fb.js

fb.js

80 ms

banner.js

banner.js

123 ms

api.js

api.js

15 ms

piwik.php

piwik.php

108 ms

jquery.json-2.2.min.js

jquery.json-2.2.min.js

98 ms

jquery-ui.min.js

jquery-ui.min.js

8 ms

select2.min.js

select2.min.js

51 ms

gmap3.min.js

gmap3.min.js

50 ms

bootstrap.min.js

bootstrap.min.js

51 ms

twitter-bootstrap-hover-dropdown.min.js

twitter-bootstrap-hover-dropdown.min.js

97 ms

js

js

36 ms

fr.js

fr.js

19 ms

Accessibility Review

azko.fr accessibility score

81

Accessibility Issues

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.

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

azko.fr best practices score

75

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

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

azko.fr SEO score

79

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

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 Azko.fr 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 Azko.fr 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

azko.fr

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