Tools & Wizards About Us

Report Summary

  • 23

    Performance

    Renders faster than
    41% of other websites

  • 65

    Accessibility

    Visual factors better than
    that of 30% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

dynux.com

Dynux | Editeur des logiciels MyAntiriade, NetPPL, Antiriade et WinPPL

Page Load Speed

7.3 sec in total

First Response

198 ms

Resources Loaded

6.9 sec

Page Rendered

195 ms

About Website

Click here to check amazing Dynux content. Otherwise, check out these important facts you probably never knew about dynux.com

Dynux, éditeur des logiciels MyAntiriade, NetPPL, et Antiriade de gestion des agents dans les collèges, les lycées pour les régions et les et les départements

Visit dynux.com

Key Findings

We analyzed Dynux.com page load time and found that the first response time was 198 ms and then it took 7.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

dynux.com performance score

23

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.8 s

4/100

10%

LCP (Largest Contentful Paint)

Value5.8 s

15/100

25%

SI (Speed Index)

Value28.0 s

0/100

10%

TBT (Total Blocking Time)

Value1,840 ms

9/100

30%

CLS (Cumulative Layout Shift)

Value0.009

100/100

15%

TTI (Time to Interactive)

Value14.4 s

9/100

10%

Network Requests Diagram

dynux.com

198 ms

www.dynux.com

3243 ms

sgr.css

164 ms

style.min.css

248 ms

styles.css

251 ms

Our browser made a total of 66 requests to load all elements on the main page. We found that 91% of them (60 requests) were addressed to the original Dynux.com, 3% (2 requests) were made to Use.fontawesome.com and 3% (2 requests) were made to Analytics.dynux.com. The less responsive or slowest element that took the longest time to load (3.2 sec) belongs to the original domain Dynux.com.

Page Optimization Overview & Recommendations

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

Content Size

2.6 MB

After Optimization

2.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Dynux.com main page is 2.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. 55% of websites need less resources to load. Images take 1.7 MB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 84.4 kB

  • Original 108.1 kB
  • After minification 106.2 kB
  • After compression 23.8 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 84.4 kB or 78% of the original size.

Image Optimization

-24%

Potential reduce by 414.7 kB

  • Original 1.7 MB
  • After minification 1.3 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. Obviously, Dynux needs image optimization as it can save up to 414.7 kB or 24% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-1%

Potential reduce by 5.9 kB

  • Original 602.0 kB
  • After minification 602.0 kB
  • After compression 596.1 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

-3%

Potential reduce by 6.3 kB

  • Original 200.9 kB
  • After minification 200.8 kB
  • After compression 194.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. Dynux.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 34 (54%)

Requests Now

63

After Optimization

29

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

dynux.com accessibility score

65

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

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

High

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

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

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

dynux.com SEO score

85

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

    UTF-8

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

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