Tools & Wizards About Us
hometown-pride.com screenshot

Report Summary

  • 9

    Performance

    Renders faster than
    23% of other websites

  • 61

    Accessibility

    Visual factors better than
    that of 27% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 84

    SEO

    Google-friendlier than
    52% of websites

hometown-pride.com

Home - VeteranBanners.com

Page Load Speed

3.5 sec in total

First Response

358 ms

Resources Loaded

2.5 sec

Page Rendered

652 ms

hometown-pride.com screenshot

About Website

Visit hometown-pride.com now to see the best up-to-date Home Townpride content and also check out these interesting facts you probably never knew about hometown-pride.com

HOMETOWN HERO veteran banner program made simple for over 10 years--honoring past and present members of: the Armed Forces (Army, Marine Corps, Navy, Air Force, and Coast Guard) and First Responders.

Visit hometown-pride.com

Key Findings

We analyzed Hometown-pride.com page load time and found that the first response time was 358 ms and then it took 3.1 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

hometown-pride.com performance score

9

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.2 s

42/100

10%

LCP (Largest Contentful Paint)

Value14.6 s

0/100

25%

SI (Speed Index)

Value8.0 s

22/100

10%

TBT (Total Blocking Time)

Value3,840 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.547

13/100

15%

TTI (Time to Interactive)

Value24.1 s

0/100

10%

Network Requests Diagram

veteranbanners.com

358 ms

mediaelementplayer-legacy.min.css

104 ms

wp-mediaelement.min.css

167 ms

magnific_popup.css

168 ms

animate.css

159 ms

Our browser made a total of 110 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Hometown-pride.com, 9% (10 requests) were made to Fonts.gstatic.com and 7% (8 requests) were made to Youtube.com. The less responsive or slowest element that took the longest time to load (1000 ms) relates to the external source Veteranbanners.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 758.2 kB (32%)

Content Size

2.4 MB

After Optimization

1.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Hometown-pride.com main page is 2.4 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 1.3 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 358.7 kB

  • Original 426.0 kB
  • After minification 418.3 kB
  • After compression 67.3 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 358.7 kB or 84% of the original size.

Image Optimization

-29%

Potential reduce by 392.4 kB

  • Original 1.3 MB
  • After minification 950.1 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. Obviously, Home Townpride needs image optimization as it can save up to 392.4 kB or 29% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-1%

Potential reduce by 6.1 kB

  • Original 486.0 kB
  • After minification 486.0 kB
  • After compression 479.9 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

-1%

Potential reduce by 976 B

  • Original 121.8 kB
  • After minification 121.7 kB
  • After compression 120.9 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. Hometown-pride.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 71 (76%)

Requests Now

94

After Optimization

23

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

veteranbanners.com

veteranbanners.com

358 ms

mediaelementplayer-legacy.min.css

mediaelementplayer-legacy.min.css

104 ms

wp-mediaelement.min.css

wp-mediaelement.min.css

167 ms

magnific_popup.css

magnific_popup.css

168 ms

animate.css

animate.css

159 ms

woocommerce-layout.css

woocommerce-layout.css

164 ms

woocommerce.css

woocommerce.css

169 ms

cookieblocker.min.css

cookieblocker.min.css

168 ms

style_1.css

style_1.css

210 ms

style.min.css

style.min.css

252 ms

css

css

41 ms

basic.min.css

basic.min.css

202 ms

theme-ie11.min.css

theme-ie11.min.css

200 ms

theme.min.css

theme.min.css

205 ms

style.css

style.css

249 ms

jquery.min.js

jquery.min.js

307 ms

jquery-migrate.min.js

jquery-migrate.min.js

269 ms

underscore.min.js

underscore.min.js

270 ms

wp-util.min.js

wp-util.min.js

270 ms

jquery.blockUI.min.js

jquery.blockUI.min.js

300 ms

add-to-cart-variation.min.js

add-to-cart-variation.min.js

303 ms

frontend-gtag.min.js

frontend-gtag.min.js

305 ms

add-to-cart.min.js

add-to-cart.min.js

340 ms

js.cookie.min.js

js.cookie.min.js

339 ms

woocommerce.min.js

woocommerce.min.js

351 ms

jquery.json.min.js

jquery.json.min.js

356 ms

gravityforms.min.js

gravityforms.min.js

478 ms

utils.min.js

utils.min.js

328 ms

et-core-unified-9518.min.css

et-core-unified-9518.min.css

329 ms

slick.js

slick.js

27 ms

index.js

index.js

141 ms

wc-blocks.css

wc-blocks.css

340 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

471 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

473 ms

wp-polyfill.min.js

wp-polyfill.min.js

475 ms

hooks.min.js

hooks.min.js

477 ms

i18n.min.js

i18n.min.js

476 ms

main.js

main.js

482 ms

accounting.min.js

accounting.min.js

482 ms

core.min.js

core.min.js

433 ms

datepicker.min.js

datepicker.min.js

375 ms

addons.min.js

addons.min.js

374 ms

sourcebuster.min.js

sourcebuster.min.js

371 ms

order-attribution.min.js

order-attribution.min.js

381 ms

scripts.min.js

scripts.min.js

442 ms

jquery.fitvids.js

jquery.fitvids.js

379 ms

magnific-popup.js

magnific-popup.js

377 ms

easypiechart.js

easypiechart.js

374 ms

salvattore.js

salvattore.js

374 ms

frontend-bundle.min.js

frontend-bundle.min.js

399 ms

dom-ready.min.js

dom-ready.min.js

397 ms

a11y.min.js

a11y.min.js

356 ms

placeholders.jquery.min.js

placeholders.jquery.min.js

336 ms

vendor-theme.min.js

vendor-theme.min.js

335 ms

scripts-theme.min.js

scripts-theme.min.js

436 ms

common.js

common.js

435 ms

complianz.min.js

complianz.min.js

407 ms

jquery.magnific-popup.js

jquery.magnific-popup.js

403 ms

847385703

847385703

271 ms

283wO-DYRK4

283wO-DYRK4

185 ms

dsm-magnific-popup-image.js

dsm-magnific-popup-image.js

372 ms

mediaelement-and-player.min.js

mediaelement-and-player.min.js

722 ms

mediaelement-migrate.min.js

mediaelement-migrate.min.js

707 ms

wp-mediaelement.min.js

wp-mediaelement.min.js

718 ms

front-end.js

front-end.js

707 ms

veteranbannerlogo_1-1.png

veteranbannerlogo_1-1.png

701 ms

Polygon-1.png

Polygon-1.png

699 ms

thank-you-veterans.png

thank-you-veterans.png

898 ms

Group-49.png

Group-49.png

634 ms

Group-50.png

Group-50.png

633 ms

Group-51.png

Group-51.png

633 ms

veteran-banner-hometowrn-heroes-honor.jpg

veteran-banner-hometowrn-heroes-honor.jpg

762 ms

Screenshot-2023-06-05-at-2.33.03-PM-400x250.png

Screenshot-2023-06-05-at-2.33.03-PM-400x250.png

762 ms

top-10-military-books-on-amazon-400x250.png

top-10-military-books-on-amazon-400x250.png

760 ms

www-player.css

www-player.css

23 ms

www-embed-player.js

www-embed-player.js

89 ms

base.js

base.js

193 ms

IMG_1871-400x250.jpg

IMG_1871-400x250.jpg

754 ms

fundraising-image.png

fundraising-image.png

1000 ms

veteranbannerlogo_1.png

veteranbannerlogo_1.png

848 ms

fan-banners-tagline-300x156.png

fan-banners-tagline-300x156.png

847 ms

logo-councilcares-dark-bkd-300x46.png

logo-councilcares-dark-bkd-300x46.png

846 ms

tDbD2oWUg0MKqScQ6A.ttf

tDbD2oWUg0MKqScQ6A.ttf

177 ms

tDbM2oWUg0MKoZw1-LPK9g.ttf

tDbM2oWUg0MKoZw1-LPK9g.ttf

177 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjr0B4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjr0B4uaVc.ttf

516 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVc.ttf

528 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVc.ttf

543 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVc.ttf

544 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVc.ttf

541 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4uaVc.ttf

541 ms

modules.woff

modules.woff

854 ms

ck.5.js

ck.5.js

476 ms

ad_status.js

ad_status.js

267 ms

obds7IdaQltrj87jonrSfRLQUvzJvCScR1OQz8UbDzI.js

obds7IdaQltrj87jonrSfRLQUvzJvCScR1OQz8UbDzI.js

184 ms

embed.js

embed.js

64 ms

et-divi-dynamic-tb-9531-tb-9267-9518-late.css

et-divi-dynamic-tb-9531-tb-9267-9518-late.css

330 ms

api.js

api.js

60 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

16 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

16 ms

Create

Create

114 ms

id

id

15 ms

GenerateIT

GenerateIT

114 ms

woocommerce-smallscreen.css

woocommerce-smallscreen.css

245 ms

847385703

847385703

306 ms

qoe

qoe

25 ms

log_event

log_event

1 ms

283wO-DYRK4

283wO-DYRK4

183 ms

ad_status.js

ad_status.js

76 ms

Create

Create

83 ms

id

id

28 ms

Accessibility Review

hometown-pride.com accessibility score

61

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

High

[aria-hidden="true"] elements contain focusable descendents

High

ARIA input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

High

[aria-*] attributes do not have valid values

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

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

[id] attributes on active, focusable elements are not unique

High

Heading elements are not in a sequentially-descending order

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

hometown-pride.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

Page has valid source maps

SEO Factors

hometown-pride.com SEO score

84

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

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 Hometown-pride.com 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 Hometown-pride.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

hometown-pride.com

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