Tools & Wizards About Us
lake.care screenshot

Report Summary

  • 68

    Performance

    Renders faster than
    80% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 68% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

lake.care

Nursing home |St. Petersburg Florida | Eagle Lake Nursing and Rehab Center

Page Load Speed

957 ms in total

First Response

123 ms

Resources Loaded

753 ms

Page Rendered

81 ms

lake.care screenshot

About Website

Welcome to lake.care homepage info - get ready to check Lake best content right away, or after learning these important things about lake.care

Welcome to Eagle Lake Nursing and Rehab Center, Long or Short term care with Full Rehabilitation Services.We provide Healthcare in St. Petersburg. This Nursing Facility is located in St Pete Florida a...

Visit lake.care

Key Findings

We analyzed Lake.care page load time and found that the first response time was 123 ms and then it took 834 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.

Performance Metrics

lake.care performance score

68

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.4 s

72/100

10%

LCP (Largest Contentful Paint)

Value3.4 s

67/100

25%

SI (Speed Index)

Value2.4 s

98/100

10%

TBT (Total Blocking Time)

Value520 ms

56/100

30%

CLS (Cumulative Layout Shift)

Value0.008

100/100

15%

TTI (Time to Interactive)

Value10.9 s

21/100

10%

Network Requests Diagram

www.lake.care

123 ms

minified.js

74 ms

focus-within-polyfill.js

129 ms

polyfill.min.js

66 ms

thunderbolt-commons.b70ee867.bundle.min.js

168 ms

Our browser made a total of 21 requests to load all elements on the main page. We found that 5% of them (1 request) were addressed to the original Lake.care, 57% (12 requests) were made to Static.parastorage.com and 24% (5 requests) were made to Static.wixstatic.com. The less responsive or slowest element that took the longest time to load (281 ms) relates to the external source Static.wixstatic.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 399.6 kB (44%)

Content Size

908.3 kB

After Optimization

508.7 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Lake.care main page is 908.3 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. 50% of websites need less resources to load. HTML takes 460.6 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 359.2 kB

  • Original 460.6 kB
  • After minification 458.9 kB
  • After compression 101.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. 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 359.2 kB or 78% of the original size.

Image Optimization

-2%

Potential reduce by 2.8 kB

  • Original 157.8 kB
  • After minification 155.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. Lake images are well optimized though.

JavaScript Optimization

-13%

Potential reduce by 37.6 kB

  • Original 289.9 kB
  • After minification 289.8 kB
  • After compression 252.2 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 37.6 kB or 13% of the original size.

Requests Breakdown

Number of requests can be reduced by 10 (50%)

Requests Now

20

After Optimization

10

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.lake.care

www.lake.care

123 ms

minified.js

minified.js

74 ms

focus-within-polyfill.js

focus-within-polyfill.js

129 ms

polyfill.min.js

polyfill.min.js

66 ms

thunderbolt-commons.b70ee867.bundle.min.js

thunderbolt-commons.b70ee867.bundle.min.js

168 ms

main.317ed945.bundle.min.js

main.317ed945.bundle.min.js

185 ms

main.renderer.1d21f023.bundle.min.js

main.renderer.1d21f023.bundle.min.js

168 ms

lodash.min.js

lodash.min.js

183 ms

react.production.min.js

react.production.min.js

168 ms

react-dom.production.min.js

react-dom.production.min.js

185 ms

siteTags.bundle.min.js

siteTags.bundle.min.js

177 ms

eagle-lake-logo.png

eagle-lake-logo.png

281 ms

bundle.min.js

bundle.min.js

159 ms

a9ff3b_af817ad90ae54d8ea02629cc23427e72.png

a9ff3b_af817ad90ae54d8ea02629cc23427e72.png

149 ms

HighFive)_edited.jpg

HighFive)_edited.jpg

242 ms

a9ff3b_af817ad90ae54d8ea02629cc23427e72.png

a9ff3b_af817ad90ae54d8ea02629cc23427e72.png

148 ms

a9ff3b_4a8688ee55da4e799ab5ca3bd06290a5.png

a9ff3b_4a8688ee55da4e799ab5ca3bd06290a5.png

148 ms

deprecation-en.v5.html

deprecation-en.v5.html

86 ms

bolt-performance

bolt-performance

117 ms

deprecation-style.v5.css

deprecation-style.v5.css

22 ms

right-arrow.svg

right-arrow.svg

22 ms

Accessibility Review

lake.care accessibility score

88

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

Heading elements are not in a sequentially-descending order

Best Practices

lake.care 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

lake.care SEO score

93

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

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 Lake.care 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 Lake.care 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

lake.care

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