Tools & Wizards About Us
ensilo.com screenshot

Report Summary

  • 19

    Performance

    Renders faster than
    36% of other websites

  • 92

    Accessibility

    Visual factors better than
    that of 78% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

ensilo.com

Fortinet acquires enSilo October 28, 2019

Page Load Speed

1.3 sec in total

First Response

213 ms

Resources Loaded

926 ms

Page Rendered

118 ms

ensilo.com screenshot

About Website

Welcome to ensilo.com homepage info - get ready to check EnSilo best content for United States right away, or after learning these important things about ensilo.com

Fortinet announced the acquisition of enSilo, Inc., a leading provider of advanced endpoint security.

Visit ensilo.com

Key Findings

We analyzed Ensilo.com page load time and found that the first response time was 213 ms and then it took 1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.

Performance Metrics

ensilo.com performance score

19

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.2 s

19/100

10%

LCP (Largest Contentful Paint)

Value9.3 s

1/100

25%

SI (Speed Index)

Value8.6 s

17/100

10%

TBT (Total Blocking Time)

Value6,590 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value29.5 s

0/100

10%

Network Requests Diagram

ensilo.com

213 ms

fortinet-acquires-ensilo.html

250 ms

fortinet-acquires-ensilo

84 ms

clientlib-all.min.a15a0271bea552e3af43d16942f4e675.css

10 ms

otSDKStub.js

50 ms

Our browser made a total of 37 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Ensilo.com, 78% (29 requests) were made to Fortinet.com and 16% (6 requests) were made to Cdn.cookielaw.org. The less responsive or slowest element that took the longest time to load (250 ms) relates to the external source Fortinet.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 267.3 kB (53%)

Content Size

502.0 kB

After Optimization

234.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Ensilo.com main page is 502.0 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 35% of websites need less resources to load. HTML takes 272.2 kB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 235.0 kB

  • Original 272.2 kB
  • After minification 218.9 kB
  • After compression 37.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. This page needs HTML code to be minified as it can gain 53.3 kB, which is 20% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 235.0 kB or 86% of the original size.

Image Optimization

-4%

Potential reduce by 985 B

  • Original 22.9 kB
  • After minification 21.9 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. EnSilo images are well optimized though.

JavaScript Optimization

-15%

Potential reduce by 30.9 kB

  • Original 205.8 kB
  • After minification 205.8 kB
  • After compression 174.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 30.9 kB or 15% of the original size.

CSS Optimization

-30%

Potential reduce by 312 B

  • Original 1.0 kB
  • After minification 1.0 kB
  • After compression 724 B

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. Ensilo.com needs all CSS files to be minified and compressed as it can save up to 312 B or 30% of the original size.

Requests Breakdown

Number of requests can be reduced by 9 (26%)

Requests Now

34

After Optimization

25

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

ensilo.com

ensilo.com

213 ms

fortinet-acquires-ensilo.html

fortinet-acquires-ensilo.html

250 ms

fortinet-acquires-ensilo

fortinet-acquires-ensilo

84 ms

clientlib-all.min.a15a0271bea552e3af43d16942f4e675.css

clientlib-all.min.a15a0271bea552e3af43d16942f4e675.css

10 ms

otSDKStub.js

otSDKStub.js

50 ms

clientlib-all.min.98dc97faab7a3449f560fe76e2f97bd2.js

clientlib-all.min.98dc97faab7a3449f560fe76e2f97bd2.js

33 ms

forticloud-one.js

forticloud-one.js

38 ms

lozad.js

lozad.js

40 ms

main.css

main.css

33 ms

f85f39fc-d7aa-467a-b762-fbb722748016.json

f85f39fc-d7aa-467a-b762-fbb722748016.json

133 ms

fortinet-logo.svg

fortinet-logo.svg

129 ms

intersection-observer.js

intersection-observer.js

211 ms

nav-cta-icon.svg

nav-cta-icon.svg

39 ms

icon-sase.svg

icon-sase.svg

40 ms

icon-secop.svg

icon-secop.svg

39 ms

icon-fgl-nav.svg

icon-fgl-nav.svg

41 ms

submit-arrow.svg

submit-arrow.svg

49 ms

linkedin_icon_footer.svg

linkedin_icon_footer.svg

48 ms

twitter_icon_footer.svg

twitter_icon_footer.svg

47 ms

youtube_icon_footer.svg

youtube_icon_footer.svg

45 ms

instagram_icon_footer.svg

instagram_icon_footer.svg

46 ms

facebook_icon_footer.svg

facebook_icon_footer.svg

52 ms

rss_icon_footer.svg

rss_icon_footer.svg

52 ms

fortinet-footer-logo.svg

fortinet-footer-logo.svg

51 ms

roman-attanasio-partnership-logo.jpg

roman-attanasio-partnership-logo.jpg

52 ms

logo-ftnt-pga-australia.png

logo-ftnt-pga-australia.png

50 ms

logo-ftnt-pga-americas.png

logo-ftnt-pga-americas.png

54 ms

logo-ftnt-european-tour.png

logo-ftnt-european-tour.png

54 ms

logo-ftnt-pga-usa.png

logo-ftnt-pga-usa.png

54 ms

footer-links.json

footer-links.json

34 ms

location

location

45 ms

otBannerSdk.js

otBannerSdk.js

27 ms

en.json

en.json

22 ms

otFlat.json

otFlat.json

18 ms

otPcTab.json

otPcTab.json

30 ms

visitorapi.min.js

visitorapi.min.js

10 ms

at.js

at.js

10 ms

Accessibility Review

ensilo.com accessibility score

92

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

ARIA IDs are not unique

Best Practices

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

Page has valid source maps

SEO Factors

ensilo.com SEO score

82

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

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Page is blocked from indexing

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 Ensilo.com 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 Ensilo.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

ensilo.com

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