Tools & Wizards About Us
ebx.sh screenshot

Report Summary

  • 19

    Performance

    Renders faster than
    36% of other websites

  • 95

    Accessibility

    Visual factors better than
    that of 87% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

ebx.sh

Echobox

Page Load Speed

1.3 sec in total

First Response

408 ms

Resources Loaded

769 ms

Page Rendered

82 ms

ebx.sh screenshot

About Website

Click here to check amazing Ebx content. Otherwise, check out these important facts you probably never knew about ebx.sh

Visit ebx.sh

Key Findings

We analyzed Ebx.sh page load time and found that the first response time was 408 ms and then it took 851 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.

Performance Metrics

ebx.sh performance score

19

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value8.1 s

0/100

10%

LCP (Largest Contentful Paint)

Value17.6 s

0/100

25%

SI (Speed Index)

Value14.6 s

1/100

10%

TBT (Total Blocking Time)

Value1,520 ms

13/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value17.2 s

4/100

10%

Network Requests Diagram

ebx.sh

408 ms

gtm.js

65 ms

fbevents.js

29 ms

hotjar-1453941.js

4 ms

6791721.js

2 ms

Our browser made a total of 6 requests to load all elements on the main page. We found that 17% of them (1 request) were addressed to the original Ebx.sh, 17% (1 request) were made to Googletagmanager.com and 17% (1 request) were made to Connect.facebook.net. The less responsive or slowest element that took the longest time to load (408 ms) belongs to the original domain Ebx.sh.

Page Optimization Overview & Recommendations

Page size can be reduced by 402.7 kB (68%)

Content Size

594.8 kB

After Optimization

192.0 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Ebx.sh main page is 594.8 kB. This result falls within a vast category (top 1 000 000) of heavyweight, probably not optimized, and thus slow loading web pages. Only a small number of websites need less resources to load. CSS take 389.8 kB which makes up the majority of the site volume.

HTML Optimization

-57%

Potential reduce by 1.6 kB

  • Original 2.8 kB
  • After minification 2.7 kB
  • After compression 1.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. 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 1.6 kB or 57% of the original size.

JavaScript Optimization

-34%

Potential reduce by 68.5 kB

  • Original 202.2 kB
  • After minification 199.0 kB
  • After compression 133.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 68.5 kB or 34% of the original size.

CSS Optimization

-85%

Potential reduce by 332.6 kB

  • Original 389.8 kB
  • After minification 320.9 kB
  • After compression 57.2 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. Ebx.sh needs all CSS files to be minified and compressed as it can save up to 332.6 kB or 85% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

2

After Optimization

2

  • JavaScript

The browser has sent 2 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ebx. According to our analytics all requests are already optimized.

Network Requests Diagram

ebx.sh

ebx.sh

408 ms

gtm.js

gtm.js

65 ms

fbevents.js

fbevents.js

29 ms

hotjar-1453941.js

hotjar-1453941.js

4 ms

6791721.js

6791721.js

2 ms

sl.js

sl.js

2 ms

Accessibility Review

ebx.sh accessibility score

95

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.

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

Best Practices

ebx.sh best practices score

75

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

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

ebx.sh SEO score

83

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ebx.sh 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 Ebx.sh 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

ebx.sh

Open Graph description is not detected on the main page of Ebx. 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: