Website review, no card needed

parts33.com logo

parts33.com website review

Visit site (opens in a new tab)Reviewed 11 November 202624 issues · 77 checks

This review found 24 issues worth fixing on parts33.com, 7 of them high impact, across 77 checks. The most urgent: page weight: 10.3 MB in 143 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
2.1 s1.4 sMay 23Nov 71.4 s
Show as table
DateReal-visitor load time (LCP)
May 23, 20261.7 s
May 30, 20261.7 s
Jun 6, 20261.7 s
Jun 13, 20261.7 s
Jun 20, 20261.8 s
Jun 27, 20261.8 s
Jul 4, 20261.8 s
Jul 11, 20261.9 s
Jul 18, 20261.9 s
Jul 25, 20262.0 s
Aug 1, 20262.0 s
Aug 8, 20262.0 s
Aug 15, 20262.0 s
Aug 22, 20261.9 s
Aug 29, 20261.9 s
Sep 5, 20261.9 s
Sep 12, 20261.9 s
Sep 19, 20261.9 s
Sep 26, 20261.8 s
Oct 3, 20261.7 s
Oct 10, 20261.5 s
Oct 17, 20261.5 s
Oct 24, 20261.5 s
Oct 31, 20261.5 s
Nov 7, 20261.4 s
Real-visitor tap response (INP)75th percentile, phones
142 ms99 msMay 23Nov 7104 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 2026123 ms
May 30, 2026125 ms
Jun 6, 2026128 ms
Jun 13, 2026126 ms
Jun 20, 2026126 ms
Jun 27, 2026124 ms
Jul 4, 2026121 ms
Jul 11, 2026125 ms
Jul 18, 2026127 ms
Jul 25, 2026129 ms
Aug 1, 2026135 ms
Aug 8, 2026132 ms
Aug 15, 2026134 ms
Aug 22, 2026137 ms
Aug 29, 2026134 ms
Sep 5, 2026133 ms
Sep 12, 2026135 ms
Sep 19, 2026129 ms
Sep 26, 2026121 ms
Oct 3, 2026115 ms
Oct 10, 2026107 ms
Oct 17, 2026104 ms
Oct 24, 2026104 ms
Oct 31, 2026105 ms
Nov 7, 2026104 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 parts33.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. parts33.com at 0.6 s0.6 s
  2. parts33.com at 1.1 s1.1 s
  3. parts33.com at 1.7 s1.7 s
  4. parts33.com at 2.3 s2.3 s
  5. parts33.com at 2.8 s2.8 s
  6. parts33.com at 3.4 s3.4 s
  7. parts33.com at 4.0 s4.0 s
  8. parts33.com at 4.5 s4.5 s

Speed

4 to fix88
  • 8,557 HTML elements

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

  • Mobile performance score: 88

    88/100

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

  • Render-blocking requests

    500 ms

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

  • Improve image delivery

    417 KiB

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

  • 1 long task on the main thread

    1 long task block the main thread while loading, the longest for 86 ms. During a long task the page ignores taps.

  • Duplicated JavaScript

    77 KiB

    77 KiB JavaScript is shipped twice across bundles.

  • 2 third-party services on the page

    2 third-party services load with your homepage (Shopify and shop.app), adding 122 KiB and 42 ms of main-thread time.

  • Reduce unused CSS

    14 KiB

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

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

  • Use efficient cache lifetimes

    4 KiB

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

  • Minify JavaScript

    3 KiB

    3 KiB could be saved by minifying JavaScript.

2 checks passed
  • Main-thread work: 1.4 s

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

  • Server response: 86 ms

    86 ms

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

Core Web Vitals

2 to fix100
  • Largest Contentful Paint: 3.8 s

    3.8 s

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

  • Time to Interactive: 4.8 s

    4.8 s

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

12 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: 2.0 s

    2.0 s

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

  • Real-user INP: 121 ms

    121 ms

    Real visitors wait 121 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.3 s

    1.3 s

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

  • Real-user TTFB: 479 ms

    479 ms

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

  • Tap response (INP) got 16% faster for real visitors

    -16%

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

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

    -14%

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

  • Speed Index: 3.2 s

    3.2 s

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

  • First Contentful Paint: 1.5 s

    1.5 s

    The first text or image appears after 1.5 s, inside the 1.8 s “good” threshold.

  • Cumulative Layout Shift: 0.002

    0.002

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

  • Total Blocking Time: 18 ms

    18 ms

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

Images and page weight

1 to fix70
  • Page weight: 10.3 MB in 143 requests

    10.3 MB

    Your homepage downloads 10.3 MB in 143 requests on a phone: media 8.5 MB (1), images 696 KiB (24) and other files 602 KiB (45). Under 2 MB keeps phones on slow connections fast.

  • 1 image below the first screen load straight away

    1 image further down the page (63 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 2.9 g of CO₂ per visit

    2.92 g

    By the Sustainable Web Design model, a visit to your homepage emits about 2.92 g of CO₂e: 350.4 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

5 to fixGoogle 9093
  • 14 text elements with low contrast

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

  • Scrollable region must have keyboard access (2 elements)

    Scrollable region must have keyboard access: 2 elements on the page fail this check, rated serious by axe-core.

  • 1 image without alt text

    1 image has no alt text, which hurts accessibility and image search.

  • All page content should be contained by landmarks (5 elements)

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

  • 9 links without text

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

  • Headings skip levels

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

1 checks passed
  • 50 automated accessibility rules passed

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

SEO

3 to fixGoogle 9285
  • Title is short (29 characters)

    Your title is only 29 characters: “PARTS33 - Drift & Racing Shop”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

  • 817 internal links, 0 external

    The homepage links to 817 pages on parts33.com and 0 external pages.

5 checks passed
  • Meta description: 127 characters

    Your meta description is 127 characters: “Onlineshop mit über 50.000 Produkten für Drift, Track, Rallye und alle anderen Motorsportarten - Beratung & Service von…”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: Organization and WebSite.

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

AI search readiness

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

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

  • Text is in the HTML

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

  • llms.txt published

    The site publishes https://parts33.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

2 to fix90
  • 14 pages without a meta description

    https://parts33.com/collections/bmw, https://parts33.com/collections/e30, https://parts33.com/collections/e36, https://parts33.com/collections/e46, https://parts33.com/collections/e8x and https://parts33.com/collections/e9x and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 5 pages without an H1

    https://parts33.com/collections/e30, https://parts33.com/collections/e36, https://parts33.com/collections/e46, https://parts33.com/collections/e8x and https://parts33.com/collections/e39 have no <h1> headline, so visitors and search engines get no clear main topic.

  • 2 pages slow to respond

    https://parts33.com/collections/e39 and https://parts33.com/collections/honda took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

5 checks passed
  • Linked pages load

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

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Titles are unique

    Every page we checked has its own title.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 14 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9693
  • 2 JavaScript errors while loading

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

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix42
  • 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.

  • Thin social proof

    Social proof on the homepage: 2 trust badges. 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 direct contact details

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

  • 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 3,130 words of copy

    The homepage carries about 3,130 words of visible text.

1 checks passed
  • 66 short forms

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

Privacy and tracking

1 to fix
  • 2 trackers load before any consent

    2

    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.

  • 7 cookies set on arrival

    7

    Opening the homepage sets 7 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.

  • 5 other companies contacted

    Loading the homepage contacts 5 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 parts33.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 4 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Powerful Form Builder · Globo Product Options · Page Speed Optimizer · Checkout Regeln Grosse Warenkoerbe 2026

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

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 24 issues on parts33.com, including 6 speed issues, 3 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