Website review, no card needed

pimberly.com logo

pimberly.com website review

Visit site (opens in a new tab)Reviewed 25 October 202644 issues · 89 checks

This review found 44 issues worth fixing on pimberly.com, 17 of them high impact, across 89 checks. The most urgent: reduce unused CSS. 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
3.2 s2.3 sMay 2Oct 172.8 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20262.5 s
May 9, 20262.4 s
May 16, 20262.5 s
May 23, 20262.6 s
May 30, 20262.6 s
Jun 6, 20262.7 s
Jun 13, 20262.7 s
Jun 20, 20262.8 s
Jun 27, 20262.8 s
Jul 4, 20262.8 s
Jul 11, 20262.8 s
Jul 18, 20262.8 s
Jul 25, 20262.8 s
Aug 1, 20262.8 s
Aug 8, 20262.8 s
Aug 15, 20262.9 s
Aug 22, 20263.1 s
Aug 29, 20262.8 s
Sep 5, 20262.8 s
Sep 12, 20262.7 s
Sep 19, 20262.7 s
Sep 26, 20262.7 s
Oct 3, 20262.7 s
Oct 10, 20262.8 s
Oct 17, 20262.8 s
Real-visitor tap response (INP)75th percentile, phones
226 ms50 msMay 2Oct 17104 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026206 ms
May 9, 2026191 ms
May 16, 2026169 ms
May 23, 2026142 ms
May 30, 2026144 ms
Jun 6, 2026144 ms
Jun 13, 2026142 ms
Jun 20, 2026132 ms
Jun 27, 2026137 ms
Jul 4, 2026131 ms
Jul 11, 2026137 ms
Jul 18, 2026123 ms
Aug 1, 2026126 ms
Aug 22, 2026114 ms
Sep 19, 202670 ms
Oct 10, 2026104 ms
Oct 17, 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 pimberly.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. pimberly.com at 1.5 s1.5 s
  2. pimberly.com at 3.0 s3.0 s
  3. pimberly.com at 4.5 s4.5 s
  4. pimberly.com at 5.9 s5.9 s
  5. pimberly.com at 7.4 s7.4 s
  6. pimberly.com at 8.9 s8.9 s
  7. pimberly.com at 10.4 s10.4 s
  8. pimberly.com at 11.9 s11.9 s

Speed

16 to fix25
  • Reduce unused CSS

    31.7 s · 1.4 MB

    About 1.4 MB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 31.7 s faster on a phone.

  • Reduce unused JavaScript

    8.2 s · 7.5 MB

    About 7.5 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 8.2 s faster on a phone.

  • Use efficient cache lifetimes

    2.7 s · 2.3 MB

    57 files are served with short cache lifetimes, so returning visitors download them again (2.3 MB).

  • Calendly adds 3.5 s

    3.5 s

    Calendly costs a phone 3.5 s of main-thread work and 14.3 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Main-thread work: 14.1 s

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

  • Mobile performance score: 25

    25/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Calendly, Stripe and Google CDN and others), adding 18.6 MB and 5.3 s of main-thread time.

  • Improve image delivery

    850 ms · 180 KiB

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

  • 20 long tasks on the main thread

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

  • Stripe adds 553 ms

    553 ms

    Stripe costs a phone 553 ms of main-thread work and 1.4 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.

  • Google CDN adds 511 ms

    511 ms

    Google CDN costs a phone 511 ms of main-thread work and 1.4 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.

  • Google Tag Manager adds 400 ms

    400 ms

    Google Tag Manager costs a phone 400 ms of main-thread work and 609 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 · 20 KiB

    20 KiB could be saved by minifying JavaScript.

  • Render-blocking requests

    300 ms

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

  • 1,590 HTML elements

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

  • LiveChat adds 48 ms

    48 ms

    LiveChat costs a phone 48 ms of main-thread work and 368 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.

  • Legacy JavaScript

    50 ms · 33 KiB

    Polyfills for old browsers add 33 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 50 ms faster on a phone.

  • Font display

    50 ms

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

  • 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: 66 ms

    66 ms

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

Core Web Vitals

10 to fix67
  • 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.

  • First Contentful Paint: 44.3 s

    44.3 s

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

  • Largest Contentful Paint: 53.6 s

    53.6 s

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

  • Speed Index: 44.3 s

    44.3 s

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

  • Total Blocking Time: 4.9 s

    4.9 s

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

  • Time to Interactive: 118.5 s

    118.5 s

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

  • Real-user LCP: 2.8 s

    2.8 s

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

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

  • Real-user TTFB: 1.6 s

    1.6 s

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

  • 35 images without width and height

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

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

    +13%

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

4 checks passed
  • 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.05

    0.05

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

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

    -48%

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

2 to fix60
  • Page weight: 21.2 MB in 276 requests

    21.2 MB

    Your homepage downloads 21.2 MB in 276 requests on a phone: scripts 13.2 MB (143), stylesheets 6.4 MB (8) and other files 856 KiB (68). Under 2 MB keeps phones on slow connections fast.

  • 1 image far larger than shown

    54 KiB

    1 image is downloaded at several times the size a phone draws it, for example CHEF_original.png at 2,197 px wide, shown at 156 px. Resized copies would save about 54 KiB.

  • 2 images below the first screen load straight away

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

  • About 6.0 g of CO₂ per visit

    6.02 g

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

5 to fixGoogle 8791
  • 29 text elements with low contrast

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

  • Hidden but focusable

    5 elements hidden from screen readers can still receive keyboard focus.

  • 2 tap targets too small

    2 tap targets are too small or too close together to hit reliably with a finger.

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

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

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

2 checks passed
  • Every image has alt text

    All 62 images in the HTML carry an alt attribute.

  • 39 automated accessibility rules passed

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

SEO

2 to fixGoogle 9294
  • Structured data has 1 problem

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

  • 1 link crawlers can't follow

    1 link has no real href, so search engines can't follow it.

  • 128 internal links, 3 external

    The homepage links to 128 pages on pimberly.com and 3 external pages.

7 checks passed
  • Meta description: 139 characters

    Your meta description is 139 characters: “Pimberly PIM - the leading enterprise Product Information Management platform. Drive amazing product experiences with q…”.

  • One H1 headline

    Your main headline reads: “Product Information Management (PIM)”.

  • Title: 44 characters

    Your title is a healthy 44 characters: “PIM Software for Digital Commerce | Pimberly”.

  • Canonical URL set

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

  • 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://pimberly.com/sitemap_index.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 contact details; sameAs (social profiles) and description would complete it.

  • Text is in the HTML

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

  • llms.txt published

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

Other pages

3 to fix86
  • 2 pages share a title

    https://pimberly.com/video and https://pimberly.com/product-tour all use the title “Pimberly PIM Platform Tour & Video Library | Pimberly”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 2 pages share a meta description

    https://pimberly.com/video and https://pimberly.com/product-tour use the same meta description. A description written for each page earns more clicks.

  • 1 link to non-canonical URLs

    Your homepage links to 1 page by a URL that isn't its canonical one, for example https://pimberly.com/product-tour, whose canonical is https://pimberly.com/video. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 15 internal pages checked

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

5 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • Every page has an H1

    Each page we checked has a main headline.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

4 to fixGoogle 5483
  • 5 third-party cookies

    5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

  • 2 small tap targets

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

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

  • 6 JavaScript errors while loading

    6 errors were logged to the browser console while the page loaded, for example “Uncaught TypeError: Cannot read properties of null (reading 'indexOf')”.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix70
  • 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 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 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.

  • About 2,013 words of copy

    The homepage carries about 2,013 words of visible text.

3 checks passed
  • 10 calls to action

    The homepage has 10 calls to action, for example “1 Minute Demo”, “3 Minute Demo” and “25 Minute Demo”.

  • Social proof on the page

    Social proof on the homepage: 61 testimonial or review blocks, 20 customer or partner logos, a star rating, 17 trust badges and “over 290 brands”.

  • Analytics in place

    Analytics detected: Google Tag Manager, Hotjar and Plausible.

Privacy and tracking

  • 5 trackers load before any consent

    5

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

  • 17 cookies set on arrival

    17

    Opening the homepage sets 17 cookies, 2 of them by other companies (measured from a US location before any click).

  • 51 other companies contacted

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

1 checks passed
  • Consent tool: OneTrust

    A consent management tool (OneTrust) 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 pimberly.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

CMS
WordPress
Framework
jQuery
Analytics
Google Tag Manager | Hotjar | Plausible

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 44 issues on pimberly.com, including 26 speed issues, 2 SEO issues and 2 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