Tools & Wizards About Us
league.io screenshot

Report Summary

  • 28

    Performance

    Renders faster than
    47% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 88% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

league.io

Powering Digital Transformation in Healthcare | League

Page Load Speed

2.7 sec in total

First Response

99 ms

Resources Loaded

1.8 sec

Page Rendered

764 ms

league.io screenshot

About Website

Welcome to league.io homepage info - get ready to check League best content right away, or after learning these important things about league.io

Payers, providers, employers and consumer health organizations use League's CX platform to deliver high-engagement, personalized health experiences.

Visit league.io

Key Findings

We analyzed League.io page load time and found that the first response time was 99 ms and then it took 2.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

league.io performance score

28

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.6 s

14/100

10%

LCP (Largest Contentful Paint)

Value12.5 s

0/100

25%

SI (Speed Index)

Value10.5 s

7/100

10%

TBT (Total Blocking Time)

Value880 ms

32/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value12.8 s

13/100

10%

Network Requests Diagram

league.io

99 ms

joinleague.com

384 ms

league.com

273 ms

OtAutoBlock.js

52 ms

otSDKStub.js

67 ms

Our browser made a total of 85 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original League.io, 58% (49 requests) were made to E3r429ujnza.exactdn.com and 35% (30 requests) were made to League.com. The less responsive or slowest element that took the longest time to load (789 ms) relates to the external source E3r429ujnza.exactdn.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 386.4 kB (31%)

Content Size

1.3 MB

After Optimization

865.0 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of League.io main page is 1.3 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 809.1 kB which makes up the majority of the site volume.

HTML Optimization

-90%

Potential reduce by 385.8 kB

  • Original 429.2 kB
  • After minification 412.7 kB
  • After compression 43.4 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 385.8 kB or 90% of the original size.

Image Optimization

-0%

Potential reduce by 527 B

  • Original 809.1 kB
  • After minification 808.6 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. League images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 57 B

  • Original 13.1 kB
  • After minification 13.1 kB
  • After compression 13.0 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 31 (39%)

Requests Now

79

After Optimization

48

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

league.io

league.io

99 ms

joinleague.com

joinleague.com

384 ms

league.com

league.com

273 ms

OtAutoBlock.js

OtAutoBlock.js

52 ms

otSDKStub.js

otSDKStub.js

67 ms

style.min.css

style.min.css

56 ms

frontend_blocks.css

frontend_blocks.css

55 ms

frontend_blocks.css

frontend_blocks.css

60 ms

style-realm.css

style-realm.css

86 ms

genericons.css

genericons.css

48 ms

font-awesome.min.css

font-awesome.min.css

77 ms

all.min.css

all.min.css

101 ms

sassy-social-share-public.css

sassy-social-share-public.css

90 ms

vendor.css

vendor.css

105 ms

style.css

style.css

155 ms

jquery.min.js

jquery.min.js

116 ms

jquery-migrate.min.js

jquery-migrate.min.js

146 ms

js.cookie.js

js.cookie.js

136 ms

handl-utm-grabber.js

handl-utm-grabber.js

138 ms

frontend.js

frontend.js

151 ms

lazysizes.min.js

lazysizes.min.js

124 ms

vendor.js

vendor.js

432 ms

lodash.min.js

lodash.min.js

431 ms

main.js

main.js

440 ms

frontend_blocks_custom.js

frontend_blocks_custom.js

431 ms

frontend_blocks.js

frontend_blocks.js

434 ms

sassy-social-share-public.js

sassy-social-share-public.js

432 ms

hoverIntent.min.js

hoverIntent.min.js

433 ms

maxmegamenu.js

maxmegamenu.js

433 ms

public.js

public.js

435 ms

161032a5-0eff-4e6c-b3d1-af9be75c9c6b.json

161032a5-0eff-4e6c-b3d1-af9be75c9c6b.json

26 ms

location

location

41 ms

Payers-Icon-Nav.svg

Payers-Icon-Nav.svg

297 ms

Provider-Icon-Nav.svg

Provider-Icon-Nav.svg

280 ms

CH-Icon-Nav.svg

CH-Icon-Nav.svg

304 ms

Hompage-Person1.webp

Hompage-Person1.webp

399 ms

Hompage-Person2.webp

Hompage-Person2.webp

401 ms

Hompage-Person3.webp

Hompage-Person3.webp

359 ms

Hompage-Person4.webp

Hompage-Person4.webp

414 ms

Hompage-Person5.webp

Hompage-Person5.webp

419 ms

HP-Your-Brand-Img.png

HP-Your-Brand-Img.png

446 ms

HP-Payer-Icon-Inverted.png

HP-Payer-Icon-Inverted.png

453 ms

HP-Payer-Icon-1.png

HP-Payer-Icon-1.png

522 ms

HP-Provider-Icon.png

HP-Provider-Icon.png

522 ms

HP-Provider-Icon-Inverted.png

HP-Provider-Icon-Inverted.png

512 ms

HP-ConsumerHlth-Icon.png

HP-ConsumerHlth-Icon.png

524 ms

HP-ConsumerHlth-Icon-Inverted.png

HP-ConsumerHlth-Icon-Inverted.png

555 ms

Accenture2.png

Accenture2.png

476 ms

XO-Health-Logo.png

XO-Health-Logo.png

501 ms

Deloitte-2.png

Deloitte-2.png

525 ms

HighmarkHealth-2.png

HighmarkHealth-2.png

537 ms

Manulife-logo.png

Manulife-logo.png

542 ms

ShoppersDrugMart-2.png

ShoppersDrugMart-2.png

543 ms

Kyruus-Health-Logo.svg

Kyruus-Health-Logo.svg

643 ms

Engen-Logo.svg

Engen-Logo.svg

574 ms

Accenture-Quote.svg

Accenture-Quote.svg

591 ms

GCP-Partner.svg

GCP-Partner.svg

596 ms

Deloitte-Partner.png

Deloitte-Partner.png

672 ms

Salesforce-Partner2.svg

Salesforce-Partner2.svg

625 ms

Pega-Partner2.svg

Pega-Partner2.svg

603 ms

Pager-Health-Logo.svg

Pager-Health-Logo.svg

619 ms

BeckersWP-2024-Member-Portal-Homepage-CTA-Image.jpg

BeckersWP-2024-Member-Portal-Homepage-CTA-Image.jpg

740 ms

HighmarkHealth-Logo3.svg

HighmarkHealth-Logo3.svg

678 ms

AsheshDesai-Manulife.png

AsheshDesai-Manulife.png

788 ms

Manulife-logo-colored.png

Manulife-logo-colored.png

663 ms

GCP-Quote.svg

GCP-Quote.svg

664 ms

Swati-Mathai-Quote.png

Swati-Mathai-Quote.png

789 ms

XO-Health_Logo_Full-Color_Horizontal_Stone-1.png

XO-Health_Logo_Full-Color_Horizontal_Stone-1.png

781 ms

icon-sprite-v8.svg

icon-sprite-v8.svg

233 ms

markbook-webfont.woff

markbook-webfont.woff

105 ms

markbold-webfont.woff

markbold-webfont.woff

103 ms

MarkOffcPro-Medium.woff

MarkOffcPro-Medium.woff

105 ms

Highmark-Blog-Img.png

Highmark-Blog-Img.png

513 ms

Manulife-Homepage-Image.png

Manulife-Homepage-Image.png

439 ms

Connect-CVSHealth-CTA-img.png

Connect-CVSHealth-CTA-img.png

362 ms

Beckers-Resource-Img-Green.png

Beckers-Resource-Img-Green.png

379 ms

league-logo-primary-vertical-1.svg

league-logo-primary-vertical-1.svg

372 ms

login.svg

login.svg

369 ms

support.svg

support.svg

375 ms

app-store-1-af-048-f-5.svg

app-store-1-af-048-f-5.svg

376 ms

play-store-16687-a-55.svg

play-store-16687-a-55.svg

365 ms

icon-linkedin.svg

icon-linkedin.svg

356 ms

icon-twitter.svg

icon-twitter.svg

335 ms

icon-instagram.svg

icon-instagram.svg

316 ms

icon-facebook.svg

icon-facebook.svg

304 ms

Accessibility Review

league.io accessibility score

96

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

league.io best practices score

83

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

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

league.io SEO score

86

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 League.io 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 League.io 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

league.io

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