Tools & Wizards About Us
fireeye.com screenshot

Report Summary

  • 15

    Performance

    Renders faster than
    27% of other websites

  • 98

    Accessibility

    Visual factors better than
    that of 94% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

fireeye.com

Trellix | Revolutionary Threat Detection and Response

Page Load Speed

1.9 sec in total

First Response

39 ms

Resources Loaded

1.4 sec

Page Rendered

494 ms

fireeye.com screenshot

About Website

Click here to check amazing Fireeye content for United States. Otherwise, check out these important facts you probably never knew about fireeye.com

Trellix empowers SecOps worldwide with the industry’s broadest and responsibly architected, GenAI-powered security platform.

Visit fireeye.com

Key Findings

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

Performance Metrics

fireeye.com performance score

15

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.1 s

21/100

10%

LCP (Largest Contentful Paint)

Value16.1 s

0/100

25%

SI (Speed Index)

Value10.6 s

7/100

10%

TBT (Total Blocking Time)

Value3,700 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.131

81/100

15%

TTI (Time to Interactive)

Value26.2 s

0/100

10%

Network Requests Diagram

fireeye.com

39 ms

fireeye.com

48 ms

index.html

108 ms

www.trellix.com

60 ms

utm-cookie-setter.min.js

36 ms

Our browser made a total of 125 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Fireeye.com, 74% (93 requests) were made to Trellix.com and 3% (4 requests) were made to Assets.adobedtm.com. The less responsive or slowest element that took the longest time to load (428 ms) relates to the external source Trellix.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 418.0 kB (21%)

Content Size

2.0 MB

After Optimization

1.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Fireeye.com main page is 2.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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 1.2 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 93.9 kB

  • Original 114.5 kB
  • After minification 98.7 kB
  • After compression 20.6 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 15.8 kB, which is 14% 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 93.9 kB or 82% of the original size.

Image Optimization

-2%

Potential reduce by 28.8 kB

  • Original 1.2 MB
  • After minification 1.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. Fireeye images are well optimized though.

JavaScript Optimization

-20%

Potential reduce by 77.0 kB

  • Original 391.7 kB
  • After minification 391.6 kB
  • After compression 314.7 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 77.0 kB or 20% of the original size.

CSS Optimization

-63%

Potential reduce by 218.4 kB

  • Original 347.9 kB
  • After minification 347.4 kB
  • After compression 129.5 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. Fireeye.com needs all CSS files to be minified and compressed as it can save up to 218.4 kB or 63% of the original size.

Requests Breakdown

Number of requests can be reduced by 60 (51%)

Requests Now

117

After Optimization

57

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

fireeye.com

fireeye.com

39 ms

fireeye.com

fireeye.com

48 ms

index.html

index.html

108 ms

www.trellix.com

www.trellix.com

60 ms

utm-cookie-setter.min.js

utm-cookie-setter.min.js

36 ms

js

js

84 ms

gtm.js

gtm.js

256 ms

hkgsujld4i

hkgsujld4i

70 ms

common.min.css

common.min.css

39 ms

gsap.min.js

gsap.min.js

65 ms

ScrollTrigger.min.js

ScrollTrigger.min.js

71 ms

ScrollToPlugin.min.js

ScrollToPlugin.min.js

138 ms

newco.min.js

newco.min.js

36 ms

launch-675ffef2af24.min.js

launch-675ffef2af24.min.js

61 ms

popper-v2.11.5.js

popper-v2.11.5.js

59 ms

sharethis.js

sharethis.js

60 ms

chart.js

chart.js

63 ms

button-control.min.js

button-control.min.js

59 ms

header-footer-control.min.js

header-footer-control.min.js

60 ms

form-control.min.js

form-control.min.js

69 ms

fancyapps-control-v5.min.js

fancyapps-control-v5.min.js

60 ms

jquery.rollNumber.js

jquery.rollNumber.js

61 ms

charts-control.min.js

charts-control.min.js

62 ms

toc-control.min.js

toc-control.min.js

60 ms

nav-control.min.js

nav-control.min.js

65 ms

clientlib-base.min.css

clientlib-base.min.css

64 ms

clientlib-jquery.min.js

clientlib-jquery.min.js

64 ms

clientlib-base.min.js

clientlib-base.min.js

61 ms

csrf.min.js

csrf.min.js

70 ms

bxsHX34

bxsHX34

73 ms

fancybox.css

fancybox.css

89 ms

carousel.css

carousel.css

37 ms

carousel.autoplay.css

carousel.autoplay.css

97 ms

fancyapps-tweaks.min.css

fancyapps-tweaks.min.css

98 ms

bootstrap-trellix.min.css

bootstrap-trellix.min.css

71 ms

icons.min.css

icons.min.css

90 ms

newsroom.min.css

newsroom.min.css

88 ms

tables-charts.min.css

tables-charts.min.css

98 ms

forms.min.css

forms.min.css

96 ms

clarity.js

clarity.js

59 ms

5PV9T-ULLTF-YKBNY-PXFLK-CCTPF

5PV9T-ULLTF-YKBNY-PXFLK-CCTPF

272 ms

Trellix-Logo-Black.svg

Trellix-Logo-Black.svg

191 ms

T0307-grad.svg

T0307-grad.svg

189 ms

T0266-grad.svg

T0266-grad.svg

185 ms

T0022-grad.svg

T0022-grad.svg

262 ms

T0001-grad.svg

T0001-grad.svg

255 ms

au.svg

au.svg

187 ms

br.svg

br.svg

262 ms

ca.svg

ca.svg

257 ms

de.svg

de.svg

258 ms

es.svg

es.svg

259 ms

fr.svg

fr.svg

263 ms

hk.svg

hk.svg

269 ms

in.svg

in.svg

267 ms

it.svg

it.svg

266 ms

jp.svg

jp.svg

332 ms

kr.svg

kr.svg

263 ms

mx.svg

mx.svg

270 ms

sg.svg

sg.svg

275 ms

gb.svg

gb.svg

271 ms

us.svg

us.svg

273 ms

platform-icons-card.jpg

platform-icons-card.jpg

271 ms

trellix-wise-card.jpg

trellix-wise-card.jpg

273 ms

trellix-thrive-card.jpg

trellix-thrive-card.jpg

275 ms

bug-report-july-2022-card.jpg

bug-report-july-2022-card.jpg

280 ms

threat-report-nov-2023-card.jpg

threat-report-nov-2023-card.jpg

276 ms

weekly-tech-talk-card.jpg

weekly-tech-talk-card.jpg

331 ms

trellix-wise.jpg

trellix-wise.jpg

277 ms

trellix-wise-logo.svg

trellix-wise-logo.svg

277 ms

cat-card-1.jpeg

cat-card-1.jpeg

331 ms

cat-card-2.jpeg

cat-card-2.jpeg

329 ms

cat-card-3.jpeg

cat-card-3.jpeg

331 ms

cat-card-4.jpeg

cat-card-4.jpeg

329 ms

cat-card-5.jpeg

cat-card-5.jpeg

339 ms

hero-data-flow-white.svg

hero-data-flow-white.svg

428 ms

T0092-whte.svg

T0092-whte.svg

348 ms

Insights-whte.svg

Insights-whte.svg

347 ms

token.json

token.json

164 ms

Endpoint-Security-whte.svg

Endpoint-Security-whte.svg

155 ms

T0114-grad.svg

T0114-grad.svg

187 ms

id

id

128 ms

AppMeasurement.min.js

AppMeasurement.min.js

120 ms

AppMeasurement_Module_ActivityMap.min.js

AppMeasurement_Module_ActivityMap.min.js

141 ms

AppMeasurement_Module_AudienceManagement.min.js

AppMeasurement_Module_AudienceManagement.min.js

142 ms

T0146-grad.svg

T0146-grad.svg

119 ms

T0074-grad.svg

T0074-grad.svg

137 ms

T0451-grad.svg

T0451-grad.svg

117 ms

xconsole-B.svg

xconsole-B.svg

117 ms

Endpoint-Security-grad.svg

Endpoint-Security-grad.svg

130 ms

T0092-grad.svg

T0092-grad.svg

131 ms

T0410-grad.svg

T0410-grad.svg

128 ms

Insights-grad.svg

Insights-grad.svg

129 ms

Endpoint-Detect-Response-grad.svg

Endpoint-Detect-Response-grad.svg

147 ms

Email-Service-grad.svg

Email-Service-grad.svg

134 ms

mrx-Cloud-SSE-grad.svg

mrx-Cloud-SSE-grad.svg

140 ms

ePO-grad.svg

ePO-grad.svg

133 ms

T0027-grad.svg

T0027-grad.svg

128 ms

xconsole.svg

xconsole.svg

148 ms

T0019-grad.svg

T0019-grad.svg

141 ms

threats-evolving.jpg

threats-evolving.jpg

147 ms

wave-3.png

wave-3.png

157 ms

cq5dam.web.1280.1280.jpeg

cq5dam.web.1280.1280.jpeg

156 ms

top-infosec-innovator-winner-2023-badge.png

top-infosec-innovator-winner-2023-badge.png

156 ms

cybersecurity-award-2023-winner-gold.png

cybersecurity-award-2023-winner-gold.png

147 ms

se-labs-logo.svg

se-labs-logo.svg

147 ms

gigaom-logo-dark.svg

gigaom-logo-dark.svg

152 ms

bootstrap-icons.woff

bootstrap-icons.woff

147 ms

gold-medal-trellix-dlp-endpoint-2023.png

gold-medal-trellix-dlp-endpoint-2023.png

150 ms

Pattern2.fa658359d032b22cee362129267e7309.svg

Pattern2.fa658359d032b22cee362129267e7309.svg

146 ms

Trellix-x-white.svg

Trellix-x-white.svg

147 ms

config.json

config.json

70 ms

dest5.html

dest5.html

67 ms

id

id

75 ms

ibs:dpid=411&dpuuid=ZkYfAAAAAIH8eAN-

ibs:dpid=411&dpuuid=ZkYfAAAAAIH8eAN-

14 ms

generic

generic

71 ms

generic

generic

10 ms

ibs:dpid=903&dpuuid=736c6b77-966f-4bfb-b649-0ed196ee9da1

ibs:dpid=903&dpuuid=736c6b77-966f-4bfb-b649-0ed196ee9da1

20 ms

dnb_coretag_v4.min.js

dnb_coretag_v4.min.js

22 ms

uwt.js

uwt.js

23 ms

6hvue8ubwiux.js

6hvue8ubwiux.js

55 ms

adsct

adsct

191 ms

adsct

adsct

137 ms

c.gif

c.gif

13 ms

results.txt

results.txt

96 ms

results.txt

results.txt

95 ms

Accessibility Review

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

fireeye.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

fireeye.com SEO score

93

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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

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

fireeye.com

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