Website review, no card needed

thedieselstore.com logo

thedieselstore.com website review

Visit site (opens in a new tab)Reviewed 1 November 202642 issues · 68 checks

This review found 42 issues worth fixing on thedieselstore.com, 18 of them high impact, across 68 checks. The most urgent: render-blocking requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
7.1 s4.2 sMay 9Oct 244.8 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20264.6 s
May 16, 20265.0 s
May 23, 20265.3 s
May 30, 20265.6 s
Jun 6, 20265.9 s
Jun 13, 20266.0 s
Jun 20, 20266.2 s
Jun 27, 20266.2 s
Jul 4, 20266.3 s
Jul 11, 20266.5 s
Jul 18, 20266.6 s
Jul 25, 20266.7 s
Aug 1, 20266.6 s
Aug 8, 20266.7 s
Aug 15, 20266.7 s
Aug 22, 20266.8 s
Aug 29, 20266.6 s
Sep 5, 20266.1 s
Sep 12, 20265.5 s
Sep 19, 20265.1 s
Sep 26, 20265.1 s
Oct 3, 20265.0 s
Oct 10, 20265.0 s
Oct 17, 20265.0 s
Oct 24, 20264.8 s
Real-visitor tap response (INP)75th percentile, phones
228 ms161 msMay 9Oct 24206 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026169 ms
May 16, 2026174 ms
May 23, 2026182 ms
May 30, 2026188 ms
Jun 6, 2026196 ms
Jun 13, 2026196 ms
Jun 20, 2026200 ms
Jun 27, 2026197 ms
Jul 4, 2026201 ms
Jul 11, 2026205 ms
Jul 18, 2026205 ms
Jul 25, 2026211 ms
Aug 1, 2026210 ms
Aug 8, 2026213 ms
Aug 15, 2026215 ms
Aug 22, 2026220 ms
Aug 29, 2026220 ms
Sep 5, 2026211 ms
Sep 12, 2026208 ms
Sep 19, 2026197 ms
Sep 26, 2026203 ms
Oct 3, 2026209 ms
Oct 10, 2026207 ms
Oct 17, 2026212 ms
Oct 24, 2026206 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of thedieselstore.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. thedieselstore.com at 0.4 s0.4 s
  2. thedieselstore.com at 0.8 s0.8 s
  3. thedieselstore.com at 1.1 s1.1 s
  4. thedieselstore.com at 1.5 s1.5 s
  5. thedieselstore.com at 1.9 s1.9 s
  6. thedieselstore.com at 2.3 s2.3 s
  7. thedieselstore.com at 2.6 s2.6 s
  8. thedieselstore.com at 3.0 s3.0 s

Speed

6 to fix72
  • Render-blocking requests

    1.5 s

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

  • Improve image delivery

    4.0 MB

    11 images could be 4.0 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Mobile performance score: 72

    72/100

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

  • 2 third-party services on the page

    2 third-party services load with your homepage (Google Fonts and Amazon Web Services), adding 7.0 MB and 2 ms of main-thread time.

  • Amazon Web Services adds 0 ms

    0 ms

    Amazon Web Services costs a phone 0 ms of main-thread work and 6.9 MB 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.

  • Reduce unused CSS

    570 ms · 114 KiB

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

  • Chained critical requests

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

  • Minify CSS

    3 KiB

    3 KiB could be saved by minifying CSS.

2 checks passed
  • Main-thread work: 0.4 s

    A phone's processor spends 0.4 s on main-thread work while loading, 11 ms of it running JavaScript. That is comfortably low.

  • Server response: 87 ms

    87 ms

    Your server sent the HTML in 87 ms, well inside Google's 600 ms guideline.

Core Web Vitals

9 to fix33
  • Fails Core Web Vitals for real visitors

    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.

  • Real-user CLS: 0.28

    0.28

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

  • Largest Contentful Paint: 8.3 s

    8.3 s

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

  • Time to Interactive: 8.8 s

    8.8 s

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

  • Real-user LCP: 3.4 s

    3.4 s

    Real visitors wait 3.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Tap response (INP) got 22% slower for real visitors

    +22%

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

  • Real-user FCP: 2.7 s

    2.7 s

    Real visitors see the first content after 2.7 s (75th percentile). Good is under 1.8 s.

  • First Contentful Paint: 2.3 s

    2.3 s

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

  • 4 images without width and height

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

  • Largest content (LCP) held steady for real visitors

    +2%

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

