Tools & Wizards About Us

Report Summary

  • 31

    Performance

    Renders faster than
    51% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 51% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

lds365.com

LDS365 Resources from the Church & from LDS worldwide

Page Load Speed

7.6 sec in total

First Response

2.9 sec

Resources Loaded

4.5 sec

Page Rendered

248 ms

About Website

Visit lds365.com now to see the best up-to-date LDS365 content for United States and also check out these interesting facts you probably never knew about lds365.com

Learn about LDS resources from the Church and from members around the world. How to use social media and technology to share goodness and bless your family.

Visit lds365.com

Key Findings

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

Performance Metrics

lds365.com performance score

31

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.8 s

4/100

10%

LCP (Largest Contentful Paint)

Value14.9 s

0/100

25%

SI (Speed Index)

Value11.4 s

5/100

10%

TBT (Total Blocking Time)

Value670 ms

45/100

30%

CLS (Cumulative Layout Shift)

Value0.025

100/100

15%

TTI (Time to Interactive)

Value13.0 s

13/100

10%

Network Requests Diagram

lds365.com

2866 ms

js

54 ms

front.min.css

94 ms

polls-css.css

125 ms

style.css

223 ms

Our browser made a total of 69 requests to load all elements on the main page. We found that 61% of them (42 requests) were addressed to the original Lds365.com, 17% (12 requests) were made to Fonts.gstatic.com and 6% (4 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (2.9 sec) belongs to the original domain Lds365.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.0 MB (49%)

Content Size

2.1 MB

After Optimization

1.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Lds365.com main page is 2.1 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 832.2 kB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 253.4 kB

  • Original 299.2 kB
  • After minification 296.2 kB
  • After compression 45.7 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 253.4 kB or 85% of the original size.

Image Optimization

-6%

Potential reduce by 52.1 kB

  • Original 832.2 kB
  • After minification 780.2 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. LDS365 images are well optimized though.

JavaScript Optimization

-70%

Potential reduce by 461.1 kB

  • Original 657.6 kB
  • After minification 650.9 kB
  • After compression 196.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 461.1 kB or 70% of the original size.

CSS Optimization

-87%

Potential reduce by 255.3 kB

  • Original 292.3 kB
  • After minification 278.5 kB
  • After compression 37.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. Lds365.com needs all CSS files to be minified and compressed as it can save up to 255.3 kB or 87% of the original size.

Requests Breakdown

Number of requests can be reduced by 37 (67%)

Requests Now

55

After Optimization

18

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

lds365.com accessibility score

81

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

Form elements do not have associated labels

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.

Best Practices

lds365.com 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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

lds365.com 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 Lds365.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 Lds365.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 LDS365. 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: