Report Summary

  • 89

    Performance

    Renders faster than
    90% of other websites

  • 59

    Accessibility

    Visual factors better than
    that of 26% of websites

  • 0

    Best Practices

  • 68

    SEO

    Google-friendlier than
    28% of websites

ezycollect.io

ezyCollect | Accounts Receivable Automation Software

Page Load Speed

946 ms in total

First Response

445 ms

Resources Loaded

446 ms

Page Rendered

55 ms

About Website

Visit ezycollect.io now to see the best up-to-date EzyCollect content and also check out these interesting facts you probably never knew about ezycollect.io

ezyCollect automates accounts receivables, debtor management and credit risk tools to speed up the cash conversion cycle & debtor management.

Visit ezycollect.io

Key Findings

We analyzed Ezycollect.io page load time and found that the first response time was 445 ms and then it took 501 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 10% of websites can load faster.

Performance Metrics

ezycollect.io performance score

89

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.4 s

97/100

10%

LCP (Largest Contentful Paint)

Value2.1 s

96/100

25%

SI (Speed Index)

Value1.4 s

100/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.319

36/100

15%

TTI (Time to Interactive)

Value1.4 s

100/100

10%

Network Requests Diagram

ezycollect.io

445 ms

Our browser made a total of 1 request to load all elements on the main page. We found that all of those requests were addressed to Ezycollect.io and no external sources were called. The less responsive or slowest element that took the longest time to load (445 ms) belongs to the original domain Ezycollect.io.

Page Optimization Overview & Recommendations

Page size can be reduced by 75.3 kB (6%)

Content Size

1.3 MB

After Optimization

1.2 MB

In fact, the total size of Ezycollect.io main page is 1.3 MB. This result falls within the top 5000 of lightweight and thus fast loading web pages. Only a small number of websites need less resources to load. Images take 709.3 kB which makes up the majority of the site volume.

HTML Optimization

-12%

Potential reduce by 22 B

  • Original 177 B
  • After minification 177 B
  • After compression 155 B

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 22 B or 12% of the original size.

Image Optimization

-2%

Potential reduce by 12.9 kB

  • Original 709.3 kB
  • After minification 696.4 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. EzyCollect images are well optimized though.

JavaScript Optimization

-2%

Potential reduce by 5.7 kB

  • Original 370.8 kB
  • After minification 370.8 kB
  • After compression 365.1 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

-25%

Potential reduce by 56.7 kB

  • Original 224.1 kB
  • After minification 224.0 kB
  • After compression 167.4 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. Ezycollect.io needs all CSS files to be minified and compressed as it can save up to 56.7 kB or 25% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

0

After Optimization

0

Besides the initial HTML request, no CSS, Javascripts, AJAX or image files were requested in the course of web page rendering.

Accessibility Review

ezycollect.io accessibility score

59

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

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

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.

SEO Factors

ezycollect.io SEO score

68

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

High

Image elements do not have [alt] attributes

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

High

Page is blocked from indexing

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

    N/A

  • Encoding

    N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ezycollect.io can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Ezycollect.io main page’s claimed encoding is . Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

Open Graph description is not detected on the main page of EzyCollect. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: