Tools & Wizards About Us

Report Summary

  • 23

    Performance

    Renders faster than
    41% of other websites

  • 98

    Accessibility

    Visual factors better than
    that of 94% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 89

    SEO

    Google-friendlier than
    66% of websites

ftnt.net

Fortinet Blog - Broad, Integrated, Automated Cybersecurity 

Page Load Speed

1.7 sec in total

First Response

109 ms

Resources Loaded

1.5 sec

Page Rendered

116 ms

About Website

Click here to check amazing Ftnt content. Otherwise, check out these important facts you probably never knew about ftnt.net

Explore the latest cybersecurity trends and innovations, leading edge threat intelligence from FortiGuard Labs, Fortinet executive insights, and customer perspectives.

Visit ftnt.net

Key Findings

We analyzed Ftnt.net page load time and found that the first response time was 109 ms and then it took 1.6 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

ftnt.net performance score

23

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.1 s

80/100

10%

LCP (Largest Contentful Paint)

Value15.8 s

0/100

25%

SI (Speed Index)

Value25.9 s

0/100

10%

TBT (Total Blocking Time)

Value8,970 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value45.2 s

0/100

10%

Network Requests Diagram

ftnt.net

109 ms

blog

99 ms

clientlib-base.min.900b148ab7b87024003111a1245cca9c.css

8 ms

otSDKStub.js

37 ms

widgets.js

25 ms

Our browser made a total of 47 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Ftnt.net, 38% (18 requests) were made to Platform.twitter.com and 30% (14 requests) were made to Fortinet.com. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Fortinet.com.

Page Optimization Overview & Recommendations

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

Content Size

3.0 MB

After Optimization

2.4 MB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Ftnt.net main page is 3.0 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. 65% of websites need less resources to load. Images take 2.1 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 129.9 kB

  • Original 157.7 kB
  • After minification 145.4 kB
  • After compression 27.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 129.9 kB or 82% of the original size.

Image Optimization

-2%

Potential reduce by 31.6 kB

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

JavaScript Optimization

-59%

Potential reduce by 418.7 kB

  • Original 705.0 kB
  • After minification 705.0 kB
  • After compression 286.2 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 418.7 kB or 59% of the original size.

Requests Breakdown

Number of requests can be reduced by 24 (53%)

Requests Now

45

After Optimization

21

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

ftnt.net accessibility score

98

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

ftnt.net 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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

ftnt.net SEO score

89

Search Engine Optimization Advices

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 Ftnt.net 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 Ftnt.net 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 Ftnt. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: