Tools & Wizards About Us
windsorgardens.com screenshot

Report Summary

  • 30

    Performance

    Renders faster than
    50% of other websites

  • 90

    Accessibility

    Visual factors better than
    that of 74% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

windsorgardens.com

Senior Living | Windsor Gardens of Bardstown | Kentucky

Page Load Speed

1.6 sec in total

First Response

43 ms

Resources Loaded

1.1 sec

Page Rendered

439 ms

windsorgardens.com screenshot

About Website

Welcome to windsorgardens.com homepage info - get ready to check Windsor Gardens best content right away, or after learning these important things about windsorgardens.com

Windsor Gardens of Bardstown offers personalized senior living. Learn more about the lifestyles we offer & our commitment to our residents.

Visit windsorgardens.com

Key Findings

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

windsorgardens.com performance score

30

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

38/100

10%

LCP (Largest Contentful Paint)

Value9.6 s

0/100

25%

SI (Speed Index)

Value5.5 s

55/100

10%

TBT (Total Blocking Time)

Value510 ms

57/100

30%

CLS (Cumulative Layout Shift)

Value0.551

13/100

15%

TTI (Time to Interactive)

Value11.5 s

18/100

10%

Network Requests Diagram

windsorgardens.com

43 ms

windsorgardens.com

548 ms

glightbox.min.css

60 ms

sbi-styles.min.css

64 ms

style.min.css

90 ms

Our browser made a total of 52 requests to load all elements on the main page. We found that 62% of them (32 requests) were addressed to the original Windsorgardens.com, 10% (5 requests) were made to Cdnjs.cloudflare.com and 8% (4 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (548 ms) belongs to the original domain Windsorgardens.com.

Page Optimization Overview & Recommendations

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

Content Size

938.8 kB

After Optimization

805.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-85%

Potential reduce by 115.3 kB

  • Original 135.0 kB
  • After minification 107.3 kB
  • After compression 19.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. This page needs HTML code to be minified as it can gain 27.7 kB, which is 20% 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 115.3 kB or 85% of the original size.

Image Optimization

-3%

Potential reduce by 16.2 kB

  • Original 592.1 kB
  • After minification 576.0 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. Windsor Gardens images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 1.3 kB

  • Original 138.3 kB
  • After minification 137.7 kB
  • After compression 137.0 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

-1%

Potential reduce by 724 B

  • Original 73.4 kB
  • After minification 73.4 kB
  • After compression 72.7 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. Windsorgardens.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 35 (76%)

Requests Now

46

After Optimization

11

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

windsorgardens.com

windsorgardens.com

43 ms

windsorgardens.com

windsorgardens.com

548 ms

glightbox.min.css

glightbox.min.css

60 ms

sbi-styles.min.css

sbi-styles.min.css

64 ms

style.min.css

style.min.css

90 ms

style-index.css

style-index.css

93 ms

platform-footer-styles.css

platform-footer-styles.css

96 ms

hero.css

hero.css

183 ms

global.css

global.css

194 ms

hover.css

hover.css

126 ms

animate.min.css

animate.min.css

52 ms

cff-style.min.css

cff-style.min.css

159 ms

font-awesome.min.css

font-awesome.min.css

54 ms

callout.css

callout.css

164 ms

styles-bundle-79.css

styles-bundle-79.css

210 ms

jquery.min.js

jquery.min.js

223 ms

jquery-migrate.min.js

jquery-migrate.min.js

224 ms

load.js

load.js

43 ms

ecps-pop-up-public.js

ecps-pop-up-public.js

238 ms

email-decode.min.js

email-decode.min.js

184 ms

glightbox.min.js

glightbox.min.js

50 ms

logician-animation.css

logician-animation.css

245 ms

highlights.css

highlights.css

255 ms

ekko-lightbox.css

ekko-lightbox.css

50 ms

slick.min.css

slick.min.css

39 ms

accessible-slick-theme.min.css

accessible-slick-theme.min.css

41 ms

custom.js

custom.js

276 ms

cff-scripts.min.js

cff-scripts.min.js

343 ms

theme.min.js

theme.min.js

344 ms

lazysizes.min.js

lazysizes.min.js

344 ms

ls.unveilhooks.min.js

ls.unveilhooks.min.js

347 ms

navbar-sibling.js

navbar-sibling.js

347 ms

ekko-lightbox.min.js

ekko-lightbox.min.js

54 ms

slick.min.js

slick.min.js

43 ms

css2

css2

63 ms

css2

css2

81 ms

ad.collect.min.js.jgz

ad.collect.min.js.jgz

43 ms

gtm.js

gtm.js

119 ms

goodworks-windsorgardensbardstown-hp-nav-background-image.jpg

goodworks-windsorgardensbardstown-hp-nav-background-image.jpg

139 ms

sbi-sprite.png

sbi-sprite.png

88 ms

goodworks-windsorgardensbardstown-hp-nav-lgoo@2x.png

goodworks-windsorgardensbardstown-hp-nav-lgoo@2x.png

89 ms

goodworks-windsorgardensbardstown-MobileHero-2022.jpg

goodworks-windsorgardensbardstown-MobileHero-2022.jpg

71 ms

goodworks-windsorgardensbardstown-hp-nav-background-image.jpg

goodworks-windsorgardensbardstown-hp-nav-background-image.jpg

70 ms

goodworks-windsorgardensbardstown-hp-sectiondivider@2x.png

goodworks-windsorgardensbardstown-hp-sectiondivider@2x.png

87 ms

jd.main.min.js.jgz

jd.main.min.js.jgz

16 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0C4n.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0C4n.ttf

35 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1y4n.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1y4n.ttf

54 ms

wlppgwHKFkZgtmSR3NB0oRJXsCx2Cw.ttf

wlppgwHKFkZgtmSR3NB0oRJXsCx2Cw.ttf

74 ms

wlppgwHKFkZgtmSR3NB0oRJX1C12Cw.ttf

wlppgwHKFkZgtmSR3NB0oRJX1C12Cw.ttf

75 ms

goodworks-windsorgardensbardstown-hp-hero-image-1.jpg

goodworks-windsorgardensbardstown-hp-hero-image-1.jpg

79 ms

GOODWORKS-NOV-BANNER.jpg

GOODWORKS-NOV-BANNER.jpg

72 ms

goodworks-clarkesville-hp-section02-background-image.jpg

goodworks-clarkesville-hp-section02-background-image.jpg

62 ms

Accessibility Review

windsorgardens.com accessibility score

90

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

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

windsorgardens.com best practices score

92

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

Page has valid source maps

SEO Factors

windsorgardens.com SEO score

85

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

windsorgardens.com

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