Tools & Wizards About Us
igel.fr screenshot

Report Summary

  • 20

    Performance

    Renders faster than
    37% of other websites

  • 95

    Accessibility

    Visual factors better than
    that of 86% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 89

    SEO

    Google-friendlier than
    66% of websites

igel.fr

The Secure Endpoint OS for Now & Next | IGEL Technology

Page Load Speed

2.5 sec in total

First Response

232 ms

Resources Loaded

1.6 sec

Page Rendered

574 ms

igel.fr screenshot

About Website

Click here to check amazing IGEL content. Otherwise, check out these important facts you probably never knew about igel.fr

IGEL is a transformative, secure enterprise endpoint OS designed for SaaS, DaaS and VDI environments.

Visit igel.fr

Key Findings

We analyzed Igel.fr page load time and found that the first response time was 232 ms and then it took 2.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

igel.fr performance score

20

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

40/100

10%

LCP (Largest Contentful Paint)

Value7.7 s

3/100

25%

SI (Speed Index)

Value4.9 s

64/100

10%

TBT (Total Blocking Time)

Value1,060 ms

25/100

30%

CLS (Cumulative Layout Shift)

Value0.776

5/100

15%

TTI (Time to Interactive)

Value14.5 s

9/100

10%

Network Requests Diagram

igel.fr

232 ms

www.igel.com

65 ms

uc.js

41 ms

css2

50 ms

style.css

27 ms

Our browser made a total of 61 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Igel.fr, 82% (50 requests) were made to Igel.com and 8% (5 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (576 ms) relates to the external source Marketing.igel.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 219.4 kB (14%)

Content Size

1.6 MB

After Optimization

1.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Igel.fr main page is 1.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. 60% of websites need less resources to load. Images take 1.0 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 126.2 kB

  • Original 153.1 kB
  • After minification 150.9 kB
  • After compression 26.9 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 126.2 kB or 82% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

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

JavaScript Optimization

-34%

Potential reduce by 89.0 kB

  • Original 260.4 kB
  • After minification 260.4 kB
  • After compression 171.4 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 89.0 kB or 34% of the original size.

CSS Optimization

-3%

Potential reduce by 4.1 kB

  • Original 156.3 kB
  • After minification 156.3 kB
  • After compression 152.2 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. Igel.fr has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 31 (58%)

Requests Now

53

After Optimization

22

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

igel.fr

igel.fr

232 ms

www.igel.com

www.igel.com

65 ms

uc.js

uc.js

41 ms

css2

css2

50 ms

style.css

style.css

27 ms

search-forms.css

search-forms.css

29 ms

partnerfinder.css

partnerfinder.css

33 ms

main.prod.css

main.prod.css

65 ms

jquery.min.js

jquery.min.js

81 ms

front_style.css

front_style.css

31 ms

style.min.css

style.min.css

31 ms

jquery.fancybox.min.css

jquery.fancybox.min.css

78 ms

total.min.js

total.min.js

45 ms

country-state-handling.js

country-state-handling.js

77 ms

bundle-main.prod.js

bundle-main.prod.js

199 ms

vcex-front.min.js

vcex-front.min.js

198 ms

bundle-main-alpine.prod.js

bundle-main-alpine.prod.js

198 ms

js_composer_front.min.js

js_composer_front.min.js

199 ms

jquery.fancybox.min.js

jquery.fancybox.min.js

223 ms

gtm.js

gtm.js

296 ms

tracking.js

tracking.js

251 ms

igel-logo-new-dark.svg

igel-logo-new-dark.svg

149 ms

solutions-menu-case-study-spot.jpg

solutions-menu-case-study-spot.jpg

147 ms

Apps.jpg

Apps.jpg

147 ms

customers-menu-spot.png

customers-menu-spot.png

148 ms

disrupt-24-munich-navbar-graphic.jpg

disrupt-24-munich-navbar-graphic.jpg

151 ms

careers.jpg

careers.jpg

148 ms

dis_main1-ok.jpg

dis_main1-ok.jpg

178 ms

carousel-slide-1-bg-wide-scaled.jpeg

carousel-slide-1-bg-wide-scaled.jpeg

245 ms

homepage-banner.png

homepage-banner.png

155 ms

ontour-home-scaled.jpg

ontour-home-scaled.jpg

247 ms

white.jpg

white.jpg

151 ms

IGEL_web_finance-Spark.jpg

IGEL_web_finance-Spark.jpg

154 ms

IGEL_web_government-Spark.jpg

IGEL_web_government-Spark.jpg

155 ms

IGEL_web_healthcare-Spark.jpg

IGEL_web_healthcare-Spark.jpg

159 ms

aws-250x100-1.png

aws-250x100-1.png

158 ms

citrix_250x100.png

citrix_250x100.png

288 ms

microsoft_250x100.png

microsoft_250x100.png

161 ms

Omnissa-250x100-1.png

Omnissa-250x100-1.png

210 ms

sc2.jpg

sc2.jpg

248 ms

ud-pocket-expo-theater-img.jpg

ud-pocket-expo-theater-img.jpg

286 ms

IGEL_WHEEL_7.png

IGEL_WHEEL_7.png

351 ms

overlay-plus.png

overlay-plus.png

249 ms

linkedin-footer-dark.svg

linkedin-footer-dark.svg

250 ms

x_twitter-footer-dark.svg

x_twitter-footer-dark.svg

252 ms

youtube-footer-dark.svg

youtube-footer-dark.svg

251 ms

facebook-footer-dark.svg

facebook-footer-dark.svg

261 ms

rss-footer-dark.svg

rss-footer-dark.svg

262 ms

slack-footer-dark.svg

slack-footer-dark.svg

263 ms

igel_community_logo_dark.png

igel_community_logo_dark.png

264 ms

xn7_YHE41ni1AdIRqAuZuw1Bx9mbZk6jFO_G87jxeebC.woff

xn7_YHE41ni1AdIRqAuZuw1Bx9mbZk6jFO_G87jxeebC.woff

181 ms

xn7_YHE41ni1AdIRqAuZuw1Bx9mbZk59FO_G87jxeebC.woff

xn7_YHE41ni1AdIRqAuZuw1Bx9mbZk59FO_G87jxeebC.woff

214 ms

xn7_YHE41ni1AdIRqAuZuw1Bx9mbZk79FO_G87jxeebC.woff

xn7_YHE41ni1AdIRqAuZuw1Bx9mbZk79FO_G87jxeebC.woff

246 ms

xn7_YHE41ni1AdIRqAuZuw1Bx9mbZk7PFO_G87jxeebC.woff

xn7_YHE41ni1AdIRqAuZuw1Bx9mbZk7PFO_G87jxeebC.woff

264 ms

xn7_YHE41ni1AdIRqAuZuw1Bx9mbZk4aE-_G87jxeebC.woff

xn7_YHE41ni1AdIRqAuZuw1Bx9mbZk4aE-_G87jxeebC.woff

246 ms

ticons-webfont.woff

ticons-webfont.woff

224 ms

js_composer.min.css

js_composer.min.css

20 ms

style.min.css

style.min.css

18 ms

wpex-visual-composer.css

wpex-visual-composer.css

24 ms

hover-css.min.css

hover-css.min.css

26 ms

form_embed.js

form_embed.js

576 ms

Accessibility Review

igel.fr accessibility score

95

Accessibility Issues

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

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Some elements have a [tabindex] value greater than 0

Best Practices

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

igel.fr SEO score

89

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

Links do not have descriptive text

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

    EN

  • Encoding

    UTF-8

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

igel.fr

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