Tools & Wizards About Us

Report Summary

  • 33

    Performance

    Renders faster than
    53% of other websites

  • 93

    Accessibility

    Visual factors better than
    that of 80% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

ecerto.io

eCERTO | INTEGRATI® | eAPPRAISAL

Page Load Speed

1.1 sec in total

First Response

39 ms

Resources Loaded

979 ms

Page Rendered

60 ms

About Website

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

eCERTO transforms the sustainability and financial performance of Capital Projects across industries with the adoption of INTEGRATI® and provision of eAPPRAISAL services

Visit ecerto.io

Key Findings

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

Performance Metrics

ecerto.io performance score

33

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.1 s

81/100

10%

LCP (Largest Contentful Paint)

Value11.1 s

0/100

25%

SI (Speed Index)

Value5.7 s

52/100

10%

TBT (Total Blocking Time)

Value1,540 ms

13/100

30%

CLS (Cumulative Layout Shift)

Value0.016

100/100

15%

TTI (Time to Interactive)

Value14.5 s

9/100

10%

Network Requests Diagram

www.ecerto.io

39 ms

originTrials.41d7301a.bundle.min.js

41 ms

minified.js

42 ms

focus-within-polyfill.js

89 ms

polyfill.min.js

219 ms

Our browser made a total of 37 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Ecerto.io, 35% (13 requests) were made to Static.parastorage.com and 32% (12 requests) were made to Sentry-next.wixpress.com. The less responsive or slowest element that took the longest time to load (409 ms) relates to the external source Static.wixstatic.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 358.9 kB (50%)

Content Size

717.7 kB

After Optimization

358.8 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Ecerto.io main page is 717.7 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. 25% of websites need less resources to load. HTML takes 378.8 kB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 289.4 kB

  • Original 378.8 kB
  • After minification 377.1 kB
  • After compression 89.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 289.4 kB or 76% of the original size.

Image Optimization

-16%

Potential reduce by 10.1 kB

  • Original 61.6 kB
  • After minification 51.5 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, ECERTO needs image optimization as it can save up to 10.1 kB or 16% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-21%

Potential reduce by 59.4 kB

  • Original 277.3 kB
  • After minification 277.3 kB
  • After compression 217.9 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 59.4 kB or 21% of the original size.

Requests Breakdown

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

Requests Now

24

After Optimization

13

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 24 CSS, Javascripts, AJAX and image requests in order to completely render the main page of ECERTO. 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

Accessibility Review

ecerto.io accessibility score

93

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

Best Practices

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

ecerto.io SEO score

92

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

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

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