5 checks passed
  • Real-user INP: 194 ms

    194 ms

    Real visitors wait 194 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user TTFB: 750 ms

    750 ms

    Real visitors wait 750 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • Speed Index: 3.1 s

    3.1 s

    Visually, the page fills in at 3.1 s (Speed Index), inside the 3.4 s “good” threshold.

  • Cumulative Layout Shift: 0.042

    0.042

    The layout barely moves while loading (CLS 0.042, good is under 0.1).

  • Total Blocking Time: 0 ms

    0 ms

    Scripts block the page for only 0 ms while loading. Good is under 200 ms.

Images and page weight

4 to fix28
  • Page weight: 7.4 MB in 44 requests

    7.4 MB

    Your homepage downloads 7.4 MB in 44 requests on a phone: images 7.1 MB (31), stylesheets 148 KiB (9) and other files 110 KiB (2). Under 2 MB keeps phones on slow connections fast.

  • 2 images over 500 KB

    2 images weigh 2.7 MB together. On a phone connection a single image that size takes seconds.

  • 9 images far larger than shown

    2.6 MB

    9 images are downloaded at several times the size a phone draws them, for example Default+Background+-+transparent_updated.png at 1,506 px wide, shown at 370 px. Resized copies would save about 2.6 MB.

  • 5 images below the first screen load straight away

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

  • About 2.1 g of CO₂ per visit

    2.09 g

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

1 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

Accessibility

6 to fixGoogle 8291
  • Images must have alternative text (8 elements)

    Images must have alternative text: 8 elements on the page fail this check, rated critical by axe-core.

  • Required ARIA attributes must be provided (2 elements)

    Required ARIA attributes must be provided: 2 elements on the page fail this check, rated critical by axe-core.

  • Malformed lists

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

  • All page content should be contained by landmarks (1 element)

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

  • 5 links without text

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

  • ARIA role should be appropriate for the element (2 elements)

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

1 checks passed
  • 45 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 51 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 passed and 6 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

7 to fixGoogle 9252
  • No page title

    Your page has no <title>, so Google has to invent the blue link in search results.

  • No meta description

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

  • No H1 headline

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

  • No canonical URL

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

  • Structured data has 2 problems

    Structured data found (Organization and WebSite) but with 2 problems, for example “Organization: logo is not an absolute URL ("https://www.thedieselstore.com/sfsites/c/cms/delivery/m…”.

  • No social preview image

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

  • Only 0 internal links

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

  • No X (Twitter) card tag

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

2 checks passed
  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.thedieselstore.com/sitemap.xml.

AI search readiness

1 to fix75
  • Most text only appears after JavaScript runs

    0%

    A phone browser shows 214 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.

  • No llms.txt

    There is no https://www.thedieselstore.com/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.

2 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Organization data: 5 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and contact details; description would complete it.

Best practices

3 to fixGoogle 8885
  • 4 small tap targets

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

  • 6 JavaScript errors while loading

    6 errors were logged to the browser console while the page loaded, for example “The source list for Content Security Policy directive 'script-src' contains a source with an invalid path: 'https://www.thedieselstore.com/?welcome'.…”.

  • 4 distorted images

    4 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix33
  • No call to action on the first screen

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

  • No calls to action

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

  • No social proof

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

  • No direct contact details

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

  • Only about 214 words

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

  • No form on the homepage

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

  • No risk reducer

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

1 checks passed
  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics, Meta Pixel and Hotjar.

Privacy and tracking

1 to fix
  • 6 trackers load before any consent

    6

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and Klaviyo and 1 more (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.

  • 16 cookies set on arrival

    16

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

  • No consent tool detected

    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.

  • 23 other companies contacted

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

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at thedieselstore.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
Bootstrap
Analytics
Google Analytics | Google Tag Manager | Hotjar
Hosting
Cloudflare

Company

Employees
557

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 42 issues on thedieselstore.com, including 15 speed issues, 7 SEO issues and 5 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25