Tools & Wizards About Us
start.ptl.org screenshot

Report Summary

  • 17

    Performance

    Renders faster than
    32% of other websites

  • 94

    Accessibility

    Visual factors better than
    that of 83% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

start.ptl.org

The Pocket Testament League (PTL): Evangelism Tools to Share Jesus

Page Load Speed

6 sec in total

First Response

297 ms

Resources Loaded

4.5 sec

Page Rendered

1.2 sec

start.ptl.org screenshot

About Website

Click here to check amazing Start PTL content for United States. Otherwise, check out these important facts you probably never knew about start.ptl.org

Helping you share Jesus, in His own words. Hundreds of millions reached. No arguments. Simply by sharing the Gospel of John. Join the movement!

Visit start.ptl.org

Key Findings

We analyzed Start.ptl.org page load time and found that the first response time was 297 ms and then it took 5.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

start.ptl.org performance score

17

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.7 s

12/100

10%

LCP (Largest Contentful Paint)

Value68.2 s

0/100

25%

SI (Speed Index)

Value16.2 s

0/100

10%

TBT (Total Blocking Time)

Value2,960 ms

3/100

30%

CLS (Cumulative Layout Shift)

Value0.022

100/100

15%

TTI (Time to Interactive)

Value50.4 s

0/100

10%

Network Requests Diagram

start.ptl.org

297 ms

www.ptl.org

3299 ms

video-js.css

63 ms

videojs-ie8.min.js

71 ms

grid.css

19 ms

