Tools & Wizards About Us
ptf.org screenshot

Report Summary

  • 8

    Performance

    Renders faster than
    22% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 68% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

ptf.org

Site is offline

Page Load Speed

3 sec in total

First Response

109 ms

Resources Loaded

2.3 sec

Page Rendered

611 ms

ptf.org screenshot

About Website

Click here to check amazing Ptf content. Otherwise, check out these important facts you probably never knew about ptf.org

Our mission is to unite and empower remarkable military veterans and spouses as the next generation of public and private sector leaders committed to service beyond self.

Visit ptf.org

Key Findings

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

Performance Metrics

ptf.org performance score

8

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.8 s

27/100

10%

LCP (Largest Contentful Paint)

Value14.2 s

0/100

25%

SI (Speed Index)

Value12.2 s

3/100

10%

TBT (Total Blocking Time)

Value3,920 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.345

32/100

15%

TTI (Time to Interactive)

Value26.4 s

0/100

10%

Network Requests Diagram

pattillmanfoundation.org

109 ms

pattillmanfoundation.org

216 ms

addthis_widget.js

102 ms

dg-builder.css

15 ms

font-awesome.min.css

47 ms

Our browser made a total of 80 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Ptf.org, 13% (10 requests) were made to Fonts.gstatic.com and 11% (9 requests) were made to Use.typekit.net. The less responsive or slowest element that took the longest time to load (857 ms) relates to the external source Use.typekit.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 137.2 kB (4%)

Content Size

3.1 MB

After Optimization

2.9 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Ptf.org main page is 3.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. 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. Images take 2.4 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 93.3 kB

  • Original 113.5 kB
  • After minification 110.1 kB
  • After compression 20.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 93.3 kB or 82% of the original size.

Image Optimization

-2%

Potential reduce by 41.1 kB

  • Original 2.4 MB
  • After minification 2.4 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. Ptf images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 2.7 kB

  • Original 336.4 kB
  • After minification 336.4 kB
  • After compression 333.7 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

-0%

Potential reduce by 67 B

  • Original 194.5 kB
  • After minification 194.5 kB
  • After compression 194.5 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. Ptf.org has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 35 (66%)

Requests Now

53

After Optimization

18

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 53 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ptf. 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 15 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

pattillmanfoundation.org

pattillmanfoundation.org

109 ms

pattillmanfoundation.org

pattillmanfoundation.org

216 ms

addthis_widget.js

addthis_widget.js

102 ms

dg-builder.css

dg-builder.css

15 ms

font-awesome.min.css

font-awesome.min.css

47 ms

svgs-attachment.css

svgs-attachment.css

31 ms

dashicons.min.css

dashicons.min.css

42 ms

font-awesome.min.css

font-awesome.min.css

61 ms

style.min.css

style.min.css

44 ms

style.min.css

style.min.css

46 ms

css

css

56 ms

style-static.min.css

style-static.min.css

81 ms

layout.css

layout.css

48 ms

default.css

default.css

57 ms

support.css

support.css

50 ms

mediaelementplayer-legacy.min.css

mediaelementplayer-legacy.min.css

52 ms

wp-mediaelement.min.css

wp-mediaelement.min.css

54 ms

gtm4wp-form-move-tracker.js

gtm4wp-form-move-tracker.js

58 ms

jquery.min.js

jquery.min.js

59 ms

jquery-migrate.min.js

jquery-migrate.min.js

63 ms

orbit.js

orbit.js

66 ms

scripts.min.js

scripts.min.js

83 ms

comment-reply.min.js

comment-reply.min.js

68 ms

frontend-bundle.min.js

frontend-bundle.min.js

69 ms

frontend-bundle.min.js

frontend-bundle.min.js

80 ms

common.js

common.js

81 ms

mediaelement-and-player.min.js

mediaelement-and-player.min.js

85 ms

mediaelement-migrate.min.js

mediaelement-migrate.min.js

80 ms

wp-mediaelement.min.js

wp-mediaelement.min.js

94 ms

jquery.fitvids.js

jquery.fitvids.js

94 ms

easypiechart.js

easypiechart.js

259 ms

gtm.js

