Tools & Wizards About Us
schnepp.net screenshot

Report Summary

  • 0

    Performance

  • 95

    Accessibility

    Visual factors better than
    that of 87% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 99

    SEO

    Google-friendlier than
    94% of websites

schnepp.net

Schnepp Senior Care & Rehab Center - A NexCare Managed Community

Page Load Speed

5.7 sec in total

First Response

91 ms

Resources Loaded

5 sec

Page Rendered

605 ms

schnepp.net screenshot

About Website

Visit schnepp.net now to see the best up-to-date Schnepp content and also check out these interesting facts you probably never knew about schnepp.net

Short-Term Rehabilitation and Long-Term Care Services; Enjoy an EPIC Stay in St. Louis, Michigan! Call us at 989-681-5721 for info or to schedule a tour!

Visit schnepp.net

Key Findings

We analyzed Schnepp.net page load time and found that the first response time was 91 ms and then it took 5.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

schnepp.net performance score

0

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.8 s

0/100

10%

LCP (Largest Contentful Paint)

Value14.4 s

0/100

25%

SI (Speed Index)

Value21.7 s

0/100

10%

TBT (Total Blocking Time)

Value17,490 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value2

0/100

15%

TTI (Time to Interactive)

Value30.2 s

0/100

10%

Network Requests Diagram

schnepp.net

91 ms

2994 ms

js

88 ms

slick.css

64 ms

jquery.min.js

67 ms

Our browser made a total of 76 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Schnepp.net, 57% (43 requests) were made to Nexcarehealth.com and 8% (6 requests) were made to Maps.google.com. The less responsive or slowest element that took the longest time to load (3 sec) relates to the external source Nexcarehealth.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 201.1 kB (18%)

Content Size

1.1 MB

After Optimization

924.3 kB

  • Images
  • JavaScript
  • CSS

In fact, the total size of Schnepp.net 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 836.0 kB which makes up the majority of the site volume.

HTML Optimization

-0%

Potential reduce by -8 B

  • Original 0 B

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 web page is already compressed.

Image Optimization

-9%

Potential reduce by 71.6 kB

  • Original 836.0 kB
  • After minification 764.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. Schnepp images are well optimized though.

JavaScript Optimization

-45%

Potential reduce by 127.2 kB

  • Original 285.1 kB
  • After minification 284.9 kB
  • After compression 157.8 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 127.2 kB or 45% of the original size.

CSS Optimization

-52%

Potential reduce by 2.2 kB

  • Original 4.3 kB
  • After minification 4.0 kB
  • After compression 2.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. Schnepp.net needs all CSS files to be minified and compressed as it can save up to 2.2 kB or 52% of the original size.

Requests Breakdown

Number of requests can be reduced by 41 (59%)

Requests Now

69

After Optimization

28

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

schnepp.net

schnepp.net

91 ms

2994 ms

js

js

88 ms

slick.css

slick.css

64 ms

jquery.min.js

jquery.min.js

67 ms

storelocator.css

storelocator.css

1047 ms

handlebars.js

handlebars.js

196 ms

js

js

106 ms

jquery.storelocator.js

jquery.storelocator.js

221 ms

normalize.css

normalize.css

196 ms

style.css

style.css

198 ms

job-styles.css

job-styles.css

182 ms

social-icon-styles.css

social-icon-styles.css

207 ms

style.min.css

style.min.css

566 ms

styles.css

styles.css

227 ms

css3-mediaqueries.js

css3-mediaqueries.js

565 ms

jquery.min.js

jquery.min.js

600 ms

jquery-migrate.min.js

jquery-migrate.min.js

588 ms

job-scripts.js

job-scripts.js

588 ms

api.js

api.js

72 ms

js

js

89 ms

slick.min.js

slick.min.js

598 ms

slickinitialize.js

slickinitialize.js

610 ms

index.js

index.js

615 ms

index.js

index.js

615 ms

api.js

api.js

96 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

615 ms

wp-polyfill.min.js

wp-polyfill.min.js

623 ms

index.js

index.js

623 ms

akismet-frontend.js

akismet-frontend.js

628 ms

analytics.js

analytics.js

22 ms

collect

collect

13 ms

gen_204

gen_204

153 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

133 ms

recaptcha__en.js

recaptcha__en.js

181 ms

fbevents.js

fbevents.js

99 ms

js

js

177 ms

Schnepp_Logo-white.png

Schnepp_Logo-white.png

171 ms

silver-2019.png

silver-2019.png

172 ms

gptw-apr-22.png

gptw-apr-22.png

172 ms

header-swoop.png

header-swoop.png

90 ms

schnepp1-m.jpg

schnepp1-m.jpg

170 ms

schnepp1-d.jpg

schnepp1-d.jpg

174 ms

swoop-bkg-cover.png

swoop-bkg-cover.png

173 ms

jobicon-therapy-2.png

jobicon-therapy-2.png

174 ms

icon-health-wellbeing-services.png

icon-health-wellbeing-services.png

316 ms

rehab1-m.jpg

rehab1-m.jpg

307 ms

swoop-bkg-from-bottom.png

swoop-bkg-from-bottom.png

315 ms

swoop-bkg.png

swoop-bkg.png

314 ms

swoop-bkg-cover-reversed-locations.png

swoop-bkg-cover-reversed-locations.png

315 ms

logo-color.png

logo-color.png

306 ms

soc-fb.png

soc-fb.png

313 ms

soc-tw.png

soc-tw.png

313 ms

soc-ig.png

soc-ig.png

386 ms

soc-li.png

soc-li.png

386 ms

epic.jpg

epic.jpg

387 ms

conversion_async.js

conversion_async.js

34 ms

mtl3cwg.js

mtl3cwg.js

230 ms

283 ms

identity.js

identity.js

146 ms

480110196388302

480110196388302

285 ms

d

d

30 ms

d

d

23 ms

d

d

43 ms

d

d

44 ms

34 ms

p.gif

p.gif

45 ms

common.js

common.js

20 ms

util.js

util.js

36 ms

map.js

map.js

28 ms

marker.js

marker.js

31 ms

openhand_8_8.cur

openhand_8_8.cur

70 ms

onion.js

onion.js

34 ms

ViewportInfoService.GetViewportInfo

ViewportInfoService.GetViewportInfo

116 ms

transparent.png

transparent.png

12 ms

spotlight-poi3.png

spotlight-poi3.png

16 ms

Accessibility Review

schnepp.net accessibility score

95

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

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

schnepp.net SEO score

99

Search Engine Optimization Advices

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Schnepp.net can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Schnepp.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

schnepp.net

Open Graph description is not detected on the main page of Schnepp. 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: