Tools & Wizards About Us
axelor.com screenshot

Report Summary

  • 31

    Performance

    Renders faster than
    51% of other websites

  • 56

    Accessibility

    Visual factors better than
    that of 24% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

axelor.com

Open Source Low Code platform for all your business apps | Axelor

Page Load Speed

3.6 sec in total

First Response

299 ms

Resources Loaded

2.5 sec

Page Rendered

815 ms

axelor.com screenshot

About Website

Visit axelor.com now to see the best up-to-date Axelor content for France and also check out these interesting facts you probably never knew about axelor.com

Discover Axelor, the Open Source full-web ERP platform, a solution to optimize your business processes.

Visit axelor.com

Key Findings

We analyzed Axelor.com page load time and found that the first response time was 299 ms and then it took 3.3 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

axelor.com performance score

31

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.9 s

25/100

10%

LCP (Largest Contentful Paint)

Value3.9 s

52/100

25%

SI (Speed Index)

Value21.4 s

0/100

10%

TBT (Total Blocking Time)

Value3,670 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.029

100/100

15%

TTI (Time to Interactive)

Value26.5 s

0/100

10%

Network Requests Diagram

axelor.com

299 ms

www.axelor.com

709 ms

wp-emoji-release.min.js

80 ms

styles.css

156 ms

style.css

313 ms

Our browser made a total of 52 requests to load all elements on the main page. We found that 85% of them (44 requests) were addressed to the original Axelor.com, 10% (5 requests) were made to Fonts.gstatic.com and 4% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1 sec) belongs to the original domain Axelor.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 720.4 kB (26%)

Content Size

2.8 MB

After Optimization

2.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Axelor.com main page is 2.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. Images take 1.9 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 35.8 kB

  • Original 43.8 kB
  • After minification 40.6 kB
  • After compression 8.0 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 35.8 kB or 82% of the original size.

Image Optimization

-2%

Potential reduce by 30.6 kB

  • Original 1.9 MB
  • After minification 1.9 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. Axelor images are well optimized though.

JavaScript Optimization

-72%

Potential reduce by 275.9 kB

  • Original 385.8 kB
  • After minification 341.8 kB
  • After compression 109.9 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 275.9 kB or 72% of the original size.

CSS Optimization

-89%

Potential reduce by 378.1 kB

  • Original 425.5 kB
  • After minification 374.9 kB
  • After compression 47.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. Axelor.com needs all CSS files to be minified and compressed as it can save up to 378.1 kB or 89% of the original size.

Requests Breakdown

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

Requests Now

44

After Optimization

24

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

axelor.com

axelor.com

299 ms

www.axelor.com

www.axelor.com

709 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

80 ms

styles.css

styles.css

156 ms

style.css

style.css

313 ms

css

css

25 ms

style.css

style.css

161 ms

shortcodes.css

shortcodes.css

166 ms

shortcodes_responsive.css

shortcodes_responsive.css

163 ms

magnific_popup.css

magnific_popup.css

170 ms

jquery.js

jquery.js

387 ms

jquery-migrate.min.js

jquery-migrate.min.js

240 ms

jquery.timelinr-1.0.js

jquery.timelinr-1.0.js

241 ms

frontend-builder-global-functions.js

frontend-builder-global-functions.js

245 ms

jquery.form.min.js

jquery.form.min.js

247 ms

scripts.js

scripts.js

337 ms

comment-reply.min.js

comment-reply.min.js

337 ms

custom.js

custom.js

337 ms

jquery.fitvids.js

jquery.fitvids.js

337 ms

waypoints.min.js

waypoints.min.js

478 ms

jquery.magnific-popup.js

jquery.magnific-popup.js

479 ms

frontend-builder-scripts.js

frontend-builder-scripts.js

487 ms

wp-embed.min.js

wp-embed.min.js

481 ms

logo_axelor.png

logo_axelor.png

234 ms

us.png

us.png

234 ms

homepage_slide3.jpg

homepage_slide3.jpg

773 ms

home.png

home.png

236 ms

vue-client.png

vue-client.png

236 ms

home-portail.png

home-portail.png

234 ms

client_vialis.png

client_vialis.png

234 ms

client_jam.png

client_jam.png

235 ms

client_bull.png

client_bull.png

236 ms

client_cg93.png

client_cg93.png

281 ms

client_soregies.png

client_soregies.png

282 ms

logo_proman.jpg

logo_proman.jpg

494 ms

logo_comeback.jpg

logo_comeback.jpg

327 ms

logo_enercoop.jpg

logo_enercoop.jpg

377 ms

photo_soregiesSLE.png

photo_soregiesSLE.png

700 ms

homepage_slideabs1.jpg

homepage_slideabs1.jpg

1036 ms

compta_modulable.png

compta_modulable.png

415 ms

adk.png

adk.png

735 ms

map3.jpg

map3.jpg

742 ms

partenaires1.png

partenaires1.png

574 ms

fond_gris1.jpg

fond_gris1.jpg

658 ms

u-WUoqrET9fUeobQW7jkRaCWcynf_cDxXwCLxiixG1c.ttf

u-WUoqrET9fUeobQW7jkRaCWcynf_cDxXwCLxiixG1c.ttf

165 ms

DXI1ORHCpsQm3Vp6mXoaTdqQynqKV_9Plp7mupa0S4g.ttf

DXI1ORHCpsQm3Vp6mXoaTdqQynqKV_9Plp7mupa0S4g.ttf

166 ms

MTP_ySUJH_bn48VBG8sNStqQynqKV_9Plp7mupa0S4g.ttf

MTP_ySUJH_bn48VBG8sNStqQynqKV_9Plp7mupa0S4g.ttf

167 ms

k3k702ZOKiLJc3WVjuplzNqQynqKV_9Plp7mupa0S4g.ttf

k3k702ZOKiLJc3WVjuplzNqQynqKV_9Plp7mupa0S4g.ttf

167 ms

EInbV5DfGHOiMmvb1Xr-htqQynqKV_9Plp7mupa0S4g.ttf

EInbV5DfGHOiMmvb1Xr-htqQynqKV_9Plp7mupa0S4g.ttf

166 ms

ETmodules_v2_4.ttf

ETmodules_v2_4.ttf

844 ms

analytics.js

analytics.js

164 ms

collect

collect

11 ms

Accessibility Review

axelor.com accessibility score

56

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

axelor.com best practices score

83

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

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

axelor.com SEO score

90

Search Engine Optimization Advices

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

    EN

  • Language Claimed

    FR

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Axelor.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed French language. Our system also found out that Axelor.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

axelor.com

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