gtm.js

480 ms

xur2lko.js

xur2lko.js

553 ms

97HsJkYM0RE

97HsJkYM0RE

375 ms

shopping_bag_24dp_FILL0_wght400_GRAD0_opsz24.svg

shopping_bag_24dp_FILL0_wght400_GRAD0_opsz24.svg

141 ms

PTF-20th-Anniversary-Logo-Source_PTF-20th-Anniversary-Logo-Horizontal.png

PTF-20th-Anniversary-Logo-Source_PTF-20th-Anniversary-Logo-Horizontal.png

139 ms

Tab4-c_25px.png

Tab4-c_25px.png

138 ms

icon-checkbox.png

icon-checkbox.png

139 ms

pat-football-yell_03.png

pat-football-yell_03.png

389 ms

bryan.watson.png

bryan.watson.png

313 ms

abdella_elkallassy_sarah_400.jpg

abdella_elkallassy_sarah_400.jpg

312 ms

Tigon_Abalos1.jpg

Tigon_Abalos1.jpg

313 ms

TOLVER_Laura_400.jpg

TOLVER_Laura_400.jpg

312 ms

PTF-20th-Anniversary-Logo-Source_PTF-20th-Anniversary-Logo-Horizontal-300x37.png

PTF-20th-Anniversary-Logo-Source_PTF-20th-Anniversary-Logo-Horizontal-300x37.png

312 ms

S6uyw4BMUTPHjxAwWw.ttf

S6uyw4BMUTPHjxAwWw.ttf

375 ms

S6u9w4BMUTPHh7USSwaPHA.ttf

S6u9w4BMUTPHh7USSwaPHA.ttf

461 ms

S6u8w4BMUTPHh30AUi-v.ttf

S6u8w4BMUTPHh30AUi-v.ttf

461 ms

S6u9w4BMUTPHh6UVSwaPHA.ttf

S6u9w4BMUTPHh6UVSwaPHA.ttf

459 ms

S6u9w4BMUTPHh50XSwaPHA.ttf

S6u9w4BMUTPHh50XSwaPHA.ttf

460 ms

modules.woff

modules.woff

252 ms

PbynFmL8HhTPqbjUzux3JEuf9l4.ttf

PbynFmL8HhTPqbjUzux3JEuf9l4.ttf

330 ms

Pby6FmL8HhTPqbjUzux3JEMq007hyJI.ttf

Pby6FmL8HhTPqbjUzux3JEMq007hyJI.ttf

328 ms

Pby6FmL8HhTPqbjUzux3JEMS0U7hyJI.ttf

Pby6FmL8HhTPqbjUzux3JEMS0U7hyJI.ttf

328 ms

fa-brands-400.woff

fa-brands-400.woff

252 ms

fa-regular-400.woff

fa-regular-400.woff

240 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

178 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

251 ms

fa-solid-900.woff

fa-solid-900.woff

250 ms

image1-1.jpeg

image1-1.jpeg

204 ms

bg_tillman-honors_2000x1333_01.jpg

bg_tillman-honors_2000x1333_01.jpg

280 ms

97HsJkYM0RE

97HsJkYM0RE

421 ms

www-player.css

www-player.css

63 ms

www-embed-player.js

www-embed-player.js

106 ms

base.js

base.js

241 ms

d

d

127 ms

d

d

211 ms

d

d

210 ms

d

d

423 ms

d

d

142 ms

d

d

174 ms

d

d

141 ms

d

d

857 ms

p.gif

p.gif

392 ms

ad_status.js

ad_status.js

197 ms

XRk6eFbYaDme_I9SSIFgFZ9I1nSvAmlSIHv6h58Lfu0.js

XRk6eFbYaDme_I9SSIFgFZ9I1nSvAmlSIHv6h58Lfu0.js

103 ms

embed.js

embed.js

21 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

29 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

29 ms

id

id

41 ms

Create

Create

104 ms

Accessibility Review

ptf.org accessibility score

88

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

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

ptf.org best practices score

92

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

Page has valid source maps

SEO Factors

ptf.org SEO score

90

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

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

    N/A

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ptf.org can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Ptf.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

ptf.org

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