2.8 sec in total
257 ms
2.3 sec
282 ms
Visit fortinet.com now to see the best up-to-date Fortinet content for United States and also check out these interesting facts you probably never knew about fortinet.com
Fortinet delivers cybersecurity everywhere you need it. We secure the entire digital attack surface from devices, data, and apps and from data center to home office.
Visit fortinet.comWe analyzed Fortinet.com page load time and found that the first response time was 257 ms and then it took 2.6 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.
fortinet.com performance score
name
value
score
weighting
Value4.4 s
17/100
10%
Value5.0 s
26/100
25%
Value9.3 s
13/100
10%
Value1,710 ms
11/100
30%
Value0.001
100/100
15%
Value26.8 s
0/100
10%
257 ms
259 ms
359 ms
178 ms
260 ms
Our browser made a total of 70 requests to load all elements on the main page. We found that 47% of them (33 requests) were addressed to the original Fortinet.com, 9% (6 requests) were made to Secure.livechatinc.com and 6% (4 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (855 ms) belongs to the original domain Fortinet.com.
Page size can be reduced by 1000.0 kB (40%)
2.5 MB
1.5 MB
In fact, the total size of Fortinet.com main page is 2.5 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.
Potential reduce by 57.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. This page needs HTML code to be minified as it can gain 9.2 kB, which is 13% 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 57.9 kB or 79% of the original size.
Potential reduce by 12.0 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. Fortinet images are well optimized though.
Potential reduce by 645.3 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 645.3 kB or 60% of the original size.
Potential reduce by 284.8 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. Fortinet.com needs all CSS files to be minified and compressed as it can save up to 284.8 kB or 82% of the original size.
Number of requests can be reduced by 33 (56%)
59
26
The browser has sent 59 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fortinet. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 21 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
fortinet.com
257 ms
index.html
259 ms
www.fortinet.com
359 ms
css_5XB5aQOGzDUVxnwtHDXg0AJDjmjZbe2Sh1K2BEkR5cM.css
178 ms
css_KfS45pm7GHEtEUHdeJbq-mWbKysFMaeErc--9W93u5Y.css
260 ms
css_MSkSCFVqPonD7Ww2gnV5xL96d6Khsojp56M4PuPrTPw.css
449 ms
css_Sp0sNiitWKfm8_Gbn7pM0rov6tfbaGXl-qpj7RWuwHo.css
364 ms
js__SgEkXktuCEtZ8TJr-AEe-UTej55kwlitFsRdlrw5oI.js
537 ms
js_lrtILjzZYy5n9kXY2y0i0DY839sMA-r8z3vaCYn-Q48.js
524 ms
E-v1.js
42 ms
respond.min.js
98 ms
showwebchat.js
111 ms
trackalyze.js
223 ms
analytics.js
22 ms
fortiguard_logo.png
122 ms
solutions.png
123 ms
HP-Banner-iSFW-1500x400-72dpi.jpg
558 ms
HP-Banner1-FortiOS-54-72dpi.jpg
571 ms
HP-ATP-Jan2016_72dpi_012216_415pm-CTA.jpg
644 ms
atp_buyers_guide.jpg
363 ms
NGFW_promo2.jpg
448 ms
ISFW_promo.jpg
281 ms
webinar_red.png
372 ms
event_red.png
454 ms
blog.png
462 ms
facebook_grey.png
542 ms
twitter_grey.png
545 ms
youtube_grey.png
554 ms
linkedin_grey.png
634 ms
feed-icon_grey.png
637 ms
gtm.js
34 ms
fortinet_logo.png
653 ms
collect
11 ms
collect
58 ms
glyphicons-halflings-regular.woff
626 ms
home_ticker_prev.png
628 ms
home_ticker_next.png
697 ms
5gnmc8mjmb
53 ms
conversion_async.js
51 ms
insight.min.js
45 ms
iMAWebCookie.js
45 ms
collect
44 ms
90 ms
119 ms
fontawesome-webfont.woff
855 ms
trackalyze.asp
98 ms
ipcountry
255 ms
elqCfg.min.js
17 ms
language-icon.png
560 ms
svrGP
90 ms
49 ms
dot.gif
79 ms
36 ms
svrGP.aspx
33 ms
17 ms
l
21 ms
tracking.js
89 ms
script_data.js
122 ms
localization.en.0.3632191afe35222a6b78c04d457adc0d_74878f81c5d7d7231512243dce585b44.js
63 ms
ping
90 ms
open_chat.cgi
87 ms
9k-RPmcnxYEPm8CNFsH2gg.woff
78 ms
livechat-modern_7cf45543dc.ttf
35 ms
embedded.20160229123341.js
114 ms
_Incapsula_Resource
31 ms
_Incapsula_Resource
28 ms
roundtrip.js
21 ms
wkfQbvfT_02e2IWO3yYueQ.woff
30 ms
KT3KS9Aol4WfR6Vas8kNcg.woff
56 ms
IS4J6SEEYJGQ3GWZLY4WQW.js
24 ms
fortinet.com accessibility score
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
Buttons do not have an accessible name
Form elements do not have associated labels
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
Heading elements are not in a sequentially-descending order
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
ARIA IDs are not unique
fortinet.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
fortinet.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
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
Document uses legible font sizes
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fortinet.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 Fortinet.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.
fortinet.com
Open Graph data is detected on the main page of Fortinet. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: