2.4 sec in total
148 ms
1.1 sec
1.2 sec
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.comWe analyzed Greathorn.com page load time and found that the first response time was 148 ms and then it took 2.2 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.
greathorn.com performance score
name
value
score
weighting
Value3.6 s
32/100
10%
Value4.1 s
46/100
25%
Value3.7 s
85/100
10%
Value30 ms
100/100
30%
Value0.025
100/100
15%
Value4.3 s
85/100
10%
148 ms
162 ms
273 ms
76 ms
29 ms
Our browser made a total of 61 requests to load all elements on the main page. We found that 84% of them (51 requests) were addressed to the original Greathorn.com, 13% (8 requests) were made to Use.typekit.net and 2% (1 request) were made to P.typekit.net. The less responsive or slowest element that took the longest time to load (372 ms) belongs to the original domain Greathorn.com.
Page size can be reduced by 173.8 kB (32%)
535.1 kB
361.2 kB
In fact, the total size of Greathorn.com main page is 535.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. HTML takes 202.7 kB which makes up the majority of the site volume.
Potential reduce by 172.1 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 172.1 kB or 85% of the original size.
Potential reduce by 0 B
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.
Potential reduce by 1.4 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.
Potential reduce by 277 B
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.
Number of requests can be reduced by 32 (67%)
48
16
The browser has sent 48 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 24 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
greathorn.com
148 ms
www.greathorn.com
162 ms
www.greathorn.com
273 ms
nxe4fxf.css
76 ms
style.css
29 ms
dashicons.min.css
74 ms
font-awesome.min.css
69 ms
style.dev.css
95 ms
style.css
58 ms
shortcodes_responsive.css
63 ms
email-decode.min.js
54 ms
mediaelementplayer-legacy.min.css
67 ms
wp-mediaelement.min.css
69 ms
frontend-builder-global-functions.js
67 ms
app.js
64 ms
jquery.mobile.custom.min.js
68 ms
custom.js
70 ms
smoothscroll.js
215 ms
frontend.min.js
80 ms
frontend-builder-scripts.js
218 ms
frontend-bundle.min.js
216 ms
new-tab.js
216 ms
jquery.fitvids.js
218 ms
waypoints.min.js
217 ms
common.js
218 ms
smush-lazy-load.min.js
221 ms
hoverIntent.min.js
218 ms
maxmegamenu.js
220 ms
public.js
226 ms
mediaelement-and-player.min.js
219 ms
mediaelement-migrate.min.js
225 ms
wp-mediaelement.min.js
228 ms
et_shortcodes_frontend.js
226 ms
salvattore.min.js
226 ms
rocket-loader.min.js
220 ms
greathorn-logo-2c.svg
232 ms
GreatHorn_logo-2c-rev.svg
227 ms
preanalysis-icon-orange.svg
229 ms
account-takeover-protection-icon-orange.svg
230 ms
mailbox-intelligence-icon-orange.svg
198 ms
microsoft-365-logo.svg
189 ms
google-workspace-logo.svg
191 ms
p.css
24 ms
star-whole.svg
372 ms
email-threat-assessment-icon.svg
187 ms
GreatHorn_logo-2c.svg
186 ms
orange-check.svg
159 ms
greathorn-owl-background.jpg
163 ms
dashboard-bkgd-screened10.jpg
160 ms
header-bkgd-texture.png
161 ms
d
168 ms
d
214 ms
d
249 ms
d
248 ms
d
89 ms
d
88 ms
d
90 ms
d
87 ms
modules.ttf
51 ms
wARDj0u
3 ms
smush-lazy-load.min.js
42 ms
greathorn.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
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
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
greathorn.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
greathorn.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
EN
EN
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.
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: