Website review, no card needed

pdidiesel.com logo

pdidiesel.com website review

Visit site (opens in a new tab)Reviewed 9 November 202633 issues · 83 checks

This review found 33 issues worth fixing on pdidiesel.com, 5 of them high impact, across 83 checks. The most urgent: reduce unused JavaScript. 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
1.2 s928 msMay 23Nov 7961 ms
Show as table
DateReal-visitor load time (LCP)
May 23, 20261.1 s
May 30, 20261.1 s
Jun 6, 20261.0 s
Jun 13, 20261.0 s
Jun 20, 20261.0 s
Jun 27, 20261.1 s
Jul 4, 20261.1 s
Jul 11, 20261.1 s
Jul 18, 20261.0 s
Jul 25, 20261.0 s
Aug 1, 20261.0 s
Aug 8, 20261.0 s
Aug 15, 20261.1 s
Aug 22, 20261.1 s
Aug 29, 20261.1 s
Sep 5, 20261.1 s
Sep 12, 20261.0 s
Sep 19, 20261.0 s
Sep 26, 20261.0 s
Oct 3, 20261.0 s
Oct 10, 20261.0 s
Oct 17, 2026977 ms
Oct 24, 2026955 ms
Oct 31, 2026954 ms
Nov 7, 2026961 ms
Real-visitor tap response (INP)75th percentile, phones
97 ms77 msMay 23Nov 795 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 202679 ms
May 30, 202682 ms
Jun 6, 202686 ms
Jun 13, 202687 ms
Jun 20, 202687 ms
Jun 27, 202686 ms
Jul 4, 202685 ms
Jul 11, 202683 ms
Jul 18, 202681 ms
Jul 25, 202682 ms
Aug 1, 202684 ms
Aug 8, 202684 ms
Aug 15, 202686 ms
Aug 22, 202686 ms
Aug 29, 202686 ms
Sep 5, 202687 ms
Sep 12, 202687 ms
Sep 19, 202687 ms
Sep 26, 202688 ms
Oct 3, 202688 ms
Oct 10, 202689 ms
Oct 17, 202688 ms
Oct 24, 202691 ms
Oct 31, 202694 ms
Nov 7, 202695 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 pdidiesel.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. pdidiesel.com at 0.8 s0.8 s
  2. pdidiesel.com at 1.6 s1.6 s
  3. pdidiesel.com at 2.4 s2.4 s
  4. pdidiesel.com at 3.2 s3.2 s
  5. pdidiesel.com at 4.0 s4.0 s
  6. pdidiesel.com at 4.8 s4.8 s
  7. pdidiesel.com at 5.6 s5.6 s
  8. pdidiesel.com at 6.4 s6.4 s

Speed

9 to fix64
  • Reduce unused JavaScript

    1.6 s · 458 KiB

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

  • Main-thread work: 4.7 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Shopify, Affirm and Klaviyo and others), adding 1.2 MB and 895 ms of main-thread time.

  • Mobile performance score: 64

    64/100

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

  • Improve image delivery

    450 ms · 322 KiB

    7 images could be 322 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 450 ms faster on a phone.

  • Shopify adds 383 ms

    383 ms

    Shopify costs a phone 383 ms of main-thread work and 632 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.

  • Minify JavaScript

    300 ms · 57 KiB

    57 KiB could be saved by minifying JavaScript.

  • 2,653 HTML elements

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

  • Klaviyo adds 208 ms

    208 ms

    Klaviyo costs a phone 208 ms of main-thread work and 328 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 long tasks on the main thread

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

  • Use efficient cache lifetimes

    178 KiB

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

  • Duplicated JavaScript

    38 KiB

    38 KiB JavaScript is shipped twice across bundles.

  • Reduce unused CSS

    26 KiB

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

  • Legacy JavaScript

    25 KiB

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

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

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

  • Minify CSS

    4 KiB

    4 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 7 ms

    7 ms

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

Core Web Vitals

5 to fix100
  • Largest Contentful Paint: 11.6 s

    11.6 s

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

  • Time to Interactive: 13.2 s

    13.2 s

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

  • Speed Index: 5.3 s

    5.3 s

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

  • Total Blocking Time: 282 ms

    282 ms

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

  • First Contentful Paint: 1.9 s

    1.9 s

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

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

    +17%

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

8 checks passed
  • Passes Core Web Vitals for real visitors

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

  • Real-user LCP: 1.3 s

    1.3 s

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

  • Real-user INP: 103 ms

    103 ms

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

  • Real-user CLS: 0.00

    0.00

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

  • Real-user FCP: 1.1 s

    1.1 s

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

  • Real-user TTFB: 744 ms

    744 ms

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

  • Largest content (LCP) got 13% faster for real visitors

    -13%

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

  • Cumulative Layout Shift: 0.002

    0.002

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

Images and page weight

2 to fix81
  • Page weight: 4.0 MB in 356 requests

    4.0 MB

    Your homepage downloads 4.0 MB in 356 requests on a phone: images 1.5 MB (51), scripts 1.3 MB (147) and other files 818 KiB (124). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    PDI_Mobile_Image_1080_X_1350_2.png is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  • About 1.1 g of CO₂ per visit

    1.13 g

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

2 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

2 to fixGoogle 9798
  • All page content should be contained by landmarks (7 elements)

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

  • 16 links without text

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

2 checks passed
  • Every image has alt text

    All 147 images in the HTML carry an alt attribute.

  • 51 automated accessibility rules passed

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

SEO

5 to fixGoogle 10076
  • Title is long (89 characters)

    Your title is 89 characters, so Google will cut it off around 60: “Performance Diesel | PDI Diesel | CAT, Cummins, Detroit, & More‎ – Performance Diesel Inc”.

  • Meta description is long (281 characters)

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

  • Structured data has 1 problem

    Structured data found (Organization and WebSite) but with 1 problem, for example “Organization: sameAs is an empty list”.

  • No social preview image

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

  • One H1 headline

    Your <h1> is empty.

  • 294 internal links, 1 external

    The homepage links to 294 pages on pdidiesel.com and 1 external page.

3 checks passed
  • Canonical URL set

    The canonical URL is https://pdidiesel.com/.

  • 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://pdidiesel.com/sitemap.xml.

AI search readiness

100
  • No llms.txt

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

3 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: 6 of 6 facts

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

  • Text is in the HTML

    Your server sends the page's text in the HTML (1,496 words), so crawlers that don't run JavaScript still read it.

Other pages

5 to fix63
  • 1 page without a title

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

  • 1 linked page hidden from search

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

  • 4 pages without a meta description

    https://pdidiesel.com/customer_authentication/redirect, https://pdidiesel.com/collections/ecm-tuning, https://pdidiesel.com/collections/pdi-big-boss%E2%84%A2-cat-exhaust-manifolds and https://pdidiesel.com/collections/pdi-big-boss%E2%84%A2-cummins-turbos have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 links to non-canonical URLs

    Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://pdidiesel.com/collections/pdi-big-boss%E2%84%A2-cat-exhaust-manifolds, whose canonical is https://pdidiesel.com/collections/pdi-big-boss%e2%84%a2-cat-exhaust-manifolds. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 1 page without an H1

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

  • 15 internal pages checked

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

2 checks passed
  • Linked pages load

    5 pages of 15 loaded without an error (the rest turned automated requests away).

  • Titles are unique

    Every page we checked has its own title.

Best practices

1 to fixGoogle 8897
  • 3 distorted images

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

  • 1 low-resolution image

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

3 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

    59 of 62 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix81
  • Local business without LocalBusiness data

    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.

  • Thin social proof

    Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No analytics detected

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

  • No opening hours

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

  • No map or directions link

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

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

  • About 1,069 words of copy

    The homepage carries about 1,069 words of visible text.

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “SHOP THE TUNER”.

  • 32 calls to action

    The homepage has 32 calls to action, for example “Shop by Engine”, “Register Products” and “Contact Us”.

  • 14 short forms

    14 short forms (1 field at most) are right on the homepage.

  • Direct contact links

    Visitors can reach you directly: 5 phone links and 0 email links.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

Privacy and tracking

1 to fix
  • 1 tracker load before any consent

    1

    Before a visitor clicks anything, the page loads Klaviyo (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.

  • 7 cookies set on arrival

    7

    Opening the homepage sets 7 cookies, 1 of them by other companies (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.

  • 18 other companies contacted

    Loading the homepage contacts 18 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 pdidiesel.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Apps on your store

Your storefront loads 7 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Inbox · Klaviyo Email Marketing Sms · Vol Fees Surcharge · Unlimited Smart Upsell Offers · ywxi.net · revy.io · nfcube.com

Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info

Upkeep, stack and company

Stack

E-commerce
Shopify
Hosting
Shopify

Company

Headquarters
St. George

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 33 issues on pdidiesel.com, including 14 speed issues, 5 SEO issues and 3 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