Tools & Wizards About Us
avtt.org screenshot

Report Summary

  • 33

    Performance

    Renders faster than
    53% of other websites

  • 76

    Accessibility

    Visual factors better than
    that of 42% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

avtt.org

American Veterans Traveling Tribute | Vietnam Wall | 197 County Road 3506, Bullard, TX, USA

Page Load Speed

2.9 sec in total

First Response

54 ms

Resources Loaded

2.8 sec

Page Rendered

57 ms

avtt.org screenshot

About Website

Welcome to avtt.org homepage info - get ready to check Avtt best content right away, or after learning these important things about avtt.org

American Veterans Traveling Tribute (AVTT) Custom Builder & Engraver of The Traveling Vietnam Memorial Wall Designer & Builder of The Cost of Freedom Tribute.

Visit avtt.org

Key Findings

We analyzed Avtt.org page load time and found that the first response time was 54 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

avtt.org performance score

33

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.2 s

44/100

10%

LCP (Largest Contentful Paint)

Value9.2 s

1/100

25%

SI (Speed Index)

Value5.1 s

61/100

10%

TBT (Total Blocking Time)

Value1,040 ms

25/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value20.1 s

2/100

10%

Network Requests Diagram

www.americanveteranstravelingtribute.com

54 ms

minified.js

30 ms

focus-within-polyfill.js

29 ms

polyfill.min.js

955 ms

thunderbolt-commons.81e79c4a.bundle.min.js

59 ms

Our browser made a total of 51 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Avtt.org, 31% (16 requests) were made to Static.wixstatic.com and 24% (12 requests) were made to Sentry-next.wixpress.com. The less responsive or slowest element that took the longest time to load (955 ms) relates to the external source Polyfill-fastly.io.

Page Optimization Overview & Recommendations

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

Content Size

2.2 MB

After Optimization

1.1 MB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Avtt.org main page is 2.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. 40% of websites need less resources to load. HTML takes 1.2 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 965.1 kB

  • Original 1.2 MB
  • After minification 1.2 MB
  • After compression 240.6 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 965.1 kB or 80% of the original size.

Image Optimization

-16%

Potential reduce by 124.1 kB

  • Original 762.5 kB
  • After minification 638.4 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, Avtt needs image optimization as it can save up to 124.1 kB or 16% 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 3.6 kB

  • Original 244.2 kB
  • After minification 244.2 kB
  • After compression 240.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. This website has mostly compressed JavaScripts.

Requests Breakdown

Number of requests can be reduced by 11 (34%)

Requests Now

32

After Optimization

21

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.americanveteranstravelingtribute.com

www.americanveteranstravelingtribute.com

54 ms

minified.js

minified.js

30 ms

focus-within-polyfill.js

focus-within-polyfill.js

29 ms

polyfill.min.js

polyfill.min.js

955 ms

thunderbolt-commons.81e79c4a.bundle.min.js

thunderbolt-commons.81e79c4a.bundle.min.js

59 ms

main.e8bb44c8.bundle.min.js

main.e8bb44c8.bundle.min.js

63 ms

main.renderer.1d21f023.bundle.min.js

main.renderer.1d21f023.bundle.min.js

63 ms

lodash.min.js

lodash.min.js

63 ms

react.production.min.js

react.production.min.js

64 ms

react-dom.production.min.js

react-dom.production.min.js

65 ms

siteTags.bundle.min.js

siteTags.bundle.min.js

63 ms

139b4f_7c5ee7bcb7824f96a7a510249ea33d00.png

139b4f_7c5ee7bcb7824f96a7a510249ea33d00.png

133 ms

b56a57_bfe0ad6b438b4139ac3492ac7b86881e~mv2.png

b56a57_bfe0ad6b438b4139ac3492ac7b86881e~mv2.png

148 ms

b56a57_f507e6fa0c4b4e06847cce5276a6571c~mv2.jpg

b56a57_f507e6fa0c4b4e06847cce5276a6571c~mv2.jpg

144 ms

139b4f_9bfecf864b084e92b23088d4da69b241.png

139b4f_9bfecf864b084e92b23088d4da69b241.png

131 ms

139b4f_8b8b4ebf2623454bad0f017892c9ee98.png

139b4f_8b8b4ebf2623454bad0f017892c9ee98.png

132 ms

139b4f_7c5ee7bcb7824f96a7a510249ea33d00.png

139b4f_7c5ee7bcb7824f96a7a510249ea33d00.png

132 ms

f9a47e_e7631916c7e4468091c47929b7acdf8a~mv2.png

f9a47e_e7631916c7e4468091c47929b7acdf8a~mv2.png

115 ms

b56a57_bfe0ad6b438b4139ac3492ac7b86881e~mv2.png

b56a57_bfe0ad6b438b4139ac3492ac7b86881e~mv2.png

114 ms

b56a57_f507e6fa0c4b4e06847cce5276a6571c~mv2.jpg

b56a57_f507e6fa0c4b4e06847cce5276a6571c~mv2.jpg

114 ms

b56a57_1e884b2eb6364f178722b26abed18c77~mv2.jpg

b56a57_1e884b2eb6364f178722b26abed18c77~mv2.jpg

115 ms

b56a57_0c1dd724990d437eac743c19f393aab7~mv2.png

b56a57_0c1dd724990d437eac743c19f393aab7~mv2.png

140 ms

b56a57_35a0bfa4ff8b456290c4a17cc227c182~mv2.jpg

b56a57_35a0bfa4ff8b456290c4a17cc227c182~mv2.jpg

140 ms

b56a57_69f3c7457d2048328e6d0faef7424f21~mv2.jpg

b56a57_69f3c7457d2048328e6d0faef7424f21~mv2.jpg

141 ms

b56a57_942f1c010e864df8993dedafdfbc96c1~mv2.png

b56a57_942f1c010e864df8993dedafdfbc96c1~mv2.png

140 ms

b56a57_cc6f8f779c6a42f0a38029fcd69ce6ff~mv2.png

b56a57_cc6f8f779c6a42f0a38029fcd69ce6ff~mv2.png

140 ms

b56a57_c818b74966e7421e9b87c1daa761e512~mv2.png

b56a57_c818b74966e7421e9b87c1daa761e512~mv2.png

142 ms

bundle.min.js

bundle.min.js

102 ms

insight.min.js

insight.min.js

109 ms

e2b9cbeb-fa8e-41cd-8a6a-46044b29ba52.woff

e2b9cbeb-fa8e-41cd-8a6a-46044b29ba52.woff

11 ms

opensans-italic-webfont.woff

opensans-italic-webfont.woff

22 ms

opensans-bolditalic-webfont.woff

opensans-bolditalic-webfont.woff

22 ms

opensans-regular-webfont.woff

opensans-regular-webfont.woff

22 ms

opensans-bold-webfont.woff

opensans-bold-webfont.woff

22 ms

127 ms

120 ms

120 ms

118 ms

116 ms

115 ms

155 ms

148 ms

148 ms

146 ms

146 ms

148 ms

deprecation-en.v5.html

deprecation-en.v5.html

4 ms

bolt-performance

bolt-performance

25 ms

deprecation-style.v5.css

deprecation-style.v5.css

7 ms

right-arrow.svg

right-arrow.svg

6 ms

WixMadeforText_W_Rg.woff

WixMadeforText_W_Rg.woff

4 ms

Accessibility Review

avtt.org accessibility score

76

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

button, link, and menuitem elements do not have accessible names.

High

ARIA progressbar elements do not have accessible names.

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

Form elements do not have associated labels

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

avtt.org 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

avtt.org SEO score

100

Search Engine Optimization Advices

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

avtt.org

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