Website review, no card needed

pepper-advantage.com logo

pepper-advantage.com website review

Visit site (opens in a new tab)Reviewed 4 November 202644 issues · 86 checks

This review found 44 issues worth fixing on pepper-advantage.com, 16 of them high impact, across 86 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
3.6 s2.5 sMay 16Oct 312.7 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20263.2 s
May 23, 20263.4 s
May 30, 20263.4 s
Jun 6, 20263.4 s
Jun 13, 20263.4 s
Jun 20, 20263.2 s
Jun 27, 20263.1 s
Jul 4, 20263.4 s
Jul 11, 20263.2 s
Jul 18, 20263.1 s
Jul 25, 20263.1 s
Aug 1, 20263.1 s
Aug 8, 20263.1 s
Aug 15, 20263.2 s
Aug 22, 20263.2 s
Aug 29, 20263.0 s
Sep 5, 20263.0 s
Sep 12, 20263.0 s
Sep 19, 20263.0 s
Sep 26, 20262.9 s
Oct 3, 20263.1 s
Oct 10, 20263.0 s
Oct 17, 20262.8 s
Oct 24, 20262.6 s
Oct 31, 20262.7 s
Real-visitor tap response (INP)75th percentile, phones
115 ms88 msMay 16Oct 3192 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026112 ms
May 23, 2026107 ms
May 30, 2026105 ms
Jun 6, 2026101 ms
Jun 13, 202697 ms
Jun 20, 202698 ms
Jun 27, 202695 ms
Jul 4, 202695 ms
Jul 11, 202694 ms
Jul 18, 202691 ms
Jul 25, 202699 ms
Aug 1, 2026101 ms
Aug 8, 2026104 ms
Aug 15, 2026108 ms
Aug 22, 2026102 ms
Aug 29, 202697 ms
Sep 5, 2026100 ms
Sep 12, 202698 ms
Sep 19, 202699 ms
Sep 26, 2026103 ms
Oct 3, 2026103 ms
Oct 10, 202698 ms
Oct 17, 2026100 ms
Oct 24, 202695 ms
Oct 31, 202692 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 pepper-advantage.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. pepper-advantage.com at 0.6 s0.6 s
  2. pepper-advantage.com at 1.2 s1.2 s
  3. pepper-advantage.com at 1.8 s1.8 s
  4. pepper-advantage.com at 2.3 s2.3 s
  5. pepper-advantage.com at 2.9 s2.9 s
  6. pepper-advantage.com at 3.5 s3.5 s
  7. pepper-advantage.com at 4.1 s4.1 s
  8. pepper-advantage.com at 4.7 s4.7 s

Speed

9 to fix54
  • Render-blocking requests

    2.5 s

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

  • Improve image delivery

    1.7 s · 420 KiB

    8 images could be 420 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.7 s faster on a phone.

  • 8,171 HTML elements

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

  • Main-thread work: 6.0 s

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

  • Mobile performance score: 54

    54/100

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

  • Use efficient cache lifetimes

    550 ms · 425 KiB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, weglot.com and Unpkg and others), adding 494 KiB and 814 ms of main-thread time.

  • Reduce unused JavaScript

    150 ms · 326 KiB

    About 326 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.

  • Google Tag Manager adds 313 ms

    313 ms

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

  • 15 long tasks on the main thread

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

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

    16 ms

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

Core Web Vitals

10 to fix50
  • 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 LCP: 4.0 s

    4.0 s

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

  • Real-user FCP: 3.7 s

    3.7 s

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

  • Largest Contentful Paint: 8.9 s

    8.9 s

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

  • Time to Interactive: 12.1 s

    12.1 s

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

  • Speed Index: 8.1 s

    8.1 s

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

  • First Contentful Paint: 3.2 s

    3.2 s

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

  • Real-user TTFB: 1.3 s

    1.3 s

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

  • Total Blocking Time: 348 ms

    348 ms

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

  • 17 images without width and height

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

