vpracingfuels.com website review

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

13 images could be 555 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.5 s faster on a phone.

About 174 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.5 s faster on a phone.

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

Google Tag Manager costs a phone 1.1 s of main-thread work and 977 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

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

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

8 third-party services load with your homepage (Google Tag Manager, Shopify and Google CDN and others), adding 2.4 MB and 1.8 s of main-thread time.

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

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

Shopify costs a phone 253 ms of main-thread work and 701 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 192 ms of main-thread work and 297 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.

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

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

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 19.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “2027 VP Racing Calendar”.

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

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

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

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

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

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

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

Your homepage downloads 4.7 MB in 267 requests on a phone: scripts 2.3 MB (108), images 1.1 MB (29) and fonts 725 KiB (16). Under 2 MB keeps phones on slow connections fast.

6 images (356 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.

4 images further down the page (216 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.35 g of CO₂e: 161.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

2 frames have no title, so screen-reader users cannot tell what they contain.

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

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

1 visible link has no text or label, so screen readers cannot say where it goes.

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

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

The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.

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

A phone browser shows 590 words, but the HTML your server sends has only 0. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.

5 errors were logged to the browser console while the page loaded, for example “Invalid left-hand side in assignment”.

Large scripts ship without source maps.

1 image is served at too low a resolution for sharp phone screens.

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

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

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

The homepage shows no opening hours. If customers visit or call, show when.

There is no form on the homepage, so every lead has to click through to another page first.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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 590 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 13 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 30 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.