etsracingfuels.com website review

About 382 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.

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

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

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

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

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

Google Tag Manager costs a phone 153 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.

8 third-party services load with your homepage (Google Tag Manager, Cookiebot and elfsight.com and others), adding 771 KiB and 353 ms of main-thread time.

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

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

4 images could be 108 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

Polyfills for old browsers add 25 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.

3 KiB could be saved by minifying JavaScript.

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

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

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

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

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

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

4 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-31, real Chrome visitors' largest content (lcp) went from 2.3 s to 2.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 4.1 MB in 196 requests on a phone: media 1.7 MB (1), scripts 998 KiB (43) and other files 853 KiB (126). Under 2 MB keeps phones on slow connections fast.

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

2 buttons have no accessible name, so screen readers announce just “button”.

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

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

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

There are 2 <h1> headlines (“” and “”). One clear main headline is easier for people and search engines.

Your meta description is 279 characters; Google truncates after about 160, so the end of your pitch is cut.

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

The homepage links to 83 pages on etsracingfuels.com and 17 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.

Your homepage links to /pages/distributors-and-dealers, which answers with an error. Visitors hit a dead end and search engines drop it.

/pages/championship-titles-new and /pages/championships all use the title “Championship Titles – ETS Racing Fuels”. Search engines can't tell which page to show for a search, so each competes with the others.

/collections/racing-fuels, /pages/fuel_finder, /pages/technical-questionnaire, /blogs/blog, /pages/products-services and /pages/partnership 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 /collections/best-sellers/products/classic-racing, whose canonical is /products/classic-racing. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

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

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

4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

1 link from your homepage to your own site is broken, for example https://www.etsracingfuels.com/pages/distributors-and-dealers (404).

HSTS is set, but max-age is 91 days; one year is the recommended minimum.

7 links go through two or more redirects, for example https://www.facebook.com/sharer.php?u=https://www.etsracingfuels.com/products/classic-racing.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

etsracingfuels.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

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.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

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

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

etsracingfuels.com has no DMARC record, so nothing tells receivers what to do with mail that fails SPF or DKIM. Gmail and Yahoo require DMARC from bulk senders.

We found no DKIM key on the selectors the big email providers use. If you send through one of them, turning on DKIM signing improves delivery.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Meta Pixel (measured from a US location before any click). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.

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

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