quad-a.org website review

14 images could be 4.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 15.9 s faster on a phone.

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

41 files are served with short cache lifetimes, so returning visitors download them again (729 KiB).

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

Your mobile performance score is 57. Pages that score under 90 lose visitors before the first paint.

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

Cloudflare CDN costs a phone 33 ms of main-thread work and 345 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.

6 third-party services load with your homepage (Google Tag Manager, givebutter.com and azure.com and others), adding 931 KiB and 369 ms of main-thread time.

6 long tasks block the main thread while loading, the longest for 148 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).

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

9 KiB could be saved by minifying CSS.

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.

Your largest element takes 21.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

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

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

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

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 6.1 MB in 65 requests on a phone: images 4.7 MB (22), scripts 917 KiB (20) and fonts 354 KiB (5). Under 2 MB keeps phones on slow connections fast.

3 images weigh 3.4 MB together. On a phone connection a single image that size takes seconds.

4 images are downloaded at several times the size a phone draws them, for example AAAA_26_ScholarshipBanner_1350x546.png at 1,350 px wide, shown at 330 px. Resized copies would save about 1.4 MB.

16 images (4.6 MB) 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.

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

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

5 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

ARIA input fields must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

Some lists contain elements other than list items, which screen readers announce wrongly.

Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.

13 images have no alt text, which hurts accessibility and image search.

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.

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.

Elements with visible text labels do not have matching accessible names. (2 elements).

No meta description, so Google writes its own snippet from whatever text it finds.

Your title is only 9 characters: “Home Page”. Between 30 and 65 characters leaves room to say what you do and for whom.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

There are 4 <h1> headlines (“2 Weeks Away - Register Now!”, “JOIN US in Kansas City!” and “American Roadhouse Evening - 11.17”). One clear main headline is easier for people and search engines.

No Open Graph image (also missing: og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

No XML sitemap at https://quad-a.org/sitemap.xml, so Google discovers your pages only by following links.

9 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

5 links have no real href, so search engines can't follow them.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 21 pages on quad-a.org and 10 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

There is no https://quad-a.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.

https://quad-a.org/27summit is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

/ and https://quad-a.org/Public/Public/Home-Page.aspx all use the title “Home Page”. Search engines can't tell which page to show for a search, so each competes with the others.

https://quad-a.org/Public/Public/Store/Product_Display.aspx, https://quad-a.org/Public/Shared_Content/Shop/Cart_Home.aspx, https://quad-a.org/Public/Public/AAAA_Membership/member_join.aspx, https://quad-a.org/26Cribbins, https://quad-a.org/27summit and https://quad-a.org/Scholarship/Scholarship/Apply/Application_Procedure.aspx and 6 others have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://quad-a.org/tlc, whose canonical is https://quad-a.org/TLC/TLC/AAAA-TLC-Foundation-Home-Page.aspx. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://quad-a.org/Public/Public/Store/Product_Display.aspx, https://quad-a.org/Public/Shared_Content/Shop/Cart_Home.aspx, https://quad-a.org/26Cribbins, https://quad-a.org/27summit, https://quad-a.org/Scholarship/Scholarship/Apply/Application_Procedure.aspx and https://quad-a.org/Public/Public/Awards/National-Awards.aspx and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.

https://quad-a.org/Public/Shared_Content/Shop/Cart_Home.aspx 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.

https://quad-a.org/Public/Public/Store/Product_Display.aspx took over 3 s to send its HTML from our server.

We fetched 14 pages linked from your homepage and read each the way a search engine does.

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

1 error was logged to the browser console while the page loaded, for example “[widgets-core] Error initializing web components NotSupportedError: Failed to execute 'define' on 'CustomElementRegistr…”.

Large scripts ship without source maps.

Social proof on the homepage: “over 5.5M members”. Pairing it with named testimonials or customer logos makes it far more convincing.

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 617 words of visible text.

Before a visitor clicks anything, the page loads 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 6 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 8 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.