Tools & Wizards About Us
greatlakeso.com screenshot

Report Summary

  • 51

    Performance

    Renders faster than
    69% of other websites

  • 82

    Accessibility

    Visual factors better than
    that of 52% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

greatlakeso.com

Great Lakes Orthopaedics | Orthopedic Surgeon Center in Great Lakes

Page Load Speed

6.6 sec in total

First Response

1.8 sec

Resources Loaded

4.4 sec

Page Rendered

366 ms

greatlakeso.com screenshot

About Website

Welcome to greatlakeso.com homepage info - get ready to check Great Lakes O best content for United States right away, or after learning these important things about greatlakeso.com

Great Lakes Orthopaedics is proudly serving Great Lakes, MI for over 60 Years. We perform over 1000 orthopedic surgeries each year, find out what makes Great Lakes Orthopaedics best.

Visit greatlakeso.com

Key Findings

We analyzed Greatlakeso.com page load time and found that the first response time was 1.8 sec and then it took 4.7 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

greatlakeso.com performance score

51

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.9 s

52/100

10%

LCP (Largest Contentful Paint)

Value17.9 s

0/100

25%

SI (Speed Index)

Value10.7 s

7/100

10%

TBT (Total Blocking Time)

Value140 ms

95/100

30%

CLS (Cumulative Layout Shift)

Value0.058

98/100

15%

TTI (Time to Interactive)

Value11.3 s

19/100

10%

Network Requests Diagram

greatlakeso.com

1824 ms

js

57 ms

flatpickr.min.css

111 ms

modern.css

111 ms

frontend-gtag.min.js

116 ms

Our browser made a total of 51 requests to load all elements on the main page. We found that 39% of them (20 requests) were addressed to the original Greatlakeso.com, 55% (28 requests) were made to Fonts.gstatic.com and 2% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Greatlakeso.com.

Page Optimization Overview & Recommendations

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

Content Size

2.2 MB

After Optimization

2.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Greatlakeso.com main page is 2.2 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.6 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 192.3 kB

  • Original 229.3 kB
  • After minification 225.1 kB
  • After compression 36.9 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 192.3 kB or 84% of the original size.

Image Optimization

-1%

Potential reduce by 10.0 kB

  • Original 1.6 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. Great Lakes O images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 1.3 kB

  • Original 351.7 kB
  • After minification 351.7 kB
  • After compression 350.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.

CSS Optimization

-1%

Potential reduce by 262 B

  • Original 19.0 kB
  • After minification 19.0 kB
  • After compression 18.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. Greatlakeso.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 9 (43%)

Requests Now

21

After Optimization

12

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

greatlakeso.com

greatlakeso.com

1824 ms

js

js

57 ms

flatpickr.min.css

flatpickr.min.css

111 ms

modern.css

modern.css

111 ms

frontend-gtag.min.js

frontend-gtag.min.js

116 ms

flatpickr.min.js

flatpickr.min.js

166 ms

all.js

all.js

166 ms

api.js

api.js

35 ms

jquery.min.js

jquery.min.js

270 ms

jquery-migrate.min.js

jquery-migrate.min.js

164 ms

scripts.min.js

scripts.min.js

292 ms

common.js

common.js

190 ms

Great-lakes-orthopeadics-2-e1569436175718.png

Great-lakes-orthopeadics-2-e1569436175718.png

151 ms

Great-Lakes-Orthopaedics-14-scaled.jpg

Great-Lakes-Orthopaedics-14-scaled.jpg

402 ms

Great-Lakes-O1.png

Great-Lakes-O1.png

244 ms

schedule-an-appointment.png

schedule-an-appointment.png

82 ms

Great-Lakes-Orthopaedics-8-300x200.jpg

Great-Lakes-Orthopaedics-8-300x200.jpg

244 ms

Great-Lakes-Orthopaedics-10-300x200.jpg

Great-Lakes-Orthopaedics-10-300x200.jpg

244 ms

Great-Lakes-Orthopaedics-6-300x200.jpg

Great-Lakes-Orthopaedics-6-300x200.jpg

244 ms

Great-Lakes-Orthopaedics-3-300x200.jpg

Great-Lakes-Orthopaedics-3-300x200.jpg

245 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0C4k.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0C4k.woff

90 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0C4n.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0C4n.ttf

146 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0C4k.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0C4k.woff

148 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0C4n.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0C4n.ttf

148 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1y4k.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1y4k.woff

149 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1y4n.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1y4n.ttf

150 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1y4k.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1y4k.woff

149 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1y4n.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1y4n.ttf

146 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1y4k.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1y4k.woff

149 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1y4n.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1y4n.ttf

151 ms

recaptcha__en.js

recaptcha__en.js

146 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Uw9.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Uw9.woff

75 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Uw-.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Uw-.ttf

74 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Ew9.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Ew9.woff

75 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Ew-.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Ew-.ttf

75 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Ew9.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Ew9.woff

75 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Ew-.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Ew-.ttf

76 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Ew9.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Ew9.woff

77 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Ew-.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Ew-.ttf

77 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Ew9.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Ew9.woff

77 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Ew-.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Ew-.ttf

78 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu170w9.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu170w9.woff

77 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu170w-.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu170w-.ttf

79 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM70w9.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM70w9.woff

79 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM70w-.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM70w-.ttf

79 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr70w9.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr70w9.woff

78 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr70w-.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr70w-.ttf

79 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC70w9.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC70w9.woff

80 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC70w-.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC70w-.ttf

81 ms

modules.woff

modules.woff

193 ms

style.min.css

style.min.css

61 ms

Accessibility Review

greatlakeso.com accessibility score

82

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

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

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

SEO Factors

greatlakeso.com SEO score

93

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

robots.txt is not valid

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

greatlakeso.com

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