Tools & Wizards About Us
www2.fireeye.com screenshot

Report Summary

  • 17

    Performance

    Renders faster than
    32% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 51% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 96

    SEO

    Google-friendlier than
    90% of websites

www2.fireeye.com

Living Security | Trellix

Page Load Speed

3.3 sec in total

First Response

205 ms

Resources Loaded

2.7 sec

Page Rendered

333 ms

www2.fireeye.com screenshot

About Website

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

Living security learns and adapts, using machine learning and AI so that your SecOps teams will stay ahead of potential attacks. Learn more today.

Visit www2.fireeye.com

Key Findings

We analyzed Www2.fireeye.com page load time and found that the first response time was 205 ms and then it took 3.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

www2.fireeye.com performance score

17

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.0 s

4/100

10%

LCP (Largest Contentful Paint)

Value9.2 s

1/100

25%

SI (Speed Index)

Value8.6 s

17/100

10%

TBT (Total Blocking Time)

Value2,360 ms

5/100

30%

CLS (Cumulative Layout Shift)

Value0.13

82/100

15%

TTI (Time to Interactive)

Value16.9 s

5/100

10%

Network Requests Diagram

www2.fireeye.com

205 ms

www2.fireeye.com

324 ms

www.fireeye.com

77 ms

optimize.js

96 ms

jquery.min.js

71 ms

Our browser made a total of 71 requests to load all elements on the main page. We found that 3% of them (2 requests) were addressed to the original Www2.fireeye.com, 55% (39 requests) were made to Fireeye.com and 7% (5 requests) were made to . The less responsive or slowest element that took the longest time to load (609 ms) relates to the external source Fireeye.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 241.8 kB (14%)

Content Size

1.7 MB

After Optimization

1.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Www2.fireeye.com main page is 1.7 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. 70% of websites need less resources to load. Images take 912.4 kB which makes up the majority of the site volume.

HTML Optimization

-71%

Potential reduce by 125.9 kB

  • Original 177.7 kB
  • After minification 177.7 kB
  • After compression 51.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 125.9 kB or 71% of the original size.

Image Optimization

-7%

Potential reduce by 63.6 kB

  • Original 912.4 kB
  • After minification 848.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. Www 2 Fireeye images are well optimized though.

JavaScript Optimization

-28%

Potential reduce by 52.1 kB

  • Original 186.8 kB
  • After minification 186.8 kB
  • After compression 134.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 52.1 kB or 28% of the original size.

CSS Optimization

-0%

Potential reduce by 205 B

  • Original 447.1 kB
  • After minification 447.1 kB
  • After compression 446.9 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. Www2.fireeye.com has all CSS files already compressed.

Requests Breakdown

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

Requests Now

57

After Optimization

42

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 57 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Www 2 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 16 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

www2.fireeye.com

www2.fireeye.com

205 ms

www2.fireeye.com

www2.fireeye.com

324 ms

www.fireeye.com

www.fireeye.com

77 ms

optimize.js

optimize.js

96 ms

jquery.min.js

jquery.min.js

71 ms

csrf.min.js

csrf.min.js

70 ms

clientlibs_nav.min.js

clientlibs_nav.min.js

70 ms

api.js

api.js

78 ms

fonts.css

fonts.css

198 ms

patch.css

patch.css

71 ms

clientlibs_fw-2021.min.css

clientlibs_fw-2021.min.css

74 ms

clientlibs_fw.min.js

clientlibs_fw.min.js

191 ms

token.json

token.json

350 ms

E579BC9404B1CAC84.css

E579BC9404B1CAC84.css

609 ms

6si.min.js

6si.min.js

227 ms

gtm.js

gtm.js

269 ms

fe-logo-white.svg

fe-logo-white.svg

232 ms

trellix-colors-bg.png

trellix-colors-bg.png

243 ms

trellix-logo-white.png

trellix-logo-white.png

230 ms

hpb-intro-helix.png

hpb-intro-helix.png

156 ms

trellix-logo.png

trellix-logo.png

153 ms

www.fireeye.com

www.fireeye.com

154 ms

tx-cds-2020.png

tx-cds-2020.png

239 ms

1632958533535.png

1632958533535.png

233 ms

cq5dam.thumbnail.200.800.png

cq5dam.thumbnail.200.800.png

239 ms

cq5dam.thumbnail.200.800.png

cq5dam.thumbnail.200.800.png

248 ms

cq5dam.thumbnail.200.800.png

cq5dam.thumbnail.200.800.png

243 ms

cq5dam.thumbnail.200.800.png

cq5dam.thumbnail.200.800.png

373 ms

tx-side-left-grey-02.png

tx-side-left-grey-02.png

241 ms

1633042555142.png

1633042555142.png

366 ms

1626824768695.png

1626824768695.png

248 ms

1626825001987.png

1626825001987.png

365 ms

hpb-bg-34.jpg

hpb-bg-34.jpg

368 ms

penn-state-health-logo-home.png

penn-state-health-logo-home.png

372 ms

stater-bros-logo-home.png

stater-bros-logo-home.png

368 ms

one-source-logo-home.png

one-source-logo-home.png

369 ms

infosys-logo-home.png

infosys-logo-home.png

369 ms

rcbc-logo-home.png

rcbc-logo-home.png

369 ms

usc-logo-home.png

usc-logo-home.png

372 ms

MKGI0=

MKGI0=

15 ms

1+jvzChiN

1+jvzChiN

13 ms

HpAawDtjwP9fo78woYjQ==

HpAawDtjwP9fo78woYjQ==

11 ms

MKGI0=

MKGI0=

9 ms

MKGI0=

MKGI0=

7 ms

fireicons.woff

fireicons.woff

272 ms

tx-bottom-right-grey-01.jpg

tx-bottom-right-grey-01.jpg

256 ms

fe-logomark-grey.svg

fe-logomark-grey.svg

256 ms

1632958533535.png

1632958533535.png

150 ms

1626824768695.png

1626824768695.png

132 ms

1626825001987.png

1626825001987.png

169 ms

1633042555142.png

1633042555142.png

139 ms

getuidj

getuidj

170 ms

c.6sc.co

c.6sc.co

190 ms

ipv6.6sc.co

ipv6.6sc.co

173 ms

insight.min.js

insight.min.js

135 ms

uwt.js

uwt.js

160 ms

munchkin.js

munchkin.js

199 ms

jukebox.js

jukebox.js

162 ms

fbevents.js

fbevents.js

80 ms

analytics.js

analytics.js

107 ms

json

json

94 ms

img.gif

img.gif

348 ms

313630683245423

313630683245423

58 ms

collect

collect

118 ms

adsct

adsct

277 ms

adsct

adsct

302 ms

progress-events.js

progress-events.js

100 ms

details

details

101 ms

collect

collect

161 ms

ga-audiences

ga-audiences

35 ms

22 ms

Accessibility Review

www2.fireeye.com accessibility score

81

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

High

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

www2.fireeye.com best practices score

67

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

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

www2.fireeye.com SEO score

96

Search Engine Optimization Advices

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

www2.fireeye.com

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