Tools & Wizards About Us
greathorn.com screenshot

Report Summary

  • 46

    Performance

    Renders faster than
    65% of other websites

  • 77

    Accessibility

    Visual factors better than
    that of 44% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

greathorn.com

Comprehensive Email Security for Microsoft 365 & Google Workspace

Page Load Speed

1.9 sec in total

First Response

140 ms

Resources Loaded

1.2 sec

Page Rendered

502 ms

greathorn.com screenshot

About Website

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

GreatHorn is an API, cloud-native email security solution that mitigates the risk of business email compromise across Microsoft 365 and Google Workspace.

Visit greathorn.com

Key Findings

We analyzed Greathorn.com page load time and found that the first response time was 140 ms and then it took 1.7 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.

Performance Metrics

greathorn.com performance score

46

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.5 s

33/100

10%

LCP (Largest Contentful Paint)

Value3.5 s

63/100

25%

SI (Speed Index)

Value5.2 s

59/100

10%

TBT (Total Blocking Time)

Value720 ms

41/100

30%

CLS (Cumulative Layout Shift)

Value0.247

50/100

15%

TTI (Time to Interactive)

Value13.4 s

11/100

10%

Network Requests Diagram

greathorn.com

140 ms

www.greathorn.com

124 ms

www.greathorn.com

55 ms

jquery.min.js

17 ms

nxe4fxf.css

32 ms

Our browser made a total of 86 requests to load all elements on the main page. We found that 83% of them (71 requests) were addressed to the original Greathorn.com, 9% (8 requests) were made to Use.typekit.net and 1% (1 request) were made to P.typekit.net. The less responsive or slowest element that took the longest time to load (498 ms) belongs to the original domain Greathorn.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 221.6 kB (20%)

Content Size

1.1 MB

After Optimization

877.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-84%

Potential reduce by 212.7 kB

  • Original 254.0 kB
  • After minification 253.9 kB
  • After compression 41.3 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 212.7 kB or 84% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

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

JavaScript Optimization

-2%

Potential reduce by 6.7 kB

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

CSS Optimization

-2%

Potential reduce by 2.3 kB

  • Original 110.0 kB
  • After minification 108.0 kB
  • After compression 107.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. Greathorn.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 55 (80%)

Requests Now

69

After Optimization

14

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

greathorn.com

greathorn.com

140 ms

www.greathorn.com

www.greathorn.com

124 ms

www.greathorn.com

www.greathorn.com

55 ms

jquery.min.js

jquery.min.js

17 ms

nxe4fxf.css

nxe4fxf.css

32 ms

index.min.css

index.min.css

33 ms

style.css

style.css

48 ms

pagenavi-css.css

pagenavi-css.css

35 ms

ivory-search.min.css

ivory-search.min.css

30 ms

magnific-popup.min.css

magnific-popup.min.css

30 ms

core.min.css

core.min.css

34 ms

style.css

style.css

54 ms

dashicons.min.css

dashicons.min.css

52 ms

font-awesome.min.css

font-awesome.min.css

51 ms

front.min.css

front.min.css

47 ms

wpp.css

wpp.css

51 ms

style.min.css

style.min.css

82 ms

style.min.css

style.min.css

81 ms

style.min.css

style.min.css

87 ms

public.css

public.css

87 ms

style.css

style.css

88 ms

jquery.min.js

jquery.min.js

123 ms

jquery-migrate.min.js

jquery-migrate.min.js

126 ms

ie-compat.min.js

ie-compat.min.js

140 ms

wpp.min.js

wpp.min.js

139 ms

851792.js

851792.js

125 ms

email-decode.min.js

email-decode.min.js

121 ms

style.min.css

style.min.css

139 ms

tooltipster.bundle.min.css

tooltipster.bundle.min.css

136 ms

style.min.css

style.min.css

139 ms

slick.min.css

slick.min.css

141 ms

popup.min.js

popup.min.js

178 ms

app.js

app.js

177 ms

magnific-popup.js

magnific-popup.js

179 ms

main.min.js

main.min.js

180 ms

dtq-default-vb.js

dtq-default-vb.js

181 ms

front.min.js

front.min.js

182 ms

scripts.min.js

scripts.min.js

183 ms

smoothscroll.js

smoothscroll.js

182 ms

frontend.min.js

frontend.min.js

446 ms

jquery.fitvids.js

jquery.fitvids.js

156 ms

p.css

p.css

26 ms

jquery.mobile.js

jquery.mobile.js

184 ms

frontend-bundle.min.js

frontend-bundle.min.js

185 ms

frontend-bundle.min.js

frontend-bundle.min.js

185 ms

frontend-bundle.min.js

frontend-bundle.min.js

184 ms

new-tab.js

new-tab.js

184 ms

common.js

common.js

174 ms

smush-lazy-load.min.js

smush-lazy-load.min.js

171 ms

hoverIntent.min.js

hoverIntent.min.js

170 ms

maxmegamenu.js

maxmegamenu.js

334 ms

public.js

public.js

169 ms

ivory-search.min.js

ivory-search.min.js

333 ms

tooltipster.bundle.min.js

tooltipster.bundle.min.js

326 ms

slick.min.js

slick.min.js

324 ms

greathorn-logo-2c.svg

greathorn-logo-2c.svg

288 ms

GreatHorn_logo-2c-rev.svg

GreatHorn_logo-2c-rev.svg

322 ms

advanced-email-threats.png

advanced-email-threats.png

324 ms

reduce-phishing-response-time.png

reduce-phishing-response-time.png

370 ms

bec-phishing-attack-warnings.png

bec-phishing-attack-warnings.png

369 ms

orange-check.svg

orange-check.svg

368 ms

d

d

286 ms

d

d

321 ms

d

d

368 ms

d

d

409 ms

email-threat-assessment-icon.svg

email-threat-assessment-icon.svg

368 ms

fb.js

fb.js

311 ms

851792.js

851792.js

476 ms

leadflows.js

leadflows.js

440 ms

conversations-embed.js

conversations-embed.js

396 ms

851792.js

851792.js

397 ms

star-whole.svg

star-whole.svg

356 ms

GreatHorn_logo-2c.svg

GreatHorn_logo-2c.svg

396 ms

great-horn-owl-wide-bg-v2.png

great-horn-owl-wide-bg-v2.png

442 ms

header-bkgd-texture.png

header-bkgd-texture.png

365 ms

d

d

139 ms

d

d

138 ms

d

d

138 ms

d

d

140 ms

fa-brands-400.woff

fa-brands-400.woff

478 ms

fa-regular-400.woff

fa-regular-400.woff

439 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

467 ms

fa-solid-900.woff

fa-solid-900.woff

498 ms

modules.woff

modules.woff

142 ms

wARDj0u

wARDj0u

15 ms

cropped-greathorn-favicon.png

cropped-greathorn-favicon.png

45 ms

Accessibility Review

greathorn.com accessibility score

77

Accessibility Issues

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

Buttons do not have an accessible name

High

Links do not have a discernible name

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

[id] attributes on active, focusable elements are not unique

High

Heading elements are not in a sequentially-descending order

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

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

Page has valid source maps

SEO Factors

greathorn.com SEO score

82

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

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

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

greathorn.com

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