Tools & Wizards About Us
swordhealth.com screenshot

Report Summary

  • 38

    Performance

    Renders faster than
    58% of other websites

  • 69

    Accessibility

    Visual factors better than
    that of 35% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 84

    SEO

    Google-friendlier than
    53% of websites

swordhealth.com

Sword Health Digital MSK | Freeing the World from Pain

Page Load Speed

2 sec in total

First Response

214 ms

Resources Loaded

1.1 sec

Page Rendered

686 ms

swordhealth.com screenshot

About Website

Click here to check amazing Sword Health content for United States. Otherwise, check out these important facts you probably never knew about swordhealth.com

Sword Health’s solutions combine AI and clinical expertise to deliver pain-fighting care without the need for opioids or unnecessary surgeries.

Visit swordhealth.com

Key Findings

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

Performance Metrics

swordhealth.com performance score

38

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

45/100

10%

LCP (Largest Contentful Paint)

Value3.1 s

74/100

25%

SI (Speed Index)

Value25.8 s

0/100

10%

TBT (Total Blocking Time)

Value24,860 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.003

100/100

15%

TTI (Time to Interactive)

Value34.6 s

0/100

10%

Network Requests Diagram

swordhealth.com

214 ms

ooKkzhKBJbMfTYuvs_GHRL8UdwA.js

48 ms

6a5914e0afeae3ed.css

182 ms

polyfills-c67a75d1b6f99dc8.js

213 ms

webpack-98acb4dba95d152e.js

181 ms

Our browser made a total of 28 requests to load all elements on the main page. We found that 75% of them (21 requests) were addressed to the original Swordhealth.com, 21% (6 requests) were made to Fonts.gstatic.com and 4% (1 request) were made to Js-agent.newrelic.com. The less responsive or slowest element that took the longest time to load (418 ms) belongs to the original domain Swordhealth.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 217.4 kB (75%)

Content Size

290.0 kB

After Optimization

72.6 kB

  • HTML
  • JavaScript

In fact, the total size of Swordhealth.com main page is 290.0 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. HTML takes 272.5 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 217.4 kB

  • Original 272.5 kB
  • After minification 272.4 kB
  • After compression 55.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. 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 217.4 kB or 80% of the original size.

JavaScript Optimization

-0%

Potential reduce by 0 B

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

Requests Breakdown

Number of requests can be reduced by 11 (73%)

Requests Now

15

After Optimization

4

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

swordhealth.com

swordhealth.com

214 ms

ooKkzhKBJbMfTYuvs_GHRL8UdwA.js

ooKkzhKBJbMfTYuvs_GHRL8UdwA.js

48 ms

6a5914e0afeae3ed.css

6a5914e0afeae3ed.css

182 ms

polyfills-c67a75d1b6f99dc8.js

polyfills-c67a75d1b6f99dc8.js

213 ms

webpack-98acb4dba95d152e.js

webpack-98acb4dba95d152e.js

181 ms

framework-3fe34326565e0106.js

framework-3fe34326565e0106.js

211 ms

main-29e280b8eb604590.js

main-29e280b8eb604590.js

211 ms

_app-105f3e3c191e2d57.js

_app-105f3e3c191e2d57.js

360 ms

317-207a68948ade0ed7.js

317-207a68948ade0ed7.js

397 ms

489-3adc65c6a48e9913.js

489-3adc65c6a48e9913.js

357 ms

index-5869995a70394e9c.js

index-5869995a70394e9c.js

416 ms

_buildManifest.js

_buildManifest.js

415 ms

_ssgManifest.js

_ssgManifest.js

418 ms

logo__white.svg

logo__white.svg

404 ms

arrow.svg

arrow.svg

358 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Ew9.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Ew9.woff

37 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Ew9.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Ew9.woff

74 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Ew9.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Ew9.woff

133 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu170w9.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu170w9.woff

157 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM70w9.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM70w9.woff

159 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr70w9.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr70w9.woff

158 ms

Gilmer-Heavy.otf

Gilmer-Heavy.otf

132 ms

Gilmer-Bold.otf

Gilmer-Bold.otf

124 ms

Gilmer-Medium.otf

Gilmer-Medium.otf

123 ms

Gilmer-Regular.otf

Gilmer-Regular.otf

121 ms

Gilmer-Light.otf

Gilmer-Light.otf

121 ms

slick.653a4cbb.woff

slick.653a4cbb.woff

23 ms

nr-spa-1215.min.js

nr-spa-1215.min.js

74 ms

Accessibility Review

swordhealth.com accessibility score

69

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

Image elements do not have [alt] attributes

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

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

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

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

swordhealth.com SEO score

84

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

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

swordhealth.com

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