Tools & Wizards About Us
johnsorthopedic.com screenshot

Report Summary

  • 63

    Performance

    Renders faster than
    77% of other websites

  • 93

    Accessibility

    Visual factors better than
    that of 80% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 79

    SEO

    Google-friendlier than
    40% of websites

johnsorthopedic.com

Orthopedic Braces Toronto | Home | John’s Orthopedic Specialties

Page Load Speed

1.2 sec in total

First Response

87 ms

Resources Loaded

921 ms

Page Rendered

226 ms

johnsorthopedic.com screenshot

About Website

Welcome to johnsorthopedic.com homepage info - get ready to check John S Orthopedic best content right away, or after learning these important things about johnsorthopedic.com

John’s Orthopedic Specialties Inc. provides residents of Toronto with orthopedic braces for backs, knees, feet and more. Call today. In business since 1977!

Visit johnsorthopedic.com

Key Findings

We analyzed Johnsorthopedic.com page load time and found that the first response time was 87 ms and then it took 1.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.

Performance Metrics

johnsorthopedic.com performance score

63

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.2 s

79/100

10%

LCP (Largest Contentful Paint)

Value3.3 s

69/100

25%

SI (Speed Index)

Value4.4 s

74/100

10%

TBT (Total Blocking Time)

Value460 ms

62/100

30%

CLS (Cumulative Layout Shift)

Value0.239

52/100

15%

TTI (Time to Interactive)

Value8.3 s

40/100

10%

Network Requests Diagram

johnsorthopedic.com

87 ms

johnsorthopedic.com

135 ms

gtm5445.html

49 ms

analytics.js

73 ms

css

30 ms

Our browser made a total of 64 requests to load all elements on the main page. We found that 34% of them (22 requests) were addressed to the original Johnsorthopedic.com, 23% (15 requests) were made to Site-assets.cdnmns.com and 17% (11 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (412 ms) relates to the external source Engage.commander1.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 118.9 kB (25%)

Content Size

477.8 kB

After Optimization

358.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-85%

Potential reduce by 111.7 kB

  • Original 130.9 kB
  • After minification 117.1 kB
  • After compression 19.1 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 13.7 kB, which is 11% 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 111.7 kB or 85% of the original size.

Image Optimization

-3%

Potential reduce by 5.5 kB

  • Original 204.2 kB
  • After minification 198.7 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. John S Orthopedic images are well optimized though.

JavaScript Optimization

-2%

Potential reduce by 1.5 kB

  • Original 101.1 kB
  • After minification 101.1 kB
  • After compression 99.6 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

-0%

Potential reduce by 104 B

  • Original 41.6 kB
  • After minification 41.6 kB
  • After compression 41.5 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. Johnsorthopedic.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 23 (52%)

Requests Now

44

After Optimization

21

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

johnsorthopedic.com

johnsorthopedic.com

87 ms

johnsorthopedic.com

johnsorthopedic.com

135 ms

gtm5445.html

gtm5445.html

49 ms

analytics.js

analytics.js

73 ms

css

css

30 ms

external-libs9cbf.css

external-libs9cbf.css

55 ms

loader9cbf.js

loader9cbf.js

110 ms

tc.js

tc.js

113 ms

ypca_tracker.js

ypca_tracker.js

111 ms

logo-whe001.png

logo-whe001.png

47 ms

mobile_logo.png

mobile_logo.png

45 ms

IMG_9548.jpg

IMG_9548.jpg

129 ms

001.jpg

001.jpg

47 ms

orthopedics.jpg

orthopedics.jpg

70 ms

home-2.jpg

home-2.jpg

48 ms

knee-cta.png

knee-cta.png

64 ms

ortho-cta.png

ortho-cta.png

69 ms

stocking-cta.png

stocking-cta.png

69 ms

CFIB.png

CFIB.png

68 ms

logo-whe001.png

logo-whe001.png

78 ms

user-styleaa92.css

user-styleaa92.css

99 ms

collect

collect

34 ms

collect

collect

45 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

98 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

33 ms

monotracker.js

monotracker.js

38 ms

jquery-modern.js

jquery-modern.js

41 ms

clear.gif

clear.gif

89 ms

386 ms

css

css

20 ms

reach

reach

412 ms

touch-events.js

touch-events.js

38 ms

nav.js

nav.js

38 ms

jquery.serialize-object.js

jquery.serialize-object.js

56 ms

monooverlay.js

monooverlay.js

52 ms

jquery.nanoscroller.js

jquery.nanoscroller.js

52 ms

anchor.js

anchor.js

55 ms

rowgroup.js

rowgroup.js

58 ms

fbsdk.js

fbsdk.js

58 ms

twittersdk.js

twittersdk.js

58 ms

lang.js

lang.js

57 ms

emailshare.js

emailshare.js

54 ms

api3071.html

api3071.html

50 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

28 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf

29 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf

35 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

34 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVc.ttf

34 ms

Yq6R-LCAWCX3-6Ky7FAFrOF6lw.ttf

Yq6R-LCAWCX3-6Ky7FAFrOF6lw.ttf

54 ms

S6uyw4BMUTPHjx4wWw.ttf

S6uyw4BMUTPHjx4wWw.ttf

34 ms

S6u9w4BMUTPHh7USSwiPHA.ttf

S6u9w4BMUTPHh7USSwiPHA.ttf

34 ms

S6u8w4BMUTPHh30AXC-v.ttf

S6u8w4BMUTPHh30AXC-v.ttf

45 ms

S6u9w4BMUTPHh6UVSwiPHA.ttf

S6u9w4BMUTPHh6UVSwiPHA.ttf

45 ms

S6u9w4BMUTPHh50XSwiPHA.ttf

S6u9w4BMUTPHh50XSwiPHA.ttf

45 ms

en.json

en.json

9 ms

widgets.js

widgets.js

35 ms

sdk.js

sdk.js

30 ms

sdk.js

sdk.js

15 ms

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

35 ms

settings

settings

67 ms

button.856debeac157d9669cf51e73a08fbc93.js

button.856debeac157d9669cf51e73a08fbc93.js

3 ms

embeds

embeds

21 ms

tweet_button.2f70fb173b9000da126c79afe2098f02.en.html

tweet_button.2f70fb173b9000da126c79afe2098f02.en.html

10 ms

reach

reach

89 ms

Accessibility Review

johnsorthopedic.com accessibility score

93

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

button, link, and menuitem elements do not have accessible names.

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.

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

johnsorthopedic.com best practices score

58

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

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

johnsorthopedic.com SEO score

79

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

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

johnsorthopedic.com

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