Our browser made a total of 81 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Start.ptl.org, 86% (70 requests) were made to Ptl.org and 4% (3 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (3.3 sec) relates to the external source Ptl.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 7.4 MB (74%)

Content Size

10.1 MB

After Optimization

2.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Start.ptl.org main page is 10.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. Only a small number of websites need less resources to load. Images take 9.5 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 99.4 kB

  • Original 124.9 kB
  • After minification 121.4 kB
  • After compression 25.4 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 99.4 kB or 80% of the original size.

Image Optimization

-75%

Potential reduce by 7.2 MB

  • Original 9.5 MB
  • After minification 2.3 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, Start PTL needs image optimization as it can save up to 7.2 MB or 75% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-11%

Potential reduce by 22.2 kB

  • Original 208.8 kB
  • After minification 208.8 kB
  • After compression 186.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 22.2 kB or 11% of the original size.

CSS Optimization

-59%

Potential reduce by 137.7 kB

  • Original 234.1 kB
  • After minification 231.1 kB
  • After compression 96.4 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. Start.ptl.org needs all CSS files to be minified and compressed as it can save up to 137.7 kB or 59% of the original size.

Requests Breakdown

Number of requests can be reduced by 65 (88%)

Requests Now

74

After Optimization

9

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

start.ptl.org

start.ptl.org

297 ms

www.ptl.org

www.ptl.org

3299 ms

video-js.css

video-js.css

63 ms

videojs-ie8.min.js

videojs-ie8.min.js

71 ms

grid.css

grid.css

19 ms

base.css

base.css

41 ms

layout.css

layout.css

40 ms

blog.css

blog.css

42 ms

postslider.css

postslider.css

40 ms

buttons.css

buttons.css

39 ms

buttonrow.css

buttonrow.css

42 ms

comments.css

comments.css

46 ms

contact.css

contact.css

45 ms

slideshow.css

slideshow.css

44 ms

contentslider.css

contentslider.css

45 ms

gallery.css

gallery.css

50 ms

gallery_horizontal.css

gallery_horizontal.css

49 ms

grid_row.css

grid_row.css

51 ms

heading.css

heading.css

50 ms

hr.css

hr.css

49 ms

image.css

image.css

50 ms

image_hotspots.css

image_hotspots.css

56 ms

promobox.css

promobox.css

54 ms

slideshow_fullsize.css

slideshow_fullsize.css

54 ms

slideshow_fullscreen.css

slideshow_fullscreen.css

54 ms

social_share.css

social_share.css

57 ms

table.css

table.css

52 ms

tabs.css

tabs.css

106 ms

timeline.css

timeline.css

105 ms

toggles.css

toggles.css

61 ms

video.css

video.css

61 ms

style.min.css

style.min.css

103 ms

cleantalk-public.min.css

cleantalk-public.min.css

104 ms

wpsm-style.css

wpsm-style.css

107 ms

shortcodes.css

shortcodes.css

114 ms

magnific-popup.css

magnific-popup.css

112 ms

avia-snippet-lightbox.css

avia-snippet-lightbox.css

107 ms

avia-snippet-widget.css

avia-snippet-widget.css

105 ms

mediaelementplayer-legacy.min.css

mediaelementplayer-legacy.min.css

111 ms

2ce790901b.js

2ce790901b.js

129 ms

wp-mediaelement.min.css

wp-mediaelement.min.css

108 ms

enfold_child.css

enfold_child.css

103 ms

custom.css

custom.css

84 ms

style.css

style.css

87 ms

pum-site-styles.css

pum-site-styles.css

85 ms

style.css

style.css

85 ms

avia-snippet-cookieconsent.css

avia-snippet-cookieconsent.css

81 ms

jquery.min.js

jquery.min.js

81 ms

jquery-migrate.min.js

jquery-migrate.min.js

81 ms

apbct-public-bundle.min.js

apbct-public-bundle.min.js

82 ms

analytics-talk-content-tracking.js

analytics-talk-content-tracking.js

82 ms

index.js

index.js

84 ms

index.js

index.js

78 ms

wpsm-script.js

wpsm-script.js

80 ms

gtm4wp-contact-form-7-tracker.js

gtm4wp-contact-form-7-tracker.js

77 ms

gtm4wp-form-move-tracker.js

gtm4wp-form-move-tracker.js

80 ms

mediaelement-and-player.min.js

mediaelement-and-player.min.js

82 ms

mediaelement-migrate.min.js

mediaelement-migrate.min.js

79 ms

wp-mediaelement.min.js

wp-mediaelement.min.js

76 ms

core.min.js

core.min.js

76 ms

pum-site-scripts.js

pum-site-scripts.js

75 ms

scripts.js

scripts.js

77 ms

smush-lazy-load.min.js

smush-lazy-load.min.js

73 ms

get-the-page.js

get-the-page.js

73 ms

avia-footer-scripts-15188648789024fc24da4a3111a0846c---66427bb01f105.js

avia-footer-scripts-15188648789024fc24da4a3111a0846c---66427bb01f105.js

70 ms

css

css

47 ms

css

css

26 ms

gtm.js

gtm.js

254 ms

fbevents.js

fbevents.js

183 ms

DSC02118-resized-MAIN-scaled.jpeg

DSC02118-resized-MAIN-scaled.jpeg

250 ms

wavy-background-v6.png

wavy-background-v6.png

174 ms

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

130 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

131 ms

KFOkCnqEu92Fr1MmgVxIIzc.ttf

KFOkCnqEu92Fr1MmgVxIIzc.ttf

134 ms

franklingothic-demicd-webfont.svg

franklingothic-demicd-webfont.svg

61 ms

entypo-fontello.woff

entypo-fontello.woff

65 ms

150-graph-no-bg.png

150-graph-no-bg.png

169 ms

App-Table-BG-1.png

App-Table-BG-1.png

164 ms

HH-kit-bg.jpg

HH-kit-bg.jpg

71 ms

PTL-logo-R-EN.png

PTL-logo-R-EN.png

56 ms

franklingothic-demicd-webfont.ttf

franklingothic-demicd-webfont.ttf

21 ms

Accessibility Review

start.ptl.org accessibility score

94

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

Links do not have a discernible name

Best Practices

start.ptl.org best practices score

75

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

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

start.ptl.org SEO score

93

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Page is blocked from indexing

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 Start.ptl.org 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 Start.ptl.org 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

start.ptl.org

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