Report Summary

  • 22

    Performance

    Renders faster than
    40% of other websites

  • 80

    Accessibility

    Visual factors better than
    that of 49% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

disciplepress.com

Home - DisciplePress - Memorial & Funeral Printing

Page Load Speed

2.9 sec in total

First Response

309 ms

Resources Loaded

1.6 sec

Page Rendered

952 ms

disciplepress.com screenshot

About Website

Click here to check amazing Disciple Press content for United States. Otherwise, check out these important facts you probably never knew about disciplepress.com

Custom funeral printing, funeral program printing, memorial printing and church printing by DisciplePress.

Visit disciplepress.com

Key Findings

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

Performance Metrics

disciplepress.com performance score

22

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

38/100

10%

LCP (Largest Contentful Paint)

Value4.2 s

45/100

25%

SI (Speed Index)

Value9.0 s

15/100

10%

TBT (Total Blocking Time)

Value5,960 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.35

31/100

15%

TTI (Time to Interactive)

Value16.3 s

5/100

10%

Network Requests Diagram

disciplepress.com

309 ms

global.css

19 ms

lrm-core-compiled.css

27 ms

wc-blocks-vendors-style.css

52 ms

wc-all-blocks-style.css

155 ms

Our browser made a total of 68 requests to load all elements on the main page. We found that 87% of them (59 requests) were addressed to the original Disciplepress.com, 7% (5 requests) were made to Use.fontawesome.com and 1% (1 request) were made to Cdn.jsdelivr.net. The less responsive or slowest element that took the longest time to load (455 ms) relates to the external source Kit.fontawesome.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 492.4 kB (43%)

Content Size

1.2 MB

After Optimization

659.1 kB

In fact, the total size of Disciplepress.com main page is 1.2 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. HTML takes 570.7 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 475.0 kB

  • Original 570.7 kB
  • After minification 570.7 kB
  • After compression 95.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 475.0 kB or 83% of the original size.

Image Optimization

-1%

Potential reduce by 198 B

  • Original 15.0 kB
  • After minification 14.8 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. Disciple Press images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 891 B

  • Original 214.7 kB
  • After minification 214.7 kB
  • After compression 213.8 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

-5%

Potential reduce by 16.4 kB

  • Original 351.1 kB
  • After minification 335.2 kB
  • After compression 334.8 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. Disciplepress.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 52 (87%)

Requests Now

60

After Optimization

8

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

Accessibility Review

disciplepress.com accessibility score

80

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

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

Best Practices

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

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

disciplepress.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 Disciplepress.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 Disciplepress.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 data is detected on the main page of Disciple Press. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: