Tools & Wizards About Us
greystone.net screenshot

Report Summary

  • 30

    Performance

    Renders faster than
    50% of other websites

  • 93

    Accessibility

    Visual factors better than
    that of 80% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 87

    SEO

    Google-friendlier than
    65% of websites

greystone.net

Greystone.Net | Education and Digital Consulting for Hospitals

Page Load Speed

931 ms in total

First Response

41 ms

Resources Loaded

622 ms

Page Rendered

268 ms

greystone.net screenshot

About Website

Click here to check amazing Greystone content. Otherwise, check out these important facts you probably never knew about greystone.net

Greystone.Net provides digital education and web consulting for hospitals and digital planning for healthcare marketers.

Visit greystone.net

Key Findings

We analyzed Greystone.net page load time and found that the first response time was 41 ms and then it took 890 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.

Performance Metrics

greystone.net performance score

30

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

39/100

10%

LCP (Largest Contentful Paint)

Value14.8 s

0/100

25%

SI (Speed Index)

Value5.8 s

49/100

10%

TBT (Total Blocking Time)

Value1,290 ms

18/100

30%

CLS (Cumulative Layout Shift)

Value0.028

100/100

15%

TTI (Time to Interactive)

Value13.1 s

12/100

10%

Network Requests Diagram

greystone.net

41 ms

greystone.net

79 ms

otSDKStub.js

52 ms

api.js

46 ms

bootstrap.min.css

25 ms

Our browser made a total of 64 requests to load all elements on the main page. We found that 77% of them (49 requests) were addressed to the original Greystone.net, 5% (3 requests) were made to Cookie-cdn.cookiepro.com and 5% (3 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (314 ms) relates to the external source Cookie-cdn.cookiepro.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 171.9 kB (9%)

Content Size

1.8 MB

After Optimization

1.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Greystone.net main page is 1.8 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. 75% 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.5 MB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 56.2 kB

  • Original 63.7 kB
  • After minification 30.3 kB
  • After compression 7.5 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 33.4 kB, which is 52% 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 56.2 kB or 88% of the original size.

Image Optimization

-4%

Potential reduce by 66.7 kB

  • Original 1.5 MB
  • After minification 1.5 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. Greystone images are well optimized though.

JavaScript Optimization

-14%

Potential reduce by 18.3 kB

  • Original 130.0 kB
  • After minification 130.0 kB
  • After compression 111.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 18.3 kB or 14% of the original size.

CSS Optimization

-32%

Potential reduce by 30.7 kB

  • Original 96.8 kB
  • After minification 96.6 kB
  • After compression 66.1 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. Greystone.net needs all CSS files to be minified and compressed as it can save up to 30.7 kB or 32% of the original size.

Requests Breakdown

Number of requests can be reduced by 30 (56%)

Requests Now

54

After Optimization

24

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

greystone.net

greystone.net

41 ms

greystone.net

greystone.net

79 ms

otSDKStub.js

otSDKStub.js

52 ms

api.js

api.js

46 ms

bootstrap.min.css

bootstrap.min.css

25 ms

video.css

video.css

39 ms

font-awesome.min.css

font-awesome.min.css

36 ms

ionicons.min.css

ionicons.min.css

36 ms

slick.css

slick.css

33 ms

stacktable.css

stacktable.css

32 ms

style.css

style.css

72 ms

uncompress-style.css

uncompress-style.css

37 ms

CookiePro.css

CookiePro.css

36 ms

ScriptResource.axd

ScriptResource.axd

38 ms

ScriptResource.axd

ScriptResource.axd

39 ms

ScriptResource.axd

ScriptResource.axd

43 ms

ScriptResource.axd

ScriptResource.axd

39 ms

Frontend.css

Frontend.css

39 ms

jquery.blockUI.js

jquery.blockUI.js

45 ms

jquery.mousewheel.min.js

jquery.mousewheel.min.js

43 ms

bootstrap.min.js

bootstrap.min.js

131 ms

wow.min.js

wow.min.js

45 ms

slick.min.js

slick.min.js

136 ms

stacktable.js

stacktable.js

69 ms

jquery.scrollify.min.js

jquery.scrollify.min.js

135 ms

scripts.js

scripts.js

215 ms

js

js

246 ms

fc1573ac-587e-4026-a699-390e826953e1.json

fc1573ac-587e-4026-a699-390e826953e1.json

314 ms

gtm.js

gtm.js

227 ms

gtm.js

gtm.js

304 ms

recaptcha__en.js

recaptcha__en.js

225 ms

h-header-bg.jpg

h-header-bg.jpg

139 ms

greystone-net-logo.png

greystone-net-logo.png

140 ms

toggle-signin-icon.png

toggle-signin-icon.png

139 ms

navbar-brand.png

navbar-brand.png

136 ms

greystone-brand-sml.png

greystone-brand-sml.png

135 ms

nav-icon-resources.png

nav-icon-resources.png

140 ms

nav-icon-prof-services.png

nav-icon-prof-services.png

141 ms

nav-icon-prof-dev.png

nav-icon-prof-dev.png

147 ms

webinar-icon.png

webinar-icon.png

223 ms

nav-icon-vendor.png

nav-icon-vendor.png

148 ms

homepage-greymatters.png

homepage-greymatters.png

225 ms

patient-experience-technology.png

patient-experience-technology.png

224 ms

homepage-news-images-brochure-02.png

homepage-news-images-brochure-02.png

226 ms

h-engage-bg.png

h-engage-bg.png

230 ms

icon-bubble-gray.png

icon-bubble-gray.png

224 ms

arrow-right-white.png

arrow-right-white.png

225 ms

icon-calendar-gray.png

icon-calendar-gray.png

228 ms

h-contact-bg.jpg

h-contact-bg.jpg

226 ms

greystone-brand-footer.png

greystone-brand-footer.png

227 ms

ProximaNova-Regular.otf

ProximaNova-Regular.otf

142 ms

ProximaNova-Medium.otf

ProximaNova-Medium.otf

144 ms

ProximaNova-Bold.otf

ProximaNova-Bold.otf

143 ms

ProximaNova-Light.otf

ProximaNova-Light.otf

143 ms

ionicons.ttf

ionicons.ttf

144 ms

fallback

fallback

76 ms

print.css

print.css

53 ms

location

location

72 ms

fallback__ltr.css

fallback__ltr.css

4 ms

css

css

28 ms

otBannerSdk.js

otBannerSdk.js

19 ms

logo_48.png

logo_48.png

12 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

17 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

21 ms

Accessibility Review

greystone.net accessibility score

93

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

greystone.net 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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

greystone.net SEO score

87

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 Greystone.net 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 Greystone.net 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

greystone.net

Open Graph description is not detected on the main page of Greystone. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: