Website review, no card needed

freshparts.it logo

freshparts.it website review

Visit site (opens in a new tab)Reviewed 12 November 202633 issues · 85 checks

This review found 33 issues worth fixing on freshparts.it, 10 of them high impact, across 85 checks. The most urgent: page weight: 49.7 MB in 368 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.0 s1.3 sMay 23Nov 71.3 s
Show as table
DateReal-visitor load time (LCP)
May 23, 20261.9 s
May 30, 20261.9 s
Jun 6, 20261.9 s
Jun 13, 20261.9 s
Jun 20, 20261.9 s
Jun 27, 20261.9 s
Jul 4, 20261.9 s
Jul 11, 20261.9 s
Jul 18, 20261.8 s
Jul 25, 20261.7 s
Aug 1, 20261.6 s
Aug 8, 20261.5 s
Aug 15, 20261.6 s
Aug 22, 20261.6 s
Aug 29, 20261.6 s
Sep 5, 20261.6 s
Sep 12, 20261.5 s
Sep 19, 20261.5 s
Sep 26, 20261.4 s
Oct 3, 20261.4 s
Oct 10, 20261.4 s
Oct 17, 20261.4 s
Oct 24, 20261.4 s
Oct 31, 20261.4 s
Nov 7, 20261.3 s
Real-visitor tap response (INP)75th percentile, phones
167 ms114 msMay 23Nov 7120 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 2026140 ms
May 30, 2026145 ms
Jun 6, 2026148 ms
Jun 13, 2026152 ms
Jun 20, 2026154 ms
Jun 27, 2026157 ms
Jul 4, 2026161 ms
Jul 11, 2026159 ms
Jul 18, 2026153 ms
Jul 25, 2026146 ms
Aug 1, 2026140 ms
Aug 8, 2026136 ms
Aug 15, 2026135 ms
Aug 22, 2026132 ms
Aug 29, 2026134 ms
Sep 5, 2026130 ms
Sep 12, 2026133 ms
Sep 19, 2026134 ms
Sep 26, 2026130 ms
Oct 3, 2026132 ms
Oct 10, 2026128 ms
Oct 17, 2026127 ms
Oct 24, 2026124 ms
Oct 31, 2026120 ms
Nov 7, 2026120 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 freshparts.it (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. freshparts.it at 1.1 s1.1 s
  2. freshparts.it at 2.2 s2.2 s
  3. freshparts.it at 3.4 s3.4 s
  4. freshparts.it at 4.5 s4.5 s
  5. freshparts.it at 5.6 s5.6 s
  6. freshparts.it at 6.7 s6.7 s
  7. freshparts.it at 7.8 s7.8 s
  8. freshparts.it at 9.0 s9.0 s

Speed

12 to fix58
  • Render-blocking requests

    1.4 s

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

  • 6,101 HTML elements

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

  • Main-thread work: 6.1 s

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

  • Improve image delivery

    300 ms · 2.5 MB

    16 images could be 2.5 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 300 ms faster on a phone.

  • Reduce unused JavaScript

    900 ms · 1.6 MB

    About 1.6 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 900 ms faster on a phone.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Shopify, Google Tag Manager and pop-convert.com and others), adding 3.1 MB and 1.3 s of main-thread time.

  • Mobile performance score: 58

    58/100

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

  • Shopify adds 633 ms

    633 ms

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

  • Use efficient cache lifetimes

    727 KiB

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

  • Reduce unused CSS

    450 ms · 123 KiB

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

  • Google Tag Manager adds 334 ms

    334 ms

    Google Tag Manager costs a phone 334 ms of main-thread work and 535 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.

  • tweakwisenavigator.net adds 100 ms

    100 ms

    tweakwisenavigator.net costs a phone 100 ms of main-thread work and 478 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 CSS

    150 ms · 9 KiB

    9 KiB could be saved by minifying CSS.

  • 15 long tasks on the main thread

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

  • Minify JavaScript

    73 KiB

    73 KiB could be saved by minifying JavaScript.

  • Duplicated JavaScript

    30 KiB

    30 KiB JavaScript is shipped twice across bundles.

  • Legacy JavaScript

    8 KiB

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

1 checks passed
  • Server response: 78 ms

    78 ms

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

Core Web Vitals

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

  • Time to Interactive: 37.6 s

    37.6 s

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

  • Largest Contentful Paint: 8.6 s

    8.6 s

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

  • Speed Index: 13.7 s

    13.7 s

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

  • Real-user FCP: 2.1 s

    2.1 s

    Real visitors see the first content after 2.1 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.

  • Total Blocking Time: 266 ms

    266 ms

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

7 checks passed
  • Real-user LCP: 2.2 s

    2.2 s

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

  • Real-user INP: 181 ms

    181 ms

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

  • Real-user CLS: 0.05

    0.05

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

  • Real-user TTFB: 584 ms

    584 ms

    Real visitors wait 584 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 140 ms to 120 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

    -29%

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

  • Cumulative Layout Shift: 0.001

    0.001

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

Images and page weight

1 to fix70
  • Page weight: 49.7 MB in 368 requests

    49.7 MB

    Your homepage downloads 49.7 MB in 368 requests on a phone: media 40.8 MB (7), images 4.3 MB (77) and scripts 3.2 MB (109). Under 2 MB keeps phones on slow connections fast.

  • 4 images below the first screen load straight away

    4 images further down the page (93 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 14.1 g of CO₂ per visit

    14.09 g

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

4 to fixGoogle 8995
  • 3 text elements with low contrast

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

  • 8 images without alt text

    8 images have no alt text, which hurts accessibility and image search.

  • 175 links without text

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

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

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (1 element).

1 checks passed
  • 52 automated accessibility rules passed

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

SEO

2 to fixGoogle 8593
  • 1 link with vague text

    1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

  • One H1 headline

    Your <h1> is empty.

  • 347 internal links, 10 external

    The homepage links to 347 pages on freshparts.it and 10 external pages.

7 checks passed
  • Meta description: 131 characters

    Your meta description is 131 characters: “Scooteronderdelen voor Piaggio, Vespa & Tomos. Ruim assortiment, scherpe prijzen en snelle levering. Bestel direct bij …”.

  • Title: 41 characters

    Your title is a healthy 41 characters: “Kwaliteit scooteronderdelen – Fresh Parts”.

  • Canonical URL set

    The canonical URL is https://freshparts.nl/en.

  • Structured data in place

    Structured data found: Organization and WebSite.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • 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://freshparts.nl/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 (2,542 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

4 to fix78
  • 2 pages share a title

    https://freshparts.nl/collections/assortiment-2 and https://freshparts.nl/en/collections/assortment-4 all use the title “Assortment – Fresh Parts”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 11 pages without a meta description

    https://freshparts.nl/en/collections/zakelijk-portaal, https://freshparts.nl/collections/assortiment-2, https://freshparts.nl/en/collections/assortment-4, https://freshparts.nl/collections/styling-1, https://freshparts.nl/collections/onderhoud-2 and https://freshparts.nl/collections/tuning-merken-1 and 5 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 13 links to non-canonical URLs

    Your homepage links to 13 pages by a URL that isn't their canonical one, for example https://freshparts.nl/en/collections/zakelijk-portaal, whose canonical is https://freshparts.nl/en/collections/business-portal. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 13 pages without an H1

    https://freshparts.nl/en/collections/zakelijk-portaal, https://freshparts.nl/collections/assortiment-2, https://freshparts.nl/en/collections/assortment-4, https://freshparts.nl/collections/styling-1, https://freshparts.nl/collections/onderhoud-2 and https://freshparts.nl/collections/tuning-merken-1 and 7 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 4 pages slow to respond

    https://freshparts.nl/collections/styling-1, https://freshparts.nl/collections/onderhoud-2, https://freshparts.nl/collections/tuning-merken-1 and https://freshparts.nl/collections/inlaat-toebehoren-1 took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

3 checks passed
  • Linked pages load

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

  • 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

2 to fixGoogle 7791
  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

  • 4 JavaScript errors while loading

    4 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

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix93
  • No analytics detected

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

  • About 1,111 words of copy

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

  • Urgency cues

    The page uses urgency cues (a countdown or limited-time wording).

6 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “PRE ORDER View the collection”.

  • 5 calls to action

    The homepage has 5 calls to action, for example “Follow your order!”, “Can I order for business purposes?” and “Where is my order?”.

  • 32 short forms

    32 short forms (3 fields at most) are right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 1 testimonial or review block, a star rating and “1000+ Reviews”.

  • Direct contact links

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

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

Privacy and tracking

  • 4 trackers load before any consent

    4

    Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager, Meta Pixel and TikTok 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.

  • 20 cookies set on arrival

    20

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

  • 50 other companies contacted

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

1 checks passed
  • Consent tool: Cookiebot

    A consent management tool (Cookiebot) loads with the page.

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 freshparts.it, 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 24 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Ot Theme Sections · Pify Size Charts · Langshop · Profitmetrics · Optis Color Swatch · Ot Section Builder · Reputon Google Reviews Widget · Shopify Cli · Ordereasy · Bundle App · Xb Wishlist · Emailwiz Email Marketing · Free Gift · Aichatbot Freshparts · 61f56232 · Easify Product Options · Wizz Sticky Cart Add To Cart · one.store · ordersify.com · dolphinsuite.com · pop-convert.com · automizely.com · avada.io · amazonaws.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

Framework
Tailwind CSS
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 33 issues on freshparts.it, including 19 speed issues, 2 SEO issues and 1 conversion gap. 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