Tools & Wizards About Us
phishme.com screenshot

Report Summary

  • 23

    Performance

    Renders faster than
    41% of other websites

  • 87

    Accessibility

    Visual factors better than
    that of 66% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

phishme.com

Phishing Protection Solutions | Cofense Email Security

Page Load Speed

1.5 sec in total

First Response

80 ms

Resources Loaded

1 sec

Page Rendered

398 ms

phishme.com screenshot

About Website

Visit phishme.com now to see the best up-to-date Phishme content for United States and also check out these interesting facts you probably never knew about phishme.com

See, remediate, and manage the risk of rapidly evolving AI-powered phishing attacks that evade traditional and AI SEGs with Cofense.

Visit phishme.com

Key Findings

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

Performance Metrics

phishme.com performance score

23

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.2 s

20/100

10%

LCP (Largest Contentful Paint)

Value7.0 s

6/100

25%

SI (Speed Index)

Value5.8 s

50/100

10%

TBT (Total Blocking Time)

Value2,280 ms

5/100

30%

CLS (Cumulative Layout Shift)

Value0.142

78/100

15%

TTI (Time to Interactive)

Value13.8 s

10/100

10%

Network Requests Diagram

phishme.com

80 ms

cofense.com

172 ms

cursor.css

29 ms

style.css

34 ms

elementor-icons.min.css

67 ms

Our browser made a total of 88 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Phishme.com, 94% (83 requests) were made to Cofense.com and 1% (1 request) were made to Js.qualified.com. The less responsive or slowest element that took the longest time to load (442 ms) relates to the external source Cofense.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 142.1 kB (17%)

Content Size

838.1 kB

After Optimization

696.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Phishme.com main page is 838.1 kB. 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 375.1 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 135.1 kB

  • Original 160.6 kB
  • After minification 155.1 kB
  • After compression 25.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. 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 135.1 kB or 84% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 375.1 kB
  • After minification 375.1 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. Phishme images are well optimized though.

JavaScript Optimization

-2%

Potential reduce by 3.4 kB

  • Original 185.5 kB
  • After minification 185.5 kB
  • After compression 182.1 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. This website has mostly compressed JavaScripts.

CSS Optimization

-3%

Potential reduce by 3.6 kB

  • Original 116.8 kB
  • After minification 114.8 kB
  • After compression 113.2 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. Phishme.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 66 (81%)

Requests Now

81

After Optimization

15

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

phishme.com

phishme.com

80 ms

cofense.com

cofense.com

172 ms

cursor.css

cursor.css

29 ms

style.css

style.css

34 ms

elementor-icons.min.css

elementor-icons.min.css

67 ms

frontend-lite.min.css

frontend-lite.min.css

47 ms

swiper.min.css

swiper.min.css

42 ms

post-15.css

post-15.css

38 ms

frontend-lite.min.css

frontend-lite.min.css

60 ms

post-4.css

post-4.css

72 ms

post-93807.css

post-93807.css

80 ms

post-104967.css

post-104967.css

63 ms

post-104976.css

post-104976.css

73 ms

widget-styles.css

widget-styles.css

120 ms

responsive.css

responsive.css

91 ms

ecs-style.css

ecs-style.css

93 ms

post-1462.css

post-1462.css

89 ms

post-86702.css

post-86702.css

102 ms

post-86773.css

post-86773.css

103 ms

post-94275.css

post-94275.css

115 ms

post-96442.css

post-96442.css

111 ms

post-96443.css

post-96443.css

136 ms

post-96445.css

post-96445.css

136 ms

post-105089.css

post-105089.css

137 ms

fontawesome.min.css

fontawesome.min.css

142 ms

solid.min.css

solid.min.css

141 ms

brands.min.css

brands.min.css

154 ms

jquery.min.js

jquery.min.js

148 ms

jquery-migrate.min.js

jquery-migrate.min.js

149 ms

ecs_ajax_pagination.js

ecs_ajax_pagination.js

172 ms

