1.7 sec in total
109 ms
1.5 sec
116 ms
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.netWe 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.
ftnt.net performance score
name
value
score
weighting
Value2.1 s
80/100
10%
Value15.8 s
0/100
25%
Value25.9 s
0/100
10%
Value8,970 ms
0/100
30%
Value0
100/100
15%
Value45.2 s
0/100
10%
109 ms
99 ms
8 ms
37 ms
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 size can be reduced by 580.3 kB (20%)
3.0 MB
2.4 MB
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.
Potential reduce by 129.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 129.9 kB or 82% of the original size.
Potential reduce by 31.6 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. Ftnt images are well optimized though.
Potential reduce by 418.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 418.8 kB or 59% of the original size.
Number of requests can be reduced by 24 (53%)
45
21
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.
ftnt.net
109 ms
blog
99 ms
clientlib-base.min.900b148ab7b87024003111a1245cca9c.css
8 ms
otSDKStub.js
37 ms
widgets.js
25 ms
clientlib-base.min.ba4f082a77dabb2c6baf715d9eb61c22.js
23 ms
f85f39fc-d7aa-467a-b762-fbb722748016.json
71 ms
fortinet-logo-white.svg
68 ms
paris-olympics-hero.png
1237 ms
fortinet-to-acquire-lacework-hero-v2.png
55 ms
red-dot-rugged-ngfw-hero-v2.png
81 ms
snake-keylogger-thumbnail.png
76 ms
sase-ai-summit-thumbnail.png
76 ms
skills-gap-vulnerabilities-thumbnail.png
76 ms
cybersecurity-jargon-thumbnail.png
62 ms
laf-0820-thumbnail.png
392 ms
widget_iframe.2f70fb173b9000da126c79afe2098f02.html
64 ms
location
46 ms
settings
108 ms
otBannerSdk.js
16 ms
en.json
29 ms
otFlat.json
17 ms
otPcTab.json
34 ms
timeline.e108540dddc96e4b707f5cf259a582d7.js
4 ms
visitorapi.min.js
12 ms
at.js
11 ms
launch-EN23cb8375449840dc93b13f34d935b8b9.min.js
24 ms
Fortinet
483 ms
FortiGuardLabs
957 ms
id
24 ms
dest5.html
22 ms
ibs:dpid=411&dpuuid=ZtBiQwAAAHmbPgN-
8 ms
polyfills-a40ef1678bae11e696dba45124eadd70.js
10 ms
runtime-b1c52fd0a13ead5fcf6b.js
25 ms
modules-96ebc7ac3ad66d681a3d.js
28 ms
main-babd9234dc048fb47339.js
26 ms
_app-a9c9f1a99e4414675fb1.js
26 ms
%5BscreenName%5D-0517bdda27d5006a5a2d.js
27 ms
_buildManifest.js
55 ms
_ssgManifest.js
55 ms
8526.0c32a8f0cfc5749221a3.js
8 ms
1755.07a49c40b12af4f75780.js
8 ms
8283.f3e5048cca7cef5eed7f.js
4 ms
3077.44bfeb00af01bc4020f6.js
8 ms
1362.42d432e02f7980bca032.js
14 ms
4956.c4e51ef593974b9db0bb.js
14 ms
5893.d500bd2a89ded806aa73.js
7 ms
ftnt.net accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
ftnt.net best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
ftnt.net SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
EN
EN
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.
ftnt.net
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: