Tools & Wizards About Us
ezlegacy.com screenshot

Report Summary

  • 15

    Performance

    Renders faster than
    27% of other websites

  • 91

    Accessibility

    Visual factors better than
    that of 76% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

ezlegacy.com

IBM Application Discovery and Delivery Intelligence

Page Load Speed

2.8 sec in total

First Response

267 ms

Resources Loaded

2.2 sec

Page Rendered

322 ms

ezlegacy.com screenshot

About Website

Click here to check amazing Ezlegacy content. Otherwise, check out these important facts you probably never knew about ezlegacy.com

A software to analyze and visualize applications, data, and jobs on z/OS.

Visit ezlegacy.com

Key Findings

We analyzed Ezlegacy.com page load time and found that the first response time was 267 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

ezlegacy.com performance score

15

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value9.1 s

0/100

10%

LCP (Largest Contentful Paint)

Value30.4 s

0/100

25%

SI (Speed Index)

Value22.3 s

0/100

10%

TBT (Total Blocking Time)

Value12,900 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value48.1 s

0/100

10%

Network Requests Diagram

ezlegacy.com

267 ms

257 ms

app-discovery-and-delivery-intelligence

774 ms

ibm-common.js

31 ms

loader.js

232 ms

Our browser made a total of 55 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Ezlegacy.com, 71% (39 requests) were made to 1.www.s81c.com and 25% (14 requests) were made to Ibm.com. The less responsive or slowest element that took the longest time to load (774 ms) relates to the external source Ibm.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.0 MB (56%)

Content Size

1.8 MB

After Optimization

811.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Ezlegacy.com main page is 1.8 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. Javascripts take 1.0 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 71.2 kB

  • Original 83.8 kB
  • After minification 66.9 kB
  • After compression 12.5 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 16.9 kB, which is 20% 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 71.2 kB or 85% of the original size.

Image Optimization

-37%

Potential reduce by 267.6 kB

  • Original 722.1 kB
  • After minification 454.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. Obviously, Ezlegacy needs image optimization as it can save up to 267.6 kB or 37% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-67%

Potential reduce by 692.4 kB

  • Original 1.0 MB
  • After minification 1.0 MB
  • After compression 337.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 692.4 kB or 67% of the original size.

CSS Optimization

-2%

Potential reduce by 172 B

  • Original 7.0 kB
  • After minification 7.0 kB
  • After compression 6.8 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. Ezlegacy.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 39 (91%)

Requests Now

43

After Optimization

4

  • Images
  • JavaScript
  • CSS

The browser has sent 43 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ezlegacy. 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 5 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

ezlegacy.com

ezlegacy.com

267 ms

257 ms

app-discovery-and-delivery-intelligence

app-discovery-and-delivery-intelligence

774 ms

ibm-common.js

ibm-common.js

31 ms

loader.js

loader.js

232 ms

clientlib-idlStylesCarbon.lc-4bcd71d5119ddf067401538b806d7bbb-lc.min.css

clientlib-idlStylesCarbon.lc-4bcd71d5119ddf067401538b806d7bbb-lc.min.css

54 ms

clientlib-idlStyles.lc-acf5f2fa77cc5dd9a1f86e0bc11ef955-lc.min.css

clientlib-idlStyles.lc-acf5f2fa77cc5dd9a1f86e0bc11ef955-lc.min.css

51 ms

plex.css

plex.css

53 ms

sans.css

sans.css

34 ms

masthead.min.js

masthead.min.js

36 ms

clientlib-idlBundle.lc-2afd79fa944130608b59c23b36700691-lc.min.js

clientlib-idlBundle.lc-2afd79fa944130608b59c23b36700691-lc.min.js

59 ms

clientlib-target-antiflicker.lc-36a1efb28e947b5873f4a28c2cf9d5eb-lc.min.js

clientlib-target-antiflicker.lc-36a1efb28e947b5873f4a28c2cf9d5eb-lc.min.js

45 ms

clientlib-idlStyles.lc-39f39727a565a0d787d4d7362b71dc56-lc.min.js

clientlib-idlStyles.lc-39f39727a565a0d787d4d7362b71dc56-lc.min.js

59 ms

cm-app.min.js

cm-app.min.js

50 ms

code-snippet.min.js

code-snippet.min.js

32 ms

footer.min.js

footer.min.js

35 ms

leadspace.min.js

leadspace.min.js

35 ms

card-group.min.js

card-group.min.js

49 ms

text-cta.js

text-cta.js

38 ms

content-block.min.js

content-block.min.js

38 ms

link-list.min.js

link-list.min.js

55 ms

link-list-item-cta.js

link-list-item-cta.js

54 ms

table-of-contents.min.js

table-of-contents.min.js

54 ms

button-group.min.js

button-group.min.js

55 ms

content-item.min.js

content-item.min.js

63 ms

content-section.min.js

content-section.min.js

64 ms

carousel.min.js

carousel.min.js

58 ms

button-cta.js

button-cta.js

57 ms

content-group-heading.js

content-group-heading.js

65 ms

content-block-segmented.min.js

content-block-segmented.min.js

56 ms

content-block-simple.min.js

content-block-simple.min.js

63 ms

horizontal-rule.min.js

horizontal-rule.min.js

58 ms

lightbox-video-player.min.js

lightbox-video-player.min.js

60 ms

content-block-cards.min.js

content-block-cards.min.js

62 ms

cta-block.min.js

cta-block.min.js

64 ms

content-group.min.js

content-group.min.js

70 ms

video-cta-container.min.js

video-cta-container.min.js

67 ms

background-media.min.js

background-media.min.js

65 ms

paragraph.min.js

paragraph.min.js

65 ms

breadcrumb.min.js

breadcrumb.min.js

66 ms

star-rating.min.js

star-rating.min.js

68 ms

aHQ

aHQ

68 ms

KFBY

KFBY

58 ms

b0kq

b0kq

58 ms

leadspace

leadspace

468 ms

image

image

583 ms

IBMPlexSans-Text.woff

IBMPlexSans-Text.woff

18 ms

IBMPlexSans-Regular.woff

IBMPlexSans-Regular.woff

112 ms

IBMPlexSans-Medium.woff

IBMPlexSans-Medium.woff

14 ms

IBMPlexSans-Light.woff

IBMPlexSans-Light.woff

111 ms

IBMPlexSans-ExtraLight.woff

IBMPlexSans-ExtraLight.woff

13 ms

IBMPlexSans-Thin.woff

IBMPlexSans-Thin.woff

12 ms

IBMPlexSans-SemiBold.woff

IBMPlexSans-SemiBold.woff

15 ms

IBMPlexSans-Bold.woff

IBMPlexSans-Bold.woff

14 ms

ffc8ae5d07a2166e6af1.ttf

ffc8ae5d07a2166e6af1.ttf

35 ms

Accessibility Review

ezlegacy.com accessibility score

91

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

[role]s do not have all required [aria-*] attributes

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

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

ezlegacy.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

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

Missing source maps for large first-party JavaScript

SEO Factors

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

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

ezlegacy.com

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