Report Summary

  • 99

    Performance

    Renders faster than
    96% of other websites

  • 93

    Accessibility

    Visual factors better than
    that of 80% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 67

    SEO

    Google-friendlier than
    26% of websites

ekium.eu

Etudes Ingénierie et Automation pour l’Industrie I Ekium

Page Load Speed

3 sec in total

First Response

351 ms

Resources Loaded

2.4 sec

Page Rendered

195 ms

About Website

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

Ekium : société spécialisée dans les métiers de l’ingénierie et de l’automation. Nous accompagnons les industries de procédé en France et à l’international.

Visit ekium.eu

Key Findings

We analyzed Ekium.eu page load time and found that the first response time was 351 ms and then it took 2.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

ekium.eu performance score

99

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.6 s

95/100

10%

LCP (Largest Contentful Paint)

Value1.6 s

99/100

25%

SI (Speed Index)

Value3.0 s

94/100

10%

TBT (Total Blocking Time)

Value20 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value1.6 s

100/100

10%

Network Requests Diagram

ekium.eu

351 ms

admin.css

188 ms

style.css

508 ms

jquery-ui-1.7.2.custom.css

465 ms

colorbox.css

280 ms

Our browser made a total of 84 requests to load all elements on the main page. We found that 68% of them (57 requests) were addressed to the original Ekium.eu, 2% (2 requests) were made to Google-analytics.com and 2% (2 requests) were made to Cm.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Ekium.eu.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.2 MB (61%)

Content Size

1.9 MB

After Optimization

730.3 kB

In fact, the total size of Ekium.eu main page is 1.9 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. 40% of websites need less resources to load. Javascripts take 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 26.1 kB

  • Original 32.4 kB
  • After minification 31.1 kB
  • After compression 6.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 26.1 kB or 81% of the original size.

Image Optimization

-3%

Potential reduce by 14.5 kB

  • Original 417.8 kB
  • After minification 403.3 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. Ekium images are well optimized though.

JavaScript Optimization

-76%

Potential reduce by 844.5 kB

  • Original 1.1 MB
  • After minification 898.2 kB
  • After compression 265.8 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 844.5 kB or 76% of the original size.

CSS Optimization

-84%

Potential reduce by 278.5 kB

  • Original 333.5 kB
  • After minification 318.0 kB
  • After compression 55.0 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. Ekium.eu needs all CSS files to be minified and compressed as it can save up to 278.5 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 59 (75%)

Requests Now

79

After Optimization

20

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

Accessibility Review

ekium.eu accessibility score

93

Accessibility Issues

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best Practices

ekium.eu best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

SEO Factors

ekium.eu SEO score

67

Search Engine Optimization Advices

Language and Encoding

  • Language Detected

    FR

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ekium.eu can be misinterpreted by Google and other search engines. Our service has detected that French is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Ekium.eu 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 Ekium. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: