avfigures.com website review

Your mobile performance score is 47. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

A phone's processor spends 4.7 s on main-thread work while loading, 2.0 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

15 images could be 2.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 200 ms faster on a phone.

About 1.0 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 750 ms faster on a phone.

8 third-party services load with your homepage (vitals.app, PayPal and Privy and others), adding 2.1 MB and 1.5 s of main-thread time.

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

vitals.app costs a phone 355 ms of main-thread work and 657 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.

PayPal costs a phone 252 ms of main-thread work and 232 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.

Privy costs a phone 200 ms of main-thread work and 294 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.

rebuyengine.com costs a phone 183 ms of main-thread work and 300 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.

The page has 1,933 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

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

11 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 200 ms faster on a phone.

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

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

About 60 KiB of CSS is downloaded but never applied on this page.

6 KiB could be saved by minifying JavaScript.

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.

Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

Your largest element takes 12.1 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 21.3 s. Good is under 3.8 s.

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

For real visitors the layout shifts by 0.12 (75th percentile). Good is under 0.1.

Scripts block taps and scrolling for 465 ms in total while the page loads. Good is under 200 ms.

The layout shifts by 0.176 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

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

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

Your homepage downloads 6.0 MB in 298 requests on a phone: images 2.5 MB (18), scripts 2.3 MB (127) and other files 861 KiB (113). Under 2 MB keeps phones on slow connections fast.

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

ARIA commands must have an accessible name: 7 elements on the page fail this check, rated serious by axe-core.

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

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

1 button has no accessible name, so screen readers announce just “button”.

All page content should be contained by landmarks: 3 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.

7 visible links have no text or label, so screen readers cannot say where they go.

1 form field has no label, so screen readers announce an empty box and autofill guesses.

ARIA role should be appropriate for the element: 8 elements on the page fail this check, rated minor by axe-core.

Headings skip levels (h1 → h3, h3 → h5 and h3 → h5), which makes the page harder to scan with a screen reader.

Your title is only 17 characters: “AV Figures - Home”. 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.

Your <h1> is empty.

The homepage links to 97 pages on avfigures.com and 5 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.

/customer_authentication/redirect has no <title>, so Google invents the link text in results.

/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

/collections/printed-figures and /collections/printed-figures/Pad-Print all use the title “Printed Figures”. Search engines can't tell which page to show for a search, so each competes with the others.

/policies/shipping-policy, /customer_authentication/redirect, /collections/clone-decals/Decals, /collections/jedi-sith/Decals, /collections/stormtroopers/Decals and /collections/auxiliary-decals and 7 others have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 4 pages by a URL that isn't their canonical one, for example /collections/clone-decals/Decals, whose canonical is /collections/clone-decals/decals. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

/customer_authentication/redirect has no <h1> headline, so visitors and search engines get no clear main topic.

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

Social proof on the homepage: 40 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

Your longest form asks for 237 fields (0 required). Every extra field lowers completion.

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

The homepage has only about 18 words of visible text; thin pages give Google and first-time buyers little to go on.

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

Before a visitor clicks anything, the page loads Google Tag Manager and Meta Pixel (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 10 cookies, 6 of them by other companies (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 21 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.