Tools & Wizards About Us
endigital.io screenshot

Report Summary

  • 41

    Performance

    Renders faster than
    60% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 58% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

endigital.io

Software Development and Cloud Native Solutions, Managed Services and Dedicated Product Teams | ENDIGITAL - ENDIGITAL

Page Load Speed

2.4 sec in total

First Response

146 ms

Resources Loaded

1.5 sec

Page Rendered

798 ms

endigital.io screenshot

About Website

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

Software Development and Cloud Native Solutions, Managed Services and Dedicated Product Teams | ENDIGITAL

Visit endigital.io

Key Findings

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

Performance Metrics

endigital.io performance score

41

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

46/100

10%

LCP (Largest Contentful Paint)

Value7.5 s

4/100

25%

SI (Speed Index)

Value4.8 s

68/100

10%

TBT (Total Blocking Time)

Value350 ms

73/100

30%

CLS (Cumulative Layout Shift)

Value0.397

25/100

15%

TTI (Time to Interactive)

Value10.1 s

26/100

10%

Network Requests Diagram

endigital.io

146 ms

www.endigital.io

367 ms

67d1c7bf76e0924f0f397b2e4895bf01-1654932346

87 ms

css

55 ms

0359d3a52b.js

78 ms

Our browser made a total of 44 requests to load all elements on the main page. We found that 59% of them (26 requests) were addressed to the original Endigital.io, 16% (7 requests) were made to Fonts.gstatic.com and 7% (3 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (592 ms) belongs to the original domain Endigital.io.

Page Optimization Overview & Recommendations

Page size can be reduced by 417.5 kB (17%)

Content Size

2.5 MB

After Optimization

2.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Endigital.io main page is 2.5 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. 60% of websites need less resources to load. Images take 2.1 MB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 27.7 kB

  • Original 36.8 kB
  • After minification 30.9 kB
  • After compression 9.2 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 5.9 kB, which is 16% 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 27.7 kB or 75% of the original size.

Image Optimization

-18%

Potential reduce by 388.2 kB

  • Original 2.1 MB
  • After minification 1.7 MB

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, ENDIGITAL needs image optimization as it can save up to 388.2 kB or 18% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-0%

Potential reduce by 1.5 kB

  • Original 310.3 kB
  • After minification 310.3 kB
  • After compression 308.7 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

-0%

Potential reduce by 117 B

  • Original 24.4 kB
  • After minification 24.4 kB
  • After compression 24.3 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. Endigital.io has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 22 (63%)

Requests Now

35

After Optimization

13

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

endigital.io

endigital.io

146 ms

www.endigital.io

www.endigital.io

367 ms

67d1c7bf76e0924f0f397b2e4895bf01-1654932346

67d1c7bf76e0924f0f397b2e4895bf01-1654932346

87 ms

css

css

55 ms

0359d3a52b.js

0359d3a52b.js

78 ms

animate.css

animate.css

156 ms

aos.css

aos.css

205 ms

normalize.css

normalize.css

288 ms

8ac88bd4baf9f816ce826b29b5f0f865-1654932346

8ac88bd4baf9f816ce826b29b5f0f865-1654932346

254 ms

a6837955d2c212d15f09ca7b6a34bfb5-1654932346

a6837955d2c212d15f09ca7b6a34bfb5-1654932346

246 ms

cookieconsent.min.js

cookieconsent.min.js

51 ms

js

js

101 ms

js

js

138 ms

a1611fcac5376cc7340087e5671d9585-1654932346

a1611fcac5376cc7340087e5671d9585-1654932346

429 ms

aos.js

aos.js

221 ms

smoothscroll.js

smoothscroll.js

273 ms

jquery.stellar.min.js

jquery.stellar.min.js

342 ms

main.js

main.js

345 ms

framework.combined-min.js

framework.combined-min.js

346 ms

framework.extras-min.css

framework.extras-min.css

346 ms

main.js

main.js

424 ms

api.js

api.js

58 ms

edxx-l4-900px-0-0-0-0-1616567780.png

edxx-l4-900px-0-0-0-0-1616567780.png

127 ms

endigital-land-hero-image.jpg

endigital-land-hero-image.jpg

219 ms

endigital-technology-software-testing-jd9843j9d.jpg

endigital-technology-software-testing-jd9843j9d.jpg

441 ms

team_in_our_office.jpg

team_in_our_office.jpg

214 ms

endigital-technology-mobile-apps-167-310-2071-1683-1616960069.png

endigital-technology-mobile-apps-167-310-2071-1683-1616960069.png

592 ms

team-software-engineers-47-14-0-400-300-1617097118.jpeg

team-software-engineers-47-14-0-400-300-1617097118.jpeg

212 ms

data-ledger-75-0-600-450-1617097254.jpeg

data-ledger-75-0-600-450-1617097254.jpeg

261 ms

thumb_17_120_120_0_0_crop.jpeg

thumb_17_120_120_0_0_crop.jpeg

213 ms

skin.png

skin.png

225 ms

team-iej9843-0-0-0-0-1617014071.jpg

team-iej9843-0-0-0-0-1617014071.jpg

546 ms

js

js

164 ms

analytics.js

analytics.js

63 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf

124 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aX8.ttf

124 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Hw5aX8.ttf

157 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw5aX8.ttf

207 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aX8.ttf

208 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf

208 ms

JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jq6R9WXh0ow.ttf

JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jq6R9WXh0ow.ttf

209 ms

recaptcha__en.js

recaptcha__en.js

166 ms

collect

collect

111 ms

light-bottom.css

light-bottom.css

13 ms

Accessibility Review

endigital.io accessibility score

85

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

ARIA input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

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

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

endigital.io best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

endigital.io SEO score

90

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

endigital.io

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