vettix.org website review

34 files are served with short cache lifetimes, so returning visitors download them again (1.4 MB).

29 files block the first paint until they finish downloading. Deferring or inlining them could save about 6.8 s.

About 374 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.1 s faster on a phone.

About 178 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 900 ms faster on a phone.

Your mobile performance score is 56 (desktop: 84). Pages that score under 90 lose visitors before the first paint.

16 images could be 495 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 500 ms faster on a phone.

awswaf.com costs a phone 168 ms of main-thread work and 310 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

Google CDN costs a phone 104 ms of main-thread work and 346 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

7 third-party services load with your homepage (awswaf.com, Google Tag Manager and Google CDN and others), adding 990 KiB and 453 ms of main-thread time.

21 KiB could be saved by minifying CSS.

7 long tasks block the main thread while loading, the longest for 92 ms. During a long task the page ignores taps.

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

18 KiB could be saved by minifying JavaScript.

Desktop scores 84 but mobile only 56. A gap that wide usually means heavy scripts and images that hit phones hardest.

Polyfills for old browsers add 9 KiB JavaScript that modern phones do not need.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

The first text or image appears after 8.3 s on a phone. Good is under 1.8 s.

Your largest element takes 12.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Event tickets for currently serving military, veterans and …”.

The page becomes fully interactive after 12.8 s. Good is under 3.8 s.

Visually, the page fills in at 8.3 s (Speed Index). Good is under 3.4 s.

15 images have no width and height attributes, so the layout jumps as each one loads.

Over the last 25 four-week periods to 2026-10-03, real Chrome visitors' tap response (inp) went from 80 ms to 79 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Over the last 25 four-week periods to 2026-10-03, real Chrome visitors' largest content (lcp) went from 2.0 s to 2.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 2.3 MB in 77 requests on a phone: scripts 966 KiB (31), images 652 KiB (19) and fonts 472 KiB (3). Under 2 MB keeps phones on slow connections fast.

4 images are downloaded at several times the size a phone draws them, for example top-rated-awards-badge-embed.png at 560 px wide, shown at 100 px. Resized copies would save about 232 KiB.

5 images further down the page (335 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

8 images (429 KiB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

By the Sustainable Web Design model, a visit to your homepage emits about 0.65 g of CO₂e: 78.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

3 tap targets are too small or too close together to hit reliably with a finger.

2 links inside paragraphs rely on colour alone to stand out.

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

All page content should be contained by landmarks: 15 elements on the page fail this check, rated moderate by axe-core.

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

There is no <h1>, so neither visitors nor Google get a clear main headline.

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

Open Graph is missing og:description, so shared links fall back to guesses.

The homepage links to 52 pages on vettix.org and 21 external pages.

There is no https://www.vettix.org/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

/ and https://www.vettix.org/visitor/home all use the title “Vet Tix - Tickets For Troops - Veteran Tickets Foundation”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.vettix.org/tixer/get-tickets, https://www.vettix.org/tixer/get-tickets/events, https://www.vettix.org/tixer/get-tickets/discounts and https://www.vettix.org/visitor/heros-wish/wish/about%C3%9F have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.vettix.org/visitor/home, https://www.vettix.org/visitor/heros-wish/about, https://www.vettix.org/visitor/the-team/about, https://www.vettix.org/visitor/the-team/partners, https://www.vettix.org/visitor/the-team/executive-staff and https://www.vettix.org/visitor/the-team/board-of-directors use the same meta description. A description written for each page earns more clicks.

https://www.vettix.org/visitor/home, https://www.vettix.org/donate, https://www.vettix.org/tixer/get-tickets, https://www.vettix.org/tixer/get-tickets/events, https://www.vettix.org/tixer/get-tickets/discounts and https://www.vettix.org/visitor/give-back/donate/tickets and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.vettix.org/visitor/heros-wish/wish/about%C3%9F has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

We fetched 15 pages linked from your homepage (of 32 found) and read each the way a search engine does.

8 of 14 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

The page uses 1 deprecated browser API that will stop working in future browsers (“`Intl.v8BreakIterator` is deprecated. Please use `Intl.Segmenter` instead.”).

3 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://www.gstatic.com/charts/51/css/util/util.css' from origin 'https://www.vettix.org' …”.

2 images are served at too low a resolution for sharp phone screens.

Social proof on the homepage: 3 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 1,055 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Google Tag Manager (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

Opening the homepage sets 3 cookies (measured from a US location before any click).

No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.

Loading the homepage contacts 10 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.