Tools & Wizards About Us

Report Summary

  • 20

    Performance

    Renders faster than
    37% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 61% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

endis.com

There's a problem

Page Load Speed

4.1 sec in total

First Response

174 ms

Resources Loaded

3.1 sec

Page Rendered

805 ms

About Website

Click here to check amazing Endis content for Morocco. Otherwise, check out these important facts you probably never knew about endis.com

Hubb.church is a Church Website, Church App, Church Admin, Communication, Giving and People management system. It is fully integrated and costs less than a cup of coffee per day.

Visit endis.com

Key Findings

We analyzed Endis.com page load time and found that the first response time was 174 ms and then it took 3.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

endis.com performance score

20

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value9.1 s

0/100

10%

LCP (Largest Contentful Paint)

Value12.3 s

0/100

25%

SI (Speed Index)

Value12.2 s

3/100

10%

TBT (Total Blocking Time)

Value1,300 ms

18/100

30%

CLS (Cumulative Layout Shift)

Value0.098

90/100

15%

TTI (Time to Interactive)

Value14.8 s

8/100

10%

Network Requests Diagram

endis.com

174 ms

endis.com

331 ms

www.hubb.church

556 ms

base.min.css

237 ms

UserSideGlobalCustom.css

318 ms

Our browser made a total of 122 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Endis.com, 88% (107 requests) were made to Hubb.church and 5% (6 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (793 ms) relates to the external source Hubb.church.

Page Optimization Overview & Recommendations

Page size can be reduced by 880.6 kB (30%)

Content Size

3.0 MB

After Optimization

2.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Endis.com main page is 3.0 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. 70% of websites need less resources to load. Images take 2.0 MB which makes up the majority of the site volume.

HTML Optimization

-68%

Potential reduce by 40.9 kB

  • Original 59.9 kB
  • After minification 55.6 kB
  • After compression 18.9 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 40.9 kB or 68% of the original size.

Image Optimization

-10%

Potential reduce by 201.3 kB

  • Original 2.0 MB
  • After minification 1.8 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. Endis images are well optimized though.

JavaScript Optimization

-64%

Potential reduce by 383.1 kB

  • Original 595.6 kB
  • After minification 584.2 kB
  • After compression 212.5 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 383.1 kB or 64% of the original size.

CSS Optimization

-83%

Potential reduce by 255.2 kB

  • Original 308.2 kB
  • After minification 242.9 kB
  • After compression 53.0 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. Endis.com needs all CSS files to be minified and compressed as it can save up to 255.2 kB or 83% of the original size.

Requests Breakdown

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

Requests Now

111

After Optimization

87

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

endis.com accessibility score

86

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

endis.com best practices score

83

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

Page has valid source maps

SEO Factors

endis.com SEO score

86

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

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

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

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