ecs.js

ecs.js

173 ms

zlo5wor.css

zlo5wor.css

175 ms

qualified.js

qualified.js

149 ms

widget-posts.min.css

widget-posts.min.css

186 ms

widget-icon-list.min.css

widget-icon-list.min.css

192 ms

widget-theme-elements.min.css

widget-theme-elements.min.css

198 ms

post-104982.css

post-104982.css

184 ms

post-104983.css

post-104983.css

185 ms

post-104984.css

post-104984.css

195 ms

post-104985.css

post-104985.css

429 ms

post-104986.css

post-104986.css

398 ms

regular.min.css

regular.min.css

393 ms

post-96724.css

post-96724.css

394 ms

animations.min.css

animations.min.css

383 ms

lazysizes.min.js

lazysizes.min.js

426 ms

typed.js

typed.js

420 ms

typed.fe.js

typed.fe.js

419 ms

navigation.js

navigation.js

413 ms

frontend-script.js

frontend-script.js

436 ms

widget-scripts.js

widget-scripts.js

434 ms

imagesloaded.min.js

imagesloaded.min.js

422 ms

webpack-pro.runtime.min.js

webpack-pro.runtime.min.js

417 ms

webpack.runtime.min.js

webpack.runtime.min.js

418 ms

frontend-modules.min.js

frontend-modules.min.js

431 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

432 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

442 ms

wp-polyfill.min.js

wp-polyfill.min.js

422 ms

hooks.min.js

hooks.min.js

407 ms

i18n.min.js

i18n.min.js

401 ms

frontend.min.js

frontend.min.js

402 ms

waypoints.min.js

waypoints.min.js

403 ms

core.min.js

core.min.js

414 ms

frontend.min.js

frontend.min.js

411 ms

elements-handlers.min.js

elements-handlers.min.js

409 ms

animate-circle.min.js

animate-circle.min.js

432 ms

elementor.js

elementor.js

385 ms

jquery.sticky.min.js

jquery.sticky.min.js

385 ms

p.css

p.css

35 ms

lazyload.min.js

lazyload.min.js

382 ms

gtm.js

gtm.js

327 ms

wMAbelCsnMXMI4AAAAASUVORK5CYII=

wMAbelCsnMXMI4AAAAASUVORK5CYII=

174 ms

cofense-blue-red-gradient.jpg

cofense-blue-red-gradient.jpg

240 ms

cofense-list.svg

cofense-list.svg

259 ms

cofense-list-last.svg

cofense-list-last.svg

242 ms

Mulish-Black.woff

Mulish-Black.woff

238 ms

Mulish-SemiBold.woff

Mulish-SemiBold.woff

189 ms

fa-solid-900.woff

fa-solid-900.woff

240 ms

fa-brands-400.woff

fa-brands-400.woff

238 ms

cofense-tagline-logo.svg

cofense-tagline-logo.svg

58 ms

cofense-2023-awards.jpg

cofense-2023-awards.jpg

128 ms

vishing-video-cofense.jpg

vishing-video-cofense.jpg

62 ms

seg-miss-cofense.png

seg-miss-cofense.png

64 ms

cofense-isms-150x150.jpg

cofense-isms-150x150.jpg

109 ms

cofense-aicpa-150x150.jpg

cofense-aicpa-150x150.jpg

65 ms

cofense-fedramp-150x150.jpg

cofense-fedramp-150x150.jpg

108 ms

blog-graphic-updated-1.jpg

blog-graphic-updated-1.jpg

110 ms

cyber-attack-targeting-meta-business-cofense.jpg

cyber-attack-targeting-meta-business-cofense.jpg

110 ms

cofense-ai-alone-is-not-enough.jpg

cofense-ai-alone-is-not-enough.jpg

108 ms

Accessibility Review

phishme.com accessibility score

87

Accessibility Issues

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

High

[aria-*] attributes do not match their roles

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.

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

phishme.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

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

phishme.com SEO score

90

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

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

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

phishme.com

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