4 checks passed
  • Real-user CLS: 0.03

    0.03

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

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

    -15%

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

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

    -20%

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

  • Cumulative Layout Shift: 0.012

    0.012

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

Images and page weight

3 to fix58
  • 12 images far larger than shown

    1.2 MB

    12 images are downloaded at several times the size a phone draws them, for example Website Homepage Banner (1)-1.png at 5,120 px wide, shown at 390 px. Resized copies would save about 1.2 MB.

  • Page weight: 3.1 MB in 105 requests

    3.1 MB

    Your homepage downloads 3.1 MB in 105 requests on a phone: images 2.2 MB (34), scripts 560 KiB (20) and fonts 204 KiB (7). Under 2 MB keeps phones on slow connections fast.

  • 6 images below the first screen load straight away

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

  • 1 image in older formats

    1 image (127 KiB) is JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

  • About 0.9 g of CO₂ per visit

    0.89 g

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

Accessibility

9 to fixGoogle 8589
  • Unlabelled dropdowns

    1 dropdown has no label.

  • 6 text elements with low contrast

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

  • Malformed lists

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

  • Interactive controls must not be nested (1 element)

    Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.

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

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

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

  • The skip-link target should exist and be focusable (1 element)

    The skip-link target should exist and be focusable: 1 element on the page fails this check, rated moderate by axe-core.

  • 2 links without text

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

  • 1 form field without a label

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

  • Headings skip levels

    Headings skip levels (h2 → h4 and h2 → h4), which makes the page harder to scan with a screen reader.

2 checks passed
  • Every image has alt text

    All 38 images in the HTML carry an alt attribute.

  • 50 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 59 WCAG 2.2 A/AA and best-practice rules on the phone render: 50 passed and 9 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 9279
  • Title is short (21 characters)

    Your title is only 21 characters: “Pepper Advantage Home”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • 6 H1 headlines

    There are 6 <h1> headlines (“LendInvest selects Pepper Advantage's PRISM”, “Pepper Advantage UK Leadership Update” and “Dilosk Agrees Sale to Pepper Advantage”). One clear main headline is easier for people and search engines.

  • Structured data has 2 problems

    Structured data found (Organization) but with 2 problems, for example “Organization: missing name”.

  • No social preview image

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

  • 8 links with vague text

    8 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • 80 internal links, 11 external

    The homepage links to 80 pages on pepper-advantage.com and 11 external pages.

4 checks passed
  • Meta description: 128 characters

    Your meta description is 128 characters: “Pepper Advantage is a global credit intelligence provider operating in six jurisdictions across the UK, Europe and Asia…”.

  • Canonical URL set

    The canonical URL is https://www.pepper-advantage.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://www.pepper-advantage.com/sitemap.xml.

AI search readiness

1 to fix88
  • Organization data is thin (2 of 6 facts)

    Your Organization JSON-LD is missing name, sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

  • No llms.txt

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

  • Text is in the HTML

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

Other pages

1 to fix95
  • 4 pages without an H1

    https://www.pepper-advantage.com/resources, https://www.pepper-advantage.com/resources/tag/company-news, https://www.pepper-advantage.com/resources/tag/case-study and https://www.pepper-advantage.com/resources/tag/insight have 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 37 found) and read each the way a search engine does.

6 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

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

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • 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 15 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9687
  • 59 small tap targets

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

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

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

  • No phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

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

    The homepage carries about 1,264 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: “Talk to our experts”.

  • 8 calls to action

    The homepage has 8 calls to action, for example “Contact us”, “Talk to our experts” and “Learn more”.

  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 15 customer or partner logos and “over 90 clients”.

  • Analytics in place

    Analytics detected: Google Analytics.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

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

  • 2 cookies set on arrival

    2

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

  • 22 other companies contacted

    Loading the homepage contacts 22 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 pepper-advantage.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
HubSpot CMS
Analytics
Google Analytics
Hosting
Cloudflare

Hiring

Hiring
1 open role
Job board
careers page

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 pepper-advantage.com, including 19 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